DP + Waves; MAS vs AU

[Archer]

Did you start with 128 or previously switchted from a different setting?
Unless you're tracking and working ITB, or using VI's, I see no point in keeping the buffers at 128. When mixing, you'll want increase the buffer setting to either 512 or 1024, I choose 1024.
I use VI's, but the lowest setting needed is 256.

[jr213]

It doesn't matter... starting at 128 or switching.... this was confirmed by Waves - that they have issues with a buffer less than 512 in DP. I like to use a buffer of 128 for tracking so I can use effects. Anything more is pointless. I agree that 256 is okay for VIs.

[jr213]

I feel obligated to reiterate that as much as I hate Waves for how they have handled this situation, the reason I still bother is because Renaissance Comp sounds so good.

[Archer]

The lowest setting I used is 256 and the quick fix mentioned previously solved the issues concerning parameter settings, which is something that happens when switching buffers. It may be that what you experience happens with 128.
As I supposed, you're tracking. If 256 gives you latency, I think you might be recording @ 44.1 kHz. Raising the sample rate to 96 kHz lowers the system's latency. I tracked drummers @ 24/96, buffers @ 256 and had no issues.
If you plan to record with effects, I'd see you using eq's and comp's. Depending on the plug-ins, there might be some inherent delay you'd have to take into account. Since you're tracking, the recording track is prone to be delayed. As the track is being written to disk, ADC is of no use in this particular case. This delay might cause "latency-like" feelings. Lowering the buffer setting "helps", but is not the cure. Manual time alignement is. Notice it depends on whether the plug-in induces processing delay or not. Some do, some don't.

This should help you.
I agree on the fact that this should be addressed.

<small>[ August 22, 2005, 12:16 AM: Message edited by: Archer ]</small>

[PJ]

Originally posted by jr213:
if my buffer is at 128, play or stop as much/little as i want, every time i open the plugin to edit settings, they are all at zero. only way for them to stay is to leave all active Waves plugins open. Not to mention, when i enter a numeric value and hit enter, i have to click on the slider to make it actually go where i told it to go. Oh yeah, that's what fixes it for me (not start/stop) - to click on a parameter, then all settings for that instance go back to where I set them..

Obviously Waves plugins doesn't work similarly in different systems. For me start/stop (after project open) has always worked, even with buffer 64. And we are talking about Waves version 5, right?

This is quite odd bug, because DP (MAS) is the only software which is having this buffer problem with Waves.

[Splinter]

jr213:

Yeah, this is ridiculous and Waves just thumbed their nose at me too. I use Waves plugs ad nauseum with the Gold + RenMaxx bundle and I love their sound, but I paid a fortune for them and these bugs ought to be fixed. I don't usually have problems because I primarily use them in a mix situation, but for as many hours as I've lost from losing settings with this bug, Waves should be paying me to own them.

I don't understand the whole MAS/AU issue, but Waves acts like it's MOTUs fault, even though they've chosen to support MOTUs format! Go find the logic in that! (no pun intended) I don't know why the AU version wouldn't work. What happens if you remove the Waveshell MAS from the MAS folder and place the Waveshell AU in the Components folder? Does the AU inspection just skip it?

This is obviously an issue with the Waveshell, but Waves blames MOTUs AU implementation. My understanding is the Waves plugs are all the same it's just the shell that accesses them. So, the Waveshell is the component that needs tweaked to fix the spec, not the other way around!

Now MOTU does not "natively" support AU, which is silly at this point, but whatever implementation they are using works with ALL my other plugs, so what's Waves hang up? I have a feeling Waves and MOTU came to an empasse and we the users are the losers.

[Archer]

I checked on my system, the fix works @ both 128 and 64.