There was a VP22 review that was posted here recently by a long term user and deleted. Either he was reviewing VP21 because he just bought it calling it VP22 in error, or he's a confused beta tester and actually was reviewing a VP22 beta thinking it was the release version???, the latter would be bad news for VP21 owners.

Yeah I don't understand the thoughts on this. There's quite a few posts where people have been recommended to revert to (208) or turn on Legacy AVC, those people inc myself have a large range of different PC components so the problems aren't specific to a certain driver or only AMD GPU's for instance. I presume this was Beta tested before release so why weren't these obvious problems picked up on or did they just think F*it & released it anyway. 🤷‍♂️

(314) came out & then very quickly (315) came out, I can't remember why but I think it was a 'fix' for (314) which was obviously a dud & they threw a patch into it.. It's been a bit of a cock-up & now it sounds like they're glazing over that.. moving on... la la la, 🙈🙉🕺 "We promise if you pay for VP22 it'll all be fixed & be much improved, trust me 👍👍", , We don't even hear that kind of BS from the developers, nothing, no response in the comments just the odd comment from a mod about how it's all going to be so wonderful in future releases.. .

They normally don't reply when they don't have good news, not always but mostly

It is the first time in years I have stopped using Vegas for short and fast edits where I need to publish in shortest possible time related to live events. Instead I used the past few months to try and improve my speed with other editors, and also in a way, I"m doing a simulation where Vegas is no more, and I'm forced to use another editor.

With Vegas though I'm choosing not to jump through hoops anymore, not doing Vegas workarounds, leave everything on defaults. Currently due to the huge amount of different media I edit I don't risk using it, There's still an AVC and HEVC problem with dropped frames to do with High@L5.1 profile which is very common media. I would hope they would not keep this version as final VP21

They normally don't reply when they don't have good news, not always but mostly

Yep normally if there's criticism about VP there's a torrent of defensive replies but with this subject there's nothing, it's as if they have no defense & are just keeping out of it...

@Gid You specifically tagged two developers in your initial post/question. Why then would there be a ton of defensive replies?. Probably none have yet noticed your query.

@Steve_Rhoden That's a slightly humorous reply as it wasn't the developers I was referring to who respond with defensive replies, anyone who reads this forum knows the developers reply with careful polite comments, it's a few loyal regulars who get defensive or feel the need to make their response stand out by putting their words in bold 😂 Instead of joining the conversation you decided to critic me pretty much proving my point

BTW I made this post 5 days ago, the only reason it's back up to the top is because I commented on it, but there have been many posts where this reverting to (208) or turning on Legacy AVC has been mentioned, there's plenty of opportunities to make a comment.

My wishful scenario would be a bugfix for 21 as 22 comes out.

@RogerS That would be nice, I'd like to know either way, If they said 'yep we're going to fix it' then good everybody would be happy 👍 If they replied saying 'sorry we ca't fix it in this version' I'd be disappointed but I'd respect & appreciate the response, so far we've heard nothing..

@Gid This is a related problem I"m seeing, people from the pleb forum (this one) bring up questions and bug complaints that are answered and talked about in the exclusive beta testing lounge and the person that brought up the problem never hears back and doesn't even know anything is being done.

It's as if a culture of elitism has taken over, we discover bugs, but don't deserve to be an ongoing part of researching and discussions. This is also a bad look for the forum, why have a dead public forum, and an active private forum. It makes it appear that this is a ghost town, everyone left, nobody is using Vegas anymore. Beta testing forum discussion should be restricted to testing betas, not testing release versions.

The possibility that a low quality beta tester but high quality Vegas Yes man may know the answer to your question but you don't deserve to know considering the high quality of your input into this forum is disappointing.

This all seems like speculation- can we just focus on what we actually know or what we'd like to see?

More feedback to bug reports in this forum- that sounds good to me.

Would be great if the people who make the reports are also able to test the solution (assuming they want to volunteer their time in this way and I can understand why some wouldn't).

can we just focus on what we actually know or what we'd like to see?

The latest Vegas builds work pretty well for my (simple) needs, with just one annoyance. The CGP, specifically using Hue v. Hue and/or Hue v. Sat, where it completely kills preview performance.

This has affected my colour correction workflow when, say, balancing against a colour chart or matching cameras.

I would be thrilled to see that fixed.

I would be surprised if the Vegas team does not have a last and final 21 patch before releasing 22.

I do not think they can afford to leave 315 with their default settings if users are recommended reinstalling build 208 or ticking legacy for some contend formats or issues.

That said, I am currently timeline editing build 315 without issues on 4K 25P RX10 mark 4 Sony camera 8 bit source material in a 25P full HD project with a lot latest BorisFX continuum effects. Very stable and no hangs eighter. So far so good.

@bitman Yep, what I'm hoping is there is some kind of upgrade going on but it can't be released until VP22 is ready to be released. Buying this 2 for 1 deal is maybe their way of saying this & just before VP22 comes out there'll be a final build of VP21, out in time to fix any problems but not out too soon to give the game away reg VP22, the problem is that once a new version is released that's it for the previous version, I don't think patches get released for old versions.

@RogerS

This all seems like speculation- can we just focus on what we actually know or what we'd like to see

Exactly the point of this post, it's all speculation, we know nothing & when VP22 comes out we have to trust that is going to be fine if we're going to put our hands in our pockets & hand over cash, having 0 feedback doesn't instil that trust.

The speculation I was referring to was regarding beta testing and development by someone who is apparently not a tester. I don't see the point of that discussion.

We'll all get a chance to test 22 for free whenever the demo is released.

@Gid You need to take into account that this forum is a "user to user" forum and whilst we are privileged in having Vegas team members occasionally respond we should not expect responses for every query from them.  I suspect that currently they are busy trying to meet Magix deadlines and simply don't have time to scan the forum.

If you want an official answer to your query you should use the official support channel. No doubt if you get an answer you will share it with us.

I would be surprised if the Vegas team does not have a last and final 21 patch before releasing 22.

I do not think they can afford to leave 315 with their default settings if users are recommended reinstalling build 208 or ticking legacy for some contend formats or issues

That would make the most sense, and beta testing VP22 now doesn't negate a VP21 Final (without the VP22 new selling features).

@EricLNZ Yep I understand this is a public forum. so seeing as this 'reverting to (208)' has been mentioned a fair few times in other posts I didn't see any harm in bringing up the matter in a separate thread to see what others thought about it, because as you say this is a forum, a place for discussion.

As far as 'scanning the forum' is concerned, I made the title as clear as possible so if they did get notified because I tagged them they wouldn't have to scan the forum for related posts they could just make a comment on this one,

I was hoping rather than expecting a reply to be honest but I shouldn't really have to, yes there have been occasional comments from Vegas team members who reply to other posts (not about this issue), posts where they haven't been tagged so I'm assuming there is a certain amount of reading of the forum done by them, surely they've noticed this 'reverting' being mentioned more than once. it's not exactly an isolated incident in one or two obscure little posts,..

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.

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?

@Todd-AO  I think I remember reading that, so disable a major part of the PC is the answer 😏 As I haven't got an integrated GPU that wouldn't be good for me.

@Todd-AO Sorry, calling my out like this ain't gonna work my friend. You have been toxic on this user forum from the day you joined..... Thanks for the penny, lol.

@Todd-AO This forum has a hierarchy & for whatever reason the upper tier is keeping shtum about this subject, or as above nothing useful to add just personal remarks, @Steve_Rhoden Surely your comment goes against community rules. ?

I can't imagine not using my GPU for video editing in 2024.

"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."

More speculation.