Comments

bgc wrote on 12/16/2002, 3:22 PM
Nope.
Chienworks wrote on 12/16/2002, 4:50 PM
You can of course render your ACID project to a .wav file and open that in Vegas. If you want to maintain individual access to the tracks, you can render each ACID track to a separate .wav file and import all of them into Vegas as separate tracks.
Weevil wrote on 12/16/2002, 6:14 PM
Not at the moment you can’t. It would be very nice if you could select a ‘save as Vegas project’ option.

All the time stretched loops and other non Vegas elements could be rendered down but all the compatible elements (envelopes, track, buss and plug-in assignments, etc) could remain intact.

...Don’t know how technically difficult it would be to implement, but from a users point of view the ability to seamlessly swap projects back and forth between the two applications would be brill.
JoeD wrote on 12/17/2002, 12:24 AM
it's still absolutely abbhorrent to make ACID/Vegas one?

Hell, I'll go one further...who here wouldn't buy the SF app that is essentially:

SF6/CDA5/V3/Acid 4 all in one LOGICAL application?

and in turn...what media authors WOULDN'T consider this app now?

SF? Do you think I ask this because you DON'T make the better UI and obtain great stability?

JoeD
Erik_Shock wrote on 12/17/2002, 8:48 PM
Thanks for the input.

Update: I simply saved the Acid project with external audio, then moved the wavs to Vegas. Not withstanding the hell of reassembling the project, it was fairly easy to move them, though mind racking.

"SF6/CDA5/V3/Acid 4 all in one LOGICAL application?

and in turn...what media authors WOULDN'T consider this app now?"

Excellent thought. This would make life easier. But, if SF did do this, SF would probably drop support for CDA again...hehe.

Thanks again! Erik