Project File Compatability 1.0 vs 2.0

Harold wrote on 5/7/2000, 1:03 AM
This question may have already been asked but, as a working
engineer that has been using Vegas for the last nine months
I have an archive of projects on 5 x 28Gig removable drives
that I still need to access. The 2.0 readme file clearly
states that the project format is not the same. Does this
apply to Vegas Audio 2.0 and if it does what the hell are
you guys thinking ! I simply do not have the time to go back
and resave every piece of work I have done during this time,
nor 5 extra drives sitting around. It would show an extreme
lack of foresight on your part to force audio users to
change formats especially when the "Video" version is a
separate product, so much so that the term amateurs comes to
mind. I have no problem paying for upgrades which
incorporate improved features (ie midi controllers, real
SMPTE, etc) but I have a real problem with a "professional"
product changing formats at random.
If I am forced to resave all my projects, please indicate
which member of your accounting dept I am to send my invoice
to. You may also note that my current rate is $75.00/hr.

Comments

Walterius wrote on 5/7/2000, 1:38 PM
HI!
I have the similar problem, but in the VegVideobeta i could load every
project from 1.0a and 1.0b without any trouble.
I hope that will stay so.
walter

Harold wrote:
>>This question may have already been asked but, as a working
>>engineer that has been using Vegas for the last nine months
>>I have an archive of projects on 5 x 28Gig removable drives
>>that I still need to access. The 2.0 readme file clearly
>>states that the project format is not the same. Does this
>>apply to Vegas Audio 2.0 and if it does what the hell are
>>you guys thinking ! I simply do not have the time to go back
>>and resave every piece of work I have done during this time,
>>nor 5 extra drives sitting around. It would show an extreme
>>lack of foresight on your part to force audio users to
>>change formats especially when the "Video" version is a
>>separate product, so much so that the term amateurs comes to
>>mind. I have no problem paying for upgrades which
>>incorporate improved features (ie midi controllers, real
>>SMPTE, etc) but I have a real problem with a "professional"
>>product changing formats at random.
>>If I am forced to resave all my projects, please indicate
>>which member of your accounting dept I am to send my invoice
>>to. You may also note that my current rate is $75.00/hr.
SonicCaleb wrote on 5/9/2000, 10:43 AM
Hi Harold,

I'm sorry for the confusion, hopefully i can clear this up for you.
All Vegas Pro 1.0 projects will be compatible with both Vegas Video
2.0 and Vegas Audio 2.0. You won't have to recreate anything.

However, you won't be able to go backwards - i.e. a 2.0 project is
not compatible with Vegas Pro 1.0.

Thanks,
Caleb


Harold wrote:
>>This question may have already been asked but, as a working
>>engineer that has been using Vegas for the last nine months
>>I have an archive of projects on 5 x 28Gig removable drives
>>that I still need to access. The 2.0 readme file clearly
>>states that the project format is not the same. Does this
>>apply to Vegas Audio 2.0 and if it does what the hell are
>>you guys thinking ! I simply do not have the time to go back
>>and resave every piece of work I have done during this time,
>>nor 5 extra drives sitting around. It would show an extreme
>>lack of foresight on your part to force audio users to
>>change formats especially when the "Video" version is a
>>separate product, so much so that the term amateurs comes to
>>mind. I have no problem paying for upgrades which
>>incorporate improved features (ie midi controllers, real
>>SMPTE, etc) but I have a real problem with a "professional"
>>product changing formats at random.
>>If I am forced to resave all my projects, please indicate
>>which member of your accounting dept I am to send my invoice
>>to. You may also note that my current rate is $75.00/hr.