January 2024 - Cin - Cinelerra-GG Mailing Lists

FranceBB's LUT collection
by Andrew Randrianasulu 17 May '25

17 May '25

forum https://forum.doom9.org/showthread.php?t=176091 it says those LUTs should be usable for ffmpeg's lut3d and therefore for CinGG? github (each *.cube can be several mb's big) https://github.com/FranceBB/LinearTransformation author says they were verified on professional equipment... list includes PAL and NTSC variants for rec. 601....

3 6

I tried to add AVC-Intra 100 output profiles
by Andrew Randrianasulu 08 May '25

08 May '25

But not sure if I did this correctly. https://en.wikipedia.org/wiki/AVC-Intra says for AVC-Intra 100: AVC-Intra 100: nominally 100 Mbit/s, size of each frame is fixed CAVLC entropy coding only. All formats are High 4:2:2 Intra Profile, Level 4.1 4:2:2 chrominance sampling frames are not scaled and yeah, this French-language pdf actually says the same: https://web.archive.org/web/20110720215759/http://www.ficam.fr/upload/docum… 50M 100M Standard MPEG-4 part10 AVC/H.264 Profile High 10 Intra High 4:2:2 Intra Level Level 3.2/4.0 Level 4.1 Resolution 1440x1080 / 960x720 1920x1080 / 1280x720 Sampling 4:2:0 4:2:2 Bit rate 54Mbps 111Mbps Block size Y: 8x8, C: 4x4 Intra Prediction Y: 9mode, C: 4mode MBAFF Yes De-block filter No Slice/frame 10 Entropy coding CABAC CAVLC so, I looked up ffmpeg cmd line https://trac.ffmpeg.org/ticket/3597 ffmpeg -v info -i /mnt-data/backup4/vol0/export/CUHK\ 2014-1/V017b.mov -vcodec libx264 -intra -pix_fmt yuv422p10le -vb 100M -x264opts avcintra-class=100 -x264opts colorprim=bt709 -x264opts transfer=bt709 -x264opts colormatrix=bt709 -threads 4 -acodec copy V017b-ffmpeg-git-avcintra100.mov Huh, said I and entered those params in opts file, actually in two files (mp4 and mov containers) mov libx264 cin_pix_fmt=yuv422p10le flags -global_header keyint_min=0 x264-params=keyint=0:colorprim=bt709:transfer=bt709:colormatrix=bt709 avcintra-class=100 bufsize=100000000 level=4.1 mp4 libx264 cin_pix_fmt=yuv422p10le flags -global_header keyint_min=0 x264-params=keyint=0:colorprim=bt709:transfer=bt709:colormatrix=bt709 avcintra-class=100 bufsize=100000000 level=4.1 both for progressive content, for interlace you must add some more flags: https://lists.ffmpeg.org/pipermail/ffmpeg-user/2017-January/035049.html -flags +ildct+ilme -x264opts interlaced=1 Also, there is still lack of (GUI) user notification if file writing failed due to NO SPACE on device :} FFStream::write_packet: write packet failed. file:/dev/shm/avci_new.mp4 err: На устройстве не осталось свободного места FFStream::encode_frame: encode failed. file: /dev/shm/avci_new.mp4 err: На устройстве не осталось свободного места FFStream::flush failed :file:/dev/shm/avci_new.mp4 err: Операция не позволена Render::render_single: Session finished. ** rendered 273 frames in 85.585 secs, 3.190 fps Render::render_single: Session finished. ** rendered 273 frames in 85.485 secs, 3.194 fps Render::render_single: Session finished. ** rendered 273 frames in 82.176 secs, 3.322 fps Profile sort of assumes you set project to some supported resolution, framerate, etc, otherwise libx264 will fail with console error message..... I found some talk about AVC-Ultra, there even was patch for x264, but it was not merged: https://mailman.videolan.org/pipermail/x264-devel/2015-September/011412.html Also, I think sound must be uncompressed, but I'm not sure.

2 5

offtopic: Quantel boxes
by Andrew Randrianasulu 26 Aug '24

26 Aug '24

Because I monitor mame WIP thread I saw some news about Quantel Paintbox emulation in MAME (0) and then I randomly followed some links to other Quantel systems Like HAL (basically like hardware compositor) http://dexterslab2013.blogspot.com/2018/03/quantel-hal-video-compositing-sy… 99 layers of SD images or video, up to 15 min storage on 20 disk array! https://m.youtube.com/watch?v=4k15hpeGzBA if you have half of hour you can watch this demo from 1997. Biggest thing so far for me? We are free to use old-fashioned optical effects in front of real camera too :) (0) - https://forums.bannister.org/ubbthreads.php?ubb=showflat&Number=120292&page…

2 2

New release update
by Phyllis Smith 19 Jul '24

19 Jul '24

October 2022 end of month new release AppImages now available. This includes a fix for a minor ffmpeg 5.1 security flaw that Andrew discovered and made us a patch for. Full release notes at: https://cinelerra-gg.org/download/releasenotes.pdf . ************ October Release Notes update ****************** *Security flaw in FFmpeg 5.1* was discovered and Andrew forwarded the patch for us to use. A *Direct Copy speed-up* has been added for EXR and PPM sequences that Andrew found. Tiny corrections and addition to Cinelerra_factory presets and plugin.opts. Newer versions of Ubuntu require an additional package install for *bld_prepare.sh as Goat found*. The Manual has had another section added, *Alternative Views of Overlay Modes*, which presents a more “real world” usage display of the overlay modes using a color/black & white gradient + video.

6 37

DAR, PAR and SAR, again
by Andrea paz 17 Feb '24

17 Feb '24

I am opening a new post because the previous one, for me, was becoming too confusing. I quote Terje's latest email: ============================================================== Well, I have prioritized more to understand what happends than interprete the somewhat ambiguous definitions. (the order of the factors is indifferent). https://stackoverflow.com/questions/18877243/why-ffmpeg-print-sar-instead-o… I think of SAR in the FFmpeg output as a correction factor for the recordered picture frame format resolution (Wp), to get the desired output display resolution (expanded Wd with square px) at a given DAR, (or in opposite order). I found a useful table at ffmpeg-user that contains information for practically all SD and HD video formats. Maybe something for the manual? https://www.mail-archive.com/[email protected]/msg27522.html display DAR picture PAR SAR = DAR/PAR =========== ==== =========== ==== ===== 16:9-2160: 3840 x 2160 16:9 : 3840 x 2160 16:9 : 1:1 4:3-2160: 2880 x 2160 4:3 : 2880 x 2160 4:3 : 1:1 16:9-1080: 1920 x 1080 16:9 : 1920 x 1080 16:9 : 1:1 4:3-1080: 1440 x 1080 4:3 : 1440 x 1080 4:3 : 1:1 16:9-576: 1024 x 576 16:9 : 720 x 576 5:4 : 64:45 4:3-576: 768 x 576 4:3 : 720 x 576 5:4 : 16:15 16:9-480: 853 x 480 16:9 : 720 x 480 3:2 : 32:27 4:3-480: 640 x 480 4:3 : 720 x 480 3:2 : 8:9 [...] =========================================================== My God, I feel like giving up.... The following is my opinion (indeed, my delirium!). The table is wrong (for ffmpeg!) because it uses PAR. As is also stated in the thread you cited: "> PAR (picture aspect ratio [1]) [noun]: 1, The horizontal-to-vertical > size [3] ratio (H:V, e.g. 5:4, 3:2) for pictures. get rid of this one altogether, because nothing in FFmpeg use it, and rightly, because nobody should use it." Instead of calling it PAR, it should be considered simply the aspect ratio of W x H of the input. That is, the W/H of the formula DAR=W/H x SAR (and not DAR=PAR x SAR). PAR and SAR cannot be different since they are the same thing (i.e. the shape of a single pixel, as seen from the image https://stackoverflow.com/questions/18877243/why-ffmpeg-print-sar-instead-o… that you mentioned). In practice, in my opinion, the PAR in the table is nothing more than the SAR meant as Storage aspect ratio; in fact, the author of the table defines it as a Picture aspect ratio, which is a frame aspect ratio and not a pixel aspect ratio. It seems to me that in an effort to be precise, it creates even more confusion. Instead, the SAR in the table is nothing more than the S(ample)AR ( = P(ixel)AR). If you think I am crazy to keep up with these definitions, you are right! The formula DAR = PAR x SAR was convenient and simple, however, ffmpeg decided to use "samples" instead of pixels and so PAR should no longer be used. That is why I was thinking of removing all reference to PAR. The trouble is that if one searches around one always finds PAR and never SAR meant as "sample a.r."; including many tutorials on ffmpeg. The sample concept is derived from analog video signals and is encoded in the standards BT. 601 and Digital. It refers to horizontal scan lines (in MHz) and not simply pixels. From Wikipedia: "analog video does not have pixels, but rather a raster scan, and thus has a well-defined vertical resolution (the lines of the raster), but not a well-defined horizontal resolution, since each line is an analog signal." S(ample)AR was created precisely to adapt the analog concept to the digital world. To further explore the concept of sample: https://web.archive.org/web/20140816103129/http://lipas.uwasa.fi/~f76998/vi… Your definition of SAR as a correction factor is right and I will use it in txt. Thank you for the cue. To summarize: in the digital domain we can use the concept of S(ample)AR when we are dealing with digital anamorphic formats (for example, when transcoding to a format that has different aspect ratio). But the most frequent use is in "standard-definition television or with DV, HDV and a few other formats. SAR is used via the formula DAR = SAR x (W/H), where SAR is the conversion factor between anamorphic Input and Output. Perhaps the clearest treatment is as follows: https://encodingwissen.de/hintergrund/videobild/anamorph/itu-r-bt601/ It is in German and therefore needs to be translated (the Italian translation is not very good...). They seem to me to be similar concepts to Raffaella Traniello's guide. As an additional (my) confusion, in CinGG we also have the W/H Ratio parameters, which are simple multipliers but, if set only one of them (with values of the classic aspect ratios, 4:3; 16:9, etc.) and leaving the other one at 1, they act as a real SAR even though they are not... @Andrew In CinGG/Info-->Detail is the data reported taken using ffmpeg? In other words: does CinGG use SAR like ffmpeg or does it have an even different way? PS: In my opinion, it would be better to change W/H Ratio to "W/H multiplier"

5 49

LV2 with Python 3.12 patches
by Phyllis Smith 09 Feb '24

09 Feb '24

I am hoping that Andrea can test the attached patches for LV2 which makes it work on Python 3.12 on Fedora39. Need testing to compare to make sure sounds correct between Before patches and After patches - especially the Calf plugins but other LV2 plugins too. Do NOT need 3.12 python because I want to make sure it works currently and I have already tested on Fedora 39 with Python 3.12. Before the patches, CinGG would not build so even if the patches are not 100% correct for 3.12, at least it will still build. No other changes needed -- just put these 6 small patch files in the cinelerra thirdparty/src subdirectory and do a full rebuild.

2 3

rusticl and DaVinch Resolve (round N)
by Andrew Randrianasulu 05 Feb '24

05 Feb '24

https://chaos.social/@karolherbst/111827770287551625 ===== Some rusticl info for AMD users Once this MR lands (and appears in 23.3 as well) Davinci Resolve should "just work" with `RUSTICL_ENABLE=radeonsi` set in the env. It already works without it on Navi GPUs, this MR just fixes a crash on older ones. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27295 ==== quote ends ===

2 5

qctools, sonic lineup
by Andrew Randrianasulu 02 Feb '24

02 Feb '24

Sorry Terje if I was too rough in my previous email. I am definitely very much want to have as error-free transcode (and as little transcode as possible in general) as you, for same reason. I am not sure you can absolutely trust ffmpeg for not doing any conversion by default. For example 6.1 seems to upconvert 16 bit audio when you select dvd_pcm audio output. /dev/shm/ffmpeg/ffmpeg -i /home/guest/CIN51.mp4 -target pal-dvd -c:a pcm_dvd -f dvd /dev/shm/cin51.mpeg ah, it only does so if decoder output floats by default (aac, may be mp3 too?) for dv it was 16 to 16. Not sure how good internal ffmpeg muxer for dvd file creation, but you probably can test this by reusing cingg created audio and video files from dvd master. I have few more ideas to test and smart-up our bash script so it will use wav output + sox + mplex automatically if wav or pcm file was detected in output directory (so you can set easy wav output and do not care about BE pcm file and its extension), but again I need some time to test this. I was looking for some quality control tools and found qctools and this post specifically on stackexchange https://sound.stackexchange.com/questions/40222/show-the-differences-betwee… it mentions program named Sonic Lineup, hopefully easy (and working on Linux) way to compare two audio files. Not sure if it supports dvd audio tho .... https://sonicvisualiser.org/sonic-lineup/index.html qctools are more aiming at video quality metrics, just build their latest tool: https://mediaarea.net/QCTools I am sure you can get Appimage or even rpm from their site.

2 7

Audio out of sync when rendering MP4s
by Matteo Bini 01 Feb '24

01 Feb '24

Hello Cinelerra GG developers, I've found a strange behaviour in this great editing software. When I render my project, sometimes the audio is out of sync. Not all the audio, but from a certain point, from half of the video the audio is out of sync and it gets worst the more we get to the end of the video. It's like latency piles up. I've only done MP4 renderings so far. My idea, but I don't know how to demonstrate it, is that ffmpeg doesn't know how to render audio and video in sync, when there's some audio that is not aligned on frames. Since I do a lot of precise audio editing in my project, there are some audio cuts that are not aligned on frames. It's not a big problem, I just wanted to let you know. The solution is very simple: render only the video track, then render the audio track in WAV and then mux them together with ffmpeg, copying the video track and encoding the audio one. This way the video is perfectly in sync with the audio. The strange thing is that, when I watch my project from the compositor window, audio and video are in sync. Thank you for making Cinelerra GG a really great free software. -- Matteo Bini

5 5

OpenGL texture limit 0
by Andrea paz 01 Feb '24

01 Feb '24

There is a request in the forum for an explanation of a warning window. Is anyone able to understand the problem? https://www.cinelerra-gg.org/forum/forum-miscellaneous/opengl-texture-limit…

2 1