Selur's Little Message Board
[BUG] Incorrect range signalling - Printable Version

+- Selur's Little Message Board (https://forum.selur.net)
+-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html)
+--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html)
+--- Thread: [BUG] Incorrect range signalling (/thread-3979.html)

Incorrect range signalling - r3dfx - 23.01.2025

Hi! I noticed that Hybrid sometimes doesn't change input/output levels correctly
Windows 10 LTSC, using latest 2024.12.21.1 release, Vapoursynth only
I encountered problem when tried to convert levels for DV stream (directly taken from camera): 
  • Overwrite Output -> Output Luminance resets every time, despite box being checked
  • "Input" section doesn't seem to care about input  Big Grin . I imported PC levels footage and it says "Luma: tv" which is obvously not true...
     
[Image: _80c864324221cba5aa597d42aef5d8b9.jpeg]
I don't understand why levels aren't setting up correctly even after I used "Levels" in Vapoursynth and explicitly changed output range signaling to PC levels

RE: Incorrect range signalling - Selur - 23.01.2025

  • "Source info" shows the data collected during the analysis of the source. Can't tell exactly where the info comes from in your case without a debug output of the analysis.
  • "Overwrite output" forces that a specific luma range value is signaled to the encoder configuration from the filtering.
    When I load a source that is signaled as 'tv'/'limited' range and check for example 'x264->VUI->Video Usability Information->Luma Range' it shows 'limited'. When changing "Filtering->Misc->Overwrite Output->Output Luminance" to 'pc' 'x264->VUI->Video Usability Information->Luma Range' changes to 'full'.
    => works here as intended.
    According to your screenshot:
    [Image: grafik.png]
    Input is detected as 'tv' but output is signaled as 'pc',....

Quote:Overwrite Output -> Output Luminance resets every time, despite box being checked
If you close Hybrid, by default, no settings get saved. If you want Hybrid to remember stuff you need to configure it to do so.
read: [INFO] About profiles and saving settings,....

=> I can't see a problem or bug, looking at the information you provided.

Side note: Overwriting the output luminance will only change the signaling flags, it will not do a conversion.
For a color matrix conversion 'Vapoursynth->Color->Matrix->ColorMatrix' is normally used.

Cu Selur

RE: Incorrect range signalling - r3dfx - 23.01.2025

Output Luminance stays checked (I set up PC levels), but after some time it stops worlking correctly: I have to manually check and uncheck box to override output parameters because it shows TV luma, despite Output Luminance pc being checked

I'm aware that level signaling does not affect actual levels, but Vapoursynth's Levels can't override for some reason output luminance signalling even if I explicitly tell it to use full range...

RE: Incorrect range signalling - Selur - 23.01.2025

Quote:Output Luminance stays checked (I set up PC levels), but after some time it stops worlking correctly:
I would need a step-by-step to reproduce it, so I can fix it. 'after some time' Rolleyes

Quote:Vapoursynth's Levels can't override for some reason output luminance signalling even if I explicitly tell it to use full range...
That is probably a bug.
Changing "Levels->Range signaling" does change the signaling in the script, but not the output signal.
=> I'll look at that. Smile

RE: Incorrect range signalling - Selur - 23.01.2025

Uploaded a new dev version which hopefully fixes the problem of "'Levels->Range signaling' not affecting the output signaling".
The problem only appeared when using FilterOrder, FilterQueue worked fine. Tongue

Cu Selur

RE: Incorrect range signalling - r3dfx - 23.01.2025

Unfortunately I can't reliably reproduce that behaviour, but I'll try... Levels started to "reset" themselves after a few jobs and I don't know exactly what caused such behaviour( 
At the moment I can't reproduce this issue

RE: Incorrect range signalling - Selur - 23.01.2025

Let me know when you find a way to reproduce the problem, and I'll try to fix it.
Smile
Cu Selur

RE: Incorrect range signalling - r3dfx - 23.01.2025

Wow, thanks!