June 2026 - Cin - Cinelerra-GG Mailing Lists

Suddenly Cinelerra keeps crashing
by Evaessen＠ziggo Nl 14 Jul '26

14 Jul '26

4 6

Updated June 30, 2026 AppImages
by Phyllis Smith 30 Jun '26

30 Jun '26

There are new AppImages available at: https://download.cinelerra-gg.org With the updated packages of the same GIT source by Andrey at: https://github.com/einhander/cin-gg-packages/releases The 5 updated libraries were only minimally tested, but the changes to them was also minimal. As always, it is preferred to have at least 2 people verify modifications. *********** Release Notes for June 30, 2026 GIT for Cinelerra-GG has the following changes from 06/01/2026-06/30/2026 *Updated libraries* include: a52dec from 0.7.4 to v0.8.0 fftw from 3.3.10 to 3.3.11 giflib from 5.2.2 to 6.1.3 openjpeg from 2.5.2 to 2.5.4 libogg from 1.3.5 to 1.3.6 *Andrew-R work*: Fixed big endian sound output for alsa and pulseaudio. Previously only little endian was recognized. Changes that were needed for ppc/g5: - Fixed mjpegtools build on ppc g5 and gcc 15.2.0. - Disabled altivec in x265 because detection was broken on g5. - Added g++11 threading to x265 by barracuda156 which fixed linking on ppc32. Checked in mods for batch rendering, batchrender_postmerge_xml_check.diff, which fixes a rare but devastating issue that causes corruption to the non-XML file being targeted. This could have happened when running a command line render as well as batch rendering and make the mistake of using a file other than the XML project file. Problem with mxf_avcintra_100.mxf render format reported in *BT #677 by Quintao*, which was working in FFmpeg 7.x but failing with FFmpeg 8.x, has been fixed by adding “g=1” to the render format. The “g” stands for “group of picture size (GOP)” so there is no grouping and all frames are keyframes. *Andrew/Andrea* tested and researched requirements of mxf and passed along this information which resulted in additional mxf render format changes and comments: - the 6 mxf_DNxHR... and dv.mxf also need to use “g=1” since all frames are keyframes. - mxf_openjpeg2000.mxf has had openjpeg2000 encoder changed to ffmpeg jpeg2000 encoder because libopenjpeg is being removed. - mxf_h264_b.mxf needs to use g=25 as the default because ffmpeg's 250 now causes muxing errors. - all 10 mxf render formats have had a comment added that at least by ffmpeg 8.1, only an audio samplerate of 48000 valid.

1 0

Updated some libraries and checked into git
by Phyllis Smith 28 Jun '26

28 Jun '26

The following libraries have been updated and mxf_avcintra_100.mxf and mxf_h264_b.mxf minor fixes applied. > a52dec from 0.7.4 to v0.8.0 > fftw from 3.3.10 to 3.3.11 > giflib from 5.2.2 to 6.1.3 > openjpeg from 2.5.2 to 2.5.4 > libogg from 1.3.5 to 1.3.6 > Built/compiled on Fedora 44/32, Debian 9.1 32-bit, and Ubuntu 16. Tested on Fedora 32 by loading a video/audio where I had one and created for gif, jpeg, and ogg.

2 4

ffv1 in mkv in ffmpeg 8.1 seems to be busted :(
by Andrew Randrianasulu 28 Jun '26

28 Jun '26

As Andrea noted ffv1.mkv preset no longer works, file encodes but crash cingg on reimport. ffmpeg itself behaves .. strange ffmpeg -i zeldaHQ.flv -c:v ffv1 -default_mode 0 -frames 100 mkv_tedt.mkv -loglevel debug only muxes 3 frames? [matroska @ 0xb400007a8916a870] stream 1 end duration = 336 [AVIOContext @ 0xb400007a59164790] Statistics: 33361 bytes written, 0 seeks, 1 writeouts [out#0/matroska @ 0xb400007a39163010] Output file #0 (mkv_tedt.mkv): [out#0/matroska @ 0xb400007a39163010] Output stream #0:0 (video): 3 frames encoded; 3 packets muxed (27141 bytes); [out#0/matroska @ 0xb400007a39163010] Output stream #0:1 (audio): 112 frames encoded (7147 samples); 19 packets muxed (1905 bytes); ---- but same command with -an (no audio) muxes all 100 frames ?! vp8/vp9/theora mkv profiles seems to be unaffected

2 3

Offtopic : powermac G5 DC 2.0 GHZ vs libvpx-vp9
by Andrew Randrianasulu 28 Jun '26

28 Jun '26

Sometime when I was sleeping test encoding finished: frame= 7045 fps=0.3 q=27.0 size= 42240KiB time=00:04:53.83 bitrate=1177.6kbits/s speed=0.0124x el[out#0/webm @ 0x8c273d0] video:38966KiB audio:3366KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: 0.390187% frame= 7073 fps=0.3 q=21.0 Lsize= 42498KiB time=00:04:55.00 bitrate=1180.1kbits/s speed=0.0125x elapsed=6:33:50.16 yeah, 6 h 33 min 50 seconds for 4:55 clip (720p, 24 fps, 8 bpc, 4:2:0, vp9) x265 was going at 0.7 fps but then Termux with ssh session without terminal software like screen was killed by memory pressure from Chrome here, so encoding not finished properly (but fps reading was quite consistent along whole vid for various codecs) x264 was doing at 5.08 fps (video only) - altivec rule! mpeg2video was zipping at 24 fps or even 26 if I set g=1 mjpeg/xvid both were slower at 17-14 fps. asv1 was champion (for being simplest yuv420 only encoder) at 30 fps. libaom-av1 failed to produce even single frame in minute, so I killed it. on x86, x86-64 and arm64 situation is better due to SIMD acceleration, but you see the trend. if av2 continued in this direction - we can set movie to encode and put it into time capsule with writing "open in year 2050" ;)

2 1

Nite about MXF sample rate limitations
by Andrew Randrianasulu 28 Jun '26

28 Jun '26

As of ffmpeg 8.1.2 I see this if I try to encode video with 22khz audio into mxf container [mxf @ 0xb4000075eef6e230] only 48khz is implemented in red. Can you pretty please add comment line into each mxf profile saying "at least ffmpeg 8.1 only implement audio samplerate 48khz for mxf, be sure to set project's samplerate to 48000" Yeah, a bit wordy. But I bet we will forgot about this little detail otherwise ... Also, may be tweak avcintra-100 mxf profile comment AGAIN noting that yeah, you can delete b=100m line but result will be not spec-compliant, better tweak mxf_h264_b profile instead?

1 0

Possible mxf profile fixes
by Andrew Randrianasulu 27 Jun '26

27 Jun '26

I think my patch "Do not set our options for mxf muxer" is not needed really, because it was different set of errors and it only "worked" because I failed to properly change profiles during my testing on Termux? I'll keep it around just in case. I tried to add g=1 to our DNxHR/dv mxf profiles too just in case, accidently added two .seg profiles I was testing some time ago (for segmented muxing) Changed openjpeg mxf profile to use internal jpeg2000 encoder, libopenjpeg based one is seems to be gone from ffmpeg (note decoder may still be there) Added g=25 to our mxf_h264_annex_b profile, may be it will work after this change? Not really tested yet, too many machines (real and virt) trying to do many things at once.

3 11

Mailing lists no send email to me
by Igor BEGHETTO 27 Jun '26

27 Jun '26

Hi, I am seeing that there are messages in the Mailing Lists Web Archive that I haven't received (from July 1). The last message I received is dated May 31. Into the Spam there are not messages. Van you help me about? Thanks! IgorBeg PS: And this my message is a test to see if it will be send to me from the mailing lists.

3 7

Re: render problem
by Andrea paz 26 Jun '26

26 Jun '26

Using CinGG compiled with your patch, I ran some tests with an H.264/MP4 source file and an audio track. When I set g=1 and b=100M, I keep getting the same errors. If I don't render the audio and set g=1 and b=100M, everything works fine. The resulting file is 2.1GB. When I don't render the audio and don't use those two parameters (i.e., using the original preset), the rendering works (file size is 25.3MB), but I get a long list of warnings: file:/home/paz/test_avc.mxf err: Not yet implemented in FFmpeg, patches welcome FFStream::encode_frame: encode failed. file: /home/paz/test_avc.mxf err: Not yet implemented in FFmpeg, patches welcome FFMPEG::mux_video err: Operation not permitted FFStream::write_packet: write packet failed. file:/home/paz/test_avc.mxf err: Not yet implemented in FFmpeg, patches welcome FFStream::encode_frame: encode failed. file: /home/paz/test_avc.mxf err: Not yet implemented in FFmpeg, patches welcome FFMPEG::mux_video err: Operation not permitted FFStream::write_packet: write packet failed. The difference in size makes me think that our mxf_avcintra_100.mxf preset is actually of the LongGOP type. I found some old FFmpeg bugs (not in FFmpeg 8, though) related to LongGOP sources that caused problems when converting to MXF. I also found other old bugs that mentioned that transcoding to MXF could cause problems due to Annex-B (which I don’t know what it is). For example: https://patchwork.ffmpeg.org/project/ffmpeg/patch/AM7PR03MB66600B2742E305A9… Could they be related to our case, even though we're using FFmpeg 8? P.S.: I'm sorry, but I won't be around for a couple of days.

2 1

render problem
by Andrea paz 25 Jun '26

25 Jun '26

On MantisBT, Quintao filed a bug report (BT 677) because he can't render avc_intra_100 in MXF format. He can, however, use MXF with DNxHR. I, on the other hand, can't use any MXF presets, but I can render avc_intra_100 in MOV format. Are any of you able to render in MXF?

3 11