Hello everyone,
The VEGAS Team is happy to announce the release of VEGAS Pro 22 build 250. Please use this thread to post general comments on this update. For details on this update, please read this post in the News forum.
If you are having any issues using the update or have specific questions, please create a new thread.
Thank you,
The Vegas Pro Team
I have successfully used SonyVegasPro and Magix VegasPpro from 8.0 through to VP21 for my business. On retirement I have loaded VP22 to build 250 and cannot edit a single thing. Clips load but do not play. Repeated requests to support have had no result. Now the VP21 licence has "expired" so I cannot even go back. What is happening?
@ian-b Can you share a screenshot? (what does load but not play mean?) You have the video preview tab selected and not the trimmer, yes?
You had VP 21 365 (subscription) and then purchased a license for 22? Otherwise you can go back.
Do either of the known-good projects in my signature play on your system?
Thank you for responding. By "Load" I mean "Add to Timeline" and by "not play" I mean click on play but the cursor does not advance or playback in the video preview. I have selected video preview as I am trying to view the output from the timeline.
I cancelled VP21 365 when I found I had VP21 (not365) installed.
I am an editor/user, not a software developer.
Thanks for clarifying. If you hit terminate it should create an error report and you can paste in here what "show problem details" says.
What is your GPU model?
The media is MTS. I'm not sure what codec it is- if it's AVC, does going to options, preferences, file io and checking legacy AVC decoding help?
You can still use 21 by the way as you purchased it. I have 21.208 and 22 installed.
How can I report a bug? I found that using Autolooks in my system (Win10, RX580, Ryzen 5 2600, 16GB RAM) eventually grinds the render process to a halt.
After testing with different combinations of files and effects (audio and video), I've learned that Autolooks is the cause. While other VFX keep Dedicated GPU RAM usage at 4.5 GB, this specific effect uses all of the dedicated GPU RAM, then moves on the Shared GPU RAM. While this is happening, system-wide RAM keeps increasing.
When system-wide RAM reaches 99%, the render process crawls. It doesn't crash, but goes really, really slow. Like, less than a frame per second. But the GPU shared RAM keeps increasing. I believe when it reaches a certain threshold, it makes the preview video glitch out (green portions, white squares, elements that are not rendered, for example) - I didn't see this happening live (takes too long), but I've seen this happening in previous render attempts, and I can only assume that is the reason why it happens.
I notice that V22 does not seem to save changes in preferences menu, eg editing tab when I check automatically overlap selected media and change the overlap from default 2.000 to 1.000 to give a one second overlap fade. restart Vegas and it is back to default settings.
Also v21 and V22 cannot import AVC files (came from DVD Architect when making DVD files a while back) V20 imports fine. I need to rewrap the file to MP4 using shutter encoder.
How can I report a bug? I found that using Autolooks in my system (Win10, RX580, Ryzen 5 2600, 16GB RAM) eventually grinds the render process to a halt.
After testing with different combinations of files and effects (audio and video), I've learned that Autolooks is the cause. While other VFX keep Dedicated GPU RAM usage at 4.5 GB, this specific effect uses all of the dedicated GPU RAM, then moves on the Shared GPU RAM. While this is happening, system-wide RAM keeps increasing.
When system-wide RAM reaches 99%, the render process crawls. It doesn't crash, but goes really, really slow. Like, less than a frame per second. But the GPU shared RAM keeps increasing. I believe when it reaches a certain threshold, it makes the preview video glitch out (green portions, white squares, elements that are not rendered, for example) - I didn't see this happening live (takes too long), but I've seen this happening in previous render attempts, and I can only assume that is the reason why it happens.
It's reported, thanks for finding this bug.
Also v21 and V22 cannot import AVC files (came from DVD Architect when making DVD files a while back)
That's strange. My VP21 imports avc files, produced by VMS17 and VP21, okay. But I find ac3 audio files produced by VP or VMS aren't recognised. It's strange that VP21 doesn't handle ac3 that it produced itself! I use tsMuxer to combine the avc and ac3 into a playable m2ts file.
I have been using Vegas for many years, 22 worked great without any problems until I made a mistake and confirmed the build 250 . Since then the software has been freezing/crashing and I have to turn off the computer (Windows 11 version 24H2) while editing during rendering and I can't get the job done!! I installed the patch and that didn't help either!! I need a solution now and immediately and if you don't have one? Please send me the previous build that worked great for me.
I have been using Vegas for many years, 22 worked great without any problems until I made a mistake and confirmed the build 250 . Since then the software has been freezing/crashing and I have to turn off the computer (Windows 11 version 24H2) while editing during rendering and I can't get the job done!! I installed the patch and that didn't help either!! I need a solution now and immediately and if you don't have one? Please send me the previous build that worked great for me.
See the '7. DIRECT LINKS' section here for older VP22 versions - https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/
I have been using Vegas for many years, 22 worked great without any problems until I made a mistake and confirmed the build 250 . Since then the software has been freezing/crashing and I have to turn off the computer (Windows 11 version 24H2) while editing during rendering and I can't get the job done!! I installed the patch and that didn't help either!! I need a solution now and immediately and if you don't have one? Please send me the previous build that worked great for me.
same exact issue. Can not render since upgrade. Support just keeps asking for more and more info. on my computer
@Ken-Tonks Go back to a build that worked for you. Try 248? The link is at the bottom of this post https://www.vegascreativesoftware.info/us/forum/new-update-vegas-pro-22-build-248--148806/
You will need to download then uninstall VP, then install with 248.
Will it prompt me to uninstall if i open file? Will I lose all my settings? Omg starting over is unimaginable. Will i still have my projects? Thanks
@Ken-Tonks Go back to a build that worked for you. Try 248? The link is at the bottom of this post https://www.vegascreativesoftware.info/us/forum/new-update-vegas-pro-22-build-248--148806/
You will need to download then uninstall VP, then install with 248.
I realized that since update actually working with Vegas is smoother, much less freezing and pausing. Is there a way to keep 250 but stop the rendering issues?
@Ken-Tonks Does a reset of VEGAS help?
https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/
Idk as I received a suggestion that worked!, at least on first try.
I just upgraded and keep getting blank black screens randomly when editing and watching the playback. Thinking about dropping back down to 248. But doesn't anyone know what is going on?
@joshua-noesser how about starting your on post and include information from "B" and "C" in this POST.
Be specific. Also, add your computer specs to your Profile>Signature like mine below. It is one of the places those trying to help look to find out what your computer specs are. Right now, your User Profile is blank.
And if possible, upload a short sample of the problematic footage for others to test.