x265 encoding error.

[murriato]

First of all, thank you very much again Mr. Selur.

I'm a bit confused since you wrote that you are doing this for years and then you write you recently changed to MapNLQ.

Yes, I have been using avs scripts in Hybrid for years (not only I have used these 2 plugins, I have also used other plugins).
And specifically about DoViBaker and MapNLQ plugins: DoViBaker I started using almost 2 years ago, and MapNLQ I've been using for the last 9 months (and as I explained before, during these last months I use MapNLQ instead of DoViBaker, so I don't use DoViBaker anymore).


And as I told you before, everything has always worked perfectly for me without problems. But in the latest versions (2024.05.11.1 and later) it doesn't work.
I guess if you go edit the scripts to manually load all the dependencies as you indicated to me days ago maybe it would work... but that would be a bit annoying and quite cumbersome and laborious, and during all these years it has never been necessary to do any of this (versions 2024.05.05.1 and earlier), before it just worked without complications.

That's why I asked you in my previous message the following:

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.

But okay, since you wrote your script with MapNLQ works with 2024.05.05.1:
1. Does the Avisynth Preview work with that version? Dreate a debug output of you opening that script in Hybrid in Avisynth Preview.
2. Create (another) debug output of Hybrid processing/encoding that script.

With Avisynth Preview you mean Hybrid > Tools > avsviewer, correct?

In that case, with the latest versions of Hybrid (2024.05.11.1 and later) it does not work, it shows this error:

Avisynth preview error: -> Script error: There is no function named 'FFVideoSource'. (C:\Users\cebol\Desktop\ENCODES\MapNLQ.avs, line 4) (C:\Users\cebol\Desktop\ENCODES\HYBRID\tempPreviewAvisynthFile23_11_46_417.avs, line 6)

But with older versions of Hybrid (versions 2024.05.05.1 and earlier) it works perfectly:

ClearAutoloadDirs()
SetFilterMTMode("DEFAULT_MT_MODE", MT_MULTI_INSTANCE)
Import("C:\Program Files\Hybrid\64bit\Avisynth\avisynthPlugins\mtmodes.avsi")
# loading source: C:\Users\cebol\Desktop\ENCODES\MapNLQ.avs
# color sampling YV12@10, matrix: bt709, scantyp: progressive, luminance scale: limited
Import("C:\Users\cebol\Desktop\ENCODES\MapNLQ.avs")
# current resolution: 1920x804
# setting output fps to 23.976fps
AssumeFPS(24000,1001)
PreFetch(16)
#  output: color sampling YV12@10, matrix: bt709, scantyp: progressive, luminance scale: limited
return last

By the way, I have tested with CMD the avsInfo64 that is included inside Hybrid and it also works without problems in older versions of Hybrid:





I attach the two debug outputs, but I think that avsviewer does not generate any text in the log (because I open the avsviewer tool and open the avs script and in the HybridDebugOutput.txt file no new text is written when I perform these steps.

Why does it say 709 instead of 2020? Is this wrong? Or is this right and correct?

The output vui values are set in the tab of the encoder, by guess is that atm. Hybrid takes the values it guesses these from the input.
You need to adjust these for HDR content. 709 is wrong for HDR content.
Yes, 709 can't represent all the colors HDR can.

Cu Selur

Yes, I know that 709 is SDR and 2020 is HDR.

My doubt was another one, not that one, let me be more specific and explain myself better:
The encodes I have done for years in HDR in Hybrid I have always obtained a correct output, that is to say the output has always been HDR... the MediaInfo of the encoded outputs are always HDR (BT.2020, PQ, MaxFALL/MaxCLL values, etc).


But as a result of this thread and the problem I have, I have had to review my logs so I can attach them to you in case they are helpful.
And I have noticed that in these logs in many occasions the text "709" appears, for example here:

"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 yuv4mpegpipe

So reading in the log so many "709" has surprised me, and I'm worried because I'm encoding HDR content and not SDR, so if I'm encoding HDR it should not appear in the log so many settings that refer to the 709 color space, should all appear as 2020.
Is this correct (should always appear 2020 and should never appear 709)?
Or do these log texts not matter and do not imply anything and I should not worry?


My encodes (my output videos that I generate with Hybrid) are all correct and all are HDR output.
But I'm worried because reading this text fragment in the log I get the feeling (or at least that's what my logic says) that the source is being read as 709 instead of 2020 (although the output is correctly written as 2020)... and in case this is really happening then it will be forming a kind of funnel/bottleneck causing a part of the color spectrum to be lost, since 2020 encompasses a wider breadth and range of colors than 709.



Thank you very much as always!





P.S.
Other things I discovered when I was testing this:

1.
I noticed that in the Log it is written that it cannot find color matrix and then it assumes it is bt709 since the video size is larger than 720*576.



Then I thought that maybe this is the problem... so I edited the avs script and removed the z_Spline36Resize line (so that the video is still 2160 instead of resized to 1080).
And indeed now in the Log it is written that it cannot find color matrix and then it assumes it is bt2020ncl since the video size is larger than 1920*1088 (although it should be 1080 instead of 1088, right?).



But this does not produce any change, the results remain the same.
So this seems to be indifferent and does not affect anything.



2.
As I told you Hybrid is not able to read the color of the source and then adjusts it as bt709, but now I have seen that the same thing happens with the framerate, it is also not able to read it well and adjusts it wrong as it configures it as 23976/1000 instead of 24000/1001.






And by the way, I noticed that the output encoded videos are actually bt709 and not bt2020 as I told you before... before this did not happen to me because I had manually set the MKV tags here (all tags, matrix/range/transfer matrix/primaries/etc): Config > MKV tagging > VUI > Matroska advanced video signaling


But I think this is not correct, Hybrid should not read these videos as bt709 and should not have these problems.

For example when I encode a mkv input (instead of avs script) I don't have any of these problems and I don't need to use MKV tagging (VUI > Matroska advanced video signaling).



3.
I noticed that the Auto crop option does not work when the input is an avs script.
That is, when the input is an MKV file you can press that option and Hybrid tries to guess the necessary crop, but when the input is an avs script you press that option and nothing happens.
I mean this:





4.
These problems (not detecting color, framerate, etc) I have noticed that they have nothing to do with MapNLQ.
Because if I make a very simple avs script, just with this line and nothing else:

FFVideoSource("C:\Users\cebol\Desktop\ENCODES\HYBRID\Material Los juegos del hambre - Balada de pajaros cantores y serpientes\Los juegos del hambre DV.mkv")

I get all these same problems and the same results.

So these problems are using avs scripts in general, no matter what text I have written inside the script.