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.

x265 encoding error.
#27
(19.09.2024, 05:25)Selur Wrote: Uploaded a new dev version, try whether that helps.

Cu Selur

Hello again Mr. Selur, sorry for the delay I've been a little busy.

I confirm that the encoding with Auto crop is now working correctly, both with MKV sources and avs scripts.
Thank you very much for your efforts!





I would like to comment again what I wrote the previous days, since the same thing is still happening and I don't know if it is my problem or Hybrid's problem or Hybrid's configuration problem or what.

I mean this:

(19.09.2024, 01:29)murriato Wrote:
(18.09.2024, 05:21)Selur Wrote:
(18.09.2024, 01:48)murriato Wrote:
(17.09.2024, 03:56)Selur Wrote:
(16.09.2024, 23:50)murriato Wrote: 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?

-color_primaries bt2020 -color_trc smpte2084 -colorspace bt709
Mentions bt709 color matrix, bt2020 color primaries and smpte2084 color transfer.

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

Yes, if you upscale, it would be better to also use a color matrix conversion to bt2020.

Yes, I think so too. That's why I wanted to try not to let that happen.

And do you know why the ffmpeg command contains bt709? How could I solve it?

It's just that checking the debug logs the ffmpeg command always contains bt709. Even if Hybrid detects the input as 2020 then in the encoding debug log you see the ffmpeg commands with bt709. And even if I use a 2160p MKV input instead of an avs script, the same thing happens. I don't know what to do.



In my previous messages I already attached several debug outputs about this, but well I have now made again some new debug outputs with the latest dev version although it happens exactly the same as before.

But now I wanted to try to do it using the options you told me (I didn't know before that those options existed), I mean the options to force the input color, this: "Filtering->Misc->Overwrite input".
I have activated these 2 options:
- Overwrite input luminance: tv
- Overwrite input color matrix: rec.2020ncl

But even if I activate these options, exactly the same thing still happens.

In the logs it appears on numerous occasions that the video input is always being read/decoded/etc as bt709 instead of being read as bt2020nc/bt2020_ncl (although then the output is correctly written as bt2020ncl). And this happens all the time, and no matter what the source is, it happens with both mkv and avs scripts.


I attach 2 debug outputs, one is made with a MKV 4K HDR input and the other with an avs script also 4K HDR.
And as I said before, this time they are made with the 2 "Overwrite input" options activated, but in previous occasions I did it without them and the same thing happened.

In the logs you will find references to 709 on many occasions.

- For example this is from MKV:

Quote:2024.09.21 - 14:12:07_Windows 11 Version 23H2 (64bit)_2024.09.19.1 - level 9:  -> decoder call:
  ffmpeg
  -y
  -loglevel
  fatal
  -noautorotate
  -nostdin
  -threads
  8
  -i
  GENERATED_SYNTHINPUTSCRIPT
  -an
  -sn
  -color_primaries bt2020 -color_trc smpte2084 -colorspace bt709 -color_range tv  -pix_fmt yuv420p10le -strict -1 -vsync 0
  -f yuv4mpegpipe
  -

Quote:return last ###  ### false ### 87.0 ###  ### HEVC ### x265 ###  ### XVID ### false ###  ###  ###  ### x265Model ### encode
  ffmpeg -y -loglevel fatal -noautorotate -nostdin -threads 8 -i GENERATED_SYNTHINPUTSCRIPT -an -sn -color_primaries bt2020 -color_trc smpte2084 -colorspace bt709 -color_range tv  -pix_fmt yuv420p10le -strict -1 -vsync 0 -f yuv4mpegpipe -
  x265 --input - --fps 24000/1001 --output-depth 10 --y4m --profile main10 --level-idc 5.1 --qg-size 16 --tu-intra-depth 4 --tu-inter-depth 4 --limit-tu 4 --me star --subme 7 --limit-modes --max-merge 4 --no-early-skip --rskip 0 --no-open-gop --opt-ref-list-length-pps --min-keyint 23 --bframes 16 --weightb --ref 5 --rc-lookahead 60 --lookahead-slices 0 --crf 16.90 --opt-qp-pps --cbqpoffs -2 --crqpoffs -2 --ipratio 1.30 --pbratio 1.20 --qpfile GENERATED_QP_FILE --rd 4 --psy-rd 2.01 --rdoq-level 2 --psy-rdoq 2.01 --aq-mode 3 --no-cutree --vbv-maxrate 160000 --vbv-bufsize 160000 --hrd --vui-hrd-info --deblock=-3:-3 --no-sao --selective-sao 0 --no-mcstf --range limited --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --chromaloc 2 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(40000000,50)" --max-cll 3421,178 --hdr10 --hdr10-opt --sar 1:1 --output "C:\Users\cebol\Desktop\ENCODES\HYBRID\Amigos imaginarios forzado fuente_1.265"
  C:\Users\cebol\Desktop\ENCODES\HYBRID\Amigos imaginarios forzado fuente_1.mkv


- And this from avs script:

Quote:2024.09.21 - 11:52:46_Windows 11 Version 23H2 (64bit)_2024.09.19.1 - level 9:  -> decoder call:
  ffmpeg
  -y
  -loglevel
  fatal
  -noautorotate
  -nostdin
  -threads
  8
  -i
  "C:\Users\cebol\Desktop\ENCODES\MapNLQ.avs"
  -an
  -sn
  -vf format=yuv420p10le,crop=3840:2064:0:48,scale=1920:1032 -color_primaries bt709 -color_trc bt709 -colorspace bt709 -color_range tv -pix_fmt yuv420p10le -strict -1 -vsync 0
  -sws_flags spline
  -f yuv4mpegpipe
  -

Quote:2024.09.21 - 11:52:46_Windows 11 Version 23H2 (64bit)_2024.09.19.1 - level 9:  videoCalls:
  CUSTOM ### 1:1 ### 23.976 ### Source_1 ### 0 ### 1920 ### 1032 ### 950/23.976 ### C:\Users\cebol\Desktop\ENCODES\MapNLQ.avs ### mkv ### false ### false ### 7.1 ###  ### 0-0 ### C:\Users\cebol\Desktop\ENCODES\HYBRID\Amigos imaginarios avs forzado_1.mkv ###  ### 1/1 ###  ###  ### false ### 87.0 ###  ### raw ### x265 ###  ### XVID ### false ###  ###  ###  ### x265Model ### encode
  ffmpeg -y -loglevel fatal -noautorotate -nostdin -threads 8 -i "C:\Users\cebol\Desktop\ENCODES\MapNLQ.avs" -an -sn -vf format=yuv420p10le,crop=3840:2064:0:48,scale=1920:1032 -color_primaries bt709 -color_trc bt709 -colorspace bt709 -color_range tv -pix_fmt yuv420p10le -strict -1 -vsync 0  -sws_flags spline -f yuv4mpegpipe -
  x265 --input - --fps 24000/1001 --output-depth 10 --y4m --profile main10 --level-idc 5.1 --qg-size 16 --tu-intra-depth 4 --tu-inter-depth 4 --limit-tu 4 --me star --subme 7 --limit-modes --max-merge 4 --no-early-skip --rskip 0 --no-open-gop --opt-ref-list-length-pps --min-keyint 23 --bframes 16 --weightb --ref 5 --rc-lookahead 60 --lookahead-slices 0 --crf 16.90 --opt-qp-pps --cbqpoffs -2 --crqpoffs -2 --ipratio 1.30 --pbratio 1.20 --qpfile GENERATED_QP_FILE --rd 4 --psy-rd 2.01 --rdoq-level 2 --psy-rdoq 2.01 --aq-mode 3 --no-cutree --vbv-maxrate 160000 --vbv-bufsize 160000 --hrd --vui-hrd-info --deblock=-3:-3 --no-sao --selective-sao 0 --no-mcstf --range limited --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --chromaloc 2 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(40000000,50)" --max-cll 3421,178 --hdr10 --hdr10-opt --sar 1:1 --output "C:\Users\cebol\Desktop\ENCODES\HYBRID\Amigos imaginarios avs forzado_1.265"
  C:\Users\cebol\Desktop\ENCODES\HYBRID\Amigos imaginarios avs forzado_1.mkv


Thank you again for your time and effort, best regards! Smile


Attached Files
.zip   HybridDebugOutput - MKV.zip (Size: 21,86 KB / Downloads: 7)
.zip   HybridDebugOutput - avs script.zip (Size: 31,33 KB / Downloads: 7)
Reply


Messages In This Thread
x265 encoding error. - by murriato - 16.08.2024, 16:28
RE: x265 encoding error. - by Selur - 16.08.2024, 16:43
RE: x265 encoding error. - by murriato - 16.08.2024, 16:51
RE: x265 encoding error. - by Selur - 16.08.2024, 16:58
RE: x265 encoding error. - by murriato - 19.08.2024, 23:24
RE: x265 encoding error. - by Selur - 20.08.2024, 04:51
RE: x265 encoding error. - by murriato - 20.08.2024, 09:52
RE: x265 encoding error. - by Selur - 20.08.2024, 14:56
RE: x265 encoding error. - by murriato - 21.08.2024, 00:02
RE: x265 encoding error. - by Selur - 21.08.2024, 05:40
RE: x265 encoding error. - by murriato - 22.08.2024, 11:18
RE: x265 encoding error. - by Selur - 22.08.2024, 11:25
RE: x265 encoding error. - by murriato - 25.08.2024, 21:22
RE: x265 encoding error. - by Selur - 26.08.2024, 04:52
RE: x265 encoding error. - by murriato - 31.08.2024, 02:37
RE: x265 encoding error. - by Selur - 31.08.2024, 07:08
RE: x265 encoding error. - by Selur - 31.08.2024, 07:16
RE: x265 encoding error. - by Selur - 31.08.2024, 09:00
RE: x265 encoding error. - by Selur - 31.08.2024, 10:05
RE: x265 encoding error. - by murriato - 16.09.2024, 23:50
RE: x265 encoding error. - by Selur - 17.09.2024, 03:56
RE: x265 encoding error. - by murriato - 18.09.2024, 01:48
RE: x265 encoding error. - by Selur - 18.09.2024, 05:21
RE: x265 encoding error. - by Selur - 18.09.2024, 18:08
RE: x265 encoding error. - by murriato - 19.09.2024, 01:29
RE: x265 encoding error. - by Selur - 19.09.2024, 05:25
RE: x265 encoding error. - by murriato - 26.09.2024, 13:10
RE: x265 encoding error. - by Selur - 26.09.2024, 13:23
RE: x265 encoding error. - by murriato - 26.09.2024, 15:44
RE: x265 encoding error. - by Selur - 26.09.2024, 15:45
RE: x265 encoding error. - by murriato - 02.10.2024, 01:43
RE: x265 encoding error. - by Selur - 02.10.2024, 04:53
RE: x265 encoding error. - by murriato - 03.10.2024, 00:45
RE: x265 encoding error. - by Selur - 03.10.2024, 06:22

Forum Jump:


Users browsing this thread: 6 Guest(s)