@Sadlylate Alpha channel formats still work in VEGAS. Quicktime decoding edit: still functions, and other formats are migrated to the native decoders such as Apple ProRes.
@Sadlylate Alpha channel formats still work in VEGAS. Quicktime decoding functions and other formats are migrated to the native decoders like Apple ProRes.
This seems to contradict this comment made by a member of the VEGAS Pro team recently:
https://www.reddit.com/r/VegasPro/comments/1nblk51/comment/nd2ruf4/
The File I/O Surrogate was rewritten with the release of 23 and its only existence is to handle Quicktime decoding. If Apple ProRes now handles the decoding natively then I'm wondering what the actual purpose of the I/O Surrogate is for or maybe I'm misunderstanding something somewhere
Yes, I think my comment was imprecise. ProRes is decoded natively as are more snd more formats. QuickTime still does DNxHR and a few others that have yet to be migrated.
@Sadlylate Alpha channel formats still work in VEGAS. Quicktime decoding functions and other formats are migrated to the native decoders like Apple ProRes.
This seems to contradict this comment made by a member of the VEGAS Pro team recently:
https://www.reddit.com/r/VegasPro/comments/1nblk51/comment/nd2ruf4/
The File I/O Surrogate was rewritten with the release of 23 and its only existence is to handle Quicktime decoding. If Apple ProRes now handles the decoding natively then I'm wondering what the actual purpose of the I/O Surrogate is for or maybe I'm misunderstanding something somewhere
@thesammy58 Just to be clear, the developer's statement about the File I/O Surrogate is, "It is still needed if you enable the QuickTime decoder." I understand that to mean that if you don't install QuickTime decoding drivers and enable them in Deprecated Preferences, the File I/O Surrogate could be completely removed from Vegas. But my experience is as @RogerS mentioned... Vegas cannot process DNxHD without both QuickTime & Avid drivers installed and QuickTime decoding enabled.
Hello, I took advantage of a promotion to buy Vegas Pro 23 on the official website https://shop.vegascreativesoftware.com/ I knew that the French version was not working, so I installed it in English version, but after the installation, the software systematically gets stuck! 😦
Hoping to have a solution / Thank you for your help, beautiful day
Problem Description
Application Name: VEGAS Pro
Application Version: Version 23.0 (Build 302)
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\WINDOWS\SYSTEM32\ntdll.dll
Fault Address: 0x00007FFCF315C1FE
Fault Offset: 0x000000000001C1FEFault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 23.0\vegas230.exe
Process Version: Version 23.0 (Build 302)
Process Description: VEGAS Pro
Process Image Date: 2025-09-27 (Sat Sep 27) 00:42:20
@Lamyss Is it an issue with Visual Studio? https://www.vegascreativesoftware.info/us/forum/warning-ms-vc-14-50-v145-kill-vegas-permanently--150332/
So, there is no keyboard shortcut to "Go to In Point" or the out point in the trimmer (e.g., "Shift + I" or "Shift + O" in Premiere? Seriously? Something so basic, so intuitive, yet missing in Vegas Pro 23 that's been available in other editors for over a decade? Who's in charge of the development?
I began with Vegas 6. It has been a rocky road but, mostly, productive. I was a happy V19 Pro user and decided to upgrade to V23 Pro because of some of the advertised improvements. I am back using, stable, productive, V19 Pro.
I purchased V23 Pro in October but didn't truly use it as I was preparing for a trip which would take up all of November. I returned in December and was almost immediately notified there was an upgrade patch. I installed it but is it quite unreliable. I have, so far, only used it on very small, completely new, test projects. It has crashed several times. I finally attempted a render and that seems to have gone smoothly and swiftly. Whew!
My biggest issue now is the display of still images. I am using HEIC images created by an Apple iPhone 17 Air. Images with the dimensions of 5712 x 3218 display with proper thumbnails on the timeline and in the project window but simply show black in the Video Preview and in the render. If I open the Pan/Crop window for the image, Vegas often crashes. Other images, usually 5712 x 4284 in dimension, display and render without issue.
No such problems with Vegas 19 Pro.
O vegas pro 22 aceita tranquilamente o Magic Bullet Looks para salvar em Filter Packages, mais infelismete o vegas pro 23 salva mais fica com o Bug as cores não reconhece como no na sua versão anterior vp22
O Ruim que famos aqui e nada resolve!
The noise reduction effect makes Vegas crash. It was working in version 22. Do you have a solution?
I see that the situation with Vp23 will be exceptionally serious that there is still no proper update. That's good. It's time for the development team to start behaving responsibly and not use us as beta testers every year.
Name one software that doesn't use us as beta testers where the software is totally bug free?
I'm a Samsung Galaxy S25 Ultra user.
I used this phone to record 4K 60fps video with HDR enabled.
When editing a file recorded in 4K HDR in Vegas Pro 23, the HDR image becomes unusable and overly bright, resulting in an unnatural look.
This HDR video can be edited as normal in Premiere Pro Edit.
Please find a solution in Vegas Pro 23 or update it.
Name one software that doesn't use us as beta testers where the software is totally bug free?
@Reyfox ... +1.
DaVinci Resolve releases beta versions before releasing the official version ... yet their user forum currently has lots of users posting problems of all sorts with the current 20.3 official Resolve release.
@si-Kim more info is needed. First, I do not have a Galaxy phone, so there is no way of testing the problematic video file. And unless the Vegas Developers have one, there again, would be no way to see where the problem is.
Also, how about listing the settings you are using? Providing an actual native file that can be downloaded?
Name one software that doesn't use us as beta testers where the software is totally bug free?
Winrar.
Winrar.
Very amusing!
How about getting real and identifying another NLE with a similar complexity to Vegas Pro that exists without any problems for any users/editors.
I could write a BASIC that has no bugs. But then, it doesn't have the thousands of lines of coding that video editing software have.
While I understand user frustration when particular issues are present for them, and not seeing any perceptible progress, I feel for you @pierre-k. Wanting Vegas to be the best is what we all want.
Winrar.
Very amusing!
How about getting real and identifying another NLE with a similar complexity to Vegas Pro that exists without any problems for any users/editors.
Pointing out that others are doing it too is childish. That's not an excuse. If the team makes a bug in Vp21 and it's still there in Vp23 and a team member writes that fixing it is not a priority for them, then I have to be upset, even if some of you don't like it. Their constant release of unfinished inovations that the team then doesn't care about is legendary. I hope that what's happening now with Vp23 will be a clear lesson for the team.
Hopefully there will be an update before long that solves the biggest problems people are reporting.
@J-Toresen it was 10 million or something like that. Still a lot to keep track of.
Yep, it's over boys.
After the recent NVIDIA drivers crashed V22 when rendering I was about to pull the trigger with a V23 update. Noticed this was actually a NVIDIA issue (apparently), sucks because I wanted to put my new 5090 through it's paces, so decided to hold off. I'm now reading the posts and comments about V23 and there is absolutely no way I'm paying for it, I'll stick with a previous version.
This happens way too often with MAGIX products and it's always the same apologists that defend it. MAGIX business practice of only including 1 year of updates for a one-off license is absolutely pointless when 3-6 months are spent being a beta tester for the product.
Quite simply, MAGIX and the Vegas platform can't keep up with new tech. I'm not spending money for an unfinished product that's going to crash, fail to render, or includes fixes that I have to implement by digging through forums and changing windows settings.