MOTUnation.com

Listening back to my sequence, keep getting these crazy bursts of white noise. I have played this sequence many times before, no problem, not pushing the performance meter. Checked clocking as well. Had to restart the mac to clear it, then the sequence played OK for a while till it happened again..5 times while a client was here .

Here is a small movie of the event, had to record through isight so sound quality is bad but the noises you hear are loud bursts of white noise.

https://files.me.com/brett.r/84yey4.mov" onclick="window.open(this.href);return false;

Anyone have any ideas? Thanks.

That, my friend, is "*%$#!!". You nailed it.

Until I heard this--- and THANKS for uploading it-- I thought I'd burned out my SPL monitor control center. I've been working through Built-In Audio for the past 10 weeks because of it.

I know that doesn't help you--- but YOU have been enlightening. Now we're both on a path to find a solution.

Someone once said-- "A shared problem is half a problem."

I'm down with that.

The quest is on.

Those are nasty bursts.
What VI's and plugs are you running?
Have you isolated the source of the bursts?
What channels?
Check the meters....

Try it without PLAY or Kontakt....

Dupe the project (so you can leave the original audio) and try merging audio tracks one at a time. See if writing a new audio track with a discrete name makes a difference.

Do you try with Kontakt KMS server disable ?

We had those burst on occasion with older versions of PLAY.

Thanks for all the responses. I do believe it is PLAY related as it shows up in some, but not all, crash logs. I am up to date with it. I will try all the different ideas and see what works.

Will report my results later.

I've had it happen without PLAY involved, fwiw.

Delete Dp preferences and then create a new project.
then try to LOAD your project into the newly created.

see if it helps

Thanks Yiannis, I had already done that and it still happened.

Anyhow, I reassigned all my PLAY instruments to Kontakt instruments, and so far haven't had a repeat. Which doesn't help you at all Frodo . When it happens, can you tell which VI the sound is coming from?

I'm wondering if it's related to the subject mentioned on other threads here, that is that once Kontakt loads it's memory server basically 'takes over' all memory outside of DP. Even though I moved PLAY up in the 'loading order' so it loaded before Kontakt.

I do have a crash log that mentions PLAY so I'm going to send it to East West.

bdr wrote:....

Anyhow, I reassigned all my PLAY instruments to Kontakt instruments, and so far haven't had a repeat. Which doesn't help you at all Frodo . When it happens, can you tell which VI the sound is coming from?

Alas, I confess that I cannot tell with 100% certainty. The last time it happened, all I had running was IK's Miroslav Philharmonik. There were other times when I had a variety of VIs up and running... with and without Miro, with and without PLAY.

Puzzling, no?

But I must assert that it's not chronic or frequent on this end. When it happens it is definitely distracting, to say the least.

I just got the noise blast for the first time ever, yay! I had a couple of Kontakt 4 loops going, but most of the tracks were Play.

thats happened to me .... once in 2004 where it happened BADLY!!!! at least 20 times per track per take.

A few times recently.

I tracked down the problem to a CPU thing. When the PLAYBACK METER spikes, it writes those errors to the hard drive.

Funny thing is, when it started happening (back on DP 4, i think), you couldnt SEE those spikes on the waveform UNLESS you zoomed VERY far in, then they'd just POP up. When you started to zoom out, they'd disappear as if not even there. But when you played back the track, they'd blow your ears out. I almost went crazy with this problem.

It's happened a few times recently and i think its a drive error when DP spikes the PLAYBACK METER.

This is a drive error/playback meter spiking issue.

Had the same thing. Started on my G4 in 03-04 or so and a few times recently.

Attributed it to a playback bottleneck and when that begins to spike, it writes error to the recorded/recording track.