July 2020 - Cin - Cinelerra-GG Mailing Lists

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

Re: [Cin] cinelerra-gg on ppc64el
by Daniel Reurich 02 Apr '22

02 Apr '22

Hi I've made some significant progress in getting the build going - and will have some patches to drop that solve some issues for builds using system libs and non x86 based archs. The current issue I'm stumbling on is that configure doesn't detect the systems liba52 and a52dec/a52.h header files as installed. This results in a linking failure during the build of libzmpeg Any thoughts on how I might overcome that? Thanks, Daniel. -- Daniel Reurich Centurion Computer Technology (2005) Ltd. 021 797 722

3 5

Blu-ray encoding again
by Andrew Randrianasulu 16 Oct '20

16 Oct '20

Hi! With Marton's patches from git clone -b mpegts https://github.com/cus/ffmpeg/ and CinGG compiled with ffmpg.git I _nearly_ got some rendering. But option files still needed some modification For example I was running into x264 errors. cin Cinelerra Infinity - built: Nov 14 2019 14:17:05 git://git.cinelerra-gg.org/goodguy/cinelerra.git (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams (c) 2007-2019 cin5 derivative by W.P. Morrow aka goodguy Cinelerra is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. There is absolutely no warranty for Cinelerra. Device type none is not supported. Available device types: vdpau cuda vaapi opencl Device type none is not supported. Available device types: vdpau cuda vaapi opencl Device type none is not supported. Available device types: vdpau cuda vaapi opencl Device type none is not supported. Available device types: vdpau cuda vaapi opencl [libx264 @ 0xe9a3c4c0] interlace + weightp is not implemented [libx264 @ 0xe9a3c4c0] using mv_range_thread = 88 [libx264 @ 0xe9a3c4c0] NAL HRD parameters require VBV parameters [libx264 @ 0xe9a3c4c0] using SAR=1/1 [libx264 @ 0xe9a3c4c0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX XOP FMA3 BMI1 [libx264 @ 0xe9a3c4c0] profile High, level 4.1 Device type none is not supported. Available device types: vdpau cuda vaapi opencl FFMPEG::encode_activate: write header failed /dev/shm//bd_20191114-163217/bd.m2ts err: Недопустимый аргумент Render::render_single: Session finished. Device type none is not supported. Available device types: vdpau cuda vaapi opencl some of them were fixed by applying parameters from http://www.x264bluray.com/home/1080i-p [libx264 @ 0xe0609640] using mv_range_thread = 88 [libx264 @ 0xe0609640] using SAR=1/1 [libx264 @ 0xe0609640] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX XOP FMA3 BMI1 [libx264 @ 0xe0609640] HRD bitrate: 40000000 bits/sec [libx264 @ 0xe0609640] CPB size: 30000000 bits [libx264 @ 0xe0609640] profile High, level 4.1 [SWR @ 0xcfba81c0] Using fltp internally between filters Device type none is not supported. Available device types: vdpau cuda vaapi opencl Render::render_single: Session finished. but there still warning at ffmpeg site about deprecation of x264opts: https://trac.ffmpeg.org/wiki/Encode/H.264 Warning: Do not use the option x264opts, as it will eventually be removed. Use x264-params instead. --- /usr/share/cin/ffmpeg/video/bluray.m2ts 417/417 100% bluray libx264 bluray-compat=1 id=0x1011 level=41 bf=2 fake-interlaced=1 bitrate=40000 slices=4 sar=1:1 # vbv-maxrate=40000 # vbv-bufsize=30000 refs=3 cin_pix_fmt=yuv420p color_range=mpeg colorspace=bt709 color_trc=bt709 color_primaries=bt709 profile=high preset=medium flags=+cgop # must be last for bdcreate.C x264opts keyint=25:min-keyint=4:qpmin=3:qpmax=33:qp_step=4:merange=8:vbv-maxrate=40000:vbv-bufsize=30000 --- /usr/share/cin/ffmpeg/format/bluray 129/129 100% mpegts mpegts_m2ts_mode=1 mpegts_start_pid=1024 mpegts_pmt_start_pid=256 muxrate 1 #sdt_period=-1 packetsize 2048 preload 500000 But please note some x264 params actually should vary for interlaced or progressive, 25 vs 30 fps: 1080p Primary and Secondary Streams 1080p23.976 / 1080p24 x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 24 --open-gop --slices 4 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 1 -o out.264 input.file x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 24 --open-gop --slices 4 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 2 -o out.264 input.file NB: the following two streams are encoded using fake-interlaced mode. This allows the stream to be encoded progressively yet flagged as interlaced. 1080p25 x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 25 --open-gop --slices 4 --fake-interlaced --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 1 -o out.264 input.file x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 25 --open-gop --slices 4 --fake-interlaced --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 2 -o out.264 input.file 1080p29.97 x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 30 --open-gop --slices 4 --fake-interlaced --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 1 -o out.264 input.file x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 30 --open-gop --slices 4 --fake-interlaced --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 2 -o out.264 input.file 1080i Primary and Secondary Streams (assumes top field first) 1080i25 x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 25 --open-gop --slices 4 --tff --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 1 -o out.264 input.file x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 25 --open-gop --slices 4 --tff --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 2 -o out.264 input.file 1080i29.97 / 1080i30 x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 30 --open-gop --slices 4 --tff --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 1 -o out.264 input.file x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 30 --open-gop --slices 4 --tff --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 2 -o out.264 input.file so, keyint must be dynamically-selected, depending on profile you (user) choose, and fake_interlaced must be present for progressive encodings More on those constrains, refering same page: https://av.community/guides/encoding-video-for-blu-ray-using-h264-avc/ "8-bit (4:2:0) Colorspace is only allowed Main and High profiles are allowed Maximum 3 B-Frames is allowed NAL-HRD Type 2 capable encoder is needed" note, according to some comments around vbv-bufsize you can mux to DVD, so test this, too? "vbv-maxrate Maximum allowed bitrate. Depend of destination media, for normal BD Media, maximum settings is allowed (40000), while for DVD Media (eg BD-5 or BD-9) there is no maximum per Blu-Ray specification, but is strongly recommended that use less or equal to 15000, since DVD reading is slower."

3 3

Linux mint 20 Ulyana
by Gerd + Beatrix Elgert 01 Aug '20

01 Aug '20

Hello mint! Need the package /mint20 ulyana main Thks Gerd

2 2

Fwd: Error in compile
by Phyllis Smith 28 Jul '20

28 Jul '20

Am forwarding a discovery from Andrea about Cuda on Arch. Yesterday there was an update of Cuda (2GB), you can see that > something went wrong. > By default with-cuda is active; I had to put without-cuda to avoid errors. > "Val.log" I put it in BT #0000482, in case others wanted to see it too. > CinelerraGG is still at version 10 but the latest version Andrea reported on is version 11. It no longer supports compute-30 so GG has checked into GIT a mod to make it possible now to compile Cuda on Arch at the latest version.

2 1

Patch against interpolation bug in cinelerra/affine.C, interp.h
by Georgy Salnikov 20 Jul '20

20 Jul '20

Recently I accidentally found the following bug in Cinelerra-GG and created a patch to correct it. When trying to stabilize video with the 'Motion' plugin I got repeatedly a constantly accumulated clockwise rotation of the video frames (when tracking 'Previous frame same block') or twitching video (when 'Tracking single frame'). After some debugging and dumping temporary frames in PPM format I found that, for example, rotation of a frame to the angle of 0.000000 degrees actually results in its translation one pixel to the right and one pixel down. This was the reason for the Motion plugin to try constantly to rotate video about 0.25 degrees each frame. The actual location of this problem was in the Affine engine, namely in the used interpolation macros. The wrong expressions for displacements of the interpolated pixels lead to that, for example, that when the input and output points should coinside (which is the case for the 0 degree rotation), the X and Y of the pixel which are to be taken with the coefficient 1.0 become (tx-1,ty-1) instead of (tx,ty). Perhaps the bug in Affine could influence also other features in Cinelerra, but to observe such a subtle displacements in most of video editing scenarios looks not so easy. On the contrary, the accumulated rotation while motion stabilization makes it evident. In cinelerra/interp.h I corrected only the expressions for the integer coords and float displacements for the interpolated pixels. The main correction in cinelerra/affine.C (look in the patch attached) is at the lines 245-246: the processed frame block size was one pixel less both in horizontal and vertical directions. I have found only one other similar place in the code, namely in the 'Lens' plugin, and there the calculation of max x and y was correct. Additionally I'd propose to correct affine.C at the lines: 188 (perhaps an unportable method to compare a float variable with 0.0) 693 (looks like a definitely incorrect calculation of y1 for the package #0) The rest, commented out, are for debugging output only. This patch is against cin_5.1.20200430-src.tgz, I posted it to bugtracker as issue 479. Thanks for the attention Georgy _______________________________________________________________________________ Georgy Salnikov NMR Group Novosibirsk Institute of Organic Chemistry Lavrentjeva, 9, 630090 Novosibirsk, Russia Phone +7-383-3307864 Email sge(a)nmr.nioch.nsc.ru _______________________________________________________________________________

1 0

Fuzzy "Align Timecodes" checked into GIT
by Phyllis Smith 20 Jul '20

20 Jul '20

I ran out of time to document concerning BT 448 description, demo, and documentation. But here is a quick demo at: https://streamable.com/nwec0t The most IMPORTANT thing to know right now is that we had no "real" data to test this but only "manufactured" data. It would take video from preferably 3 cameras filming the same scene from different angles but not started at the same time AND cameras that are smart enough to supply "real" timecodes in the data. Here is the unfinished documentation: *New Feature – Align Timecode* New feature includes the following relevant parts: - Align Timecode under the Window pulldown - Clapperboard icon on the main timeline to set a timecode - Timecode option added to timebar choices (where you have hh:mm:ss, etc) - Time Code Start in the Resources window on the bottom of Info for the media (when set) - MMB on a track allows for Timecode option to display the timecode for that particular track Here are the comments from the code ; ) /* * 1) if the format context has a timecode * return fmt_ctx->timecode - 0 * 2) if the layer/channel has a timecode * return st->timecode - (start_time-nudge) * 3) find the 1st program with stream, find 1st program video stream, * if video stream has a timecode, return st->timecode - (start_time-nudge) * 4) find timecode in any stream, return st->timecode * 5) read 100 packets, save ofs=pkt.pts*st->time_base - st->nudge: * decode frame for video stream of 1st program * if frame->timecode has a timecode, return frame->timecode - ofs * if side_data has gop timecode, return gop->timecode - ofs * if side_data has smpte timecode, return smpte->timecode - ofs * 6) if the filename/url scans *date_time.ext, return date_time * 7) if stat works on the filename/url, return mtime * 8) return -1 failure */

3 2

News in Git
by Andrea paz 20 Jul '20

20 Jul '20

I answer here to all the news made in Git (great job, thanks!): ResampleRT --> OK Save on OpenEDL session --> OK Full Play paste, freeze --> OK Align timecode --> I can't test it, sorry. But I'm delighted with this addition to the Pro world. Auto Rotate --> OK

1 0

Auto Rotate checked into GIT is default preference
by Phyllis Smith 20 Jul '20

20 Jul '20

Just so no one is surprised, there is a new FLag Settings->Preferences for "Auto rotate for ffmpeg media". The default is to do this rotation so if in the past you loaded cell phone media and it was off by 90 or 180 degrees, it will now be automatically rotated in the display AND the render. If you do not want this behavior, change the Preference flag. See forum topic on "Rotation Meta Data usage in viewer/compositor". The reason this was implemented after all is to keep up with the smart phones/go pro usage (and maybe drones, but I do not know for sure).

1 0

New Appendix in Manual pdf
by Andrea paz 17 Jul '20

17 Jul '20

I wanted to ask for an opinion on a couple of new things that I have introduced in the manual (but going back is easy; that's why I ask for advice): 1. The nice pdf tutorial of fary54 I put it in a new section of the appendix, both because it is 4 pages long, but above all to give it more importance and accessibility. What do you think about it? Is it better to put it back in the body of the manual, in the corresponding section? 2. Also, in the fary54 tutorial I put links to his videos that illustrate some passages. These videos are uploaded in our Youtube channel, but they are not visible to the public. Thanks to Sam's idea, they are put as "unlisted" and can be seen only by following the link put on the manual. They're not real tutorials, they're simply the analog of the videos that we sometimes put on streamable to make new users understand how some tools work. Do you like the idea of integrating the manual with explanatory video links or is it better to keep Manual and videos separate? Note: if you want to contribute, describing the type of workflow you use in your daily editing work, it would be a valuable addition to the manual. I personally would like to know how to do audio editing (sync, audio in different tracks, sound mixing, etc), since I'm totally ignorant about it.

2 1