Upgraded to build 300, and opened a project I had been building and working well before the upgrade. When I upgraded and opened the same file and received notifications that it could not find some images, even though they were located where Vegas 21 said the location were. Additionally, I have about 4 mp4 files that Vegas 21 shows in the Project Media window and on the timeline except in the Project Media window there are no graphics, just a green thumbnail and on the timeline there is no graphics but there is sound in all locations where that mp4 file is referenced. When I look at the file details I note that 3 of the files are MP4 v2-AVC and one is MP4, Sony XAVC-S-AVC. They worked fine with the previous version of Vegas 21. The issue only came up with build 300. Any guidance would be appreciated.
Thank you for your response and guidance. I have been using and upgrading my Vegas SW in the middle of projects well before and after Magix took control of it with no issues. I understand what you are saying and now, with my current experience, I will keep your guidance in mind. All my images and video clips came over and are placed properly in my project. Even the MP4s are still placed properly in the project other than Vegas Pro 21 not reading graphics of the MP4. Build 300 has changed in how it reads the MP4s. Additionally, those MP4s were built and rendered in an earlier version on Vegas. More concerning is that I may want to modify/update my project at a later date. As I understand your guidance I would need to have both versions of Vegas on my computer to do this, i.e., Build 300 for new projects and a pre-Build 300 for my older projects. Am I understanding that correctly?
I have on additional question. My project worked great in the pre-build 300 version of Vegas Pro 21, and I a backup saved in that previous version. How to I ensure that when I reinstall Vegas Pro 21 that I get the version prior to Build 300. I did not see an option to download an earlier version, but then I didn't go past the download screen because I assumed that it would download the most current version, i.e., build 300.
Thank you.
You can download all recent versions of VEGAS here. 21.208 was the prior build.
In general incremental updates are fine but 300 is like a new version of VEGAS. Unfortunately it introduced numerous bugs along with major improvements. Those should be worked out and patched before long- how big a hurry are you in?
If you can revert to a 21.208 era project just skip 300 until it's done and then test an update to 300 and make sure it works with your projects and media.
@The_Aviator, once you save a project in say B300, you will not be able to open that project in B208. What I would do is load the project into B300, then save it with a different name. I'll add what version of Vegas I am using. My current project is on European bison here in Poland. I started in VP20, and am now in VP21. I can bring in any past project, but I save it with something like "Polish Bison VP21 B300". I also, for each version of Vegas, I have separate folders for everything. Working on that project with VP21 B208, guess what the project name has at the end.... 😉
Ok, understand. Sounds like B300 was put out too early. I will revert to my older version and wait for a B300 update and then ensure it brings over my project properly. I usually always upgrade to the most recent version. Never had an issue before.
Really appreciate your patience, time, and guidance.
Thank you for your quick responses.
@The_Aviator ... there is a basic truism in editing that is never to update to a newer version mid-project. But I've always ignored that (my projects are personal projects, not money-making professional projects). Another 'but' ... always keep the original .veg file intact and don't override it in the next version/upgrade - always save the new project created in a new version/upgrade with a new project name. That way, if things go sour, you can always go back to the previous Vegas Pro build/version using the older .veg file even though that will mean having to redo the more recent editing - but not the entire project. Also, regularly copy project .veg files to backup locations such as an external HDD/SDD, memory card and/or cloud based storage such as OneDrive.
As a last resort, if you have an earlier version of Vegas Pro, you could always copy/paste the timeline from Vegas Pro 21 back to the earlier Vegas Pro version (if available). The downside of that is that track/project FX won't copy/paste and any FX in the newer version of Vegas Pro that are not availbale in the earlier version of Vegas Pro will disappear.
Understand, and that is what I have done. In this case I do have earlier versions on several external hard drives, my logic was more if one HD fails I always have a backup, but clearly, based on other logic I have learned here, I will modify my backup methodology. I will uninstall my B300 and re-install B208. My projects are all personal but are family photo and video related for my kids. For me they are priceless.
Thank you.
My projects are all personal but are family photo and video related for my kids. For me they are priceless
Very understandable! Good that you have backups.
Well, this saga continues. I checked my backup copies and they are saved in Build 300, but I did some digging and experimenting and came up with the following results:
1. I copied, from a backup drive, and pasted one of the 4 MP4s over one of the same name that was giving me an issue. It worked. Build 300 read it and placed on the timeline properly. It initially gave me an error then closed down. I re-opened it and it came up with the file in the project and timeline properly. Really thought I figured it out. Wrong.
2. I did the same thing with the other 3 MP4s and it didn't work. Same issue, green thumbnail with only audio in the timeline. In looking at the MP4s I noticed the one that worked was a little over 1GB, but the ones I am having the issues with are 9.6GB, 10.5GB, and 17.3GB. Pretty large. It appears that B300 has an issue with large MP4s where B208 didn't. I loaded one of the large MP4s in B300 as a new project. It didn't like that at all, same issue. B300 has no issue with 11+ GB AVIs though. Perhaps I need to convert the large MP4s to something else. Suggestions?
Do you have to use 300? It has numerous known issues with the new decoder that I don't think are a good use of user time to work around.
Depending on what is in the MP4 check "legacy AVC" or "experimental HEVC" decoder in preferences to return to the one that 208 used. I don't think the file size has any bearing on this, it's what is in the file.
AVI doesn't use the new decoders.
If you really have to use 300 and the legacy checkboxes don't help I guess you could convert it all to ProRes which should work (ShutterEncoder can do that).
I really wish I could go back to the Build 208 for my project, but I saved my project under B300 and it is my understanding that I can't go backward to use B208. I did try once but if failed to do so.
RogerS - Thank you, Thank you. I have been pulling my hair out over this, and I really don't have much to pull out, and your suggestion worked. I will try to finish this project in B300 then go back to B208 to finish the others until Magix can provide an update of B300 with fewer bugs. Albeit, I guess this is not really a bug but my unfamiliarity with Vegas.
Thanks to all who have provided input. I learned something from every post.
The decoding errors including green screens are definitely bugs. Once the issues with MxCompound and certain media are resolved VEGAS will be in a strong place and there won't be a need for the old media decoders you have to fall back to.
@The_Aviator do you have an older version of Vegas Pro on your computer? If so, start B300 with your project, and copy that project and paste it in an older version of Vegas. Save it and you can open it in B208.
I can load up an older version, i.e., Pro 20. I will try your suggestion. Thank you.
Let us know how it goes.....
RogerS - Thank you, Thank you. I have been pulling my hair out over this, and I really don't have much to pull out, and your suggestion worked. I will try to finish this project in B300 then go back to B208 to finish the others until Magix can provide an update of B300 with fewer bugs. Albeit, I guess this is not really a bug but my unfamiliarity with Vegas.
Thanks to all who have provided input. I learned something from every post.
Is there a time-sensitive deadline? If not, it is recommended to proceed with project b 300, if feasible. Otherwise, it would be advisable to wait until returning to b 208.
I'm really disappointed, when rendering there are constant jerks and disappearances of tracks, it is impossible to get a decent result. I've been using Vegas for over 10 years, but it's never worked so bad. Can`t use effects.
@Andrii-Selivanov Please create a new thread that includes information necessary to help you like your system specs, the type of media and the render format.
Hello VEGAS team!
I've been trying Vegas Pro 21 a few days ago and i gotta say that i'm kinda impressed by the leap and differences between the previous version and this one.
Lots of improvements, especially in preview and rendeing that was awful in previous versions, at least for my configuration.
Rendering is smooth, not a single blink or a glitch on the effects, transitions that could be audio or video, as long as you have tweaked the appropriate settings.
I appreciated a lot the new rendering window feature that displays a lot of informations in real time and can help planning stuff and getting an idea of the potential of your machine regarding video editing.
Also, enabling multi thread rendering allows using maximum potential of the core, making it possible to render multiple projects at the same time without any problems (as long as you have a powerful enough computer) !
The best features are the HEVC/AVC and legacy render mode plugins that can make some renders who use different or older codec formats smoother and sometimes even faster, gaining a precious amount of time during the editing. It is also a significant gain in RAM using, both during editing and rendering!
Compatibility with Nvidia GPU is alright overall, but i find it difficult to tweak the appropriate configuration for most of the videos you are editing, particularly when having multiple and different video/audio codecs and formats in the same timeline.
Finally lots of interesting neat features like auto masking or AI assisting that could help empower any project but i'm focusing mostly on the optimization and quality of preview and rendering of the software in the first time.
Anyway overall that new Vegas Pro release looks promising in lots of aspects.
Looking forward to a final and stable release to decide whether or not it will be my principal video editing software in the future. Time will tell...
I'd like to thank Magix staff for making it possible to get a taste of the latest products so we can decide if it fits our needs and matches the computer's specs.
Good luck with your future releases, cheers!