Flashing Black frames

Comments

Phil_P wrote on 11/30/2021, 3:41 AM

Thanks Roger,

Everything was checked carefully as usual. And I was aware that it was interlaced.

I was not getting the issue on Render - It was while simply playing. (It did happen on Render too).

On top of this, I was wondering why would a Voukoder render preset that has been used hundreds of times make this issue.

Vegas does not playback Interlaced video? If so that is new to me.

After searching around I also find that some folks with Magic YUV have this issue. (I have that installed). Not sure if that is connected.

Anyway not to worry. I only posted as it seemed that the issue was similar to the OP.

No biggie and thanks for your smart reply. Very helpful. :-)

EricLNZ wrote on 11/30/2021, 3:50 AM

Vegas does not playback Interlaced video? If so that is new to me.

Presumably you are referring to playing on your timeline. How it plays back will depend on your project settings but yes it should play.

 

RogerS wrote on 11/30/2021, 3:52 AM

I don't really understand your issue- feel free to create your own thread where you can fully explain it. You shared one file that didn't work well that was interlaced and then converted it to progressive after the fact? That's the part I don't get.

Yes Vegas supports interlaced files. Voukoder just follows project properties. For errors with Voukoder renders in my limited experience (as it usually works well), it may be something with the decoding of the source file, the computer overheating while rendering and the decoder getting out of sync as it throttles. I usually use it in x264 mode, not with hardware encoders.

MagicYUV works fine as well (I also have that installed) and don't see evidence it hinders any other codecs.

RogerS wrote on 11/30/2021, 4:04 AM

I see, the Voukoder interlaced render is completely corrupted when brought back into Vegas though it plays fine with a general media player. Interesting. That's not what I was thinking (or had seen before) with gaps or flashing black frames, or entirely missing footage. This is a special case for some reason. I don't think it's interlacing but rather something with the encoding settings. This is very different from the earlier cases we were looking at here.

The file is decoding with so4compound and that's using my Intel HD 630 iGPU on this system. With legacy AVC enabled it hardly plays back at all and is mostly black:

Last changed by RogerS on 11/30/2021, 4:09 AM, changed a total of 1 times.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD and 2TB Samsung 980 Pro cache drive, Windows 11 Pro 64 bit https://pcpartpicker.com/b/rZ9NnQ

ASUS Zenbook Pro 14 Intel i9-13900H with Intel graphics iGPU with latest ASUS driver, NVIDIA 4060 (8GB) with latest studio driver, 48GB system ram, Windows 11 Home, 1TB Samsung SSD.

VEGAS Pro 21.208
VEGAS Pro 22.250

Try the
VEGAS 4K "sample project" benchmark (works with VP 16+): https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark (works with VP 20+): https://forms.gle/eErJTR87K2bbJc4Q7

Phil_P wrote on 11/30/2021, 4:09 AM

Eric thank you. Project settings are as they always have been. I have not seen this issue before. Although I did try changing the field order to no avail. And also using the match media function.

Roger thank you. As explained I converted afterwards (as I had a feeling that Interlacing may be causing an issue). The Voukoder / YUV was just thoughts. I added to this thread as I thought it may be a similar issue. (the symptoms are identical).

The video was originally shot on GoPro9 then rendered as mentioned using the same template I have used for a couple of years.

Anyway, no need for further replies.

The two videos are linked above if anyone is really interested to see if the first one will play (no matter what are the project settings). And also you will no doubt find that the video plays fine in any other standard media player.

My best, P.

RogerS wrote on 11/30/2021, 6:18 AM

Is this issue repeatable from the same source footage through Voukoder? Does it happen with just a straight MagixAVC/Mainconcept render? Unlike black frames, this is unusual.

Anyway if it happens again do make a thread and hopefully we can get to the bottom of it. GoPros are popular cameras, though I'm not sure if many people use them on interlaced timelines. If it's HEVC you could try both the non-legacy and legacy decoders and see if that makes a difference (file i/o tab under preferences).

Brent-Grosvenor wrote on 1/31/2022, 3:22 PM

Hi. This problem began with Vegas 18 with ANY Canon files. Same issues with 6D and my new 5R. This issue still does not exist with Vegas 17 and I (LIKE YOU) AM FRUSTRATED. Now it's almost Feb of 2022 and MAGIX has not found a solution that is actually over a year old. I'm pulling my hair out. Has anyone solved this? I have 10 core, 128 gigs of Ram, Windows 10.... No issues with any other type of file, 4K.... nothing. Please post if this has been solved for you. Thank you.

Brent-Grosvenor wrote on 1/31/2022, 3:33 PM

It does appear that if I set "Hardware Decoder" to OFF.... this Canon problem is SOLVED. But I'd sure rather use my NVIDIA card to decode. Does anyone have more input on this?? Thanks.

RogerS wrote on 1/31/2022, 7:18 PM

Hi. This problem began with Vegas 18 with ANY Canon files. Same issues with 6D and my new 5R. This issue still does not exist with Vegas 17 and I (LIKE YOU) AM FRUSTRATED. Now it's almost Feb of 2022 and MAGIX has not found a solution that is actually over a year old. I'm pulling my hair out. Has anyone solved this? I have 10 core, 128 gigs of Ram, Windows 10.... No issues with any other type of file, 4K.... nothing. Please post if this has been solved for you. Thank you.

Please start a new thread and share your system info and your MediaInfo.

If you have an Intel CPU use the more compatible Intel decoder.