Audio Unit playback glitch at soundbite start DP 5.01

dcate1971 · Post by **dcate1971** » Wed Nov 14, 2007 7:05 am

Hi folks,

Has anyone run into this and found a solution? I've got DP 5.01 running on 10.3.9. I don't know if this has always happened or if I just started noticing it with any AU FX plugs:

On a track with an AU fx inserted, when the play cursor reaches the soundbite (this works better when there's a short bit of quiet at the top of the soundbite) I'll get an audio glitch. Like a little playback buffer dump before the soundbites waveform kicks in.

Example: If the AU is a compressor it'll just pop at soundbite start. If it's a reverb or delay unit, it's like the last few audio buffers play back as soon as the play cursor hits the soundbite edge, so I'll hear a little delay of whatever was playing when I last stopped the transport.

Has anyone else run into this on this version? If so is it fixed with an update or is there a solution?

I've trashed preferences and monkeyed with buffer and configure studio settings with no success.

This is on a G5 2.0 PPC running 10.3.9 and 4 gigs of RAM. I'm using an 828 MKII and MTP-AV USB. The plug ins I"ve noticed this on are Nomad Factory and Apple AU plugins.

Thanks for your help.

Mr_Clifford · Post by **Mr_Clifford** » Wed Nov 14, 2007 4:30 pm

DP 5.01 was a particularly buggy version of DP5. If it's possible I'd recommend updating to Tiger (or even bypass it straight to Leopard) and use DP 5.11 (free update if you own DP5). Avoid DP 5.12 though.

Frodo · Post by **Frodo** » Wed Nov 14, 2007 6:21 pm

Agreed!

dcate1971 · Post by **dcate1971** » Thu Nov 15, 2007 6:38 am

I'm heading down that update road, i've got 10.4 ready to install. I've been in the middle of some projects and didn't want to do the update until they're complete. Plus, I did an earlier update from 10.3 to 10.4 and took quite a performance hit. I'm going to try a fresh install of 10.4 to see if that's better.

At least no one's experiencing this in 5.11 or higher as far as I can tell (no responses anyway). So this will just force me to quit stalling and do the updates. Procrastinators, the leaders of tomorrow...

Thanks for your help!

daniel

wurliuchi · Post by **wurliuchi** » Thu Nov 15, 2007 9:33 am

I've noticed it in 5.11. It's driving me nuts. The only solution I've found so far is to play silent portions of soundbites before bouncing (or real-time mixing) or before any critical listening at the beginning of tracks. See this thread:

http://www.unicornation.com/phpBB2/view ... hp?t=24521

dcate1971 · Post by **dcate1971** » Thu Nov 15, 2007 10:31 am

Hmm. That's discouraging. I've noticed it only recently and I would think a lot of users are running into this, but apparently not, so I wonder if it's a setting or if it only occurs with certain AUs.

Turning on/off pre-rendering does not seem available to the AU plug-ins I'm using (Nomad Factor, the option is grayed out in mini menu).

msmith92 · Post by **msmith92** » Thu Nov 15, 2007 11:34 am

i've had it happening in 5.12 and 10.4 when i have automation bypass/unbypass a plugin. sooo, it's a problem i'd say. it creates a popping sound.

wurliuchi · Post by **wurliuchi** » Thu Nov 15, 2007 1:06 pm

dcate1971 wrote:Hmm. That's discouraging. I've noticed it only recently and I would think a lot of users are running into this, but apparently not, so I wonder if it's a setting or if it only occurs with certain AUs.

Turning on/off pre-rendering does not seem available to the AU plug-ins I'm using (Nomad Factor, the option is grayed out in mini menu).

I think I've only noticed it on Reverb AUs--Blueverb, CSR and Breverb. I'm not at the studio right now, but I believe Pre Rendering or Run In Real Time is available on each of them. But it didn't make any differernce whichever I chose.

msmith92 · Post by **msmith92** » Thu Nov 15, 2007 1:15 pm

i just updated to 10.4.11 and the problem left (for that song). who knows?

wurliuchi · Post by **wurliuchi** » Thu Nov 15, 2007 1:24 pm

msmith92 wrote:i just updated to 10.4.11 and the problem left (for that song). who knows?

That's good to know. I'm happy for you. Though I'm tempted, I just can't upgrade from 10.4.10 to 10.4.11 right now. I'm too chicken, and this project is two weeks out from being complete.

Shooshie · Post by **Shooshie** » Thu Nov 15, 2007 4:15 pm

I get this all the time. I got it in 5.11, and I get it in 5.12. I get it in Mach Five2 even worse than anywhere else. It happens at the beginning of every note in MachFive2.

In DP, all kinds of things happen. Muted tracks kick in, and even phantom sounds will play, which I suspect are coming from other chunks in the same file. They're quick, and over with in an instant. But it's too much to overlook. Further, MOTU has known about this for years, and they haven't done anything about it yet. That's got me worried.

In MachFive2 and other VI's I add a tiny delay to the notes. About 10 to 15 milliseconds. That seems to kill most of it. But when it happens in DP, it's different. It's like a track-related thing, and there is no stopping it.

Shooshie

msmith92 · Post by **msmith92** » Thu Nov 15, 2007 4:32 pm

well, i had it happen constantly for the past 3 days on one track. if i used the automation to turn on a bypass for a waves flanger it would create a click at the bypass point of automation.

just today i updated to 10.4.11 and now it is gone??? what does that mean? maybe it was just my computer get bogged down and the new update "FRESHENED" something up?

point being. it's gone. so..it's just trial and error.

Shooshie · Post by **Shooshie** » Thu Nov 15, 2007 5:06 pm

Well, I'm about to install 10.4.11, and I'm going to cross my fingers and hope for the best. I know it won't help the VI thing. Those pops at the beginning of samples are just poorly programmed sampler/player algorithms. But the other things... one can hope.

Shooshie

dcate1971 · Post by **dcate1971** » Fri Nov 16, 2007 7:36 am

Thanks everyone for your replies, I'm going to try 10.4.11 this weekend and report back.

thanks
d

dcate1971 · Post by **dcate1971** » Sun Nov 18, 2007 4:33 pm

Well, I updated to 5.12 and 10.4.11 and I still get the same behavior. It seems like a bug to me.