October 2019 - Cin - Cinelerra-GG Mailing Lists

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

Nested clip and proxy
by Igor BEGHETTO 26 Jan '20

26 Jan '20

I was reading the manual "CinelerraGG_manual.pdf" (created March 31 2019) and the manual "CinelerraGG_manual_WIP.pdf" (dated 20190826) by LaTex about Nested Clips. (really good job, guys. And I could print it on the paper in a A5 size) I noticed... - "CinelerraGG_manual.pdf", pg.116, Nested Clips - "CinelerraGG_manual_WIP.pdf", pg.122, Nested Clips The final sentence: "...compositions. They can not be proxied" By my tests/works, you CAN create proxies for Nested clips. Proxies are created in Cinelerra folder (where there is "cin" file) instead of the clip folder as usual (with Cin TAR version. With Package version I don't know). Before saving your project, pay attention to disable Proxy feature. You MUST SAVE your PROJECT with PROXY DISABLED otherwise you lose the link to the clips (more or less). Is it right that proxies are created in Cinelerra folder? Is there any reasons they are not created in the clip folder? Thanks. IgorBeg

3 19

Latex and Manual
by Andrea paz 13 Jan '20

13 Jan '20

@Olaf. Every month I write an email containing LaTeX and Manual in the title to continue the discussion and translation work with einhander. I installed the whole package, plus the Greek and Russian languages. Of course I also installed an editor, that is TexStudio. It would be nice if you could also contribute (in any way). "I also noticed that the lines in the TeX documents are all written without wrapping. When using Git and Diff, however, hard line breaks could be useful, short lines limited to less than 80 characters simplify the clarity." My knowledge of \LaTeX is very superficial and therefore I have not understood what you mean by wrapping the text. It would be nice if you could also contribute (in any way).

7 52

Latest CinGG release builds are ready for download
by Phyllis Smith 02 Nov '19

02 Nov '19

The latest CinGG builds are ready at cinelerra-gg.org to download. This month's big deal is "Scaling" so you can use it and actually see the text, icons, and menus on a 4K monitor as well as change the size on any monitor if you just want it to be a little bigger; for example 1.25 is quite nice on a 1080p monitor. Below are the abbreviated Release Notes that you can also find on the website. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Cinelerra-GG (Version Infinity) *Release Notes* for 10/01/2019-10/31/2019 for builds *Celebrating 1 year of the cinelerra-gg.org <http://cinelerra-gg.org> website!* Without *Sam*, we would not have even started or progressed this far and continued onward. Without* Pierre*, we would not have had the motivation. Now moving forward with assistance of *Andrea/Andrey* converting the manual to Latex, plus much help from *IgorB* with testing, demos, suggestions, and photo-montages, and then there is all of *Andrew *and *Olaf* contributions, insights and updates, besides the testing/using/wiki updating of *MatN*. *Every single user* who has taken the time to log a bug, do a test, make a feature request, or simply used the software helped to keep Cinelerra alive and going strong. This includes a “Thank You” to the *lurkers*. 1. *Scaling for any monitor to include 4K HiDPI* monitors is now available. For usage there is an automatic probe if you do nothing different or you can easily modify the Scaling in the Layout section of Settings→Preferences, Appearance tab – be aware that when you click OK, the application will restart all by itself. If you make a mistake in the value you set in Preferences, you can workaround this by starting from a window using BC_SCALE=1 {your cinelerra path/bin/cin} (orriginal request a long time ago from Terje, + a post in Forum and BT #25). 2. *Updated dav1d library* from 0.4.0 to 0.5.0 which has good speedups (Andrew notification). 3. *Usability Improvements*: Several new Shape Wipe transitions have been added to include: Butterfly, Circle-s, Clouds-s, Diamond-s, Venetian Blind-s, Cross-s, Diagonal-s, Double Door’s, Gravity, Linear-s, and Plasma for an additional 25 (thanks to IgorB). Large rework of the Shape Wipe program code to include an additional Feather (blend) slider. Update layout of the menu (based on IgorB’s design). Icons/pngs mods and additions for Cakewalk theme have been provided. This includes replacement icons for the default Insertion Strategy icons (thanks to Olaf). Added Insertion Strategy icons back in for the Load Files, Render, Record, and Menu Effects and at the same time cleaned up this code (D. Quinton suggestion). Mouse over the effects and transitions in the Resources window will show a short definition when “Info on” is enabled via the right mouse button over an empty space or the shortcut of the letter “i” (D. Quinton suggestion). Added a “Are you sure?” when updating Preferences if a Render or Record is in progress or if a Restart is pending (Olaf suggestion). Russian translation updated to include many more translations plus fixes (Andrew’s work). 14 new audio/video opts files to choose for a Render in the quicktime (qt) and avi categories (Andrew contribution). Qt files now render with automatic extension of .mov instead of .qt because mov is what works. 5. *Bugs/Issues Fixed*: Thirdparty build for Nvenc/Cuda fix has been added. Fixed error in the About September Features of note. Informational definitions for the Effects and Transitions have been corrected – plugins.txt. Booby lock problems in plugin 720to480, updatefilter, and another routtine have been fixed as well as another 2 potential fixes as found by Andrew. SEGV in popup menu found while using SVG via Inkscape when an empty file name is fixed. Rework of the resource_init routine has been completed. YUV411 plugin fixed to immediately show a warning message if the session format is not YUV. SEGV in Resources Window, Clip folder, when you click rmb, and paste clip when nothing in the clipboard to paste, has been fixed (Olaf found). Plugin Selective Temporal Averaging radio buttons were not working, but are now fixed (Andrew). Plugin Deinterlace-CV had a deadlock that has been corrected and the missing dial is now back (Andrew reported this). The opts file avi.xvid has been fixed and put into the correct subtype as xvid.avi (Andrew note). The differences.pdf file has been updated to include the latest features added.

4 3

UPD2: Interesting info about EDL I found ....
by Andrew Randrianasulu 30 Oct '19

30 Oct '19

ah, found this in release notes: 5.1 Release Notes for changes from 07/01/2017 to 07/31/2017 for these builds Removed Reel Name, Reel Number, Time Code Start from Asset Info in Resources & Preferences. so, I can conclude this commit broke CMX3600 support, if there was any .... Hm, time to load CinCV :} Ok, CinCV doesn't load xml from CinGG correctly, but at least creates something ..... cat '/dev/shm/DOG.edl' TITLE: Cinproj FORMAT: CMX 3600 4-Ch 001 cin0000 V C 00:00:00:00 00:01:10:06 00:00:00:00 00:01:10:06 002 BL V C 00:00:00:00 18518:31:06:00:01:10:06 00:01:10:06 18518:32:17:01 So, reel_name was important for this feature to work. I'll open feature request (low prio) ---------- Пересланное сообщение ---------- Тема: UPD: Interesting info about EDL I found .... Дата: Четверг 31 октября 2019 Отправитель: Andrew Randrianasulu <randrianasulu(a)gmail.com> Получатель: "Cinelerra.GG" <cin(a)lists.cinelerra-gg.org> I actually tried this 'EDL export function, with simple one track dog file. Hm ... I can't see any info about file used? cat '/dev/shm/dog/dog/dog.edl' TITLE: Cinproj FORMAT: CMX 3600 4-Ch 001 BL V C 00:00:00:00 00:00:17:09 00:00:00:00 00:00:17:09 002 BL V C 00:00:00:00 00:00:11:13 00:00:17:09 00:00:29:07 according to https://developer.blender.org/T53615 this file format at least initially included reel_name (is this info still around in CinGG?) but late tools used other way to identify source files ... ------------------copypasta------ Description In 2.79 The file path parsing gives an error. Open an EDL file, hit 'Refresh Reels' - gives the error: "File not found". However, this bug isn't in 2.77. Cross dissolve transitions are added to the entire following clip and not just the transition duration. 'Import EDL" script will give a non-descriptive error if there are space characters in the reel name. The in EDLs the reel name column is always 8 characters wide and can contain spaces. "* From clip name:" should(also) be used to id filenames. All Pro NLEs(Ex. Avid, Premiere, Final Cut and Davinci Resolve) are using this comment to locate source files(full file name with extension, but no path). Once mentioned here: https://developer.blender.org/T48146 Only archaic EDL importers like the one in Lightworks only uses the reel name for file id, however in Lightworks the time code and reel name must be embedded in the source files (ffmpeg can read/write this). But as mentioned most other pro EDL importers have the option to ignore embedded time codes and use the comments to id filenames(instead of reel name). Ex. EDL file from Premiere: TITLE: 4tin2tin FCM: NON-DROP FRAME 001 AX AA/V C 00:07:16:20 00:07:21:12 00:00:00:00 00:00:04:17 * FROM CLIP NAME: 4tin2tin.mp4 002 AX V C 00:07:16:20 00:07:20:12 00:00:00:00 00:00:03:17 * FROM CLIP NAME: 4tin2tin.mp4 003 AX V C 00:07:20:12 00:07:20:12 00:00:03:17 00:00:03:17 FCM: NON-DROP FRAME 003 AX V D 025 00:37:45:21 00:37:47:12 00:00:03:17 00:00:05:08 EFFECTS NAME IS CROSS DISSOLVE * FROM CLIP NAME: 4tin2tin.mp4 * TO CLIP NAME: 4tin2tin.mp4 004 AX V C 00:37:46:21 00:37:48:12 00:00:04:17 00:00:06:08 * FROM CLIP NAME: 4tin2tin.mp4 005 AX V C 00:37:46:21 00:37:47:12 00:00:04:17 00:00:05:08 * FROM CLIP NAME: 4tin2tin.mp4 ------copypasta ends----- Apparently this summer interesting framework OpenTimelineIO was opened, with (buggy?) CMX 3600 module: https://opentimelineio.readthedocs.io/en/latest/tutorials/otio-plugins.html also https://github.com/iluvcapra/pycmx pycmx The pycmx package provides a basic interface for parsing a CMX 3600 EDL and its most most common variations. Features The major variations of the CMX 3600: the standard, "File32" and "File128" formats are automatically detected and properly read. ---------- Пересланное сообщение ---------- Тема: Interesting info about EDL I found .... Дата: Среда 30 октября 2019 Отправитель: Andrew Randrianasulu <randrianasulu(a)gmail.com> Получатель: "Cinelerra.GG" <cin(a)lists.cinelerra-gg.org> While translating (attempting to translate few still untranslated things) CinGG I found interesting note about EDL export. Intially I assumed it only works with some long-obsoleted device/soft, but today I found this page (while looking at timecode feature): https://eyeframeconverter.wordpress.com/mlt2edl/ MLT2EDL NB. Since Shotcut version 16.06 this script is not needed anymore. Shotcut can export EDL files natively: https://www.shotcut.org/blog/new-release-1606/ Mlt2edl is a python script for converting Shotcut mlt files into ex. Blender (v. 2.72 beta or higher) friendly CMX 3600 EDL files. The converted EDL files will also work in Lightworks and Resolve. Mlt2edl is based on the Kdenparse python script by Will Riley. Because CinGG (and original Cin) should be able to output exactly this EDL (???) format ... This mean she automatically compatible with "Lightworks and Resolve" and Blender, too?? Anyone can test this? ------------------------------------------------------- -------------------------------------------------------

1 0

UPD: Interesting info about EDL I found ....
by Andrew Randrianasulu 30 Oct '19

30 Oct '19

I actually tried this 'EDL export function, with simple one track dog file. Hm ... I can't see any info about fle used? cat '/dev/shm/dog/dog/dog.edl' TITLE: Cinproj FORMAT: CMX 3600 4-Ch 001 BL V C 00:00:00:00 00:00:17:09 00:00:00:00 00:00:17:09 002 BL V C 00:00:00:00 00:00:11:13 00:00:17:09 00:00:29:07 according to https://developer.blender.org/T53615 this file format at least initially included reel_name (is this info still around in CinGG?) but late tools used other way to identify source files ... ------------------copypasta------ Description In 2.79 The file path parsing gives an error. Open an EDL file, hit 'Refresh Reels' - gives the error: "File not found". However, this bug isn't in 2.77. Cross dissolve transitions are added to the entire following clip and not just the transition duration. 'Import EDL" script will give a non-descriptive error if there are space characters in the reel name. The in EDLs the reel name column is always 8 characters wide and can contain spaces. "* From clip name:" should(also) be used to id filenames. All Pro NLEs(Ex. Avid, Premiere, Final Cut and Davinci Resolve) are using this comment to locate source files(full file name with extension, but no path). Once mentioned here: https://developer.blender.org/T48146 Only archaic EDL importers like the one in Lightworks only uses the reel name for file id, however in Lightworks the time code and reel name must be embedded in the source files (ffmpeg can read/write this). But as mentioned most other pro EDL importers have the option to ignore embedded time codes and use the comments to id filenames(instead of reel name). Ex. EDL file from Premiere: TITLE: 4tin2tin FCM: NON-DROP FRAME 001 AX AA/V C 00:07:16:20 00:07:21:12 00:00:00:00 00:00:04:17 * FROM CLIP NAME: 4tin2tin.mp4 002 AX V C 00:07:16:20 00:07:20:12 00:00:00:00 00:00:03:17 * FROM CLIP NAME: 4tin2tin.mp4 003 AX V C 00:07:20:12 00:07:20:12 00:00:03:17 00:00:03:17 FCM: NON-DROP FRAME 003 AX V D 025 00:37:45:21 00:37:47:12 00:00:03:17 00:00:05:08 EFFECTS NAME IS CROSS DISSOLVE * FROM CLIP NAME: 4tin2tin.mp4 * TO CLIP NAME: 4tin2tin.mp4 004 AX V C 00:37:46:21 00:37:48:12 00:00:04:17 00:00:06:08 * FROM CLIP NAME: 4tin2tin.mp4 005 AX V C 00:37:46:21 00:37:47:12 00:00:04:17 00:00:05:08 * FROM CLIP NAME: 4tin2tin.mp4 ------copypasta ends----- Apparently this summer interesting framework OpenTimelineIO was opened, with (buggy?) CMX 3600 module: https://opentimelineio.readthedocs.io/en/latest/tutorials/otio-plugins.html also https://github.com/iluvcapra/pycmx pycmx The pycmx package provides a basic interface for parsing a CMX 3600 EDL and its most most common variations. Features The major variations of the CMX 3600: the standard, "File32" and "File128" formats are automatically detected and properly read. ---------- Пересланное сообщение ---------- Тема: Interesting info about EDL I found .... Дата: Среда 30 октября 2019 Отправитель: Andrew Randrianasulu <randrianasulu(a)gmail.com> Получатель: "Cinelerra.GG" <cin(a)lists.cinelerra-gg.org> While translating (attempting to translate few still untranslated things) CinGG I found interesting note about EDL export. Intially I assumed it only works with some long-obsoleted device/soft, but today I found this page (while looking at timecode feature): https://eyeframeconverter.wordpress.com/mlt2edl/ MLT2EDL NB. Since Shotcut version 16.06 this script is not needed anymore. Shotcut can export EDL files natively: https://www.shotcut.org/blog/new-release-1606/ Mlt2edl is a python script for converting Shotcut mlt files into ex. Blender (v. 2.72 beta or higher) friendly CMX 3600 EDL files. The converted EDL files will also work in Lightworks and Resolve. Mlt2edl is based on the Kdenparse python script by Will Riley. Because CinGG (and original Cin) should be able to output exactly this EDL (???) format ... This mean she automatically compatible with "Lightworks and Resolve" and Blender, too?? Anyone can test this? -------------------------------------------------------

1 0

Interesting info about EDL I found ....
by Andrew Randrianasulu 30 Oct '19

30 Oct '19

While translating (attempting to translate few still untranslated things) CinGG I found interesting note about EDL export. Intially I assumed it only works with some long-obsoleted device/soft, but today I found this page (while looking at timecode feature): https://eyeframeconverter.wordpress.com/mlt2edl/ MLT2EDL NB. Since Shotcut version 16.06 this script is not needed anymore. Shotcut can export EDL files natively: https://www.shotcut.org/blog/new-release-1606/ Mlt2edl is a python script for converting Shotcut mlt files into ex. Blender (v. 2.72 beta or higher) friendly CMX 3600 EDL files. The converted EDL files will also work in Lightworks and Resolve. Mlt2edl is based on the Kdenparse python script by Will Riley. Because CinGG (and original Cin) should be able to output exactly this EDL (???) format ... This mean she automatically compatible with "Lightworks and Resolve" and Blender, too?? Anyone can test this?

1 0

Segfault if I try to change effect's position (below/above) relative to second effect (video)
by Andrew Randrianasulu 30 Oct '19

30 Oct '19

Hello again. I was looking at too-dark video from my phone and trying to use histogram + brightness/contrast filters. Attempting to move one full-video (from four files) spanning effect below/above (via context menu on effect's bar) another full-video spanning effect resulted in crash :( LANG=ru_RU.utf8 cin Cinelerra Infinity - built: Oct 26 2019 18:11:11 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 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 ** segv at 0x8658649 in pid 15344, tid 15449 writing debug data to /tmp/cinelerra_15344.dmp lock_items: 34 lock_frees: 3 ** dump complete Ошибка сегментирования

2 1

New dav1d is out - 0.5.1, claims even more speed on older processors
by Andrew Randrianasulu 30 Oct '19

30 Oct '19

I can't believe my eyes, but apparently this is not a typo ... https://code.videolan.org/videolan/dav1d/-/releases#0.5.1 dav1d 0.5.1 'Asiatic Cheetah', the fast and small AV1 decoder This is a minor update of the 0.5.0 version of dav1d, the fast and small AV1 decoder, codename 'Asiatic Cheetah'. 0.5.1 brings improvements in speed for SSE2 CPUs (up to 50% speedup), and ARMv7 CPUs (up to 41% speedup). It also fixes minor issues and minor speed improvements for other architectures. Changes for 0.5.1 'Asiatic Cheetah': ------------------------------------ 0.5.1 is a small release improving speeds and fixing minor issues compared to 0.5.0: - SSE2 optimizations for CDEF, wiener and warp_affine - NEON optimizations for SGR on ARM32 - Fix mismatch issue in x86 asm in inverse identity transforms - Fix build issue in ARM64 assembly if debug info was enabled - Add a workaround for Xcode 11 -fstack-check bug Found via Phoronix. Compiled and installed .. apparently no .so bump this time, so no recompile needed :P

2 1

Fwd: Can someone check DV-AVI (type 2) profiles I try to create with real interlaced project?
by Andrew Randrianasulu 29 Oct '19

29 Oct '19

I actually read some documentation, it says DV (usual Standard Resolution, at least) uses bottom field first: https://www.provideocoalition.com/field_order/ https://forums.creativecow.net/docs/forums/post.php?forumid=8&postid=566441… so, I put top=0 options in my profiles, they still render. but for HD DV story will be different: https://trac.ffmpeg.org/ticket/5092 ------------ The field order (i.e. topfield first) is wrong for DV HD video. It's actually due to a stupid change they made to the spec. The bits in the VAUX are the same but their meaning changed. In SMPTE 314M, which is for SD, field 2 refers to the even fields and field 1 refers the odd fields. But in SMPTE 370M, which is for HD, field 1 refers to the even fields and field 2 refers to the odd fields. So if the FS bit in the VAUX is 1 it means BFF in SD but TFF in HD. So we need a line in the code to flip the TFF flag if the file is HD. (the current code parses it according to the SMPTE 314M spec regardless of resolution) ------------- I have no idea what will happen if you try to fix two or more sources with different field order .. ---------- Пересланное сообщение ---------- Тема: Can someone check DV-AVI (type 2) profiles I try to create with real interlaced project? Дата: Понедельник 21 октября 2019 Отправитель: Andrew Randrianasulu <randrianasulu(a)gmail.com> Получатель: "Cinelerra.GG" <cin(a)lists.cinelerra-gg.org> I was trying to convince CinGG to make AVI DV (type 2, with separate audio, 48Khz/stereo/16 bit) I can use in older versions of Cin or for testing Kino. I think I'm closer to this goal, but I tried to make my dv files out of progressive content. real interlaced source/project probably will require "flags=+ildct+ilme" ? And probably field order .... Attached are my attemts, put avi_pcm_s16.avi in /usr/share/cin/ffmpeg/audio (or where your Cin installation put those profiles) and dv_pal.avi/dv_ntsc.avi in /usr/share/cin/ffmpeg/video Kino was segfaulting if I tried to use 422p (DVCPRO ? ) pixel format at encoding. 411p/420p still works .... Also, theora avi opt file just for lulz. -------------------------------------------------------

3 2