April 2026 - Cin - Cinelerra-GG Mailing Lists

Colors questions
by Andrea paz 05 May '26

05 May '26

Two questions about colors: 1- Regardless of the color space used for the sources, and regardless of the operations we perform on the timeline, do we always see only an sRGB signal on the monitor? Even if the monitor is set to a different color space? I mentioned this in the manual where I had gathered various comments from GG and others, but I can no longer find the sources. Can we see from the code how the signal sent to the monitor works? 2- In the rendering window, is it possible to use any options to set a color space (e.g., BT.709 or DCI-P3) of our choice? For example, can we use the zscale or libplacebo parameters?

4 9

another web page with icc profile check
by Andrew Randrianasulu 01 May '26

01 May '26

https://chromachecker.com/page/en/show/web_browser_tester works in ff 140.9.1esr (32-bit) I see "better" than sRGB images even on my 8bpc, HDMI->VGA connected monitor. But if I save two images and try to load them in cingg even compiled with lcms2 support and flags2=icc_profiles set in decode.opts I do not see any difference! cin /dev/shm/gradient\ *.jpg I toggle top track and text changes but relative width of green bar (very visible in gimp when you compare those two) does not change. So for now I think we can conclude color profiles in image actually not supported on reading/displaying ? writing ffmpeg/png with whole set of trc/primaries params (in avcodec kind of encoder params gui) gives you some embedded profile, so I think lcms2 support in embedded ffmpeg libs is working. I tried to add .opts file with video_filter=iccgen but it does not change anything :(

2 7

Brief maintenance window today + new forum coming soon
by Sam 01 May '26

01 May '26

Hi everyone, just a quick heads-up: the Cinelerra-GG server will be briefly offline today for maintenance work. We expect the downtime to be short. We're also happy to share that we're working on a new forum for the Cinelerra-GG community, which we plan to launch soon. It will replace the current WordPress-based forum with a modern, dedicated forum platform — more on that shortly. Sorry for any inconvenience and thanks for your patience! Cheers Sam

3 5

new zscale params
by Andrew Randrianasulu 30 Apr '26

30 Apr '26

I think those works, I see small difference between filter on and off Main line from this website https://digitensions.home.blog/2025/11/27/rescaling-video-with-ffmpeg/#Resc… but two lines that actually worked for me ffmpeg -i /dev/shm/icc-profile.mp4 -c:v v210 -color_primaries smpte431 -colorspace bt2020nc -color_trc bt2020_10bit -color_range tv -c:a copy -map 0 /dev/shm/out_file.mov ffmpeg -i /dev/shm/out_file.mov -c:v v210 -vf zscale=r=limited:m=2020_ncl:t=2020_10:p=smpte431:c=topleft,format=yuv422p10,scale=1920:-1:flags=lanczos -color_primaries smpte431 -colorspace bt2020nc -color_trc bt2020_10bit -color_range tv -c:a copy -map 0 /dev/shm/1out_file.mov otherwise I got code 3074: no path between colorspaces Error while filtering: Generic error in an external library Failed to inject frame into filter network: Generic error in an external library Error while processing the decoded data for stream #0:0 Conversion failed! icc-profile.mp4 file from https://vectronic.io/posts/ffmpeg-now-supports-icc-profiles-in-mp4/ but not sure if you can embed random profile this way, example was more about remuxing It seems iccdetect filter does not apply icc transformations, in commit it says other filters should do this job but no such filter exist in ffmpeg repo!

1 0

ocio filter in ffmpeg 8.1/cingg
by Andrew Randrianasulu 30 Apr '26

30 Apr '26

It says at plugin index building time (first start) [OpenColorIO Info]: Color management disabled. (Specify the $OCIO environment variable to enable.) [ocio_643 @ 0xe450140] Error: Config or arguments invalid. [ocio_643 @ 0xe450140] Input color space is null [ocio_643 @ 0xe450140] Display is null [ocio_643 @ 0xe450140] View is null [ocio_643 @ 0xe450140] Failed to create OCIO processor. PluginFFilter::new_ffilter(ocio) err: Invalid argument so it may work, if you have ocio config already for Natron/Blender?

1 0

Revival of batchrender xml patch
by Phyllis Smith 29 Apr '26

29 Apr '26

Starting a new thread for a subject in the middle of recent email titled "Failed to compile" on Apr 21, 2016 where Andrea wrote: > Do you have any patches you'd like me yo try out, from the ones you've > created recently? > Andrew responded: > I think I do not have new patches, only old and again controversial > patch for batchrender batch file ? > > Right now if you point batch render function from command line to > non-xml file Cin will chew first, fail later. I added check hopefully > preventing this from happening at least on non-xml files (you can > still shoot your xml file with this gun) > > It still compiles ... but I did not test it recently :( > > cat > /home/guest/botva/src/cinelerra-git/cin-5/batchrender_postmerge_xml_check.diff > | patch -p1 I think I found the original thread but not sure about controversy: https://www.mail-archive.com/cin@lists.cinelerra-gg.org/msg02349.html Maybe not controversial anymore and it does fix a problem so any succinct clarification of issue or should we just apply the patch as attached?

3 2

Add dlfcn folder to system installed folders
by Andrew Randrianasulu 26 Apr '26

26 Apr '26

Noticed it was missing from system installs. Now picking syslib in BlendAlgebra opens folder with preinstalled programs.

2 1

Failed to compile
by Andrea paz 26 Apr '26

26 Apr '26

I tried compiling CinGG from Git without using any patches. I wasn't able to do it; I'm not sure if it's because of libaom or something else. Here's a link to the log. Maybe I need to use some patches? I haven't been able to keep up with the latest developments, so I'm pretty confused about what to do. https://limewire.com/d/qteft#dqNRnvN80N

3 9

batchrender
by Andrea paz 21 Apr '26

21 Apr '26

> Right now if you point batch render function from command line to > non-xml file Cin will chew first, fail later. I added check hopefully > preventing this from happening at least on non-xml files (you can > still shoot your xml file with this gun) I'm not sure if I understand what to do. I'm getting these results: Without the patch: ./cin -r prova_1.rc [plain text, no xml file] [...] ** rendered 0 frames in 0.000 secs, 0.000 fps Session time: 0:00:00 Cpu time: user: 0:00:00.118 sys: 0:00:00.043 ./cin -r expanders.txt [plain text, no xml file] [...] ** rendered 0 frames in 0.000 secs, 0.000 fps Session time: 0:00:00 Cpu time: user: 0:00:00.111 sys: 0:00:00.034 With the patch: ./cin -r expanders.txt [...] Not XML file!

2 3

compiling on freeBSD 14.0 still works
by Andrew Randrianasulu 16 Apr '26

16 Apr '26

But I think new pkgsrc (newer than nov 2023) might introduce some errors ? There is link to freeBSD bugzilla with my patches for freeBSD's pkgsrc from Nov 2023 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275374 I think they need some updating because address from where fetch sources changed, not to mention we updated our codebase a bit since that time (even if for non-thirdparty build this means little) NetBSD also works and I pushed update to their own version of pkgsrc-wip If anyone uses or just plays with those two BSDs they can test current git too (BSD use separate versioning for base set like kernel/utilites/compiler/X and user packages from pkgsrc - so base can be 14.0 but userspace vary wildly)

1 0