Stability and hardware accelearation.

Norbert wrote on 10/19/2024, 5:35 AM

I used to use Vegas as my primary tool between 2009-2019 and I liked lots of things about it but due to the stability issues and hardware acceleration problems I had to switch my primary NLE.

As we see AI is getting better and better and I hope in the next 5-8 years we will have AI tools that can easily transcode from C++ to Phyton. Now this seems to be overcomplicated and time consuming but I was thinking about a Vegas, rewritten in Phyton fully with AI based bug fixing methods to "make Vegas great again" :)

Maybe we will get one day a Vegas on steroids with no stability and hardware acceleration problems.

Comments

andyrpsmith wrote on 10/19/2024, 6:08 AM

I would say that using Sony XAVCS 4K footage and Nvidia GPU (GTX 1080Ti and now RTX 4080 Super) I have had very little issues with stability or GPU acceleration. V22 seems the most stable so far. Vegas is very sensitive to media and GPU, there are many issues with users using OBS to generate media files. Would be great for Vegas to be rewritten from the ground up but I think there are not enough resources to do so, the team are targeting the key areas of user dissatisfaction as time allows. I think its still the best NLE out there for ease of use and low learning curve.

mark-y wrote on 10/19/2024, 8:41 AM

The megalith Sony Corp. gave up on porting our Vegas to Mac after years of work and a LOT of $$$.

I don't think putting last century's obsolete code in a slick teflon codebase is going to happen, nor would it solve any of Vegas' stability or 21st Century evolvement issues.

Just one guy's perspective . . .

RogerS wrote on 10/19/2024, 9:13 AM

With the rewrite of the video engine starting last year, I think we're heading towards your vision of what the program should be.

bitman wrote on 10/22/2024, 4:15 AM

I used to use Vegas as my primary tool between 2009-2019 and I liked lots of things about it but due to the stability issues and hardware acceleration problems I had to switch my primary NLE.

As we see AI is getting better and better and I hope in the next 5-8 years we will have AI tools that can easily transcode from C++ to Phyton. Now this seems to be overcomplicated and time consuming but I was thinking about a Vegas, rewritten in Phyton fully with AI based bug fixing methods to "make Vegas great again" :)

Maybe we will get one day a Vegas on steroids with no stability and hardware acceleration problems.

@Norbert

Towards the end patches of VP21, and now in VP22 I can say that Vegas is not plagued any more with frequent hangs and crashes, so much so I do not franticly save anymore after each edit action. It can still occasionally crash or hang on certain complex plugins, but many days go by with day long intense editing and no crashes or hangs.

On the matter of Phyton, this language is not suitable for Vegas source code, it is too slow as it is an interpreted programming language and to make things worse for a NLE, it is only single threaded. As Vegas needs real-time or faster timeline edits, it will lag. Also the extra step of interpreting means extra execution cycles, more CPU use, more heat and ultimately more of a human footprint on an ecologic large scale with many users.