 |
there is also 'colorspace' plugin, hopefully it also can convert part of timeline between those colorspaces |
 |
@Andrew-R You are quite right about the colorspace filter: I had not seen the 'irange' option and had only played with 'range'. When YUV color range is set to MPEG (in Cin Preferences>Appearance), setting irange to 2 in the colorspace filter does change the contrast, however the data outside the 16-235 range is already gone (clipped). Interestingly, when YUV color range is set to JPEG, using the colorspace plugin to set the range to MPEG does not hard clip, and values outside the 16-235 range can be be brought back into range using another plugin such as Blue Banana. |
|
|
so, this hack shows color range for asset in it info window.. how just need to learn how to make this dropdown list, and pass user selection back to program..
asset_col_range_show.diff (1,626 bytes) |
|
|
so, cin already carries this info in ff_color_range variable in asset.c $ grep ff_color_range cinelerra/* grep: cinelerra/armv8l: Is a directory cinelerra/asset.C: ff_color_range = -1; cinelerra/asset.C: ff_color_range = asset->ff_color_range; cinelerra/asset.C: ff_color_range = GET_DEFAULT("FF_COLOR_RANGE", ff_color_range); cinelerra/asset.C: UPDATE_DEFAULT("FF_COLOR_RANGE", ff_color_range); cinelerra/asset.C: fprintf(fp," ff_color_range=%d\n", ff_color_range); cinelerra/asset.h: int ff_color_space, ff_color_range; grep: cinelerra/ci: binary file matches grep: cinelerra/data: Is a directory cinelerra/ffmpeg.C: if( (vid->color_range = asset->ff_color_range) < 0 ) cinelerra/ffmpeg.C:int FFMPEG::ff_color_range(int stream) cinelerra/ffmpeg.h: int ff_color_range(int stream); cinelerra/fileffmpeg.C: if( asset->ff_color_range < 0 ) cinelerra/fileffmpeg.C: asset->ff_color_range = ff->ff_color_range(0); grep: cinelerra/randrik: Is a directory grep: cinelerra/tests: Is a directory we just need to expose it as changeable param in assetedit.c|h or so I think... |
|
|
@glitterball this filter have two ranges - range for output and irange for input.. setting range to mpeg while irange at jpeg (with jpeg in prefs) definitely changes output picture... |
|
|
@Andrew-R Yeah, I tried that filter, and changing the range there doesn't seem to make any difference either. |
|
|
@glitterball have you tried ffmpeg plugin I mentioned (with cin preference set to full)? |
|
|
@Andrew-R I tried changing the x11 settings as suggested and none of the changes made any difference. Rendering a video produces a file where the those values are clipped. The only way to keep the full range is to set the YUV color range to 'JPEG' in appearance. However this means that all clips must be transcoded to the same range before being imported into Cinelerra, as Cinelerra cannot handle video files with differing ranges within the same project. |
|
|
@glitterball, as far as I can see this preferences setting control ffmpeg's swscaler, before it converted to rgba-float. May be x11 output clip them? try x11-opengl, try uncheck direct x11 path, also try to render into some image/video file and see if those values still around.... if they are - then we need to look at video output specifically... |
|
|
@Andrew-R Sorry I wasn't clearer: it makes no visible difference to the clip (I.e. everything outside 16-35 is still clipped even with those settings). I do get some extra error messages when adding the .opts file mostly "[swscaler @ 0x7efd9c20d900] deprecated pixel format used, make sure you did set range correctly" |
|
|
@glitterball $ cat ~/matrixbench_highdivx_ac3.opts #lowres=1 #fast=1 #video_filter=format=yuv422p video_filter=scale=in_range=limited:out_range=full sorry, try optS? in my case it prints something: [swscaler @ 0xe0d24000] No accelerated colorspace conversion found from yuv420p to rgba. |
|
|
@Andrew-R Thanks for the response, I gave your suggestion a go, but unfortunately adding the .opt file didn't appear to make any difference. |
|
|
@glitterball, yeah, from user perspective this is good idea, nit sure if I am up to task about coding it (soecifically, not sure if ffmpeg>cin transfer has access to specifics of assets/clips) I found another answer, you can try to add this into opt files, one per asset/file https://superuser.com/questions/1405177/ffmpeg-how-to-handle-color-range-conversions "Input is limited range, I want to output full range Use the scale filter, -vf scale=in_range=limited:out_range=full" try to put this line (without leading "-") in file named exactly like your input file just with opt extension...? sure, this is workaround (if it works as I think it works!) and not resolution.. |
|
|
The way Davinci Resolve handles this, is to allow the user to set whether a clip's data levels are 16-235 or 0-255 under 'Clip Attributes'. Specifically there is a radio button under 'Clip Attributes' (right-click on a clip, then Clip Attributes) called 'Data Levels' with the following options: Auto, Video or Full. In Cinelerra, the same options could be provided in the 'Info...' dialog box (found by right-clicking on a file in Resources>Media). Thinking about it, this is the logical solution, as many video projects will use video files with differing frame rates, data levels etc, so it should be possible to set this on a per-file basis rather than project-wide. I also note that the 'auto' option for data levels did not work in Davinci Resolve, and I had to set this manually. |
|
|
also, may be ffmpeg's filter colorspace can help here? seems to be enabled in Cingg and suppirts >8 bit depth https://github.com/FFmpeg/FFmpeg/blob/master/libavfilter/vf_colorspace.c |
|
|
does same problem exist in ffmpeg? I think until recently ffmpeg was internally 8bit, so clipping may happen there... |
- Anonymous
