URGENT! HEVC 10-Bit 4:2:0 crashing VP18-373.2

AVsupport wrote on 11/2/2020, 8:04 PM

I noticed

Now filtering out unsupported 4:2:2 10 bit HEVC that are decoded with the Intel HEVC decoder files which may cause a crash or result in artifacts being displayed

in Update 2 changelog.

Trying to look at a 10-Bit HEVC 4:2:0 file from Sony A7Siii in the Vegas Explorer window immediately crashed the application.

Doesn't do this when legacy HEVC encoder is used. But this also means you just about can't play this back because of poor performance. Biggest problem being, if explorer looks as this folder, it will crash, no matter it you select the actual file, if it's the first one in the list. Also want to note that the proper Windows Explorer actually does see a thumbnail.

Windows media player plays the file no issues, full nVidia GPU support..

General

Complete name :F:\EditMedia\A7Siii_test\2-11-2020\AVS_20201102_0001.MP4

Format :XAVC

Codec ID :XAVC (XAVC/mp42/iso2/nras)

File size :1.19 GiB

Duration :1 min 5 s

Overall bit rate :156 Mb/s

Encoded date :UTC 2020-11-02 12:31:19

Tagged date :UTC 2020-11-02 12:31:19

 

Video

ID :1

Format :HEVC

Format/Info :High Efficiency Video Coding

Format profile :Main 10@L5.1@High

Codec ID :hvc1

Codec ID/Info :High Efficiency Video Coding

Duration :1 min 5 s

Bit rate :150 Mb/s

Width :3 840 pixels

Height :2 160 pixels

Display aspect ratio :16:9

Frame rate mode :Constant

Frame rate :50.000 FPS

Color space :YUV

Chroma subsampling :4:2:0

Bit depth :10 bits

Bits/(Pixel*Frame) :0.362

Stream size :1.14 GiB (96%)

Encoded date :UTC 2020-11-02 12:31:19

Tagged date :UTC 2020-11-02 12:31:19

Color range :Full

Codec configuration box :hvcC

Last changed by AVsupport

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Comments

AVsupport wrote on 11/5/2020, 5:21 AM

...anyone with good ideas?

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Howard-Vigorita wrote on 11/7/2020, 1:48 PM

Be happy to try the clip if you post it somewhere for download.

AVsupport wrote on 11/7/2020, 2:47 PM

I will be taken to celebrate my 50th over the next few days, but I shall do there after, thanks @Howard-Vigorita!

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

AVsupport wrote on 11/8/2020, 8:19 PM

Here's a download link to some test files from my A7Siii @Howard-Vigorita

https://avsupport.com.au/clients/public/

files are named accordingly to what they are.

 

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

BruceUSA wrote on 11/8/2020, 9:13 PM

AVsupport. I just test out your hevc 4K 100P. Imported into VP18 just fine. I play back the clip here and there at different points. I could not get VP to crash. The only down side is this, won't get smooth play back thru out. Start out at 100P then 62P then slow come to a craw. I guest I could create proxy but I did not bother.

Last changed by BruceUSA on 11/8/2020, 9:21 PM, changed a total of 2 times.

Intel i9 Core Ultra 285K Overclocked all P Cores @5.6, all E-Cores @5ghz               

MSI MEG Z890 ACE Gaming Wifi 7 10G Super Lan, thunderbolt 4                                

48GB DDR5 -8200mhz Overclocked @8800mhz                  

Crucial T705 nvme .M2 2TB Gen 5  OS. 4TB  gen 4 storage                    

RTX 5080 16GB  Overclocked 3.1ghz, Memory Bandwidth increased from 960 GB/s to 1152 GB/s                                                            

Custom built hard tube watercooling.                            

MSI PSU 1250W, Windows 11 Pro

 

AVsupport wrote on 11/8/2020, 9:36 PM

Hi @BruceUSA, the 100p clip AVS_20201108_0055_XAVC10Bit4K100p422.MP4 is not HEVC, it is actually XAVC-S. Apart from playback performance, that one shouldn't be an issue. Just thrown it in for good measure ;-) How did you go with the rest?

HEVC is the problem here.

Last changed by AVsupport on 11/8/2020, 9:38 PM, changed a total of 1 times.

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

lenard wrote on 11/8/2020, 9:48 PM

Have you upgraded to version 373?

It should not allow you to load the HEVC by default, and when you load with legacy avc it will load and play but at such a frame rate to be useless. You can force it to crash by loading video with Legacy avc, saving project, turning legacy avc decoding off, and restart vegas. It will then crash on startup

BruceUSA wrote on 11/8/2020, 9:49 PM

Hi @BruceUSA, the 100p clip AVS_20201108_0055_XAVC10Bit4K100p422.MP4 is not HEVC, it is actually XAVC-S. Apart from playback performance, that one shouldn't be an issue. Just thrown it in for good measure ;-) How did you go with the rest?

HEVC is the problem here.

You are right. I did not look closely. I was just happen to click on 1 clip and downloaded. As for what I remembered previously I had test the hevc file from A7S III do indeed caused VP to crash, just like the EOS R5.

Intel i9 Core Ultra 285K Overclocked all P Cores @5.6, all E-Cores @5ghz               

MSI MEG Z890 ACE Gaming Wifi 7 10G Super Lan, thunderbolt 4                                

48GB DDR5 -8200mhz Overclocked @8800mhz                  

Crucial T705 nvme .M2 2TB Gen 5  OS. 4TB  gen 4 storage                    

RTX 5080 16GB  Overclocked 3.1ghz, Memory Bandwidth increased from 960 GB/s to 1152 GB/s                                                            

Custom built hard tube watercooling.                            

MSI PSU 1250W, Windows 11 Pro

 

AVsupport wrote on 11/8/2020, 10:05 PM

Have you upgraded to version 373?

It should not allow you to load the HEVC by default

This is 373.2 latest update. latest nvidia Studio drivers. latest Win10.

I know it shouldn't load. And it doesn't with the HEVC 4:2:2. But the 4:2:0 crashes. And tha'ts the one I'd like to work with, but not with legacy codec . HEVC 4:2:0 should have nVidia and Intel iGPU hardware support. Windows Explorer sees it, and Windows Media player plays it. That's embarassing.

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Howard-Vigorita wrote on 11/9/2020, 12:12 AM

Just downloaded the 420 mp4 and the problem is the audio track. MP4 spec does not provide for a pcm audio track. Some vendors do it anyway and you might be able to get away with it in Vegas if you check off "Use Legacy HEVC" on the i/o page but I recommend you get legal. If the camera can be told not to record an audio track, that should fix it. Or if you can specify aac audio for the mp4. Or if you can specify mov format that should be fine with pcm. Other possibilities are using ffmpeg or whatever to convert either the clip container to mov or just the audio track within the mp4 to aac. eg...

convert mp4 clip to mov:

ffmpeg -i clip.mp4 -c:v copy -c:a copy clip.mov

or just convert the audio track:

ffmpeg -i clip.mp4 -c:v copy -c:a aac newclip.mp4

neither of these transcode the video stream so they run rather briskly.

lenard wrote on 11/9/2020, 12:17 AM

In my experience, the HEVC 4.2.0 still crashes, but not instantly. instead it behaves the way many videos do with so4 reader. May get red or black screens during playback and then vegas eventually crashes. Vegas is not compatible with the HEVC videos from this camera. Now if you convert the actual video file, instead of just the audio file that could be a different story

AVsupport wrote on 11/9/2020, 12:53 AM

Thanks @Howard-Vigorita this is a good step forward analysing the problem. I hope the dev team looks at this quickly! I know legacy codec will read the file, but it's not near good enough because the ultimate goal is hardware acceleration for HEVC where it can be done. Strange that using a different container format 'fixes' the issue. Would wish Magix would hurry up with the ingest/file tool that has been promised at the VP18 release. Where is it? Or fix so4compound, even better.

@lenard, I was chasing 10Bit/SLOG for a while, and now I can, it's so frustrating I can't. This is the way of the future, and it was coming, and we knew about it. Vegas is first and foremost a Video Editor, and it's primary function is to do just that. And traditionally, it has a strong Sony user base, so it needs to satisfy. I definitely don't want to convert (recode) the video file, if I need to re-pack, maybe, but this is a bulk action I currently can't do and wish for.

And yes, I can do Intra, but not 100p so this is part of the dilemma..

Thanks for chipping in guys, would be nice to hear the team acknowledge.. @VEGASHeman ?

 

Last changed by AVsupport on 11/9/2020, 3:08 PM, changed a total of 1 times.

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

VEGASHeman wrote on 11/11/2020, 4:02 PM

@AVsupport: I downloaded the files, and am able to reproduce the crash with the 4:2:0 HEVC. I will look into this further, and get back to you ASAP. And yes, we do not want VEGAS users to rely on transcoding or changing the default preferences for popular file formats - they should work properly, straight out of the box.

Howard-Vigorita wrote on 11/11/2020, 5:12 PM

I understand Premier accepts mp4 files with pcm audio streams without a problem. Whether it benefits from gpu decoding acceleration depends on what the gpu's support. I'm guessing that Vegas crashes on these because it blindly submits them to the gpu causing it to barf. I tried the file with amd, nvidia, and intel decoding and got the same reaction from all 3.

AVsupport wrote on 11/11/2020, 6:02 PM

Means a lot @VEGASHeman having this acknowledged, I'm still backwards forwards with official support wanting screenshots..;

This is the first of probably many more Sony ILCE's now offering HEVC 10-Bit, and whilst their own support via Catalyst Browse is still lacking, this is a great opportunity to the Magix team to be of the forefront. For me using this codec during aquisition is quite vital as HEVC 4K is the only variant that can record with moderate file sizes at 100fps SLOG. Down the track I could only hope that Magix will be able to use the Sony Gyro data to stabilize those clips in post (like Catalyst Browse does), but this is wishlist for later. For now, I just need to be able to load the file, and can accept if there is not-yet 4:2:0 hardware support, even though there should, allowing me to use a proxy workflow for the time being.

Thanks for your checks @Howard-Vigorita very helpful. I'm wondering if Sony latest 4-channel audio support could be part of the issue. If it's the audio format that causes the crash

Audio

ID :2

Format :PCM

Format settings :Big / Signed

Codec ID :twos

Duration :24 s 0 ms

Bit rate mode :Constant

Bit rate :1 536 kb/s

Channel(s) :2 channels

Sampling rate :48.0 kHz

Bit depth :16 bits

Stream size :4.39 MiB (1%)

Encoded date :UTC 2020-11-07 22:10:22

Tagged date :UTC 2020-11-07 22:10:22

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

lenard wrote on 11/11/2020, 7:00 PM

I"ll upload this comparison between the big 3 editors playing this file, with a hope that I can revise in near future showing Vegas to perform just as well as the others

AVsupport wrote on 11/11/2020, 7:06 PM

would be nice to see evidence of GPU utilization if indeed happening @lenard ;-)

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

lenard wrote on 11/11/2020, 7:23 PM

What I found interesting in that comparison is that Premiere Pro has the superior playback in relation to resources used. Resolve needs to use more than twice the GPU as Premiere, and yet does not have lower cpu use. Premiere has improved greatly