June 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

AOMedia AV1 2.0
by Andrew Randrianasulu 10 Jul '20

10 Jul '20

Hi all! Just was refreshing Phoronix page and this scrolls into view: https://www.phoronix.com/scan.php?page=news_item&px=AOMedia-libaom-2.0-Rele… --- AOMedia AV1 2.0 Codec Library Released With Many Improvements Written by Michael Larabel in Multimedia on 19 May 2020 at 06:53 AM EDT. 2 Comments MULTIMEDIA -- Version 2.0 of the libaom AOMedia AV1 video encoder / video codec SDK library is now available as the first major update in nearly two years. Libaom 2.0 is the first release since the original 1.0 release back in mid-2018 after the AOMedia codec working group approved the 1.0 release. The developers view this AOMedia AV1 2.0 release as now being their "first official release" for production. Libaom 2.0 adds a real-time encoding mode, SVC support, drops multi-resolution encoding, documentation updates, and other improvements to this open-source AV1 reference encoder. -- Hm, beaware about possible buildsystem changes, I guess? I have early snapshot running, from around Mar, 19 2020 but I have recent Cmake and stuff ....

2 5

New monthly pkgs and tars available on the website
by Phyllis Smith 08 Jul '20

08 Jul '20

https://cinelerra-gg.org/download/pkgs/ https://cinelerra-gg.org/download/tars/ https://cinelerra-gg.org/download/CinelerraGG_Manual.pdf The "gang modes" (to include DAW-like audio channel mash) is very minimally tested and some improvements have already been suggested and are planned for next month. Andrea has converted from pdf to latex and added to the manual with some quite helpful images in section 5.2.1. As usual, if you have problems, please report them and remember you can always back out to last month's build in old_pkgs or old_tars directory. A copy of the release notes, also available on the website is below. GG/Phyllis *********************************** *Cinelerra-GG (Version Infinity) Release Notes for 06/01/2020-06/30/2020 for builds* Cinelerra’s *youtube channel* can be accessed from the website *as set up by Sam*. The link is under the Support header - https://www.youtube.com/channel/UCW97mOMN_tAqVCn8k4Euf1w/ An update for the* Italian wikipedia by MatN and Andrea *is now live. The *Elive distro by Thanatermesis* has been routinely including Cinelerra for years and so Sam has added a link as a choice for users (BT# 453). 1. Add master/armed_gang track *operations for closer to DAW-like editing*. A method has been implemented to treat multiple audio channels as one so that the edits made to the master channel are automatically duplicated for each channel (BT 433 / Glen of AVLinux). For usage details refer to the updated manual on the website, section 5.2.1. This feature is not limited to this purpose as more usage scenarios are likely to be quite useful and additionally free up monitor display space. 2. *IMPORTANT - Changed Behavior*: A minor change to “move up” and “move down” tracks was implemented to correct what was an exchange on the top track or bottom track instead of a move. 3. *Usability Improvements*: The *Perspective *plugin has added visible 1-4 numbers on each of the 4 points for ease of use and the number of the point is shown next to the X box in the menu (MatN request, BT #443). The *Rotate plugin* has been modernized with improvements by a Contributor. A minimum Speed auto value is now used for the update instead of the zero value causing problem. FFmpeg will show a “seek retry limit message” for information purposes. An easy method to reopen a closed mini-viewer mixer is now in the Window pulldown which displays each of the media that occupied a mini-viewer window. Minor improvement in Settings→Preferences, Appearance tab to better accommodate languages and for aesthetics (MatN contribution). The Spanish translations have been improved some more (RafaMar) and minor RU/FR (by MatN). Setting and changing Audio or Video track height has been slightly modified and Shift-rmb resets to the original configuration default. 4. *Bugs/Issues fixed:* A patch for the commercials feature was generated and applied (contributed by mehw BT#458). The “clear frame” was not working in Tracer as a result of background color, but now fixed. Keyframe Spanning was not working for Sketcher, Tracer, and CriKey due to their unique multiple points/curves setup. This was quite a difficult/involved fix (RafaMar BT #441). Rework of the plugin presets was completed plus Text was changed to Data for spanning keyframes. Some additional code cleanup was performed as usual. Embedded object fix – looking for open delimiter followed by closing delimiter. Deadlock fix by opening files one at a time. Fixed hang caused by an extra lock (Andrew found). Reset caches were crashing on vicon drawing, but this has been corrected (Andrew diagnosed). SEGV for reset cache fixed as found (in dmp file provided by Skinkie). Vicon checkout fix + fixed vicon video/cache errors + address delays created by vicon drawings. Cache checkout tweak to remove_all/delete_oldest rework. Extract name Valgrind bug fix. Fixed some show window deadlocks and X10 remote control memory error. An old bug just found, where removing a shared plugin worked incorrectly, is now fixed. Collect proxy/nested clips fixes (BT #427 by IgorBeg). A new environment variable, BC_TRACE_XERROR will dump the stack on this type of error, thus aiding in analyzing any of these types of crashes.

7 27

Problems with Camera Automation?
by John Coppens 03 Jul '20

03 Jul '20

I had this problem with camera automation yesterday when trying to do the following: - I have a full-screen take of a talking person's face and wanted to reduce the size and move the image to the lower right corner when other contents had to appear. - Moving the cursor in the Camera animation only move the image very slightly (maybe 10% of the screen size). - First scaling the Z-axis reduced the image Ok, but still almost no X or Y movement. - Dragging the image on the screen worked, but the X and Y parameters became huge (1000's). And the animation algorithm was completely confused - on play, the image disappeared way out of screen and then reappeared. The position was not exactly the one 'edited'. Any way to accomplish this? John

5 9

Rendering multi-threads
by Andrea paz 01 Jul '20

01 Jul '20

I have a CPU 8 cores / 16 threads, but the final rendering uses only one core. I tried with mp4/h264-5; webm/VP9; mkv/h264-5 e Prores. A 45 min video takes 3h 30m. I tried adding the parameters "threads=15", "wpp" which should be active by default and "frame-threads=3"; but the result is the same. On average I do 15 fps. Using h264-5 with nvenc takes 1h20m; but the CPU still uses only one core. On average I make 115 fps. Using an external engine (handbrake, which uses ffmpeg) you can use both the Cpu and the GPU; the rendering will take 10m! (but with lower quality). Since I'm compiling CinGG (note: all threads are used for compiling), maybe I need to enable some flags or something like that? Are there any customizations to do? Or should I set something in the operating system? Another question: How do you configure the render farm to use only the local CPU cores?

3 13

Subtitles view.
by Rafa Mar Multimedia en Gnu\Linux 30 Jun '20

30 Jun '20

Hello, I wanted to ask the veteran Cinelerra users a question to see if there is any way that the subtitles can be seen in the composition viewer. [image: cinSubtitles.png] thanks.

3 7

HW in render farm
by edouard chalaron 27 Jun '20

27 Jun '20

Hi all I am using several headless machines (cin -d 1200) as a render farm. Question : If the master node is using an accelaration (HW) do the slave nodes automatically use the said acceleration ? if no but is a matter of local configuration for a slave where can I set it up ? Now, to make it more complex : if the master is running on vdpau (or CUDA) can a slave run on vaapi ? Thanks in advance Ed

3 4

Re: [Cin] HW in render farm
by Phyllis Smith 27 Jun '20

27 Jun '20

Ed, we do not have a definitive answer for this and really have no easy way to test, but if we think of some way to test, will attempt it. > I am using several headless machines (cin -d 1200) as a render farm. > > My understanding is that generally headless machines would not have any graphical libraries installed or X for that matter. At any rate, the vdpau and/or vaapi software would need to be installed for usage on each client. Question : > If the master node is using an accelaration (HW) do the slave nodes > automatically use the said acceleration ? > > Without testing, we can not say for sure, but the $HOME/.bcast5/Cinelerra_rc file is used for all of the nodes, master and clients. If that file has "USE_HW_DEV vaapi" or "USE_HW_DEV vdpau", conceivably the clients would also use the designated hardware device if the graphics board can handle it. if no but is a matter of local configuration for a slave where can I > set it up ? > > I do not know if there is any way to set this up or to vary between vaapi or vdpau on different clients. The one thing you can try is to set an environment variable for specific clients like the following and hope it uses that specific Cinelerra_rc CIN_CONFIG="/pathname>/<ﬁlename_such_as_.bcast5>" {path}cin -d port# where that specific Cinelerra_rc has "USE_HW_DEV=vdpau" or "USE_HW_DEV=vaapi" appropriately. Alternatively, an environment variable can be set and tried. For example: export CIN_CONFIG=/tmp/.bcast5 or even export IN_HW_DEV=vdpau or export CIN_HW_DEV=vaapi It looks like this will take some effort to figure out and if you do find something, please let us know. Phyllis/GG

1 0