Tascam DP-24 Spikes

[Moose52]

I am getting loud snaps or spikes sometimes when recording, sometimes when mixing. Recording: when I stop the machine and use the jog wheel to go back and I hit play again, there is a loud spike that occurs right after play starts. It doesn't occur again; it's only after I jog back and hit play. Mixing: right after I hit record and start to mix, I get a spike. Doesn't happen during the song, just in the beginning. Any thoughts? Thanks.

 

[Mickster]

I think we could use a bit more info but my first thoughts are..........Do you hear the noise through both headphones and monitors? Have you made any "preference" changes or other changes lately? Are you using a new SD card? Does the spike show on the levels of all any or certain track(s)? I assume the noise appears on the recorded material? How long have you had your DP-24? Is this your first recording? Maybe you can post a sample. Don't be offended by my questions........the more you can tell us the more chance we can help you.

 

[Moose52]

Thanks for ur reply. The unit is a little older than a year. The card is a SanDisk Ultra, 16GB, class 10. Not my first recording; started happening about 4 months ago. It's not on a particular track. It happens on the track I'm recording on if I punch in. I record at 24bit, 44.1. It remains on the track during playback. I hear it on monitors and on phones. Also, I recently completed a song and did not hear it. I had just updated the firmware, so I thought it was fixed. But when I began to record my mix, there it was. It also doesn't matter which input I use; it still appears. The only preference change I made was to configure my footswitch to punch in/out, cue locate, and play/stop. I thought I might have been recording too hot, so I set my levels about -6. Still have problem.
Thanks for your help.

 

[Moose52]

Thanks for the suggestion.

I'll try that. I will also try grounding the machine.


M

Taking a guess.....

Can you or have you tried reformatting the memory card (save all data on it first)? Possibly the data on the card has become fragmented/corrupted over time and when the machine attempts to locate the data it is causing the spike.