Looking forward for the details!

You should focus on bug fixes in V21 b315. I went back to version Vp 21 b208 and I have peace of mind. I will definitely not buy a new version if it has the same errors as in the b315.

There's always a demo you can test to be sure.

@pierre-k What are the issues you are dealing with in b315?

@pierre-k I am also interested in hearing your issues in 315 in contrast to 208. In my experience, I have had significantly less issues in 315

You should focus on bug fixes in V21 b315. I went back to version Vp 21 b208 and I have peace of mind. I will definitely not buy a new version if it has the same errors as in the b315.

@pierre-k Make the truck play properly, if you can't do that much of the bugs you see probably aren' even real in VP21b315, it's as if you have bits old older Vegas's mixed in with b315. It seems hard to believe a mainstream system like yours with an Intel 13700K decoding with it's IGPU see's the truck problem with VP21b315 and to this date not a single other person on earth does.

Your results are unreliable, you could try completely cleaning Vegas's registry and all related files on your hard drive. When the truck video plays properly then you will know any reports of bugs in VP21315 are credible. If you've fixed the issue already let us Team Vegas Helpers know.

*Realized I said decoding with IGPU, but truck video isn't using GPU decoder, but you've also turned off GPU processing completely and still see the problem. So you have a very unremarkable system except you have an old Nvidia GPU, but that's already been ruled out as the problem.

If users have VP21b315 (NOT b314) try out the truck video(If you haven't already) do you get the @pierre-k terrible playback including this image

https://we.tl/t-qIXs6hsDCp

Sure, I can break decoding on this clip though it takes a bit of work. Playing it repeatedly, stepping back frame by frame, creating a fadeout, etc. This is with my GTX 1050 (4GB) GPU with GPU acceleration of video processing set to this GPU.

Edit: try to make the screenshots easier to see the timeline. (I could get the errors to appear more readily by holding the back arrow)

I've had issues with a variety of AVC in MXF files.

Performance is okay- about 18fps.

Anyway this is straying from the VP 22 teaser.

@RogerS You're right! So what we didn't see was Pierre playing back and forth maybe, before he played it for the screen cap. holding on the cursor scrubbing back and forth triggers it.

So that's confirmed, let the VP22 anticipation people get back to it

Are you asking me what bugs are in the b315? This.........

- MFX open as multichanel

https://www.vegascreativesoftware.info/us/forum/vp21-b300-and-big-problem-with-mxf--145196/?page=2#ca919677

https://www.vegascreativesoftware.info/us/forum/vp-21-b315-mxf-events-always-stop-at-the-end-when-editing--146216/

https://www.vegascreativesoftware.info/us/forum/vegas-pro-21-build-314-and-315-general-thread--145728/?page=7#ca919795

https://www.vegascreativesoftware.info/us/forum/vegas-pro-21-build-314-and-315-general-thread--145728/#ca914200

I think they are serious bugs and some historically annoying ones - since VP12. It's definitely not a problem with my system. I don't use GTX970 in Vegas. I have everything set to UHD770 in Vegas. Until the bugs mentioned here are fixed, I will not be interested in the next versions of Vegas.

Recommendations to other users:

Please read the whole thread properly before you start giving me advice. You give advice without knowing the context and keep asking me the same questions over and over. I'm tired of it even if you mean well. Unfortunately, it seems like you're making fun of me and not taking me seriously.

@pierre-k What works best is to tick "Enable legacy AVC decoding" in the File I/O tab. I see right pixel-decoding on the truck-clip, but it is stuttering during playback. The legacy decoder works best with Sony XAVC content.

 

Please read the whole thread properly before you start giving me advice. You give advice without knowing the context and keep asking me the same questions over and over. I'm tired of it even if you mean well. Unfortunately, it seems like you're making fun of me and not taking me seriously.

@pierre-k You weren't making sense, I thought you were stuck in a K-Hole. Said the truck video was fixed in 314, but broke again in 315, but for me 314 showed your problem just as your described, but no problem in 315, nobody else saw the truck problem in 315, not in the public forum anyway, and the people in the exclusive invite only club aren't allowed to tell us they know a problem exists, one such beta tester got his message deleted, CRAZY!

The formidable Vegas Helper RogerS did what you could not, described how to create the truck fault in b315, instead of being annoyed learn from this, better communicate 😀💯

How about that VP22, it's gonna be amazing!

@Todd-AO wrote

the people in the exclusive invite only club aren't allowed to tell us they know a problem exists, one such beta tester got his message deleted, CRAZY!

Please note that discussions about beta builds are privileged information until otherwise advised by devs or marketing. Discussions about VP 21 or earlier releases are not under NDA. The "deleted" message was moved to the appropriate forum, not hidden or deleted. "CRAZY"? I don't think so.

@vkmast

but you must be able to appreciate the annoyance of us in the public forum discovering bugs that the guys in the private forum already know about, but nobody acknowledges it, doesn't show any interest in the bug. And you have people like Pierre getting very upset because nobody is taking notice of the bugs he's found. He doesn't know if he's not being taken seriously or you guys already know about it so you're bored by him.

This working in parallel with one team not knowing about the research and results of the other team is problematic and inefficient . I understand that's different when the beta testers are working on a non released beta, but when they aren't information should be shared between the 2 teams by them joining in threads on the public board.

Also a Mod with appropriate security clearance could allow us on the public board to know a specific bug has been verified and a fix is in the works.

@Todd-AO

I do not understand what you are talking about. What is the "private forum", what is the "public forum"?

And your interpretation, that nobody is interesting in the bug, is simply wrong. More, it is a lie. In THIS DISCUSSION HERE a lot of users have tested the reported bugs - and some of them are beta testers. And you do not know, what kind of activities were started in the background, to identify bugs. But nobody is perfect.

Your cynicism is biting and unbearable. While users like @pierre-k deserve help and respect, it is not acceptable that you uses here a wording that Pierres findings are unreliable, or give advices that seems to be not seriously. Or a wording like "Team Vegas Helpers".

This is the last warning.

Re VP 22, no "appropriate security clearance" in effect yet, but please see the first comment in this thread.

I have revisited the MXF-discussion thread, and reviewed Pierres tests. While it is correct that the Vegas preview on an external monitor is not perfect - I see also some questionmarks in the test settings.

The monitor should be a native UHD 50p monitor - so 60 Hz - to preview UHD 25p footage and not with 1280x1045 60Hz, in an ideal world one bypasses the graphic card and uses cards like the Blackmagic Decklink 4K or Ultrastudio 4K, even if these drivers have not been updated for a long time. But even then the preview will not be perfect - and for 25p footage one should stick to the shutter speed of 1/50s too. Unclear, what it was here.

Where he is right is that mxf footage is imported in Vegas Pro 21 b315 with 5 audio streams - regardless what is set in options/preferences/file i/o. This is a known bug in VP21 b 315.

but you must be able to appreciate the annoyance of us in the public forum discovering bugs that the guys in the private forum already know about, but nobody acknowledges it, doesn't show any interest in the bug. And you have people like Pierre getting very upset because nobody is taking notice of the bugs he's found. He doesn't know if he's not being taken seriously or you guys already know about it so you're bored by him.

This working in parallel with one team not knowing about the research and results of the other team is problematic and inefficient . I understand that's different when the beta testers are working on a non released beta, but when they aren't information should be shared between the 2 teams by them joining in threads on the public board.

Also a Mod with appropriate security clearance could allow us on the public board to know a specific bug has been verified and a fix is in the works.

The only people who can comment that a bug has been verified and a fix is in the works are VEGAS staff and they seem to be busy with the upcoming release of VP 22 as I've seen them less active here as of late.

Whether any individual beta tester finds a problem report in the forum relevant or interesting enough to test themselves must be their own personal decision as they too are just volunteers/users.

Personally I'm happy enough that when we replicate issues with VEGAS in threads here it makes it somewhere and ultimately gets fixed and the changelog is evidence of that. Otherwise I wouldn't bother personally.

More transparency from Magix/VEGAS would be meaningful (for a time there was someone, maybe in a QA role noted issues raised here as logged) but perhaps there are staff constraints that prevented this from continuing.

Feature list has been posted.

Feature list has been posted.

@VEGASDerek Do you already have the doc for us to view?

I read the list. It seems that what we are dealing with here will be fixed in Vp22.

I am glad that I will finally see the function that I proposed to you five years ago "selecting events with the right mouse button".

I'm sorry that you don't fix all the errors with mxf and the slow import of events that remained in Vp21 b315 and either I have to stay with b208 or buy Vp22. It is not fair.

@VEGASDerek

do you have a selection of events with the left mouse button in the news?? I left-click on an empty space in the timeline when I want to move the playback head. I hope it won't be a problem and I won't be constantly shown a frame when clicking. Why is it not the right mouse button?