C:\Program Files\VEGAS\VEGAS Pro 21.0\FileIO Plug-Ins\mxcompoundplug
Does renaming this directory help? For example, "11111". Then restart Vegas.
Why would you recommend that? Just enable legacy AVC.
OK, I thought legacy AVC would use compoundplug instead of So4compoundplug. After testing, it does use So4.
Of course, happy to help. If all your media is like this clip then I think you are done.
If you use a variety of media there are benefits to the non-legacy AVC decoder so I'd consider converting it for editing.
If your camera has other settings like ALL-I, try recording a clip as that and see how it works with VEGAS and the new decoder.
Here's some background from Canon: https://www.canon.com.hk/cpx/en/technical/va_EOS_Movie_Compression_Options_All_I_and_IPB.html
Thank you @RogerS, my Cannon M50 Mark II does not have ALL-I setting.
@Rony-Alfandary: I have reproduced the problem and I will have the engineering team examine the problem. Thank you for providing the example file for us.
Similar like my 100p video with long gop, but this one hasn't long gop size.
Thank you @RogerS, after I followed your initial workaround solution, all seems well so I don't think I need to convert my media. Unless I am missing something. I wonder if I need to change anything else in my settings. Thank you for your time and kind response!
The issue should be solved - for the future - without using the legacy AVC encoder. Have forwarded it to the development team, and Derek has confirmed the issue.
The best way to come up with a solution also for the future.
Hello @Rony-Alfandary could you be so kind to re-enable the file on that google drive? I'd like to have a look, the footage is no unusual video material, the Nvidia driver should be able to decode this. We also have options to file a bug directly for Nvidia.
Hello @Rony-Alfandary could you be so kind to re-enable the file on that google drive? I'd like to have a look, the footage is no unusual video material, the Nvidia driver should be able to decode this. We also have options to file a bug directly for Nvidia.
https://drive.google.com/file/d/1ZKMD2DaLDqflRkHRkxJZhu8B2PTu2zHY/view?usp=sharing
just to clear - since posting that query the issue has been resolved. you can see it in the previous threads. I ue Cannon M50 MarkII
No issue with only Intel video adapter. Please state camera model.
It's an issue with MxCompound and NVDEC that we replicated earlier in this thread.