@iEmby I doubt it. It's only for VP21 and it's a patch for it unless it's purchased now Certainly VP15 is out of the question since there is no HUB for it to begin with.

@David-Marcou and @Wolfgang S. playback from the start, if left alone plays back fine. Jump around to different parts of the clip, stutter and out of sync issues. But again, if left alone to play back, no problems. But certainly issues moving around the clip. Easy to reproduce.

@Reyfox

That is what I see here, too. But editing means, that you have to jump around. We have no video-player, we have a NLE.

VEGAS Hub features for perpetual users 

VEGAS Hub features are no longer exclusive to subscription customers. Perpetual users can now enjoy the benefits of Text to Speech and Speech to Text, VEGAS Content downloads, Media Share, and so on. 

I have VEGAS 15 & VEGAS 20 perpetual license.
so is there any chance that i can get VEGAS Hub Feature now too??

Sure. Purchase an upgrade to Vegas Pro 21. ;)

Previewing in Vegas explorer I hear and see no sync problem, what I do see if playing from the timeline

I changed the main recording format on my Canon XF605 to "MP4(HEVC) YCC420 10-bit", instead of "XF-AVC YCC422 10-bit", and the preview video stutter, pixelization, and audio sync issues are no longer there. Setting "MP4 (H.264) YCC420 8-bit" also works fine.

I NEED URGENT HELP!

After Build 300 my files are opening and being rendered like this. What do I do VEGAS?

I am having same issue ..also pixellig when i scrub timeline

New update still causing trouble with MXF files, taking too long to open projects and becoming unresponsive

Here is a what Media Info reports on troublesome files

And here are PC Specs

Graphics is an AMD Radeon RX 6600

@VEGASDerek What direction do you give the beta testing team, the 2 extremes are 'use Vegas as you normally would with your normal media report problems', all the way to 'do everything you can to break Vegas with every format possible' and have a library of formats to help the process.

If you released Vegas without knowing about these mxf problems then something is very wrong with the beta testing program.

@jamie-oxenham Of course, you cana download all versions here: https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/

You can also check "enable legacy AVC" in preferences file io which is what build 208 used.

What media are you specifically having issues with? Would be great if we can replicate it as we just did with Canon files.
https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

These are canon c70 4k uhd mxf files. Which I believe are xfavc?

@jamie-oxenham Thanks so much Jamie. Could you make an example available for download via Google Drive or Dropbox or another service? Happy to check it out.

What is your GPU model? Is it AMD?

Processor    AMD Ryzen 7 4800H with Radeon Graphics            2.90 GHz
Installed RAM    16.0 GB (15.4 GB usable)
System type    64-bit operating system, x64-based processor
Nvidia GeForce GTX 1660 Ti

I did roll back to the previous version, and aside from cineform, or prores converts from cineform it seems to at least be behaving as it did. It seems that prores, and cineform, start to break the software when I get too many in the timeline. I have a music video that had about 25 cineform/ prores files in it, and the more I added, the worse Vegas performed. To the point we had to abandon any further edits, as I could no longer open the project, or any previous saved versions. And re-editing it from scratch was not an option any longer. The mxf files from the c70 seem to work as expected in this version, vs build 300, where I experienced all the MXF problems everyone else has mentioned here. I did try all the tips that people have suggested, but they didn't really make any difference in build 300 on my machine.

Thanks to everyone for not only helping me, but helping everyone else on here as well!

Cineform and other media that rely on the 32 bit QuickTime plugin have always had memory limitations. Stick to ProRes and you'll be fine

 

I did roll back to the previous version, and aside from cineform, or prores converts from cineform it seems to at least be behaving as it did. It seems that prores, and cineform, start to break the software when I get too many in the timeline. I have a music video that had about 25 cineform/ prores files in it, and the more I added, the worse Vegas performed.

@jamie-oxenham Cineform never worked well on Vegas, but you're saying it works even worse in b300?

Have you tried a prores project without the cineform , are you also seeing a reduction in performance with a lot of prores too?

I NEED URGENT HELP!

After Build 300 my files are opening and being rendered like this. What do I do VEGAS?

I am having same issue ..also pixellig when i scrub timeline

I haven't solved it yet, I had to go back to VEGAS 20 because I couldn't go back to the previous 21 either.

@VEGASDerek What direction do you give the beta testing team, the 2 extremes are 'use Vegas as you normally would with your normal media report problems', all the way to 'do everything you can to break Vegas with every format possible' and have a library of formats to help the process.

If you released Vegas without knowing about these mxf problems then something is very wrong with the beta testing program.

I'm not a Vegas beta tester but have been with other software. I suggest that your question should be "how did the beta testers miss the problem?". From posts it's apparent not all users are having the problem with mxf files. So it appears unique to some systems, and presumably none of the testers had on their systems whatever causes the problem. Maybe it's another GPU driver issue?

I suggest that Vegas be publicly tested before it is officially released, just like Resolve.

Because obviously, the existing Vegas/Magix employees and Beta testers can't find all the potential problems, when the new functions replace the old ones.

There have been many such examples before, such as when the so4 replaced legacy compoundplug, and when the new VP18 FX window replaced VP17's.

Only by conducting extensive public tests and receiving feedback can potential problems be found and solved completely.

Of course, this is just personal opinions.

This type of checking is a QA function not a beta testing one in my opinion.

I also agree with a soft public launch for new builds to get feedback from users who consent to testing software before it is pushed out broadly.

The odd thing is some of these graphical corruption issues are with formats that aren't GPU decodable (10-bit 422 AVC MXF) so it really shouldn't be a GPU-specific issue either.

 

I did roll back to the previous version, and aside from cineform, or prores converts from cineform it seems to at least be behaving as it did. It seems that prores, and cineform, start to break the software when I get too many in the timeline. I have a music video that had about 25 cineform/ prores files in it, and the more I added, the worse Vegas performed.

@jamie-oxenham Cineform never worked well on Vegas, but you're saying it works even worse in b300?

Have you tried a prores project without the cineform , are you also seeing a reduction in performance with a lot of prores too?

Yes i do get the same problem with prores. But, that prores was converted from cineform, so dont know if thats the issue? I use cineform as thats what Hitfilm outputs with 422 yuv 10bit. So id like to keep everything in that environment.

From posts it's apparent not all users are having the problem with mxf files. So it appears unique to some systems, and presumably none of the testers had on their systems whatever causes the problem. Maybe it's another GPU driver issue?

@EricLNZ One of the problem forms of mxf is 4:2:2 AVC , both intra and closed GOP versions, no hardware 'chip' can decode that but there would be GPU interaction. I turned my GPU off and problem was possibly less but still very obvious at edits.

When you say not everyone is having the problem, it's already been seen that people aren't testing correctly and reporting no problem with mxf because they're simply putting the file on the timeline pressing play and that's it, but Vegas is an editor not a video player so should be editing those clips, and in this case every person most likely will report the fault.

This could be a good learning exercise of not what to do.

Have you tried a prores project without the cineform , are you also seeing a reduction in performance with a lot of prores too?

Yes i do get the same problem with prores. But, that prores was converted from cineform, so dont know if thats the issue? I use cineform as thats what Hitfilm outputs with 422 yuv 10bit. So id like to keep everything in that environment.

For the ProRes can you make it outside of VEGAS, say by using ShutterEncoder? I don't trust VEGAS to decode and render Cineform well. Is that the only output Hitfilm can do with such qualty? There's no MagicYUV (paid plugin) or ProRes option I take it?

Small bit of good news on a bad news day, VP21b300 is almost a real 32bit FPU color 8K editor and performance of AV1 is not that far behind HEVC. The decoder performance is unlike anything seen before from Vegas, HEVC decoder use is close to 100% with the scene detect test.

(playback 8K 32bit, footage is 10bit)

The problem for me is as before blending tracks causes a dramatic slow down.

But why should someone grade av1?

Even if I appreciate that you find something positiv!

SOLVED - Under preferences -> File I/O - My hardware decoder needed reselected. We're good now!

@Hamilton53!

Yes, in previously releases and Builds I’ve “stumbled” on that one too. Annoying.

I also see good HEVC and AV1 GPU decode performance. I just wouldn't render to AV1 at present (no GPU encoding I believe and artifacts).