This forum has been archived. All content is frozen. Please use KDE Discuss instead.

RGB parade & lag when showing values?

Tags: None
(comma "," separated)
lefthook
Registered Member
Posts
30
Karma
0

RGB parade & lag when showing values?

Sat Apr 13, 2013 12:21 pm
Hi! I have applied Levels effect to whole track, but RGB parade shows different values when playing than when I Stop video. On play values max can jump and show 240 but when I stop It shows 233 everywhere which I have set with the Levels effect. Which one is the right value? Play or Stop?
lefthook
Registered Member
Posts
30
Karma
0
I rendered one part to mp4 to check, but it still shows 240 max in RGB parade and not 233 which I tried to set with Levels effect? Levels on the whole track did not make nothing? Effect dragged over the track title. Has a little star.
lefthook
Registered Member
Posts
30
Karma
0
If I edit more roughly with Levels it seems to make effect. Enough down from 235. Is there anyway to see whole clip max and min values?
yellow_drupal
Registered Member
Posts
748
Karma
0
I don't see these problems with values changing between play and stop, tested with recent git build and h264 and dv files. Not sure if it makes any difference but I'm using OpenGL and X11 in kdenlive config but think your problem may be more to do with earlier kdenlive versions relating to SDL preview differing between play and stop.

As an aside I noticed you posted an earlier thread about broadcast safe and you mention 235 values in this post which would suggest trying to keep luma levels within the 16 - 235 YCbCr range so they convert to RGB 0 - 255 using standard methods for color space conversion. But as you're looking at an RGB Parade then that 16 - 235 YCbCr to 0 - 255 RGB levels conversion is accounted for, so if you set your levels to 235 based on an RGB scope you're actually reducing your levels unnecessarily.

It may be better to use the levels effect + RGB Parade to set what you want as your brightest highlight in the frame to 255 and your darkest shadows to 0. This assumes your source files levels and exposure are not clipped and crushed in camera, if they are then the clip and crush levels 'should' be at 255 & 0 respectively.


Bookmarks



Who is online

Registered users: bartoloni, Bing [Bot], Google [Bot], Yahoo [Bot]