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
#1
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
Reply
#2
  • "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
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#3
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...
Reply
#4
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
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#5
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
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#6
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
Reply
#7
Let me know when you find a way to reproduce the problem, and I'll try to fix it.
Smile
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#8
Wow, thanks!
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)