I'm hoping someone might have a workaround for this.
One of my contractors started with Vegas 3, and moved to Vegas 4 while we were working on an [audio-only] project in 5.1 surround. There were no issues moving from v3 to v4.
The time has come to do some minor revisions for a "definitive" version of that project [now 2+ year old], and they have moved on to Vegas 5. Opening the projects in v5 results in completely invalid surround pan automation tracks that can only be corrected by completely erasing the automation for each audio track and starting over from scratch. Needless to say, I don't want to spend the required several weeks remixing the whole thing from scratch.
We also tried taking the project to another shop running Vegas 6, and it has the same issue. Surround projects from v4 open with garbage pan automation in v6. [v6 on a single CPU also seems to run about 1/4 as fast as v5, oddly - I'm glad my contractor hasn't upgraded again.]
If anyone has a solution or workaround for this, any info would be greatly appreciated.
At the least - if anyone else could confirm this is happening or not for them..
Thanks,
dex.
One of my contractors started with Vegas 3, and moved to Vegas 4 while we were working on an [audio-only] project in 5.1 surround. There were no issues moving from v3 to v4.
The time has come to do some minor revisions for a "definitive" version of that project [now 2+ year old], and they have moved on to Vegas 5. Opening the projects in v5 results in completely invalid surround pan automation tracks that can only be corrected by completely erasing the automation for each audio track and starting over from scratch. Needless to say, I don't want to spend the required several weeks remixing the whole thing from scratch.
We also tried taking the project to another shop running Vegas 6, and it has the same issue. Surround projects from v4 open with garbage pan automation in v6. [v6 on a single CPU also seems to run about 1/4 as fast as v5, oddly - I'm glad my contractor hasn't upgraded again.]
If anyone has a solution or workaround for this, any info would be greatly appreciated.
At the least - if anyone else could confirm this is happening or not for them..
Thanks,
dex.