The funny thing / problem is, that I never used any ASIO drivers, nor have any special hardware (just a Sound Blaster Audigy).

I tried saving a new version of the Vegas 2.0 project where the master effect and the assignable effect was removed, but I still got the same error message. The project isn't even particularly complicated. Just a Timeworks 4080L reverb as an assignable FX, and a Waves L1 Ultramaximizer+ as the master effect. A bunch of tracks with some envelopes and crossfades. Nothing fancy. I can't honestly see anything that would cause compatibility problems.

Frankly, whatever the reason is, this is completely unacceptable. Software should always be downwards compatible. If this problem isn't soon fixed, we'll have to return and refund the software.

*fellow VGM'er says hi =)*

Hm, I never got that problem with my v2 projects. A totally wild guess could be that the plugin enumeration system has changed from v2 to v4 for some reason. Have you tried opening a v2 project with just a few native SoFo plugins on the master output?

I totally agree about getting it fixed, of course, but it might be nice to know what's causing it.

Heya Johan. :)

"Have you tried opening a v2 project with just a few native SoFo plugins on the master output?"

I haven't, but as I mentioned, I tried removing the master FX and the assignable FX from the V2 project prior to opening it with V4 - and still got the same error message. However, many of the tracks contained a non-SoFo native plugin: the Waves DeEsser (but not in the master output). All these plugins work without problems - I can even build the very same plugin chain within Vegas 4 - I just cannot import such a chain from Vegas 2. Which seems rather silly.

I'll have to experiment with this more when I'm less busy with work (a tight internal deadline approaching).

You're not alone, I'm having the same problem. I agree with Skaven, this is completely unacceptable.

And to clarify, I'm not doing anything that's rocket science either...just using SoFo plugins. I have projects with 50+ audio tracks, a dozen busses, using multiple FX on each, etc. Come on Sonic Foundry, do you really expect us to recreate all of this stuff!?!?!?! Is this a bug or a "feature"? I could hardly wait for the package to arrive with my copy of Vegas4+DVD, now I can hardly look at it without getting disgusted. If this problem isn't fixed and fixed soon, you guys just lost a customer...permanently!

Any official response from Sonic Foundry on this?

Alan

A little followup... after some playing around I'm able to get more of a Vegas 2.0h file to open.

At first, without modifying the default audio properties for a project (0 busses, 16 bit depth, etc.), I could open the files, but no busses would appear, and only tracks that were on the Master Bus would play (as if the other tracks knew they were on different busses, but couldn't play because the busses didn't exist). So, I tried adding a bus manually. Sure enough, all the bus indicators on each track showed up and they were on the correct busses. A, B, C, etc. Even though I only added one bus, A. Then only the tracks that used the master and A bus would play. Adding a B bus would then allow the tracks that used the B bus to play, etc...

Next I changed the default number of busses to 16 (just a big number that I would more than accomodate this project), checked the "start all new projects with these settings" checkbox, and applied the changes. When I re-opened the same Vegas 2.0h project, it loaded all the tracks, 16 busses were there, the tracks were assigned to their respective busses, but the busses had no effects associated with them. This is a little closer, but still not much better. And I still receive the error message

"Vegas 4 is unable to recover all of the audio routing settings from Vegas 2 projects."

I can repeat this by changing the default project audio settings from 0 busses to multiple busses. And there is still the issue of nothing being attached to the busses...

It appears as though when opening a project in Vegas 4, it somewhat relies on what the default settings are for a project, and not how the project was actually setup. I would call this a bug. Why should you be required to have set your default busses to a high number just so you can be sure every project can load, when maybe your average project only uses 4 busses? And does this mean that if your default bit depth is 16 bits, then you'll have problems with 24 bit files? When loading a project, you should ALWAYS load the settings of that project, not the defaults! Wouldn't everyone agree?

Can someone else confirm this?


Alan

Quote: "We just upgraded to Vegas 4.0 from 2.0f, since we concluded it would make my work easier. How wrong I was."

Just curious, did you download the V4 demo and try to open V2 projects before you concluded to buy V4?

Lars

The only workaround I have found is to open the V2 project in it V3, save it in V3 format and then load that file into V4. It works perfectly and is so straightforward and simple [rolls eyes].

I will reinstall v2.0 and try and repro this for you. I did beta test v3.0 projects opening them in v4.0 and a little over a year ago I beta tested opening v2.0 projects in v3.0 beta. In both instances before release I found problems with routings and busses. I never did try opening v2.0 projects in v4.0 though, but the previous message makes perfect sense to me or opening in v3.0 and saving, then opening in v4.0. Guess that doesn't help you much if you don't have v3.0 though.

"Just curious, did you download the V4 demo and try to open V2 projects before you concluded to buy V4?"

Actually I didn't (and thining about it, I should have). But I did try the Beta version. I became aware of the problem already then, but I thought that it would be fixed in the final release. Wishful thinking...

Weevil:
"The only workaround I have found is to open the V2 project in it V3, save it in V3 format and then load that file into V4. It works perfectly and is so straightforward and simple [rolls eyes]."

Good heavens. So we're like, supposed to purchase V3 just so we can use V4. So, do we now bitterly regret skipping a version? Yes indeed.

Could Sonic Foundry *at least* create some kind of a batch conversion utility that would make V2 projects compatible with V4? Of course, simply making V4 able to open V2 projects correctly would be the best option.

I honestly believe they're working on it, but I suspect the next update will be a while longer. April seems to be the customary month for fixing problems that appeared in the NAMM release, for Logic, Kontakt, Vegas etc =)

Good idea about using v3 as a converter, but like a lot of people, I ended up going straight to 4.0. So I'm broken until they fix it or come out with a conversion utility as someone suggested.

Again I ask.... Any official response from Sonic Foundry? Hello? Hello? Do Sonic Foundry reps read these posts or not?

I finally, got around to reinstalling vv2.0 on my system and varified your problem. Yuck!!!! This is ugly...basically you lose all your mixer section. Adding a bus in the mixer section in V4 seems to help with the output routings, but they're not exact. Changing the amount of buses under the properties gets you closer to where you need to be as you mentioned. The assigned inputs are incorrect also. It would be nice if you could do some copy and pastes of the data between the 2 programs...verified that's not possible either. They do give you a nice disclaimer message though don't they?

"Vegas 4 is unable to recover all of the audio routing settings from Vegas 2 projects."

This is a pretty obvious error message saying they're aware of this problem don't you think? Looks to me, they just decided to throw their hands in the air and forfeit on this one. Looking at this, it seems if they can't find a work around fix, then they should have just left off opening Vegas 2 projects all together. I haven't tried opening any Vegas 1 projects either, but I know they didn't list that one as being supported. This seems more like an "OMF" file support opening now doesn't it? This is exactly what you would expect if you opened an OMF file. You'ld get most of your editing and audio, but your routings and FX's wouldn't be the same between different apps.