Re: [Cin] BUG on Clear keyframes (CinGG-release by GIT 30Aug 2020)
В сообщении от Monday 31 August 2020 19:34:20 Phyllis Smith via Cin написал(а): > Thanks Igor and Andrew for testing some more, > GG was hoping to come up with a fast solution to get into the builds but > unfortunately it is going to take a design change which needs a week to > code and test. So he decided it is better to do the builds and leave in a > "known bug" instead of create an unknown one. He says a workaround is to > turn on/off "keyframes follow edits when this error could surface. Yes ... this seems to work! Please add this to known issues for this release? Also, documentation (pdf) is not up-to-date for now (file modification from 9 aug 2020). May be wait few days or week before all this synced again? I'm not aware about any scripted automatic download/builders for CinGG outside your dev. machine ... > > Sorry about this. It is mostly my fault as I have been unable to test this > major mod for bump autos. > > On Mon, Aug 31, 2020 at 6:57 AM Igor BEGHETTO via Cin < > cin@lists.cinelerra-gg.org> wrote: > > > 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 > > -- > > Cin mailing list > > Cin@lists.cinelerra-gg.org > > https://lists.cinelerra-gg.org/mailman/listinfo/cin > > > -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] BUG on Clear keyframes (CinGG-release by GIT 30Aug 2020)
Thanks Igor and Andrew for testing some more, GG was hoping to come up with a fast solution to get into the builds but unfortunately it is going to take a design change which needs a week to code and test. So he decided it is better to do the builds and leave in a "known bug" instead of create an unknown one. He says a workaround is to turn on/off "keyframes follow edits when this error could surface. Sorry about this. It is mostly my fault as I have been unable to test this major mod for bump autos. On Mon, Aug 31, 2020 at 6:57 AM Igor BEGHETTO via Cin < cin@lists.cinelerra-gg.org> wrote: > 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 > -- > Cin mailing list > Cin@lists.cinelerra-gg.org > https://lists.cinelerra-gg.org/mailman/listinfo/cin > -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] BUG on Clear keyframes (CinGG-release by GIT 30Aug 2020)
-- Пересланное сообщение -- Тема: Re: [Cin] BUG on Clear keyframes (CinGG-release by GIT 30Aug 2020) Дата: Понедельник 31 августа 2020 Отправитель: Andrew Randrianasulu Получатель: cin@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 --- -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] BUG on Clear keyframes (CinGG-release by GIT 30Aug 2020)
В сообщении от 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? > 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 -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] BUG on Clear keyframes (CinGG-release by GIT 30Aug 2020)
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 -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] Crash at fast 'z' (undo) for many-fade-keyframes?
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 ** segv at 0xf6a2d558 in pid 3994, tid 4011 created on Mon Aug 31 15:26:53 2020 by 1000:100 guest() OS: CPUS: 4 CPUINFO: processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 2 model name : AMD FX(tm)-4300 Quad-Core Processor stepping: 0 microcode : 0x6000852 cpu MHz : 2599.151 cache size : 2048 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 16 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate ssbd vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid
Re: [Cin] Today's GIT checkin includes fixes + Ctrl-s for save session
All my personal opinion. I am not an old Cinelerra-GG user like most of You (I am using Cinelerra-GG since January 2018 ) and, for me, some shortcuts should be changed (I already speak about). For me there are foundamental shortcuts that a NLE must have, for example J-K-L for PlayBackward-Stop-PlayForward and I-O for In point-Out point. Ctrl+S is good for me and Ctrl+Z shortcut would be welcome. And, I think, the old "Save 's' " could be deleted. I understand the old users but, the old users can do an effort to change (hey!, I no longer have the shortcuts for the old "Move tracks Up/Down"). I think that Ctrl+S for Save is a standard. IMHO some shortcuts could go away and to be available for feature, new or old, more used. For me a shortcut should be assigned to a tool most frequently (or important?) used. For example I would not assign any shortcuts to the following items in File menu: - BD Render... (Ctrl+Shift+D) - DVD Render... (Alt+D) - SubTitle... (Alt-Y) About Speed feature: Very good. Thanks! I noticed that Speed tool must be used with care because the different types of keyframes can upset your work. IMHO, I would have preffered to be implemented at the clip level that you can change with RMB menu on it, and the Speed lines on the track to be hidden. Of course, this way, could not have the Speed Ramp. About F_minterpolate: I have done a short test. On my Charlie F_minterpolate can not work in real time (Proxy without Scaler enabled). I have to use a workaroud. So I can decide if create a SlowMo with FFmpeg by command line or inside Cinelerra-GG: good! IgorBeg -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] New ffmpeg plugins
If it were possible to make the "F_subtitles" filter work, it would solve BT#0282. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
