x265 encoding error.

[murriato]

That post of yours, is trash. It's a pain to read. Too many layers of quotes, which contain only already said data.
You answered inside quotes.
=> please, keep your posts more readable or I will not try to read them.

Thank you very much again Mr. Selur.
And sorry, you are right, my message is a bit confusing with so much text and so many quotes. Sorry for that!
I will try to do it in a cleaner way and I will try not to respond inside quotes.

By the way, when I encode in this version of Hybrid the result ends up with 2 files (.265 and .mkv) instead of only .mkv as it has always happened to me.
I guess it's because this option is disabled as well as the Auto crop option. And I have always chosen MKV in this option but now I can't choose anything, and I guess this is the cause of this problem, but I don't know.

No clue why this happens. Deinstall Hybrid, delete your settings, install latest dev, try if it still happens with that version.
If it does write a step-by-step on how to reproduce the problem and I can try to look into it.

No clue, why the 'Default container' combo box is empty on your screenshot, can't reproduce that here.

I have done what you indicated (reinstall and clean) and now it works correctly.
I guess when I installed it days ago something was installed wrong or it was missing configuration files or something strange happened, I don't know.

I tried to test the Auto crop option to see if it now works with avs scripts, but I can't use it.
The option appears disabled and you can't interact with it. And this happens all the time, both with avs scripts and MKV files.

It's disabled since you enabled 'Crop/Resize->Misc->On Source Change->Auto Crop' which disables the controls and only triggers the crop detection on a source change. If you enable it after a source already has been loaded, it only disables the controls.

I did not know that this option existed.
Actually I did not enable that option, it would have been enabled by default when installing Hybrid. I suppose it has something to do with the previous point, that is to say that Hybrid must not have been installed correctly.

In the new current installation this option is no longer enabled by default and the Auto crop option no longer appears disabled and I can activate it without problems.


I have tested with Auto crop and I will tell you my results:
The option works perfect, I press the button and it detects well the amount of pixels to crop.

But there is a problem:
If you then try to encode (I mean with the Crop set) it gives error during the encoding process.
Although it should be noted that if the input is an MKV it works fine and does not give error, but if the input is an avs script it gives error.

And the content of the avs script is indifferent and that is not a problem, simply if it is an avs script the encoding process always fails.

I also want to say that obviously I have tried to make those same encodes but unchecking the picture crop option and it works perfectly and does not give any error. It only fails if the crop option is activated.

I attach a debug output in case it is useful to you.

And now obviously the same thing is still happening, but the strange thing is that even though this happens (Hybrid assumes the color as bt709) if I make an encode and then open it in MediaInfo it turns out that the encode is bt2020 anyway.
That is, it doesn't matter if Hybrid assumes that the matrix color is bt709 or bt2020ncl, because anyway it always generates a resulting encode that is 2020.

Is this normal?

That depends on your setting, if you tell Hybrid to flag the content as bt2020 it will even if the content it has is bt709.

Yes, it makes sense and I suppose that this behavior is the correct one.

But I wanted to comment it because I was surprised because in previous versions of Hybrid this did not happen, in this same situation the previous versions of Hybrid generated me encodes with Matrix coefficients BT.709.

And now Hybrid generates the encodes correctly as Matrix coefficients BT.2020 non-constant, even though Hybrid has assumed the color as bt709 (since the video size is larger than 720*57).
Previously this did not happen and in that situation Hybrid generated encodes with Matrix coefficients BT.709.

It should be noted that there is a strange thing that keeps happening as I explained in previous messages, and I do not understand why.
And that is that I have checked the text of the logs after doing encodes and it still continues to appear many times the text "709" by numerous places, despite the fact that I am encoding 2020.

Is this a bit strange? Or is it normal and nothing to worry about?

Tagging the content is independent of the processing of the content.

-color_primaries bt2020 -color_trc smpte2084 -colorspace bt709

Mentions bt709 color matrix, bt2020 color primaries and smpte2084 color transfer.

I attach several debug outputs of some encode tests, in which you can search and find many "709":
- HybridDebugOutput - MKV (4K): Encode of a 4K MKV (the input is a normal mkv, not an avs script).
- HybridDebugOutput - avs script (4K): Encode of an avs script (the original 4K is kept, without resizing to 1080)
- HybridDebugOutput - avs script (4K resize to 1080): Encode of an avs script (resize to 1080 within the avs script itself)

Okay, not sure what to do with that. Since I'm unsure what you want to know about them.

Yes, that is precisely what I am referring to.

According to the log it seems that the video input is always being read as bt709 instead of being read as bt2020nc/bt2020_ncl (although then the output is correctly written as bt2020ncl). This I think always happens with mkv input or avs script input.

Wouldn't it be better and more appropriate for the ffmpeg command to be -colorspace bt2020nc/bt2020_ncl instead of -colorspace bt709?

I say this because I am concerned that this might cause what I explained to you in previous messages:
"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."


Greetings and thank you very much as always!