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.

[BUG] Incorrect range signalling
#11
Thanks. 
I think I found another bug, where configuration, that's used for a job is incorrect: it uses old config, from the time when you select a file. You're trying to add a job, but it uses old config and the only way to refresh that - is re-import a file... Going to create a separate thread for that if this isn't an intended behaviour
Reply
#12
No clue what that means.
Can you give a more detailed description?
Some settings only have an effect while loading a source, this might be correct.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#13
Ok, I'll try to reproduce this behaviour and make a video
Reply
#14
Uploaded a new dev version which hopefully fixes the 'overwrite output luminance' problem.
About the other problem: Like I wrote, I need details on how to reproduce this.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#15
Sad 
Well, time for round 3, I guess
The issue still persists in latest March 3 dev buld...
A part of the batch processing log
Still reports "Color range                : Limited", even though in Hybrid I have "Luma: pc"
This bug alone makes batch processing literally unusable, since i need to drag&drop each file manually if I want to retain correct color range tag
Reply
#16
2025.03.05 - 19:09:24_Windows 10 Version 21H2 (64bit)_2025.03.03.1 - level 9: source_inputColorMatrix:
2025.03.05 - 19:09:24_Windows 10 Version 21H2 (64bit)_2025.03.03.1 - level 9: inputColorMatrix: pc
2025.03.05 - 19:09:24_Windows 10 Version 21H2 (64bit)_2025.03.03.1 - level 9: resulting colorMatrix: pc
2025.03.05 - 19:09:24_Windows 10 Version 21H2 (64bit)_2025.03.03.1 - level 9:   adjustVUIColorMatrixValue->inputColorMatrix: pc
That seems wrong, color matrix should never be pc.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#17
Debug output doesn't contain the analysis of the source, so no clue where the problem comes from.
I need detailed instructions on how to reproduce this so I can fix it.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#18
ARGH,.... the whole start seems useless,..

For the frist encoding Hybrid used:
"C:\Program Files\Hybrid\64bit\Vapoursynth\vspipe.exe" "I:\TEMP\encodingTempSynthSkript_2025-03-05@19_10_39_9510_0.vpy" - -c y4m | "C:\Program Files\Hybrid\64bit\ffmpeg.exe" -y -noautorotate -nostdin -hwaccel cuda -hwaccel_output_format cuda -threads 1 -color_primaries bt709 -color_trc bt709 -colorspace bt470bg -color_range pc -f yuv4mpegpipe -i - -an -sn -color_primaries bt709 -color_trc bt709 -colorspace bt470bg -color_range pc -sws_flags accurate_rnd+full_chroma_inp -pix_fmt yuv420p -fps_mode passthrough -vcodec ffv1 -coder 0 -context 0 -g 500 -level 3 -slices 4 -slicecrc 0 -metadata encoding_tool="Hybrid 2025.03.03.1" "I:\TEMP\tapeC_5_1_2025-03-05@19_10_39_9510_02.mkv"
ffmpeg reported:
ffmpeg version N-118548-gf622598d05-ge24920375c+1 Copyright (c) 2000-2025 the FFmpeg developers
  built with gcc 14.2.0 (Rev2, Built by MSYS2 project)
  configuration:  --pkg-config=pkgconf --cc='ccache gcc' --cxx='ccache g++' --ld='ccache g++' --extra-cxxflags=-fpermissive --extra-cflags=-Wno-int-conversion --disable-autodetect --enable-amf --enable-bzlib --enable-cuda --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-nvenc --enable-zlib --enable-sdl2 --enable-ffnvcodec --enable-nvdec --enable-cuda-llvm --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libdav1d --enable-libaom --disable-debug --enable-fontconfig --enable-libass --enable-libbluray --enable-libfreetype --enable-libharfbuzz --enable-libmfx --enable-libmysofa --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-gpl --enable-avisynth --enable-libxvid --enable-libopenmpt --enable-librav1e --enable-libsrt --enable-libgsm --enable-libvmaf --enable-libsvtav1 --extra-cflags=-DLIBTWOLAME_STATIC --extra-cflags=-DLIBXML_STATIC --extra-libs=-liconv --disable-w32threads
  libavutil      59. 57.100 / 59. 57.100
  libavcodec     61. 33.102 / 61. 33.102
  libavformat    61.  9.107 / 61.  9.107
  libavdevice    61.  4.100 / 61.  4.100
  libavfilter    10.  9.100 / 10.  9.100
  libswscale      8. 13.100 /  8. 13.100
  libswresample   5.  4.100 /  5.  4.100
  libpostproc    58.  4.100 / 58.  4.100

Input #0, yuv4mpegpipe, from 'fd:':
  Duration: N/A, start: 0.000000, bitrate: N/A
  Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p(pc, bt470bg/bt709/bt709, progressive), 720x576, 50 fps, 50 tbr, 50 tbn

Stream mapping:
  Stream #0:0 -> #0:0 (rawvideo (native) -> ffv1 (native))

Output #0, matroska, to 'I:\TEMP\tapeC_5_1_2025-03-05@19_10_39_9510_02.mkv':
  Metadata:
    encoding_tool   : Hybrid 2025.03.03.1
    encoder         : Lavf61.9.107
  Stream #0:0: Video: ffv1 (FFV1 / 0x31564646), yuv420p(pc, bt470bg/bt709/bt709, progressive), 720x576, q=2-31, 200 kb/s, 50 fps, 1k tbn
    Metadata:
      encoder         : Lavc61.33.102 ffv1

For the 2nd encoding Hybrid used:
"C:\Program Files\Hybrid\64bit\Vapoursynth\vspipe.exe" "I:\TEMP\encodingTempSynthSkript_2025-03-05@19_38_54_7310_0.vpy" - -c y4m | "C:\Program Files\Hybrid\64bit\ffmpeg.exe" -y -noautorotate -nostdin -threads 8 -color_primaries bt709 -color_trc bt709 -colorspace bt470bg -color_range pc -f yuv4mpegpipe -i - -an -sn -color_primaries bt709 -color_trc bt709 -colorspace bt470bg -color_range pc -sws_flags accurate_rnd+full_chroma_inp -pix_fmt yuv422p -fps_mode passthrough -vcodec ffv1 -coder 0 -context 0 -g 1 -level 3 -slices 4 -slicecrc 0 -metadata encoding_tool="Hybrid 2025.03.03.1" "I:\TEMP\tapeC_2_1_2025-03-05@19_38_54_7310_05.mkv"
and ffmpeg reported:
ffmpeg version N-118548-gf622598d05-ge24920375c+1 Copyright (c) 2000-2025 the FFmpeg developers
  built with gcc 14.2.0 (Rev2, Built by MSYS2 project)
  configuration:  --pkg-config=pkgconf --cc='ccache gcc' --cxx='ccache g++' --ld='ccache g++' --extra-cxxflags=-fpermissive --extra-cflags=-Wno-int-conversion --disable-autodetect --enable-amf --enable-bzlib --enable-cuda --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-nvenc --enable-zlib --enable-sdl2 --enable-ffnvcodec --enable-nvdec --enable-cuda-llvm --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libdav1d --enable-libaom --disable-debug --enable-fontconfig --enable-libass --enable-libbluray --enable-libfreetype --enable-libharfbuzz --enable-libmfx --enable-libmysofa --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-gpl --enable-avisynth --enable-libxvid --enable-libopenmpt --enable-librav1e --enable-libsrt --enable-libgsm --enable-libvmaf --enable-libsvtav1 --extra-cflags=-DLIBTWOLAME_STATIC --extra-cflags=-DLIBXML_STATIC --extra-libs=-liconv --disable-w32threads
  libavutil      59. 57.100 / 59. 57.100
  libavcodec     61. 33.102 / 61. 33.102
  libavformat    61.  9.107 / 61.  9.107
  libavdevice    61.  4.100 / 61.  4.100
  libavfilter    10.  9.100 / 10.  9.100
  libswscale      8. 13.100 /  8. 13.100
  libswresample   5.  4.100 /  5.  4.100
  libpostproc    58.  4.100 / 58.  4.100

Input #0, yuv4mpegpipe, from 'fd:':
  Duration: N/A, start: 0.000000, bitrate: N/A
  Stream #0:0: Video: rawvideo (Y42B / 0x42323459), yuv422p(pc, bt470bg/bt709/bt709, progressive), 720x576, 50 fps, 50 tbr, 50 tbn

Stream mapping:
  Stream #0:0 -> #0:0 (rawvideo (native) -> ffv1 (native))

Output #0, matroska, to 'I:\TEMP\tapeC_2_1_2025-03-05@19_38_54_7310_05.mkv':
  Metadata:
    encoding_tool   : Hybrid 2025.03.03.1
    encoder         : Lavf61.9.107
  Stream #0:0: Video: ffv1 (FFV1 / 0x31564646), yuv422p(pc, bt470bg/bt709/bt709, progressive), 720x576, q=2-31, 200 kb/s,  50 fps, 1k tbn
    Metadata:
      encoder         : Lavc61.33.102 ffv1

in both cases the calls Hybrid uses look correct and ffmpeg reports that pc scale is used.


Looking at the muxing call in the log:
"C:\Program Files\Hybrid\64bit\mkvmerge.exe" --ui-language en -o "I:\2025-03-05@19_38_54_7310__07.mkv" --global-tags "I:\TEMP\mkvtags_2025-03-05@19_38_54_7310__07.xml" --default-track 0:yes --color-matrix-coefficients 0:1 --color-range 0:1 --color-transfer-characteristics 0:1 --color-primaries 0:1 --default-duration "0:50/1fps" --aspect-ratio-factor 0:1/1 --no-chapters --compression -1:none --forced-track 0:yes --field-order 0:0 --no-audio --no-subtitles "I:\TEMP\tapeC_2_1_2025-03-05@19_38_54_7310_05.mkv" --track-name 0:"Track1" --default-track 0:yes --forced-track 0:no -a 0 --compression -1:none --no-video --no-subtitles --no-chapters "I:\TEMP\iId_17_aid_0_2025-03-05@19_38_54_7310_02.flac" --track-order 0:1,1:2

"--color-range 0:1" is wrong!
see: https://mkvtoolnix.download/doc/mkvmerge...olor_range
it should be 2.

=> I'll create a version which will output more debug output during the creation of the muxing call, maybe that will help to find the problem.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#19
(05.03.2025, 18:09)Selur Wrote:
2025.03.05 - 19:09:24_Windows 10 Version 21H2 (64bit)_2025.03.03.1 - level 9: source_inputColorMatrix:
2025.03.05 - 19:09:24_Windows 10 Version 21H2 (64bit)_2025.03.03.1 - level 9: inputColorMatrix: pc
2025.03.05 - 19:09:24_Windows 10 Version 21H2 (64bit)_2025.03.03.1 - level 9: resulting colorMatrix: pc
2025.03.05 - 19:09:24_Windows 10 Version 21H2 (64bit)_2025.03.03.1 - level 9:   adjustVUIColorMatrixValue->inputColorMatrix: pc
That seems wrong, color matrix should never be pc.

0_0
I thought pc == rec.709. I got "pc" color matrix frequently...
Do i need to run a single file and send you a full log? I thought I started debugging before import, sorry
Reply
#20
Updated the dev version, which changes a few things that might fix the problem.
Note: If you have "Config->MKV tagging" and "Config->MKV tagging->VUI->Range" enabled any detection and overwrite setting for luminance is ignored when muxing to mkv with mkvmerge, since you specifically said to signal XY for the mkv container.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Forum Jump:


Users browsing this thread: r3dfx, 1 Guest(s)