February 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

AgingTV plugin issue
by Phyllis Smith 26 Apr '24

26 Apr '24

(ometimes I just can not stop myself and just had to look at AgingTV.) I think I found the problem. If everything is unchecked and then one of the 3 items of Scratch, Pits, or Dust is checked BUT set to zero, you can still see that item in the compositor. Grain is either on or off and works as expected. The good news is that at least you can designate which type of aging you want, be it grain, scratch, pits, dust, or all or none. I will log a BT on this in case anyone wants to look at it in the future.

3 7

Fwd: Chromakey + blur testcase from IgorV
by Andrew Randrianasulu 27 Feb '24

27 Feb '24

---------- Forwarded message --------- From: Andrew Randrianasulu <randrianasulu(a)gmail.com> Date: Thu, Feb 22, 2024 at 2:19 AM Subject: Chromakey + blur testcase from IgorV To: Phyllis Smith <phylsmith2017(a)gmail.com> oh, it weights 1.4 mb, so not for list ... I think swapping effects relative to cin-cv makes image in compositor more like it was supposed to be but still. even if I disable chromakey - blur behaves strange, like rounding unprocessed (processed as black?) transparency into image ..? ===== https://drive.google.com/file/d/1kqt4bfy53drwQqOvD5RIJ1E7UWeJNF1A/view?usp=… hopefully uploaded to gdrive for everyone to test/see ....

4 20

disable a_key in blur.C harder
by Andrew Randrianasulu 26 Feb '24

26 Feb '24

At this point I am not sure if best course of action to disable it harder or restore it ... but I hope attached patch at least visually restores strange mess we see by default now in test project.

1 0

Ghosts from the shell!
by Andrew Randrianasulu 23 Feb '24

23 Feb '24

IgorV pointed out that while our manual still describes multiple projector keyframes/boxes in compositor it doesn't (reliably?) work this way, namely I think I created second box somehow but can't reproduce :) https://cinelerra-gg.org/download/CinelerraGG_Manual/Compositor_Keyframes.h… "Move the projector slightly in the compositor window to create a keyframe. Then go forward several seconds. Move the projector a long distance to create another keyframe and emphasize motion. This creates a second projector box in the compositor, with a line joining the two boxes. The joining line is the motion path. If you create more keyframes, more boxes are created. Once all the desired keyframes are created, disable automatic keyframe mode." small video describing how it worked in cinelerra-cv 1.2.1 using old dynebolic 1.4 iso https://m.youtube.com/watch?v=08UCImr82CE I wonder how "long" must be long distance? offscreen? tried this, also with enlarged projector range .... no two boxes! I can't even see this behavior in cincv 2.3.* from 2017, but may be I am doing it wrong for all versions?

3 5

Possibly better conversion quality at 2x speed/ bitrate and 25fps/ 50 fps
by Terje J. Hanssen 20 Feb '24

20 Feb '24

Thirty years ago I tape recordered some hundreds of old genealogy photos, which I now plan to convert from SD-DV files to burn on DVD video discs. The camcordings were made with fade in/out, zoom closeups and pan effects, which fit well at 2x playback speed and with additional pause/play navigation on DVD videos. Signal/noise at 2x speed with same fps and bitrate (halph of the fps are dropped), should result in output with 1/2 playback duration and equivalent quality as normal speed. Yet I wonder if it possible in some way to achieve better quality if also 2x bitrate and fps are possible to utilize temporarily as a better quality base (downsampling), even if DVD video limits the fps and bitrate? Here are my test samples so far: du -sh dv95* 1) 2,0G dv95.dv (input source) 2) 1,1G dv95_2x_25fps.dv 3) 2,0G dv95_2x_50fps.dv 4) 218M dv95_2x_25fps.mpg 5) 218M dv95_2x_50fps.mpg 1) ffprobe -hide_banner dv95.dv (source DV, Duration: 00:09:56.48) [dv @ 0x55d65d6ca080] Estimating duration from bitrate, this may be inaccurate Input #0, dv, from 'dv95.dv': Metadata: timecode : 00:00:00:00 Duration: 00:09:56.48, start: 0.000000, bitrate: 28800 kb/s Stream #0:0: Video: dvvideo, yuv420p, 720x576 [SAR 16:15 DAR 4:3], 28800 kb/s, 60k fps, 25 tbr, 60k tbn Stream #0:1: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s ffmpeg conversions using the FFmpeg setpts filter http://trac.ffmpeg.org/wiki/How%20to%20speed%20up%20/%20slow%20down%20a%20v… 2) ffmpeg -i dv95.dv -vf "setpts=0.5*PTS" -an dv95_2x_25fps.dv ffprobe -hide_banner dv95_2x_25fps.dv [dv @ 0x5582eb685080] Estimating duration from bitrate, this may be inaccurate Input #0, dv, from 'dv95_2x_25fps.dv': Metadata: timecode : 00:00:00:00 Duration: 00:04:58.32, start: 0.000000, bitrate: 28800 kb/s Stream #0:0: Video: dvvideo, yuv420p, 720x576 [SAR 16:15 DAR 4:3], 28800 kb/s, 60k fps, 25 tbr, 60k tbn 3) I wonder why the Duration is still 00:09:56.52 here ? ffmpeg -hide_banner -i dv95.dv -r 50 -vf "setpts=0.5*PTS" -an dv95_2x_50fps.dv ffprobe -hide_banner dv95_2x_50fps.dv [dv @ 0x55fe0b5bb080] Estimating duration from bitrate, this may be inaccurate Input #0, dv, from 'dv95_2x_50fps.dv': Metadata: timecode : 00:00:00:00 Duration: 00:09:56.52, start: 0.000000, bitrate: 28800 kb/s Stream #0:0: Video: dvvideo, yuv420p, 720x576 [SAR 16:15 DAR 4:3], 28800 kb/s, 60k fps, 25 tbr, 60k tbn 4) ffmpeg -hide_banner -i dv95.dv -f dvd -target pal-dvd -aspect 4:3 -vf "setpts=0.5*PTS" -an dv95_2x_25fps.mpg ffprobe -hide_banner dv95_2x_25fps.mpg [mpeg @ 0x55a330208080] start time for stream 0 is not set in estimate_timings_from_pts Input #0, mpeg, from 'dv95_2x_25fps.mpg': Duration: 00:04:58.32, start: 0.540000, bitrate: 6115 kb/s Stream #0:0[0x1bf]: Data: dvd_nav_packet Stream #0:1[0x1e0]: Video: mpeg2video (Main), yuv420p(tv, progressive), 720x576 [SAR 16:15 DAR 4:3], 25 fps, 25 tbr, 90k tbn Side data: cpb: bitrate max/min/avg: 9000000/0/0 buffer size: 1835008 vbv_delay: N/A Unsupported codec with id 98312 for input stream 0 5) ffmpeg -hide_banner -i dv95.dv -f dvd -target pal-dvd -r 50 -vf "setpts=0.5*PTS" -an dv95_2x_50fps.mpg ffprobe -hide_banner dv95_2x_50fps.mpg [mpeg @ 0x555e13da2080] start time for stream 0 is not set in estimate_timings_from_pts Input #0, mpeg, from 'dv95_2x_50fps.mpg': Duration: 00:04:58.26, start: 0.520000, bitrate: 6118 kb/s Stream #0:0[0x1bf]: Data: dvd_nav_packet Stream #0:1[0x1e0]: Video: mpeg2video (Main), yuv420p(tv, progressive), 720x576 [SAR 16:15 DAR 4:3], 50 fps, 50 tbr, 90k tbn Side data: cpb: bitrate max/min/avg: 9000000/0/0 buffer size: 1835008 vbv_delay: N/A Unsupported codec with id 98312 for input stream 0

2 2

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