SOS! AMD VCE 10 bit encoding, Vegas Pro 16? Need help.

Musicvid wrote on 11/29/2018, 8:08 PM

Would you be quite certian that AMD VCE supports 10 bit hardware encoding? Having a hard time finding mention of it here.

https://en.m.wikipedia.org/wiki/Video_Coding_Engine

Certainly you wouldn't be posting on a software forum without knowing that first, right?

Former user wrote on 11/29/2018, 8:32 PM

There is only 10bit decoding on vega and polaris VCE, not encoding. Why not use your IGPU (qsv) for 10bit HEVC, it's a superior encoder to VCE

Constantine-Van-Horne wrote on 11/30/2018, 8:44 AM

Thank you for your prompt response.

Yes, I did not know that Vega FE (AMD VCE 4.0) does not support 10 bits encoding. I will know, thanks. As for Intel. I have problems with IntelQSV. When I use IntelQSV (10 bit encoding), the final video is obtained with bugs: 1) strange FPS: 31 FPS, 61 FPS (see on screenshot), although in the settings I put 29 FPS or 59. 2) At the end of the video clip, the video can speed up (2-3x compare to normal temp) and go to black screen... (see screenshot) while the audio track is at a normal temp. If i use only the CPU(MainCOncept HEVC 10 bit encoding), (without QSV or VCE) its all OK. FPS is OK. Final video doesnt have any bugs or problems. Maby Is there something wrong in my render settings?

Please, give advice.
P.S. I use footage from Fuji x-t3 H.265 4k 10 bits 60p.

Thank you for your attention and answers.

Constantine-Van-Horne wrote on 11/30/2018, 8:46 AM

Would you be quite certian that AMD VCE supports 10 bit hardware encoding? Having a hard time finding mention of it here.

https://en.m.wikipedia.org/wiki/Video_Coding_Engine

Certainly you wouldn't be posting on a software forum without knowing that first, right?

Thanks you. Please read my answer.

Constantine-Van-Horne wrote on 11/30/2018, 8:46 AM

There is only 10bit decoding on vega and polaris VCE, not encoding. Why not use your IGPU (qsv) for 10bit HEVC, it's a superior encoder to VCE

Thanks you. Please read my answer.

Musicvid wrote on 11/30/2018, 9:59 AM

Please repost your source medi properties using MediaInfo, in English please?

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

You are now discussing source media issues that have nothing to do with rendering.

Constantine-Van-Horne wrote on 11/30/2018, 12:30 PM

Yes, of course.

Mediainfo from final movie.

General
Complete name : X:\Greece New\Untitled 1 2 2 9 3.mp4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (isom/mp42)
File size : 447 MiB
Duration : 1 min 16 s
Overall bit rate mode : Variable
Overall bit rate : 49.0 Mb/s
Encoded date : UTC 2018-11-10 01:29:45
Tagged date : UTC 2018-11-10 01:29:45

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@High
Codec ID : hvc1
Codec ID/Info : High Efficiency Video Coding
Duration : 1 min 16 s
Bit rate : 49.0 Mb/s
Width : 4 096 pixels
Height : 2 160 pixels
Display aspect ratio : 1.896
Frame rate mode : Variable
Frame rate : 30.141 FPS
Minimum frame rate : 29.970 FPS
Maximum frame rate : 30 000.000 FPS
Original frame rate : 29.970 (30000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.184
Stream size : 444 MiB (99%)
Language : English
Encoded date : UTC 2018-11-10 01:29:51
Tagged date : UTC 2018-11-10 01:29:51
Codec configuration box : hvcC

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Format profile : AAC@L2
Codec ID : mp4a-40-2
Duration : 1 min 16 s
Bit rate mode : Variable
Bit rate : 317 kb/s
Maximum bit rate : 480 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 : 2.89 MiB (1%)
Language : English
Encoded date : UTC 2018-11-10 01:29:51
Tagged date : UTC 2018-11-10 01:29:51

Constantine-Van-Horne wrote on 11/30/2018, 12:39 PM

...and this is media info from Fuji x-t3 footage

Complete name : X:\Greece New\DSCF4548.mov
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt 0000.02 (qt )
File size : 3.34 GiB
Duration : 19 s 19 ms
Overall bit rate mode : Variable
Overall bit rate : 1 510 Mb/s
Movie_More : FUJIFILM DIGITAL CAMERA X-T3
Encoded date : UTC 2018-10-17 07:47:54
Tagged date : UTC 2018-10-17 07:47:54
Writing application : FootageStudio.11
Comment : FUJIFILM DIGITAL CAMERA X-T3

Video
ID : 1
Format : ProRes
Format version : Version 0
Format profile : 422 HQ
Codec ID : apch
Duration : 19 s 19 ms
Bit rate mode : Variable
Bit rate : 1 508 Mb/s
Width : 4 096 pixels
Height : 2 160 pixels
Display aspect ratio : 1.896
Frame rate mode : Constant
Frame rate : 59.940 (60000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:2
Scan type : Progressive
Bits/(Pixel*Frame) : 2.844
Stream size : 3.34 GiB (100%)
Writing library : Apple
Language : English
Encoded date : UTC 2018-10-17 07:47:54
Tagged date : UTC 2018-10-17 07:47:54
Color primaries : BT.709
Transfer characteristics : BT.601
Matrix coefficients : BT.601

Audio
ID : 2
Format : PCM
Format settings : Little / Signed
Codec ID : in24
Duration : 19 s 19 ms
Bit rate mode : Constant
Bit rate : 2 304 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Bit depth : 24 bits
Stream size : 5.22 MiB (0%)
Language : English
Default : Yes
Alternate group : 1
Encoded date : UTC 2018-10-17 07:47:54
Tagged date : UTC 2018-10-17 07:47:54

Other
ID : 3
Type : Time code
Format : QuickTime TC
Duration : 19 s 19 ms
Time code of first frame : 01:01:39;01
Time code, striped : Yes
Language : English
Default : No
Encoded date : UTC 2018-10-17 07:47:54
Tagged date : UTC 2018-10-17 07:47:54

Musicvid wrote on 11/30/2018, 4:17 PM

You have provided source MediaInfo indicating 59.94p.

You have provided encoded MediaInfo indicating 29.97p.

The "31" and "61" you got are just clock rounding jitter; forget about it

In order to make this work in Vegas without blurring, you will need to do one of two things:

-- Render at the SAME framerate as your source, 59.94p.

-- Disable Resample on every media event, and render at 29.97p with decimation.

Field Interpolation or blending using Auto Resample is not a framerate conversion technique in Vegas.

Constantine-Van-Horne wrote on 11/30/2018, 5:29 PM

Thank you very much for your help and time.

The problem with Intel remained. Example video (IntelQSV and MainConcept) on the link https://we.tl/t-wwiA706wgE, if you have time, please, look.

After switching from Nvidia GTX to Vega FE, the speed of the preview and rendering (MainCocept 10 bits) increased by 2-3 times. It's good for me.

Have a nice time!

Musicvid wrote on 11/30/2018, 8:37 PM

Thanks for posting that link. Others here will have far more insight into the details of hardware encoder settings than me. Glad to have been of help, and best of luck.

Please understand that for the "software" (Vegas) to expose a certain feature (ten bit recording), the "firmware" (video drivers) and "hardware" (graphics and CPU) must support it first.

The problem with Intel remained.

OK, what's your best guess here? Is that the domain of your hardware or software?

Former user wrote on 12/1/2018, 1:32 AM

Thank you for your prompt response.

Yes, I did not know that Vega FE (AMD VCE 4.0) does not support 10 bits encoding. I will know, thanks. As for Intel. I have problems with IntelQSV. When I use IntelQSV (10 bit encoding), the final video is obtained with bugs: 1) strange FPS: 31 FPS, 61 FPS (see on screenshot), although in the settings I put 29 FPS or 59. 2) At the end of the video clip, the video can speed up (2-3x compare to normal temp) and go to black screen... (see screenshot) while the audio track is at a normal temp.

It looks like the encoder stops rendering video at 29seconds, but continues rendering audio for the full 1m16s, it's not rendering black, there's no actual video, causing players to freak out, lagging & reporting strange fps from 80fps to 18fps. The first 29s looks perfect & syncs with audio fine (but may not look that way depending on player)

I don't see an obvious reason for that to occur.

astar wrote on 12/2/2018, 2:14 PM

The Radeon Pro series cards indicate 10-bit support, also indicate VCE included. Only AMD pre-sales or support would be able to confirm 10-bit VCE support from a specific card, or test it yourself and return the card.

c_future81 wrote on 7/10/2019, 11:00 AM

Hi

I have more or less the same issue.

I'm using Vegas Pro 16

Rendered a 16 minutes video - all source material is in 4K resolution in 25FPS HEVC.

The project settings match the source settings.

I'm using a AMD Ryzen 7 1800X CPU and Gforce GTX 1070 GPU

First: rendering with Intel QSV and 40 - 50 mbit data rate takes 8 hours for this 16 minute clip.

Second: as Constantine initially wrote, the output file is somehow damaged.

It plays nicely the 1:50 minutes and then, based on the player the replay speed is suddenly 2 or 3 times too fast, audio is still played normally.

VLC player even stops playing at this point.

I'm now re-rendering everything again with Mainconcept, not using the Intel QSV .. .

And: I have never seen AMD VCE as an option at the render settings.

I'm using Windows 10 64bit and just freshly setup the system.

ryclark wrote on 7/10/2019, 11:22 AM

You won't see an AMD VCE option since you seem to be using a NVidia graphics card. You need an AMD GPU if you want to render using VCE I believe. And will you even be able to use Intel QSV if you only have an AMD Ryzen processor?

fr0sty wrote on 7/10/2019, 2:11 PM

Nvidia's equivalent of VCE is NVENC, which is also supported by Vegas.

You say project settings match media settings, but do render settings also match? Same resolution AND framerate?

As for HEVC taking so long, if your GPU doesn't support hardware acceleration of HEVC encodes (if you don't see VCE or NVENC next to the template names when you render), it will take forever. HEVC is a very CPU intensive format for both encode and decode. I had to deal with this when I had a GTX 970, it had NVENC for H264 but not HEVC. When I upgraded to my Radeon 7, VCE renders of HEVC format now go as fast as H264, about real time speed.

fifonik wrote on 7/10/2019, 5:16 PM

Mediainfo from final movie.
...

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@High

...

Frame rate mode : Variable
Frame rate : 30.141 FPS
Minimum frame rate : 29.970 FPS
Maximum frame rate : 30 000.000 FPS

I did not even know that Vegas can render in VFR (Variable Frame Rate) mode.

Musicvid wrote on 7/10/2019, 8:04 PM

I did not even know that Vegas can render in VFR (Variable Frame Rate) mode

If that was VFR, the frame rates would have varied widely, by many fps, not by fractions.

The render is constant frame rate; that report is the result of the actual frame rate divided by clock frequency, giving an irrational result, that can only be represented by its nearest rational neighbors, thus the controlled jitter.

Example: [1-(30 (1000/1001)) / 90,000] = 0.999666999666999666___

This anomaly of MediaInfo (handling irrational outcomes) has been discussed here, on Handbrake, and around the internet.