25.08.2024, 21:22
No, my script does not convert HDR to SDR. The input is HDR and the output is also HDR.
UHD Blu-rays include two types of Dolby Vision: MEL and FEL.
MEL is an "empty" video (no image) that simply contains the Dolby Vision metadata (RPU), and FEL is a video that in addition to containing the metadata (RPU) also shows image and to correctly encode the FEL video you must also process that second video and "bake in" the FEL into the BL video (the main HDR video).
There are several plugins that do this, for example:
- MapNLQ: https://github.com/Asd-g/AviSynthPlus-MapNLQ
- DoViBaker: https://github.com/erazortt/DoViBaker
If you want to encode videos with Dolby Vision coming from UHD Blu-rays it is essential and necessary to use these plugins, otherwise the resulting video will not be the right one.
And in short, the script I use in Hybrid uses the first plugin, that is MapNLQ.
I have some questions that maybe you could help me to understand, if you know something I would be very grateful:
- 1
As I told you in previous messages, I have been doing encodes in Hybrid for almost 2 years using these plugins (I used to use DoViBaker and now I use MapNLQ as it is better optimized and faster, but both perform the same function) and I have never had any problem.
I don't know if I have been doing it correctly during these last years, but what I have always done is simply to set Avisynth 64bit in Hybrid (that is : Config > Internals > Avisynth type: 64bit) and then in Hybrid I click on the open file option and instead of choosing an MKV file as I would normally do, I choose an avs file (which contains the script of MapNLQ or DoViBaker or whatever)... and that's it, then I perform an x265 encode as I would normally do as if it were an MKV. Is that correct?
By the way, I have Avisynth+ installed on my PC: https://github.com/AviSynth/AviSynthPlus/releases
And this plugins pack: https://gitlab.com/uvz/AviSynthPlus-Plugins-Scripts1
And I use avs scripts in AvsPmod (https://github.com/gispos/AvsPmod/releases) and Hybrid without problems.
And I have never needed to read dependencies or anything inside the scripts, I have always just used the functions without loading anything and it has always worked perfectly for years.
The problem why I opened this thread, is that a few days ago I formatted my PC and reinstalled Windows and then I installed Hybrid (the current version) and when I tried to open an avs file as I have been doing for years it didn't work.
I couldn't get it to work, so I thought maybe it was a problem with this version of Hybrid, I don't know.... So I started to try older versions of Hybrid, and indeed I got to version 2024.05.05.1 and now everything was working correctly, now works the same as it has always worked for years.
So:
The latest version of Hybrid that loads avs scripts without problems is version 2024.05.05.1, in all versions after that I can't get it to work (version 2024.05.11.1 and later).
And in the Hybrid changelog I do not find anything that has changed in this regard or anything that has nothing to do with this apparently.
Would it be possible that the current version of Hybrid (or in future Hybrid updates) this will work again as it has always worked for years (no need to load dependencies or do anything weird)? Since I've been using it this same way for years and I've never had any problems, so this is a bit frustrating for me and I wouldn't want to be stuck forever on an old version of Hybrid.
- 2
And a second question:
Following on from this thread and from looking at the log texts you have highlighted for me, I usually read in them the text "709". For example in your last messages you have shared me this text (coming from my logs):
And then I was a bit surprised to find so many settings referring to the 709 color space, since I'm doing HDR encodes and therefore the color space should be 2020 and not 709.
So I'm a bit worried...
Why does it say 709 instead of 2020? Is this wrong? Or is this right and correct?
Does this mean that the source is being read as 709 instead of 2020 (even though later the output is correctly written as 2020)?
Because if it really is reading the source as 709 then I would guess that a sort of "funnel" or "bottleneck" is forming and then they are missing a portion of the color spectrum, since 2020 encompasses a wider breadth and range of colors than 709. correct? So my logic tells me that.
Best regards and thank you very much as always!
UHD Blu-rays include two types of Dolby Vision: MEL and FEL.
MEL is an "empty" video (no image) that simply contains the Dolby Vision metadata (RPU), and FEL is a video that in addition to containing the metadata (RPU) also shows image and to correctly encode the FEL video you must also process that second video and "bake in" the FEL into the BL video (the main HDR video).
There are several plugins that do this, for example:
- MapNLQ: https://github.com/Asd-g/AviSynthPlus-MapNLQ
- DoViBaker: https://github.com/erazortt/DoViBaker
If you want to encode videos with Dolby Vision coming from UHD Blu-rays it is essential and necessary to use these plugins, otherwise the resulting video will not be the right one.
And in short, the script I use in Hybrid uses the first plugin, that is MapNLQ.
I have some questions that maybe you could help me to understand, if you know something I would be very grateful:
- 1
As I told you in previous messages, I have been doing encodes in Hybrid for almost 2 years using these plugins (I used to use DoViBaker and now I use MapNLQ as it is better optimized and faster, but both perform the same function) and I have never had any problem.
I don't know if I have been doing it correctly during these last years, but what I have always done is simply to set Avisynth 64bit in Hybrid (that is : Config > Internals > Avisynth type: 64bit) and then in Hybrid I click on the open file option and instead of choosing an MKV file as I would normally do, I choose an avs file (which contains the script of MapNLQ or DoViBaker or whatever)... and that's it, then I perform an x265 encode as I would normally do as if it were an MKV. Is that correct?
By the way, I have Avisynth+ installed on my PC: https://github.com/AviSynth/AviSynthPlus/releases
And this plugins pack: https://gitlab.com/uvz/AviSynthPlus-Plugins-Scripts1
And I use avs scripts in AvsPmod (https://github.com/gispos/AvsPmod/releases) and Hybrid without problems.
And I have never needed to read dependencies or anything inside the scripts, I have always just used the functions without loading anything and it has always worked perfectly for years.
The problem why I opened this thread, is that a few days ago I formatted my PC and reinstalled Windows and then I installed Hybrid (the current version) and when I tried to open an avs file as I have been doing for years it didn't work.
I couldn't get it to work, so I thought maybe it was a problem with this version of Hybrid, I don't know.... So I started to try older versions of Hybrid, and indeed I got to version 2024.05.05.1 and now everything was working correctly, now works the same as it has always worked for years.
So:
The latest version of Hybrid that loads avs scripts without problems is version 2024.05.05.1, in all versions after that I can't get it to work (version 2024.05.11.1 and later).
And in the Hybrid changelog I do not find anything that has changed in this regard or anything that has nothing to do with this apparently.
Would it be possible that the current version of Hybrid (or in future Hybrid updates) this will work again as it has always worked for years (no need to load dependencies or do anything weird)? Since I've been using it this same way for years and I've never had any problems, so this is a bit frustrating for me and I wouldn't want to be stuck forever on an old version of Hybrid.
- 2
And a second question:
Following on from this thread and from looking at the log texts you have highlighted for me, I usually read in them the text "709". For example in your last messages you have shared me this text (coming from my logs):
"C:\Program Files\Hybrid\64bit\ffmpeg.exe" -y -loglevel fatal -noautorotate -nostdin -threads 8 -i "C:\Users\cebol\Desktop\ENCODES\MapNLQ.avs" -an -sn -vf format=yuv420p10le,scale=1920:1038 -color_primaries bt709 -color_trc bt709 -colorspace bt709 -color_range tv -pix_fmt yuv420p10le -strict -1 -vsync 0 -sws_flags spline -f yuv4mpegpipeAnd then I was a bit surprised to find so many settings referring to the 709 color space, since I'm doing HDR encodes and therefore the color space should be 2020 and not 709.
So I'm a bit worried...
Why does it say 709 instead of 2020? Is this wrong? Or is this right and correct?
Does this mean that the source is being read as 709 instead of 2020 (even though later the output is correctly written as 2020)?
Because if it really is reading the source as 709 then I would guess that a sort of "funnel" or "bottleneck" is forming and then they are missing a portion of the color spectrum, since 2020 encompasses a wider breadth and range of colors than 709. correct? So my logic tells me that.
Best regards and thank you very much as always!