Blank spots in recorded soundbites...

[dmshep]

I first had this happen on Sunday. I recorded the band's take (18 tracks) and we were listening back, and we found a spot, a second or two long, on all of the tracks but two where the audio just suddenly disappeared. I couldn't figure out what was going on as I could see the waveform, but when I selected it to audition, there was nothing played back. When I zoomed in past a certain point, the waveform suddenly dissappeared and showed silence.

This happened to me again today when I was recording a triggered kick track. The track I recorded kept getting 2-3 second sections where there would be a waveform shown, but no sound, and the waveform disappears when you zoom in on it.

I'm running DP 4.52 on a dual 1GHz G4, OSX 10.3.8. Both DP and the OS are newly installed as of a few days ago.

[dmshep]

Has anyone else run into this? I'm in the middle of a session and it's got me somewhat freaked.

[JuicyPeachMastering]

I had that issue once when I was running DP 4.12 At the time I had stock RAM and was spiking the performance meters. My solution was to increase RAM to 2.5gigs and fiddle with the buffers (depending on the track count). i havent had the issue since. Your recording 18 channels ? Hows the performance meters looking ? Any spikes ?

[dmshep]

Originally posted by Juicy Peach:
I had that issue once when I was running DP 4.12 At the time I had stock RAM and was spiking the performance meters. My solution was to increase RAM to 2.5gigs and fiddle with the buffers (depending on the track count). i havent had the issue since. Your recording 18 channels ? Hows the performance meters looking ? Any spikes ?

I'll keep an eye out to see today. As I mentioned, it also did it while recording a single track, though it was triggering a kick sample out of Reason, which may have been a strain on the resources, but we've got 1GB of RAM and dual 1 GHz processors, so I don't see why that should be...

What adjustments did you make to the buffers? Increasing the size?

[JuicyPeachMastering]

Yes. I increased the buffer size upwards to 1024 and kept the tracking plugins to a minimum. Of course this adds latency for the band. Not only disabling the plugs but removing them during tracking. Ive noticed the problem only in 96k... what are you recording in ? 44.1 ? 96k ?

[DCD]

Had a similar problem in the past. Once opened a project and the last minute of five of my track were blank. Could never really find a answer to the problem. Good luck to you.
You are not alone!

D

[dmshep]

Originally posted by Juicy Peach:
Yes. I increased the buffer size upwards to 1024 and kept the tracking plugins to a minimum. Of course this adds latency for the band. Not only disabling the plugs but removing them during tracking. Ive noticed the problem only in 96k... what are you recording in ? 44.1 ? 96k ?

44.1. It's behaving itself today. I'm running 14 tracks instead of 18, so that might be a factor. I have just some minimal EQ on a couple of the tracks, so I don't think it's effects.

I've been noticing that 4.5 acts at times like 3.1 did in OS9, occassionally freezing, and once or twice actually taking down the whole system and forcing me to reboot. I never had that happen with 4.1

[pencilina]

This happens to me all the time. Since v3. Now I'm on 4.52 with a kickin dual g5 and STILL this stupid bullsh•• happens!! _Usually_ it happens the first time I record many tracks after starting the system. After that first glitch things are usually ok. My voodoo cure is to let things roll in record a minute or two and then undo it. This actually works. BTW, I use 2 adats and a 2408 for multitracking (no adat comments please- anybody who would like to send me a 1296 is welcome to). Good luck.

<small>[ April 06, 2005, 02:59 PM: Message edited by: pencilina ]</small>