John,
Thanks for that, but I'm not interested in re-encoding the video. If need be, I'll export this project as an EDL and open in Premiere. I'll lose color corrections and titles, but I also don't want to reencode what's already a low-grade stream from Zoom. I'd rather see Magix address this, or find a means of modifying the decode. This is a huge issue for us, as I've got over 100 clips from Zoom and other mono sources on this timeline.

[edit] but this link DID get me to a post where i can download previous builds. Thank you for the link.

@Douglas-SpottedEagle

The workaround doesn't re-encode the video. Rather, extracts the video and audio as elementary streams. It is a hassle to have to re-group them, but may be preferable if a lot of effort has been invested in a 21-300 project.

I can't comment on Vegas Creative Software update schedule.

@Douglas-SpottedEagle...good to see you here. It has been a long time.

We finishing wrapping up development of a patch to build 300 which will address this and other issue that have been discovered in that build. I cannot give a precise release date, but it probably will be a few more weeks before we can finalize the release testing.

Thank you @VEGASDerek. Was really surprised to see this error, and glad to hear there is focus. I've been able to reinstall build 208, and although it can't read the original project saved in a later build, I was able to export an EDL, which enables us to finish this particular project. It was dumb of us to update the two machines with build 300 in the middle of a project. We broke a cardinal rule. :) Doing so in Vegas is usually safe.

Better to have multiple VEG projects based on build version as well, for safety :)

Not to forget the .veg.bak backup that you can also try to be opened while hoping it's not yet overwritten by newer build version.

Thank you for the point. I'm very new to the whole Vegas and editing thing. 😉

So, help me understand how you'd edit for "different builds" of Vegas? The .bak feature is great, but that too, is version specific. TMK, EDLs are the only means of bridging to legacy software builds?

TMK, EDLs are the only means of bridging to legacy software builds?

DSE, as of right now.... well, unfortunately yes.

The best thing I can say around this, while observing the continues development of the VEGAS Pro....usually compatibility between different builds is tried to be kept maintained, means the older build of the same Vegas Pro still able to open newer build saves. But, due to some recent required development status of VEGAS Pro, it's quite possible that the newer build might need to 'lost compatibility' to prior version so that it no longer can be opened with older build.

So for making safe, I agree if we better not update the software build in the middle of project, in case something goes wrong. And if we decided to update the software build in the middle of project, better to save as new project VEG file of the project you are working, again, for another safety purpose if something doesn't work right.

Thankfully that veg projects are small file sizes in general, so it should not hurt to have multiple VEG project files rather than one. 😊

@Douglas-SpottedEagle wrote

I'm very new to the whole Vegas and editing . 😉

Only 10997 posts/comments on the Vegas forum before the MAGIX era. Several (Sony) Vegas Pro Editing Workshop guides, etc.

Welcome back!

@Douglas-SpottedEagle wrote

I'm very new to the whole Vegas and editing . 😉

Only 10997 posts/comments on the Vegas forum before the MAGIX era. Several (Sony) Vegas Pro Editing Workshop guides, etc.

Welcome back!

10997 are not enough! Welcome back, too. :)

Even here in Vienna, I have some of your earlier Vegas books (when I started with Vegas Pro 4 was the first one).

So, help me understand how you'd edit for "different builds" of Vegas? The .bak feature is great, but that too, is version specific. TMK, EDLs are the only means of bridging to legacy software builds?

 

I include in the name the version and the build that was used to edit the footage. At least, that allows me to know which version was used. It I continue to work with a newer one, I save it with the additional informaton of the newer version/build. Borring, sure, but at least you have some transparency.

Even here in Vienna, I have some of your earlier Vegas books (when I started with Vegas Pro 4 was the first one).

Got one too 😁, during early days of learning VP.

I think I got it 3 times - my oldest one is Vegas 4.

Douglas-SpottedEagle wrote on 5/3/2024, 8:06 PM

Thank you for the point. I'm very new to the whole Vegas and editing thing.

I don't think he's the same DSE...

geez ed, you've forgotten me already?😉

Still around, still using Vegas daily, but also working a fair amount with Resolve these days. I did present Vegas at NAB this year, however.

geez ed, you've forgotten me already?😉

Still around, still using Vegas daily, but also working a fair amount with Resolve these days. I did present Vegas at NAB this year, however.

Dont think so. But you did not use your old account. Ok, years have passed.

@Douglas-SpottedEagle Yes, of course, I remember DSE. I would have expected to see the posts made under your old account, though.

AFAIK, this is the only account I have/had. Apparently my old account from SF and Sony days carried over to another account.
Regardless, thanks to those who provided some insight. In haste to get the nag windows out of my face, I updated both systems and obviously, that wasn't too smart. Been a long time since a software update has really bitten my butt hard.
It all worked out.
Putting the video into a previous version of Vegas, rendering the audio to a .wav file and syncing up in V21/300, allowed us to complete the project. Had this been BMD or other high-quality source, we could have likely recompressed and all would have been fine. Since a good chunk of the source was low-grade 1080 from Zoom, recompression and compositing wasn't an option.

Thanks again.