This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

HDR encoding
#11
Quote:The filename was missing in the place of "-" that is why I thought that was the reason for crashing.
File name has nothing to do in the encoder call, it should only appear in the decoder call.
I doubt that has anything to do with why anything is crashing.

Quote:It seems Hybrid thinks the source is 8-bit (wants to dither to 8 bit instead of 10 bit)
No hybrid assumes the source to be more than 8it otherwise it wouldn't use format="YUV420P16".
It looks like it thinks you set the encoder to 8bit output and thus creates 8bit output for the encoder. (=> make sure you set the output bit depth in the encoder properly)
Quote:# dithering from 16 to 8bit for encoder

Quote:and doesn't let me modify e.g. the matrix from bt.709 to bt.2020, etc...:
Hybrid doesn't offer anything to convert bt.709 to bt.2020 it only offers to signal a specifc matrix (through the encoder).
I don't know of any way to convert SDR to HDR content.
-> if you know of a way to do a bt.709 to bt.2020 conversion using Avisynth or Vapoursynth, let me know and I can add support for it in Hybrid.

Cu Selur

Ps.: small side note normally HDR is 10bit not 12bit. 12bit is only used by Dolby Vision afaik.
Reply
#12
(29.08.2017, 05:40)Selur Wrote:
Quote:The filename was missing in the place of "-" that is why I thought that was the reason for crashing.
File name has nothing to do in the encoder call, it should only appear in the decoder call.
I doubt that has anything to do with why anything is crashing.

Ok.

Quote:No hybrid assumes the source to be more than 8it otherwise it wouldn't use format="YUV420P16".

It looks like it thinks you set the encoder to 8bit output and thus creates 8bit output for the encoder. (=> make sure you set the output bit depth in the encoder properly)

I have set the output bit depth to 12 bit surely.

Quote:Hybrid doesn't offer anything to convert bt.709 to bt.2020 it only offers to signal a specifc matrix (through the encoder).
I don't know of any way to convert SDR to HDR content.
-> if you know of a way to do a bt.709 to bt.2020 conversion using Avisynth or Vapoursynth, let me know and I can add support for it in Hybrid.

Cu Selur

Ps.: small side note normally HDR is 10bit not 12bit. 12bit is only used by Dolby Vision afaik.

But I do not want to convert bt. 709 to bt. 2020 (SDR to HDR). The source is HDR as I stated earlier. I just want to signal the info which is already in the source.
The source is using 10 bit main profile 4:2:0 and I want to convert it to 12 bit main profile 4:2:0. The renderer I am using will be simply dithering the source to the bit level of my display.

Please help!
Reply
#13
If you simply want to signal use the options under x265->Signaling
Reply
#14
(29.08.2017, 09:39)Selur Wrote: If you simply want to signal use the options under x265->Signaling

I can do this only by using a lot of customly set parameters (not a problem), because Hybrid does not let me modify e.g. the matrix etc. So, I have to disable them and then
use them as custom parameters.

I just would like to be sure Hybrid does not dither the 10-bit source down to 8-bit and then convert it back to 12-bit (according to the output depth of the encoder).
Cropping can be made on a 10-bit source, right?
Reply
#15
If the field is greyed out, it is probably because Hybrid assumed this should be set automatically,.. (check the other enabled optins) using a custom command line usually is the wrong approach.

Yes, Hybrid can do cropping in 10/16 bit.
Reply
#16
(29.08.2017, 11:08)Selur Wrote: If the field is greyed out, it is probably because Hybrid assumed this should be set automatically,.. (check the other enabled optins) using a custom command line usually is the wrong approach.

Yes, Hybrid can do cropping in 10/16 bit.

Do you think HDR data is independent from the bit depth of the video (number of steps between each color)?
I would prefer 12 bit HDR output in case of 10 bit HDR sources as well, but do not know if it has some impact on the HDR properties during encoding.
Reply
#17
No clue. Also since most hardware decoder don't support 12bit, I would avoid it. Also only 10bit content is expected to have hdr data. Afaik only Dolby Vision is defined for 12bit.
Reply
#18
Quote:No, Hybrid doesn't support decoding anything above 2048x2048 atm. through DGDecNV.
(VP7 cards should be able to decode HEVC Main and Main 10 profile; VP8 cards should be able to handle HEVC Main 12; VP8 cards should also support 8k resolutions iirc.)
-> might come in the future isn't supported atm. by Hybrid (probably when I get my hands on a newer card, atm. I use a Geforce GTX 980 ti, which doesn't support hevc)

With this feauture missing from Hybrid, what does the program use for decoding 4K (main, main10, main12) sources?
This kind of current software decoding can have the same quality compared to DGDecNV (or has nothing to do with it)?

I have some 4K material to reencode but don't want to degrade the quality during decoding. In the past I always used DGDecNV with excellent results.

P.S. I am going to borrow you one of my GTX 10xx Pascal cards to be able to use DGDecNV for decoding... Wink
Reply
#19
Since decoding through DGDecNV isn't supported atm. Hybrid will use a libav based decoder like FFmpegSource or LibAvSource. Decoding quality should be the same for hardware and software decoders unless one is buggy.

I can probably create a Dev version for testing for you without the DgDecNV restrictions if you're interested.

Cu Selur
Reply
#20
(06.09.2017, 16:13)Selur Wrote: Since decoding through DGDecNV isn't supported atm. Hybrid will use a libav based decoder like FFmpegSource or LibAvSource. Decoding quality should be the same for hardware and software decoders unless one is buggy.

I can probably create a Dev version for testing for you without the DgDecNV restrictions if you're interested.

Cu Selur

I would be very interested, perhaps can speed up my encodes significantly.
My card is a GTX1060 using the latest DGDecNV. I know that HEVC format is supported by DGDecNV and my card supports main10 and main12 profiles, so hopefully will be working. 
I really appreciate your help!
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)