I usually record the engine, motor sound of the train as a hobby.
Recently, I bought a new ZOOM F3 recorder and Clippy EM272Z1 microphone and recorded it, but sometimes in the underground section, the input level is lowered (to the point of being close to silence) and then comes back to normal. (To be honest, it happens quite often, once every minute or two.)
I don't know if it's due to RF interference or if the limiter is operating in F3, but it happens under certain conditions or randomly depending on the type of train.
I would appreciate it if you could let me know if you have any stories to help me solve this problem.
Could changing the microphone be the solution?
The budget is about 250 dollars. and I'd like to do a stereo recording.
- Behringer C-2
- ZOOM ZPC-1 I'm thinking between the two above, which one would be good? You can also recommend other microphones.
*I used a translator. Please understand my poor English skills.
Add details below.
miking method: ORTF Channel: Stereo Used Material: Clippy EM272Z1 + ZOOM F3 Recording format: 48k 32-bit float
- Major Problem Situation When recording a drive in a tunnel, the input level is randomly lowered and then returned. (It occurs in the underground section of all routes regardless of the route)
- a condition that usually occurs (IGBT Vehicle) Opening/Closing the Door (PMSM vehicles) At acceleration and deceleration
- Why RF interference is suspected
- As the problem develops, occasional RF noise comes in.
- It does not occur in the ground section, but only in the tunnel section.
- Other than that
- It is too early to dismiss it as a matter of RF interference, given that it only occurs when the door is opened and closed, as in the case of an IGBT vehicle.
- However, in the case of PMSM vehicles, noise is often mixed at the same time as the phenomenon occurs, so it is difficult to rule out the influence of RF interference.
- Judging from the cases of 1 and 2, it may be a phenomenon caused by a combination of effects.
*I have uploaded the recording file and time table that caused the problem to Google Drive.