Moving 3.0 to 4.0 projects, all going OK?

decrink wrote on 3/8/2003, 11:04 AM

I worked with the beta version of 4.0 and loved many of its new features for audio. I'm an academic and ordered that version which will be here shortly. As I'm in the middle of tracking a major project in 3.0, I will be at mixing stage when 4.0 arrives. For those of you that have been using it for awhile, has it been pretty clean transferring projects to the update? Stability? CPU usage? Plugins? I'd like to use automation and buss tracks when I do the mix but not at the expense of lots of additional time trying to work out anomalies from the changeover.

How's it gone for you early adopters?

Comments

PipelineAudio wrote on 3/8/2003, 12:44 PM

make sure you make a copy of your 3.0 mixes, and save new ones for 4 so that you can go back no matter what

decrink wrote on 3/8/2003, 8:46 PM

Of course I'll do that. There is a point at which old mixes that have been moved over become pretty obsolete so I'm just wondering how the audio end is holding up for people in 4.0 now.

Geoff_Wood wrote on 3/8/2003, 11:55 PM

.... and be careful openning VV3 project in V4 with 'autosave ' on !

geoff

imac wrote on 3/9/2003, 5:26 PM

Does the official release allow a v2 veg to open in v4?

The beta did not.

jdmh wrote on 3/9/2003, 5:59 PM

Uh, no - not okay :-(. 4.0 introduced apparently random audio glitches when rendering my projects. For others who seem to be having similar problems see: "Rendering and mixing to new file unusable" - pvnuk - 3/7/2003.

I've had a support query in for a week and a half and am still waiting for an acknowledgement of the problem and date for a fix or workaround. Hopefully this will be forthcoming soon :-/.

David