Ableton Forum

I downloaded a 14-day demo of the Waves Diamond Bundle and while they appear to be functionning in all my programs, when used in Live, they don't keep their settings when I re-open a project. For example, everyday when I go back to my currect project in Live, I have to re-adjust all my Reneq and Rencompressor settings on all the tracks using Waves (the threshold, ratio, makeup gain are completely out of whack upon rebooting, output on eq is all the way down, etc.).

Is there a fix to this? Thanks

known problem. Suck ass. hard. especially when Q10 eqs load at +12.0 dB!!! I've bitched and moaned about it here a lot, but please join my cause. There's another recent thread you might search for, it basically had a reply that Waves is working on it, to officially support aBleton.

ryan

Like I already wrote in a previous thread, this is also the case in digital performer. So we've gotta wait for for waves to adress it I guess.

Yep I've spoken to waves tech support a few times (they are the best I've come accross for customer service and tech support BTW) and the first time they were a little cagey as they didn't support live, but more recently they've said their developers are currently in the process of testing it to support it officially, so they are on to it,

but I think that particular problem is actually more to do with the way live handles the plug ins/automation, but I've also had a reply from Alex at ableton before saying they're working on it but 'we need to be patient'

but in the mean time you can just record enable live, tweek your settings using the live plug-in GUI (press triangle) to get the settings where you want them and press play for a split second and it records it as automation - bit of a faff but you only have to do it once for each live set.

Cant wait till they solve this as I think using waves in live can make the difference between using another sequencer or not - the quality is professional, high-end studio quality and using them in Live I hardly use anything else.

this is from another thread, but relative, any help would be greatly appreciated:

hey muzza, funny thing just happened--I had the behaviour you described while rendering big projects with Waves plug-ins for the first time ever. Here's the only two things that are different from hundreds of problem-free renders:

1) I had a bit of automation on one Waves C1 effect on one track
2) I had soloed that track (I almost always am rendering the whole mix) and was just trying to render it.

Surprisingly, I had previously rendered the whole mix without a glitch, and just for a test, I tried rendering the track with the automated C1 soloed a few times to see if it was consistent. Seemed like every other render or so caused the freeze-up. this blows. The waves are so damn expensive, and they forget their settings in Live when you re-open a project. My previous work-around was to always save presets for the waves effects so I can re-load the preset when I re-open a set. Another new workaround I was trying was automating the effect parameters in order to avoid having to re-load all my presets each time I open a song--now it seems this may cause rendering issues. Were your Waves automated at all in your problem sets? Other Waves users out there, whats up with your rendering (we're both on pc)?

Ryan

off hand I can't think if I've rendered directly from Live with the plugs in or whether I've done it through Tracktion...

I'm working on mac at the moment but I use an ilok and swap between them, but one thing I can say is that the problem of not remembering settings and resetting them to minimum (on the L1 at least, but generally erratic on the others) on mac OSX, but not in other apps, so i definitely think it's a problem with Live.

Alex - if you're out there any ideas if this is going to be looked at soon??

cheers