October 2020 - Cin - Cinelerra-GG Mailing Lists

Including libavformat/internal.h into ffmpeg.h was huge mistake on my side....
by Andrew Randrianasulu 29 Oct '20

29 Oct '20

It caused all those weird errors in filedv/fileexr. now, I have dilemma about resetting those changes from ffmpeg or trying to localize effect of this header inclusion to just some function ..... (not sure if such thing even possible) sorry ....

1 0

OpenCL benchmarking ....
by Andrew Randrianasulu 27 Oct '20

27 Oct '20

Hi all, and happy editing Not VERY useful for CinelerraGG yet, still I found whole topic attractive enough :} http://www.bealto.com/gpu-benchmarks_mem.html I compiled benchmarks for my machine, with two simple fixes, and uploaded result to github: https://github.com/Randrianasulu/MPBenchmarks IMO my current devices quite fast: ===== Host to device copy 223 424 771 1182 1770 2147 2403 2378 2506 2501 1490 1828 756 743 777 771 776 708 683 0 Device to host copy 325 613 1155 1971 3320 4811 6282 7188 8039 8316 7039 5471 2817 2695 3107 3256 3221 2634 2716 0 copyN 327 651 1272 2189 3300 4486 5419 5932 6193 6266 6299 6320 6330 6345 6348 6349 6346 6335 0 0 For fastest NVA3 gpu (reclocked manually) GPU<->GPU copy still slow ..... https://gitlab.freedesktop.org/mesa/mesa/-/issues/3479 This is with very hacked mix of two experimental mesa branches ... Master (mesa3d) doesn't support compute on nv50-era cards. This bench requires images(2D) support, and works with OpenCL 1.1 driver

2 2

Can 'play track' status propagate to ganged tracks?
by Oon-Ee Ng 26 Oct '20

26 Oct '20

Title says it all really. Didn't notice the new ganged tracks functionality till now (have a new project which needs a bit more than my usual workflow), and it looks like it'll help, but for this project I'm lining up a tonne of media in different tracks and would like to be able to easily 'mute' tracks (I use the 'play track' green arrow for that). I know I can just adjust the volume as a stop gap, but that tends to lead to volume issues at the end when I'm pushing everything back up (something will definitely get only halfway till 100%).

6 20

Render farm - client nvenc and main none, can this work?
by Oon-Ee Ng 23 Oct '20

23 Oct '20

I've been using cinelerra for years with software encoding. The size of my projects has never been big enough for this to be a problem (just render over lunch break). My machine is an ultrabook with a 1.8GHz i7 8th gen quad-core chip (so 8 threads) and a dinky MX150 nvidia card (no nvenc). Recently however the render times have been becoming a problem. Also, I now have a second machine (desktop) with an AMD Ryzen 5 3600 and an nVidia 1660. I've set up renderfarming and it seems to work fine (my one and a half hour render is down to half an hour). Now I'm wondering whether that nice graphics card can be used (without me having to actually sit at the desktop, I'd much rather work/edit on my ultrabook with all its attached monitors) for editing. It seems whether nvenc gets used depends on whether I select h264-nvenc (or h265-nvenc) on the main machine, but obviously I can't do that on this particular main machine. Is there a way to get this to work, or am I forced to choose between software renderfarm and single-machine nvenc (in my specific situation, I'm assuming that if I had two nvenc-capable machines this would work fine). Or is there some cuda-related speed up I could use?

3 3

Add 16:10 aspect ratio to dropdown menu in format window?
by Andrew Randrianasulu 20 Oct '20

20 Oct '20

Hello, I was screencapturing lately, and of course was confused *again* by my monitor being 1440x900 (16:10) vs 1920x1080 being 16:9 ..Of course I corrected myself, yet black bars remain ... I re-encode into 1080p for Youtube, because otherwise it really blurry :( https://www.youtube.com/watch?v=gozlazgZOcU&feature=youtu.be you see, there is black area around actual image ... When I *finally* realized I must manually enter aspect ratio 16:10, some of those bars disappeared .... Sorry for not testing CinGG much - I have new toy: https://gitlab.freedesktop.org/pmoreau/mesa/-/tree/nv50_compute_support :} (no, ffmpeg's openCL still doesn't work with this)

1 0

Demo for Youtube channel
by Andrea paz 19 Oct '20

19 Oct '20

In the Youtube channel of CinGG, there is a video presentation, this one: https://www.youtube.com/watch?v=anFROt2wJLQ We promised to present a tutorial on how it is done. Already two visitors have requested the tutorial. Does anyone want to take on the task of creating a short video in order to meet the users' request?

2 1

ffmpeg.git.patch4 is not needed anymore?
by Andrew Randrianasulu 16 Oct '20

16 Oct '20

Hello, all! for my usual rebuild of CinGG with ffmpeg.git I found ffmpeg.git.patch4 is not applicable anymore, and ffmpeg log list this commit: https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/a7bd37927628df3672488e07f71… avfilter/af_aformat: Add uninit function so, i just moved this patch away from buildsystem for now. sadly, bigger patch ffmpeg.git.patch2 (mpegts/blu-ray) also started to show at least one failure: (as of ffmpeg commit 649a6969f75f2378c65768deb9debd325eb2fc7f): root@slax:/dev/shm/tmp/cinelerra-goodguy-20200826/cinelerra-5.1/thirdparty/ffmpeg.git# cat ../src/_ffmpeg.git.patch2 | patch -p1 patching file libavformat/mpegtsenc.c Hunk #1 succeeded at 57 (offset 1 line). Hunk #2 succeeded at 78 (offset 1 line). Hunk #3 succeeded at 93 (offset 1 line). Hunk #4 succeeded at 109 (offset 1 line). Hunk #5 succeeded at 218 (offset 1 line). Hunk #6 succeeded at 238 (offset 1 line). Hunk #7 succeeded at 260 (offset 3 lines). Hunk #8 succeeded at 282 (offset 3 lines). Hunk #9 succeeded at 295 (offset 3 lines). Hunk #10 succeeded at 324 (offset 4 lines). Hunk #11 succeeded at 676 (offset 28 lines). Hunk #12 succeeded at 702 (offset 28 lines). Hunk #13 succeeded at 742 (offset 28 lines). Hunk #14 succeeded at 755 (offset 28 lines). Hunk #15 succeeded at 814 (offset 28 lines). Hunk #16 succeeded at 876 (offset 28 lines). Hunk #17 succeeded at 1077 (offset 28 lines). Hunk #18 succeeded at 1086 (offset 28 lines). Hunk #19 succeeded at 1104 (offset 28 lines). Hunk #20 succeeded at 1173 (offset 28 lines). Hunk #21 succeeded at 1233 (offset 28 lines). Hunk #22 succeeded at 1241 (offset 28 lines). Hunk #23 succeeded at 1315 (offset 28 lines). Hunk #24 succeeded at 1345 (offset 28 lines). Hunk #25 succeeded at 1363 (offset 28 lines). Hunk #26 succeeded at 1424 (offset 28 lines). Hunk #27 succeeded at 1522 (offset 28 lines). Hunk #28 succeeded at 1534 (offset 28 lines). Hunk #29 FAILED at 1585. Hunk #30 succeeded at 1644 (offset 28 lines). Hunk #31 succeeded at 1789 with fuzz 1 (offset 85 lines). Hunk #32 succeeded at 1843 (offset 85 lines). Hunk #33 succeeded at 1857 (offset 85 lines). Hunk #34 succeeded at 1925 (offset 86 lines). 1 out of 34 hunks FAILED -- saving rejects to file libavformat/mpegtsenc.c.rej cat libavformat/mpegtsenc.c.rej --- libavformat/mpegtsenc.c +++ libavformat/mpegtsenc.c @@ -1585,7 +1446,7 @@ static int mpegts_write_packet_internal(AVFormatContext *s, AVPacket *pkt) ret = avio_open_dyn_buf(&ts_st->amux->pb); if (ret < 0) - return ret; + return AVERROR(ENOMEM); ret = av_write_frame(ts_st->amux, &pkt2); if (ret < 0) { I tried to make new patch (by manually adding missed chunk), but not tested it yet (attached)

3 6

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

I tried to build CinGG for Rosa, but it segfaults on startup ....
by Andrew Randrianasulu 06 Oct '20

06 Oct '20

Dump attached. Files (rpm) themselves at https://cloud.mail.ru/public/4UHi/u7GSkKZp5 Terminal output was: Cinelerra Infinity - built: Oct 1 2020 21:55:26 git://git.cinelerra-gg.org/goodguy/cinelerra.git (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams 2007-2020 mods for Cinelerra-GG 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. init plugin index: /usr/lib64/cin/plugins init lv2 index: ** segv at 0xae5b88 in pid 11125, tid 11709 writing debug data to /tmp/cinelerra_11125.dmp lock_items: 23 lock_frees: 8 ** dump complete Ошибка сегментирования (слепок снят) From brief look it still tries to access some media files, I asked user (Vlad) to try and tar up .bcast5 and then remove it altogether .... It might provide some clue(s)? Waiting for archive from Vlad ....

3 8

Cool stuff
by Sam 05 Oct '20

05 Oct '20

Hi guys, i have found an interesting video which shows how you can convert footage with a lower FPS to a video with a much higher FPS without any losses. https://youtu.be/sFN9dzw0qH8 https://github.com/baowenbo/DAIN The nice thing is that this software is free of charge. For my commercial projects I mainly use Da Vinci Resolve and there is the same possibility which I use again and again. This feature is great if you want to create slow motion effects and you only have footage that was created with a low FPS. I don't know if one day this software will be used for Cinelerra, but it would be a great feature to use. Maybe you can transfer footage from Cinelerra to this tool with a mouse click and transfer it back to Cinelerra after the rendering is finished? Even if an integration would not be possible, you can use this tool independently. Sam P.S.: By the way, the problems with the language plugin and web site are still bothering me, but a solution will surely be found soon.

3 3