with their recent official Resolve 17.1 release.
When is VP catching up with the rest of the world?
BMD adds HEVC 422 hardware decoding for Intel (+482 update)
Back to post
Comments
Howard-Vigorita
wrote on 3/14/2021, 7:58 AM
Isn't Rocket Lake about to be released?
@RogerS Looks like it might be imminent. Intel 11900 and 11700 cpus are announced with an end of Feb release date and I was just reading about the coming release of the Asus Maximus XIII motherboard with it's z590 pci4 chipset and onboard hdmi. That looks like a combo that should have Intel Iris/XE 422 decoding capability. But I think we'll have to wait till someone here gets their hands on one for a report on how well Vegas' supports it. Support could certainly make Vegas very competive platform for ProRes422 and all the cameras like Canons that shoot Hevc 422. Btw, I wouldn't infer Resolve's claim as support for either of these till it's demonstrated by someone.
AVsupport
wrote on 3/14/2021, 6:28 PM
@lenard, what software would you use to convert HEVC 422 to 444? I just would like to see what the resulting files look and 'feel' like in VP and elsewhere.
Also, why not playing with the thought of using HEVC Intra as a viable alternative to Prores etc? XAVCS-I edits like butter so perhaps this could be a way forward, in dealing with HEVC422 source?
lenard
wrote on 3/14/2021, 11:58 PM
4:4:4 10 BIT HEVC NVENC encode support doesn't look to be very popular. Resolve does it, but my normal transcoder caller Shutter Encoder doesn't (it's gui is not the most intuitive but couldn't find a setting). I would guess ffmpeg command line can but I stick to GUI's. My old pascal card can encode it but doesn't decode, Turing+ cards encode B frames which I think is the reason for it's higher quality, and will decode
Marco.
wrote on 3/15/2021, 2:39 AM
For the new Intel generation VP18 current build 482 supports HEVC 422 hardware decoding.
RogerS
wrote on 3/15/2021, 6:38 AM
For the new Intel generation VP18 current build 482 supports HEVC 422 hardware decoding.
Thanks Marco! Fantastic news. Does anyone have such a system to test it with? Curious to hear how it works in practice.
Marco.
wrote on 3/15/2021, 6:40 AM
"Does anyone have such a system to test it with?"
Soon, I'll hopefully be able to test in a few days.
lenard
wrote on 3/15/2021, 6:53 AM
Well there you go @AVsupport with the purchase of an i7 11700K in a couple of weeks your Sony A7S III Vegas Pro editing problems may be solved
JN-
wrote on 3/15/2021, 7:12 AM
"Does anyone have such a system to test it with?"
Soon, I'll hopefully be able to test in a few days.
Looking into my crystal ball, I think I see a new set of Benchmarking project results!
lenard
wrote on 3/15/2021, 9:38 AM
Marco.
wrote on 3/15/2021, 9:43 AM
With which GPU used?
lenard
wrote on 3/15/2021, 9:45 AM
Nvidia GPU, 10/16/20/30 series
RogerS
wrote on 3/15/2021, 9:58 AM
Great news thanks for sharing, but hopefully I could save some $$grand upgrading board, cpu and the rest with HEVC 420 NVDEC support??
Not sure if you had already tested the new update when you said that, but unfortunately the HEVC 420 10bit footage from your camera still doesn't GPU decode
I think he was joking that he could bribe the Magix engineers to implement it. Nobody said NVIDIA decoding was added to this build.
Marco.
wrote on 3/15/2021, 10:16 AM
"Not sure if you had already tested the new update when you said that, but unfortunately the HEVC 420 10bit footage from your camera still doesn't GPU decode"
Not sure which particular footage you mean but in general VP18 b.482 does use GPU decode for HEVC 4:2:0 10 bit footage on my low end low powered Intel notebook.
lenard
wrote on 3/15/2021, 10:21 AM
I used A7S III HEVC 420 10 bit footage. I think there's a link to avsupport's sample video earlier on (if not he's linked it in a similar thread)
Marco.
wrote on 3/15/2021, 10:39 AM
The 4:2:0 A7S footage linked in the other thread use GPU at between 30 % and 75 % here, whereas other HEVC 4:2:0 10 bit video (don't know the source) I tested use GPU between 70 % and 90 %.
Howard-Vigorita
wrote on 3/15/2021, 3:43 PM
For the new Intel generation VP18 current build 482 supports HEVC 422 hardware decoding.
@Marco. Just happened to be trying some 10-bit hevc-lossless mov clips and the hevc 422 one was not recognized by Vegas v482 and could not be dropped onto a timeline. Same behavior on my Dell Laptop and Intel Nuc.
Hevc 422 Media Info:
General Complete name : C:\videos\17 zcamE2 hevc-lossless 422 zLog2.MOV Format : MPEG-4 Format profile : QuickTime Codec ID : qt 0000.02 (qt ) File size : 2.32 GiB Duration : 30 s 806 ms Overall bit rate : 648 Mb/s Encoded date : UTC 2021-03-11 16:54:43 Tagged date : UTC 2021-03-11 16:54:43 CameraMaker : Z CAM CameraModel : E2 creation_time : 2021-03-11T16:54:43.000000Z com.zcam.camera.prepend : v0 com.zcam.camera.sn : 441A0070293 com.zcam.camera.fw : 0.98.0 com.zcam.camera.movieType : MOVIE com.zcam.camera.lut : Z-Log2 com.zcam.camera.iso : 2500 com.zcam.camera.shutterSpeed : Auto com.zcam.camera.aperture : F7.1 com.zcam.camera.ev : 0.0 com.zcam.camera.hash : 379a com.zcam.camera.splitIndex : 0 com.zcam.camera.lensType : .64x EF24-105/4L IS USM com.zcam.camera.lensFocalLength : 67mm com.zcam.camera.focusDistance : 103330mm com.zcam.camera.whiteBalanceMode : Auto com.zcam.camera.whiteBalanceKelvin : 5900K com.zcam.camera.whiteBalanceTint : 7 com.zcam.camera.projectFps : 29.97 com.zcam.camera.captureVfr : Off com.apple.proapps.clipID : A001C0035_20210311115443_0001 com.apple.proapps.cameraName : A com.apple.proapps.reel : 001 com.apple.proapps.shootingRate : 29.97 com.zcam.camera.battery : 7.4V com.zcam.camera.noiseReduction : Off com.zcam.camera.sharpness : Medium encoder : Lavf57.72.101 Video ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Format Range@L6.2@High Codec ID : hvc1 Codec ID/Info : High Efficiency Video Coding Duration : 30 s 731 ms Bit rate : 650 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 29.970 (29970/1000) FPS Color space : YUV Chroma subsampling : 4:2:2 Bit depth : 10 bits Bits/(Pixel*Frame) : 2.613 Stream size : 2.32 GiB (100%) Language : English Encoded date : UTC 2021-03-11 16:54:43 Tagged date : UTC 2021-03-11 16:54:43 Color range : Limited Color primaries : BT.709 Transfer characteristics : BT.709 Matrix coefficients : BT.709 Codec configuration box : hvcC Audio ID : 2 Format : AAC LC Format/Info : Advanced Audio Codec Low Complexity Codec ID : mp4a-40-2 Duration : 30 s 806 ms Bit rate mode : Constant Bit rate : 125 kb/s Channel(s) : 2 channels Channel layout : L R Sampling rate : 48.0 kHz Frame rate : 46.875 FPS (1024 SPF) Compression mode : Lossy Stream size : 472 KiB (0%) Language : English Default : Yes Alternate group : 1 Encoded date : UTC 2021-03-11 16:54:43 Tagged date : UTC 2021-03-11 16:54:43 Other ID : 3 Type : Time code Format : QuickTime TC Duration : 30 s 731 ms Frame rate : 29.970 (29970/1000) FPS Time code of first frame : 11:54:42:00 Time code, striped : Yes Language : English Default : No Encoded date : UTC 2021-03-11 16:54:43 Tagged date : UTC 2021-03-11 16:54:43
The Hevc 420 clip, otherwise identical, loads and plays just fine:
General Complete name : C:\videos\17 zcamE2 hevc-lossless 420 zLog2.MOV Format : MPEG-4 Format profile : QuickTime Codec ID : qt 0000.02 (qt ) File size : 2.24 GiB Duration : 30 s 806 ms Overall bit rate : 626 Mb/s Encoded date : UTC 2021-03-11 16:54:43 Tagged date : UTC 2021-03-11 16:54:43 CameraMaker : Z CAM CameraModel : E2 creation_time : 2021-03-11T16:54:43.000000Z com.zcam.camera.prepend : v0 com.zcam.camera.sn : 441A0070293 com.zcam.camera.fw : 0.98.0 com.zcam.camera.movieType : MOVIE com.zcam.camera.lut : Z-Log2 com.zcam.camera.iso : 2500 com.zcam.camera.shutterSpeed : Auto com.zcam.camera.aperture : F7.1 com.zcam.camera.ev : 0.0 com.zcam.camera.hash : 379a com.zcam.camera.splitIndex : 0 com.zcam.camera.lensType : .64x EF24-105/4L IS USM com.zcam.camera.lensFocalLength : 67mm com.zcam.camera.focusDistance : 103330mm com.zcam.camera.whiteBalanceMode : Auto com.zcam.camera.whiteBalanceKelvin : 5900K com.zcam.camera.whiteBalanceTint : 7 com.zcam.camera.projectFps : 29.97 com.zcam.camera.captureVfr : Off com.apple.proapps.clipID : A001C0035_20210311115443_0001 com.apple.proapps.cameraName : A com.apple.proapps.reel : 001 com.apple.proapps.shootingRate : 29.97 com.zcam.camera.battery : 7.4V com.zcam.camera.noiseReduction : Off com.zcam.camera.sharpness : Medium encoder : Lavf57.72.101 Video ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main 10@L6.2@High Codec ID : hvc1 Codec ID/Info : High Efficiency Video Coding Duration : 30 s 731 ms Bit rate : 627 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 29.970 (29970/1000) FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 10 bits Bits/(Pixel*Frame) : 2.523 Stream size : 2.24 GiB (100%) Language : English Encoded date : UTC 2021-03-11 16:54:43 Tagged date : UTC 2021-03-11 16:54:43 Color range : Limited Color primaries : BT.709 Transfer characteristics : BT.709 Matrix coefficients : BT.709 Codec configuration box : hvcC Audio ID : 2 Format : AAC LC Format/Info : Advanced Audio Codec Low Complexity Codec ID : mp4a-40-2 Duration : 30 s 806 ms Bit rate mode : Constant Bit rate : 125 kb/s Channel(s) : 2 channels Channel layout : L R Sampling rate : 48.0 kHz Frame rate : 46.875 FPS (1024 SPF) Compression mode : Lossy Stream size : 472 KiB (0%) Language : English Default : Yes Alternate group : 1 Encoded date : UTC 2021-03-11 16:54:43 Tagged date : UTC 2021-03-11 16:54:43 Other ID : 3 Type : Time code Format : QuickTime TC Duration : 30 s 731 ms Frame rate : 29.970 (29970/1000) FPS Time code of first frame : 11:54:42:00 Time code, striped : Yes Language : English Default : No Encoded date : UTC 2021-03-11 16:54:43 Tagged date : UTC 2021-03-11 16:54:43
AVsupport
wrote on 3/15/2021, 4:00 PM
@Howard-Vigorita, thanks for confirming the identical issues I am having with my A7S3 with your Z-cam files. 422 doesn't import. @Marco. With your 420, do you indeed see nvidia activity on playback or iGPU? [where does one get b482?]
add:
Fyi, Intel Iris Xe Graphics 32 (Rocket Lake S): 1,380 GFLOPS vs my 'old' nVidia 1060/6 @3855 GFLOPS. Don't expect this to be the miracle cure either.
Please do yourself a favour and compare that to the upcoming nVidia Ampere A100 chipset happily doing 19.5 TFLOP (yea, tera-flops)
suggesting the ability to decode 157 HEVC 1080/30 clips, 32bit float...
set
wrote on 3/15/2021, 4:26 PM
try uncheck for 'enable legacy HEVC decoding' ?
Marco.
wrote on 3/15/2021, 4:50 PM
@AVsupport
"With your 420, do you indeed see nvidia activity on playback or iGPU?"
Not sure why you think I have an Nvidia equiped notebook. Currentlly it's a low end Intel notebook with an Intel HD Graphics 520 only. The new one won't be Nvidia equiped either (but Intel Iris Xe (iGPU) and Iris Xe Max (dedicated GPU)).
"where does one get b482"
Use the download manager which you can download via your Magix web account.
Marco.
wrote on 3/15/2021, 4:55 PM
@Howard-Vigorita
"Just happened to be trying some 10-bit hevc-lossless mov clips and the hevc 422 one was not recognized by Vegas v482 and could not be dropped onto a timeline. Same behavior on my Dell Laptop and Intel Nuc."
I guess your system is not based on the new (11.) Intel generation (with Intel XE or XE Max graphics), is it?
Howard-Vigorita
wrote on 3/15/2021, 5:01 PM
try uncheck for 'enable legacy HEVC decoding' ?
Just tried checking legacy HEVC decoding and the 422 clip is unrecognized either way. The 420 clip played either way but I got more gpu utilization on my laptop's hd630... checked: 65%; unchecked: 95%.
AVsupport
wrote on 3/15/2021, 5:13 PM
[482 update:] not seeing the ability to load a HEVC 422 clip into project media, whether it's Intel accelerated or not, it cannot be edited. checked that 'legacy decoders' are indeed disabled.
Cannot see evidence of nVidia timeline playback decode for HEVC 420 clips either (checked for NVDEC is selected, yes):
So where I sit, no improvements. That's sad.
lenard
wrote on 3/15/2021, 8:02 PM
The 4:2:0 A7S footage linked in the other thread use GPU at between 30 % and 75 % here, whereas other HEVC 4:2:0 10 bit video (don't know the source) I tested use GPU between 70 % and 90 %.
You must look at decode only. You mentioned using an intel IGPU, it would be very easy to get 70+ percent GPU activity with that
The 420 clip played either way but I got more gpu utilization on my laptop's hd630... checked: 65%; unchecked: 95%.
@Howard-Vigorita so you're confirming HEVC 420 10bit decode on intel igpu?
It may have always worked, and the same situation as DolbyVision 420 HEVC 10 bit files. It works because GPU decoding is enabled, but is blocked with Nvidia GPU