August 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

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

BUG on Clear keyframes (CinGG-release by GIT 30Aug 2020)
by Igor BEGHETTO 07 Sep '20

07 Sep '20

Clear Keyframes (Shift+Del) do not delete the right keyframes. Maybe it's too late for the monthy release but a bug I found. I don't know if this bug is also in the last GIT release. 1. Create three (or more) Fade keyframes 2. Highlight an area to select one or more Fade keyframe 3. Hit Shift+Del shortcut or Keyframes-> Clear Keyframes 4. It delete the wrong keyframes and move others. (Note: Settings-> keyframes follow edits = checked) Take a look the screencast at https://streamable.com/q58t37 Thanks! (Sorry for the late) IgorBeg

4 15

August Monthly Builds now available on cinelerra-gg.org
by Phyllis Smith 04 Sep '20

04 Sep '20

There are new binaries for the latest version of cinelerra gg at: https://cinelerra-gg.org/download/ as well as the releasenotes.pdf. The release notes contain the known bug and workaround. The manual is currently undergoing major reorganization by Andrea so in order to avoid interference is not being modified until this effort is complete. 2 of the lesser used distros information: Gentoo did not build but Tumbleweed did. Text version of release notes is below. *Cinelerra-GG (Version Infinity) Release Notes for 08/01/2020-08/31/2020 for builds* *Special thanks to Andrew, Andrea, Houku, IgorBeg, and RafaMar for testing* this month, especially of the speed fixes and Auto Bumps as Phyllis was unable to do so. *Release contains a known bug with a workaround.* Clear Keyframes in some cases does not delete the right keyframes. The verified workaround is to turn on/off "keyframes follow edits” when this error could surface. It will be fixed as soon as possible and will be correct in next month’s release. 1. *Bump float Autos* feature has been added which provides a good solution for adding speed to a selection, like an edit, as well as some nice useful applications to the camera, projector, etc. Temporary document/explanation is at: https://cinelerra-gg.org/download/testing/bump_autos.pdf . A new “Create Keyframes”option for a selection area under the Keyframes pulldown was added. 2. Upgraded operating system distros on the build computers. 3. *Changed behavior:* Shortcut for Undo is “z” as originally + *Ctrl-z* so that new users are less confused. Because Ctrl-z was already in use with the middle mouse button on a track for “Cut Pack”, that was changed to Ctrl-Alt-z (video - Top 8 open source video editor – by Nice Micro). Shortcut for Save is “s” as originally + *Ctrl-s* so that new users are less confused. Because Ctrl-s was already in use under the Settings pulldown for Save settings now, that was changed to Ctrl- Shift-S (forum - Ideas for UI Modifications (Improvements?) - note by Tupper). 4. *Usability Improvements:* *Language preference* is now available in the pulldown Settings→Preferences, Appearance tab on the left hand side to make it easy to have CinGG always start in the user’s preferred language (BT #113 by MatN and Gerd via mailing list). Note that the only current choices are the ones that I am quite sure are actually being used. You can still set the environment variable LANGUAGE for other translations like Slovenia, Chinese, Portuguese, etc and if requested, we will add another possible translation in but they have not been updated in a long time and are only done via an automatic translator with no personal corrections done. Ydiff was upgraded to work for rgb/yuv and 16 bit depth. This was done in order to better analyze the problem in the forum of “Loss of detail” by dejay. *Prores format* for rendering was modified to use a default of “profile=3” for High Quality instead of the original “profile=2”. I will take longer to render and produce a larger file but the quality difference is certainly better with a ydiff difference of only 1.7 versus 7.7. This is again in reference to the forum “Loss of detail” by dejay. *Default settings for new configuration* setup in $HOME/.bcast5 have been changed. This does not affect any currently existing setups. Changes include default Load Mode, Click to Activate/Deactivate Focus, and Clear Toggles (Sam suggestion to align with user expectations) now is 0) and Size (was 24 and now 48). More video is of bigger width and height and it was difficult to even see the smaller characters the first time (suggestion from Andrea). Time-reference metadata value that showed up in Audio examples has been added as necessary for “Align Timecodes” (Katacuts supplied examples). Updated es.po Spanish (thanks to RafaMar as he has faithfully been providing for months now). A new feature is *drag speed highlight*s; it is quite useful because it shows you the change that the speed up/down will make to the timeline while moving and then drops it there when you let up on the mouse. *Multiple edit selection* capability has been added. 5. *Bugs/Issues Fixed:* Auto-Rotate for ffmpeg video was not working with hardware vaapi/vdpau devices. Had to rework ffmpeg a/v filter setup and hw decode with vid filters (notified by Ig0r in the forum). Speed Auto edit cuts resulted in incorrect results. This has been fixed as far as we have been able to test. A note about usage is: “ When working with edits and the speed auto, if you make a "cut" in a section, the speed curve values should not change over the remaining playable edits. It is possible to easily add "disjoint" curve points at the boundaries of the edit to preserve the curve shape (houku BT #477). Paste automation tweaks; undo fixes and tweaks for undo commit logic. Normalize speed follows (for example plugins/labels) enhancement. Update shortcuts to reflect changes and make some corrections. A fix was added to the video code interface with ffmpeg in order to make F_minterpolate functional. Although it will now work single-threaded, it is slow and does not seek so using the command line may be a much better way to go (IgorBeg suggestion). Anyway as a result there are now an additional 7 more usable ffmpeg plugins available (Andrea went through the set to find these). Bug fix for get_auto_at_position equivalence test.

4 6

Crash at fast 'z' (undo) for many-fade-keyframes?
by Andrew Randrianasulu 03 Sep '20

03 Sep '20

I was playing with new bump autos, set some on fade curve, played with type of each keyframe point, and then decided to remove them all by hitting 'z' fast. This resulted in: cin Cinelerra Infinity - built: Aug 31 2020 05:07:06 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. RenderFarmClient::main_loop: client started FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv Mutex::lock: Resource temporarily unavailable Mutex::unlock: Invalid argument ** segv at 0xf6a2d558 in pid 3994, tid 4011 writing debug data to /tmp/cinelerra_3994.dmp lock_items: 19 lock_frees: 6 FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv ** dump complete Ошибка сегментирования Dump attached

2 1

Re: [Cin] BUG on Clear keyframes (CinGG-release by GIT 30Aug 2020)
by Andrew Randrianasulu 31 Aug '20

31 Aug '20

---------- Пересланное сообщение ---------- Тема: Re: [Cin] BUG on Clear keyframes (CinGG-release by GIT 30Aug 2020) Дата: Понедельник 31 августа 2020 Отправитель: Andrew Randrianasulu <randrianasulu(a)gmail.com> Получатель: cin(a)lists.cinelerra-gg.org В сообщении от Monday 31 August 2020 15:56:28 Igor BEGHETTO via Cin написал(а): > Clear Keyframes (Shift+Del) do not delete the right keyframes. > Maybe it's too late for the monthy release but a bug I found. I don't > know if this bug is also in the last GIT release. I think bug still exist in latest (0678b17975f50a831fb8a1cda6baaa961e3b6de7) code, at least if I try to cover all existing keyframes by highlighting them - they all disappear. But if I only select 2-3 out of 4 - yes, remaining keyframes moved left, into higlighted region. Thing is, because those keyframes represent change ... deleting only SOME of them will create new curve (default value in highlighted region, abruptly starting to climb to remaining keyframes as we move outside of highlighted region). I mean, isn't this operation ought to *create* some keyframes in such case, too? *****update***** No, my thinking above was not useful here, but may be keyframes saved not as absolute pairs (distance from start of timeline, value), but as relative (delta) to previous keyframe values? If so, 'delete keyframes' should recalculate this delta for next left keyframe outside of highlighted region relative to keyframe right before highlight started (if any). And then apply those values to left (next) keyframe. At least when it comes to automatization keyframes like fade, speed, etc. Not sure how plugin automatization should react. > 1. Create three (or more) Fade keyframes > 2. Highlight an area to select one or more Fade keyframe > 3. Hit Shift+Del shortcut or Keyframes-> Clear Keyframes > 4. It delete the wrong keyframes and move others. > (Note: Settings-> keyframes follow edits = checked) > > Take a look the screencast at > https://streamable.com/q58t37 > > Thanks! (Sorry for the late) > > IgorBeg -------------------------------------------------------

1 0

Today's GIT checkin includes fixes + Ctrl-s for save session
by Phyllis Smith 31 Aug '20

31 Aug '20

Hopefully this solves some of the new user complaints -- *Ctrl-s ALSO saves the session as does the original "s" shortc*ut. We can not lose the "s" since too many users already know and use this consistently but since according to the forum, 99% of people use Ctrl-s to save the session. Unfortunately, this means that "Save Settings" under settings has had to change to Ctrl-Shift-S. If you have concerns about this, please let us know -- I am sorry that we find it necessary to ever change anything. Also, we would like to change Ctrl-z to be a undo in addition to the current shortcut "z" -- as this is another major complaint of new users. Same reasoning as above. We have not done this yet as ctrl-z in currently in use in a couple of different ways. If you have objections about this change, now is the time to say so. GIT changes also include: - Igor's last auto bump found error where the effects did not correctly stay put - other auto bump fixes - updated es.po (thanks to RafaMar as he has faithfully been providing for months now) - undo tweaks - *new feature is drag speed highlights; *check this out as I believe it is quite useful because it shows you the change that the speed up/down will make to the timeline while moving and then drops it there when you let up on the mouse - fix to ffmpeg filter parameters for video (to match previous change already done for audio); this allows for usage of f*_minterpolate *(and possibly other ffmpeg plugins that were commented out but I did not have time to test); "yes", it can be cpu intensive like Igor suggested and it does not seek so I *do not know if minterpolate will be useful* anyway but at least it does not crash. In order to get use of this plugin, you will have to "Reload Plugins" which you can do from Preferences. - normalize speed tweaks.

4 4

New ffmpeg plugins
by Andrea paz 31 Aug '20

31 Aug '20

I enclose my plugins.opts after testing some of the ffmpeg plugins that were commented before: 15 now work, although some I have no idea how they work or what use they have. The others still don't work, giving the usual errors. There are some that do not give errors when booting CinGG but then do not appear in the list of plugins. Probably you can make them work, but I don't know if it is worth wasting time. WORKS: allrgb; allyuv; cellauto; codecview (I don't know how to use it!); copy; fps; freezedetect; null; pixdesctest (I don't know how to use it!); pullup (I don't know how to use it!); random; reverse; selective colors; settb; tonemap; vmafmotion (I don't know how to use it!). NO ERROR but NO LOADS: alphaextract; decimate; displace; extractplanes; hdcd; join; mergeplanes; noformat; removelogo; replaygain; xmedian; mix; drawtext; subtitles.

2 2