In the past when 'issues' have been noted there's been replies from either the Vegas team members who can give more specific answers or from Mods/Beta testers who have a little inside knowledge & can give a hint as to poss future fixes but for whatever reason this issue has been ignored for a lack of a better word, even the replies by you a Mod & Steve a long term regular whom I believe is a Beta tester are directed at me rather than the topic of this post, I feel left in the dark & I'm sure I'm not the only one.

@Gid Steve has spoken about his secret to Vegas Pro bug free operation, don't use a GPU, turn GPU processing off, turn GPU decoding off. He's leaked images showing he's a beta tester. The problem releases of VP21 b300,314,315 are all related to GPU processing and GPU decoding. I"m concerned other beta testers have learnt from Steve. It would explain why we instantly picked up on GPU related bugs that Steve and other beta testers never did, not complex operations, simple GPU decoding of AVC and HEVC in MP4 and MXF containers.

@Steve_Rhoden A penny for your thoughts?

 

I can confirm this is not even close to true. I don't have any issues whatsoever using my RTX 3090 with any build of 21, so it isn't just "turn off your GPU and the problems will go away". Sometimes certain formats can slip through the cracks, but it's never something as widespread as disabling a critical piece of system hardware for all the testers because of some "that's the secret sauce to making this app work" philosophy.

As for updates, I can't say if there will or will not be future 21 updates... I do know that we're in the part of the summer a new version typically releases in, so chances are that will happen soon. Sometimes if it turns out that a bug in an older version is affecting a large number of users, they've been known to release fixes for older versions then, but I don't know if that'll be the case with your issues. As mentioned earlier, any queries directed at Magix/VEGAS Creative Software should go through official channels.

But I will put that rumor to rest now, I test VEGAS Pro with my GPUs enabled at all times. I also test with the current decoders enabled at all times, as that's what we're here for, to make sure VEGAS works in its state of the art state, not in some gimped state that is a workaround. We're not perfect, sometimes we miss stuff, sometimes QA misses stuff, but we're doing our best.

Interesting thread @Gid. So I hope you don't mind if I add my thoughts to it.

My computer builds have been all AMD for a very long time. The software I use, the games I might play, and the editing software I have all work well with my all AMD computer. Specs in my Signature.

Now, I can and have tested other user video clips that they've had issues with on my computer and have adding the results to their threads. I don't do "MKV", XAVC any flavor, BRAW, ProRes of any sort, nor HEVC even though my gear can shoot HEVC. I edit what my G9, Mini Pro 3, and other Panasonic gear create. And, never an issue for "me".

My GPU gets plenty used, depending on what I've done to the clips, I never turn it off except for testing purposes of someone else's problematic clip.

These are my experiences. Vegas works pretty good. I also have Resolve Studio like a lot of others here. But my preference, for what I do, Vegas rarely crashes and just works. That's all I ask. Another editor may render faster, may have a feature I might like, but that is how it is in everything. But overall, Vegas works for me.

If there is a bug that affects a lot of people, I do hope that it will get fixed.

@Reyfox Hi, I take it you're talking about (315), what File I/o do you have set?

I've mentioned it before in other posts that VP21 (315) is the most stable there has been, for me anyway, I honestly can't remember when it crashed last, render times are improved & playback with HEVC is flawless.

I use HEVC in both my cameras, I 99.9% of the time trim the start & end of an event so these unquantified ends do get removed & then I add a 12fr crossfade, that I can live with but Render to a new track is a different story, if the short sections are only 150 frames long for instance & it has to blend back into the orig event I can't go chopping of a frame. I can adjust it but I shouldn't have to. (I must add that not all unquantified ends create a black frame, they flow correctly one event onto another despite the timeline showing it's unquantified,, 🤷‍♂️ ?)

I'm not talking about the problems per se, all I want to know is this going to be resolved before the new VP22 is released, & hopefully that will give an answer as to why there's been very little talk of this from anyone who might know in the posts that were 'resolved' by reverting or turning on Legacy.

We know that once a new version comes out the previous one is pretty much dead in the water reg updates or patches & I know every version has it's own share of problems..

@Gid screenshot of the File I/O in B315. Depending on the fps I shoot at, the crossfade is usually 1 second. I also don't render to a new track. If I do, I'll use Happy Otter Scripts.

 

 

I can confirm this is not even close to true. I don't have any issues whatsoever using my RTX 3090 with any build of 21, so it isn't just "turn off your GPU and the problems will go away".

@fr0sty As a beta tester you should be noticing problem files with b315 because they still exist. I acknowledge that you and others may not have problems with what you personally do outside of testing and works great for you on default settings, but you have to account for all media a Vegas user may edit.

@Todd-AO

You are very wrong. No voluntary beta tester is accountable to test all footages that may be available. He or she has the function to bring in some kind of users perspective, with the hardware available, with the footage available. Most of the testers tend to collect different types of footages to extend that, sure, but given the limited resources no tester can bring in more then his limited perspective.

@Gid

nobody can be sure, but given the major tasks like the ongoing renewal of the video engine (started but not finished with the actual Vegas version, as announced many times by Derek) I doubt that there will be capacity for additional bug fixes in VP21. I may be wrong here, and this is my personal perception only, simply because every change is in the hand of the development team.

@ All

if you are unhappy with what beta testers, you could think about what you are willing to contribute. Up to you.

@Wolfgang S. Thanks for the reply, I've heard bits about the poss new video engine, mainly from @fr0sty i think, it's been a while so I can't remember who it was exactly but what were the - 'as announced many times by Derek' ? I've read pretty much every post but I must have missed those announcements, was it in a comment in a post somewhere.. ?

I'm not trying to start an argument I just genuinely can't remember seeing those 'many' posts?

---------------

if you are unhappy with what beta testers, you could think about what you are willing to contribute. Up to you.

I think generally we do all contribute, we test each others files & try to find solutions, one of which is to turn on Legacy or to revert to to (208), I'm not sure how we can contribute more?

---------

PS. In case i did miss those many announcements I just read @Dereks comments going back to this 5/14/2024 post by the VEGAS_CommunityManager Update: VEGAS Pro 21 Build 315 (Patch for 314), Apart from 'Build 314 also addressed several issues mostly revolving around the new video engine upgrades.' by the OP of that post there's no further mention or announcement of a new engine by Derek, should I look further back?

• VP21 (208) was released
• VP21 (300) was released, there were problems so ..
• VP21 (314) was released, there was a problem with that too & very shortly after
• VP21 (315) was released, there's still problems with that as reported by the community, that's there 'contribution'
• Revert to (208) the solution.

Basically since (208) you've been testing this on the public & have given very little feedback apart from promises of a new engine, of which we may have to pay for with VP22.

I think generally we do all contribute, we test each others files & try to find solutions, one of which is to turn on Legacy or to revert to to (208), I'm not sure how we can contribute more?
 

if you identify bugs, and are able to describe them in a very clear way, that allows others to repro your finings - then this is really helpful. Only with a repro someone can analyse and solve a bug.

Personally, build 315 works great for me. But I don't use that one specific type of file either.

Here is the main comment I found re: the video engine which we all have been testing since build 208 (and MxCompound which goes with it)

https://www.vegascreativesoftware.info/us/forum/new-video-engine-in-vegas--143158/#ca895245

Lots of promise but clearly a work in progress as stated here:

https://www.vegascreativesoftware.info/us/forum/new-video-engine-coming-in-the-next-update-this-month--144799/#ca906938

As already stated in that first thread re progress

https://www.vegascreativesoftware.info/us/forum/new-video-engine-in-vegas--143158/#ca895259

The video engine has already had some of its elements deployed, and will be a work in progress as it has other elements deployed and refined over time. I already posted one video that showed how much faster 21 b315 is at decoding 4K 10 bit AVC 4:2:2 media, it's faster by orders of magnitude, to the point that for many projects, I no longer have to use proxies when decoding media created by my Panasonic S1 cameras.

More updates will come in time.

208 saw some improvements to HEVC decoding if I remember right. 300 is the build that saw the first major change in the video engine. It did introduce a few bugs, most of which were patched in 315. A few remain. We can't expect a complete rewrite of the code to not come with a few growing pains, but the team is doing their best.