Posted: Tue Mar 23, 2004 7:26 pm
still happening Live 3.0.2 and Waves 4.5---ABleton, any word on this yet??
new waves issue from another thread, help needed:
hey muzza, funny thing just happened--I had the behaviour you described while rendering a big project with lots of Waves plugs 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