December 2018 - Cin - Cinelerra-GG Mailing Lists

End of December builds are available
by Phyllis Smith 02 Jan '19

02 Jan '19

There are new builds available at the cinelerra-gg.org website. GG really pushed the limits of coding this month in order to get closer to fully meeting expected features of an NLE. But thanks to additional support from testers and users and people reporting via email and MantisBT, this new release will hopefully be in good shape. He will be slowing down some in the "Happy New Year"! gg/Phyllis ------------------------------------------------------------------------------------------------------------- Cinelerra-GG (Version Infinity) Release Notes for 12/01/2018-12/31/2018 for builds 1. Inter-View mode / Identifying Source Targets shows in the Resources window preview are where the media is used or unused plus allows for seeing that portion in the viewer and positioning along the timeline. Usage is easy but not immediately obvious, so refer to section 46 in Features. 2. Cut and Paste behavior for moving, deleting, inserting, and grouping edits with various options has been added. And the selection process makes it possible to add transitions to multiple edits. In the same area Dragging changes and improvements have been made. See Section 47 in Features for details (or just middle mouse button on a track to see the options). Labels, autos, and keyframes will also be moved along in this new drag method but that feature has not yet been incorporated in the old drag method. 3. Color titles per media/proxy files is now an option with Autoselect colors (Settings→Preferences, Appearance tab) or Self-color. Refer to section 48 in Features Pdf file to details. *Super Testers* this month for the above 3 new features deserve special thanks for testing, feedback, and patience to include *Andrea, IgorBeg, Pierre, and Sam*. It made development a lot easier. 4. Because this is pervasive, a bugfix to Draw/ReDraw on the timeline is emphasized here to make you aware that in spite of testing, there could still be an issue. 5. Usability Improvements: View Thumbnail size, Vicon memory size, and Vicon color mode are now settable in Preferences to allow for bigger or less pixelated thumbnails when previewing. Preview window zoom scale for vicons in the Resources window using the middle mouse wheel. Video plugin expanders in Resources now has more categories and is improved thanks to Andrea. Cut and Paste editing mode (I-beam) now allows for grouping and column dragging. Shortcuts for “Align cursor on edits” and “Save settings now” have been added. New drag arrow so can see behind, for all themes except Bright, Blue Dot, and Neophyte. 6. Bugs/Issues fixed: Last month the following was mistakenly left out of the release notes – for deleting icons in the Resources window, the shift-delete control was replaced with Ctrl-shift-delete Upgraded bccmdl.py to python3 – credit to Frank Dana of rpmfusion. Reworked vicon view popup in order to add more capability. The Proxy preview has had 2 bugs fixed that led to bad behavior in the Resources window. A bug with listbox usage in the Titler plugin for font choice that made it more difficult to choose has been fixed. The fix affects all listbox but there should not be any repercussions. Drag and Drop mode had the white box highlighting incorrectly positioning; now fixed. Highlighting in the Resources window problem is now working correctly. Fix for vframe get_frame sporadic crashes when creating clips, or using Sketcher/CriKey. Placement for Vicons preview has been slightly modified to work better. Proxy with multiple viewers switch under certain conditions had a SEGV; now is fixed. Fixed crash occurring when removing from project while a preview of a thumbnail was playing. A problem with Proxy that had audio, which does not have a index, has been corrected. The drop position in Drag and Drop mode was incorrect in some cases. This has been fixed. Package creation, etc, for rpmFusion (credit Frank Dana) has recommended some improvements that make packaging more current mainstream. This includes adding noexecstack option on load, ensuring the executable bit is only set when necessary, and updating the desktop cin icon. Updated COPYING file containing GPLv2+ GNU General Public License. Double delete in Titler was found and fixed. Default proxy ffmpeg/mp4 selection had an incorrect setup so switched it to faster mpeg. Minor fixes in the Preferences sections for French language translations that were corrupted. Fix for filebox apply button on resize has been applied. Phantom keyframes showing on the timeline are now gone. Some leftover references were corrected to point to cinelerra-gg.org.

6 5

LATE last week's Summary Report for cinelerra-gg.org website (12/22-28 only)
by Phyllis Smith 31 Dec '18

31 Dec '18

*Summary Report for week Dec. 22 through Dec. 28 on Cinelerra-GG* Sorry for lateness and for some additional unnecessary commentary that I just had to add. For past weeks, see: https://lists.cinelerra-gg.org/pipermail/cin/ Website: - Always more website maintenance by Sam who keeps an eye on everything to ensure secure/usable. - *Good start* *on some initial translations *work for the website have been provided by WPfilmmaker – see issue #35 for work in progress by Sam/WPfilmmaker. More helpers welcome to assist. *Forum:* - The forum has been reworked to better align with user expectations. See issue #55 for discussion. Now, *especially the Q&A section *is better attuned to usage as it has been sectioned into Video, Audio, Hardware, and Miscellaneous and made more obvious as far as graphics and statistics. - Check out suggestions for some interesting ideas, such as gafferhq.org, voodoo camera tracking, contour jog wheel (which led to issue #83) *BugTracker:* 13 issues have been resolved or closed this week: ------------------------------------------------------------------- 7 real drag and drop without having to lock tracks (HIGH PRIORITY long awaiting implementation) 37 select feature on media resources works bad if proxy enabled 38 no red/white bar on preview vicon if proxy enabled 44 phantom keyframes boxes 45 load window apply minor bug 55 add filmmaking/video editing sections to the forum 58 changeable colors for the titles and background (IgorBeg has been “begging” for this for long time) 63 add BRAW to News and "Motion Graphics" to Features 67 the boxes encroach on French translations in Preferences 75 scrolling with mouse wheel doesn't work on the website 76 can't find a way to register on the forum 80 crash by repeatedly moving clips with effects. 82 mute button does not work correctly with selected clips 3 issues are resolved from our point of view, but waiting to close to make sure no fallout: -------------------------------------------------------------------------------------------------------------------- 59 packaging issues identified in source tree (this is resolved and will close soon) 60 cinelerra-gg sets unnecessary executable bits (this is resolved) 72 "Identifying source targets", does not work if I load old .xml files (vacillating on disarmed tracks) 7 new bugs/feature requests have been added and not resolved or closed: -------------------------------------------------------------------------------------------------- 73 Proxy folder behind the scenes instead 77 Review for creating a single manual (this will be ongoing and will be asking for review help) 78 FFStream::decode: Retry limit 79 AudioALSA::write_buffer err -32(Broken relay (pipe)) at sample 1 81 Add a donation page to the website? 83 Support for jog-wheels CONTOUR DESIGN ShuttlePRO V.2 and ShuttleXpress 84 Copy just the effects without the clip 16 are still open as previously noted: ------------------------------------------------ 2 masking enhancements and improvements (scheduling this to hopefully begin in January) 6 add a reset button to the video/audio plugins 25 Gui HiDPI future support (see Dec. 30 email from Terje for his information on this issue) 28 Add titler own background paper 31 the new function of identifying “source” targets still causes crashes (no new crashes yet) 34 label mouse over feature 35 translate the web site in different languages (progress being made here!) 42 live preview feature 57 mark the thumbnail when the clip is used 61 fedora installation instructions on website do not copy/paste correctly (Phyllis having trouble!) 62 google summer of code 2019 63 add BRAW to News and "Motion Graphics" to Features 64 Global Color Management in CinGG 66 remove "w" shortcut from all windows which closes the window 70 resource window: thumbnail preview 71 improve Videoscope plugin

1 0

Packaging for Arch Linux
by David Runge 30 Dec '18

30 Dec '18

Hey there, I have just dropped the cinelerra-cv package from the official repositories on Arch Linux (to the AUR). Initially I planned on replacing it with cinelerra-gg, but I don't think this is very feasible at this point in time. I started to attempt a build, that is dynamically linked against the required system libraries [1], but it seems to be an equal amount of work compared to cinelerra-cv, which is not at all feasible. This is not because of the libraries themselves failing to work or missing symbols or anything like that, but because the build system actively prevents building a dynamically linked application! However, I already hack-fixed a great deal of things compared to the upstream provided attempt [2] (on a static build), which really doesn't need to depend on all the packages, that the PKGBUILD lists in depends=() (because of its static nature). That aside, a static build of this size in the official repositories of Arch Linux is not ever going to become a reality (nor in any other distribution), if nearly all of the components are available as a package. Therefore I would like you to consider to fix a great deal regarding the build system of cinelerra-gg to remedy this situation and move towards a (mostly) dynamically linked application instead. I believe this can be fairly straight forward with dynamic rebuilds against different versions of the required libraries in a continuous integration pipeline! The tools are there. In case static builds is what you will be going for no matter what, disregard the rest of my e-mail. That being said, I had to hack in nearly all of the --libs (which could just easily be gotten by calls to pkg-config, instead of hardcoding some of them or just not making them available at all) and also some of the --cflags for lv2 integration. I'm left with a (working!) application (probably with a bunch of broken edges), that - unfortunately - doesn't feature full RELRO [3] (because LDFLAGS are not propagated throughout all the components), PIE [4] (not implemented), has executable stack [5] (which I haven't encountered before with any of the other software I package, but is apparently pretty bad) and *a lot* of "unused shared library" references (due to the bizarre "libs" files being used to store all the library names instead of dynamically assembling them, when needed). The naming of the project, its subdirectories and (un-)declared/undocumented thirdparties (which of them are real thirdparties, which are your own/modified?) are confusing. The project does not (yet) have a form of versioning (at least not reflected in actual git tags), unless you're up for using calver (I recommend semver to actually be able to discern different levels of stability, feature availability and to work towards a roadmap). Considering providing (unsupported) builds for Arch Linux: Please use the AUR for providing PKGBUILDs and name the package according to your upstream (cinelerra-gg), unless you have the intent to rename the project. Make sure to use devtools [8] (e.g. `extra-x86_64-build -c` in the directory of the PKGBUILD) to build your package. It will give you *a lot* of additional information, as the package build is done in a pristine containered build, using systemd-nspawn. In case cin [7] is done by you: Please, never push binary data to the repositories! Closing, please don't get me wrong: It's your project and all, but this is a situation, that will drive away any potential packager of the software as it's just too complicated to plainly build (no matter the eventual runtime problems one might get)! I know this project has come a long way, but I believe it would benefit from a general cleanup and restructuring, which will render it much more accessible! Best, David P.S.: If you have any questions regarding the Arch Build System (ABS), or packaging on Arch Linux, or my PKGBUILD (which was still a WIP, when I stopped), shoot away! [1] http://pkgbuild.com/~dvzrv/aur/cinelerra-gg/PKGBUILD [2] https://git.cinelerra-gg.org/git/?p=goodguy/cinelerra.git;a=blob;f=cinelerr… [3] https://mudongliang.github.io/2016/07/11/relro-a-not-so-well-known-memory-c… [4] https://en.wikipedia.org/wiki/Position-independent_code [5] https://en.wikipedia.org/wiki/Executable_space_protection [6] https://aur.archlinux.org [7] https://aur.archlinux.org/cgit/aur.git/tree/?h=cin [8] https://www.archlinux.org/packages/extra/any/devtools/ -- https://sleepmap.de

2 3

Open Issue "#25 Gui HiDPI future support"
by Terje J Hanssen 29 Dec '18

29 Dec '18

Hi, According to the weekly reports, the open Issue list includes "#25 Gui HiDPI future support". For information, on a Dell XPS 13 (9370) ultrabook with a 13.3" UHD 4K panel with Leap 15/Gnome 3.26.2 installed (beside Ubuntu 18.04), its HiDPI properties are xrdb -query | grep dpi Xft.dpi: 240 xrandr Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 8192 x 8192 eDP-1 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 294mm x 165mm The first attached screenshot shows that the Cinelerra 5.1 default UI scale become too small and tiny and "difficult readable" here. As a work-around the font and icon scales can be extended twice using the following commands in typical the .profile: export BC_ICON_SCALE=2 export BC_FONT_SCALE=2 This fit well on the main window menu text, but causes distorted located text on i.e the Setting>Format subwindow as shown on the second screenshot attached. -------- Terje J. H

1 0

Re: [Cin] Cinelerra crash when loading DV files
by Terje J Hanssen 29 Dec '18

29 Dec '18

Hi Joe, Just some additional comments, as neither me experienced any crash when I tested loading DV files of various sizes on two different Leap 15 machines with the current Cin-gg build (one month newer than yours): //usr/bin/cin // //Cinelerra Infinity - built: Nov 29 2018 09:49:38// //git://git.cinelerra-gg.org/goodguy/cinelerra.git// //(c) 2006-2018 Heroine Virtual Ltd. by Adam Williams// //(c) 2007-2018 cin5 derivative by W.P. Morrow aka goodguy/ The original source for my DV files (408MB, 508MB, 2.1GB) has been analog Hi8 video converted to DV through an A/D video converter. These DV files also play ok with ffplay on Leap 15 (ffmpeg-3 v. 3.4.4-lp150.9.5 x86_64, packman) which in my case confirms the following file properties: /ffplay dv02_06.dv // //ffplay version 3.4.4 Copyright (c) 2003-2018 the FFmpeg developers// // built with gcc 7 (SUSE Linux)// // configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --incdir=/usr/include/ffmpeg --extra-cflags='-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g' --optflags='-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g' --disable-htmlpages --enable-pic --disable-stripping --enable-shared --disable-static --enable-gpl --disable-openssl --enable-avresample --enable-libcdio --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libcelt --enable-libcdio --enable-libdc1394 --enable-libfreetype --enable-libgsm --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libzimg --enable-libzvbi --enable-vaapi --enable-vdpau --enable-libfdk_aac --enable-nonfree --enable-libx264 --enable-libx265 --enable-libxvid// // libavutil 55. 78.100 / 55. 78.100// // libavcodec 57.107.100 / 57.107.100// // libavformat 57. 83.100 / 57. 83.100// // libavdevice 57. 10.100 / 57. 10.100// // libavfilter 6.107.100 / 6.107.100// // libavresample 3. 7. 0 / 3. 7. 0// // libswscale 4. 8.100 / 4. 8.100// // libswresample 2. 9.100 / 2. 9.100// // libpostproc 54. 7.100 / 54. 7.100// // //[dv @ 0x7fb934000b40] Estimating duration from bitrate, this may be inaccurate// //Input #0, dv, from 'file:///run/media/terje/Seagate_4TB_back/video/DV/dv02_06.dv':// // Metadata:// // timecode : 00:59:38:22// // Duration: 00:02:26.88, start: 0.000000, bitrate: 28800 kb/s// // Stream #0:0: Video: dvvideo, yuv420p, 720x576 [SAR 16:15 DAR 4:3], 25000 kb/s, 25 fps, 25 tbr, 25 tbn, 25 tbc// // Stream #0:1: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s// / --------------------- Terje J. H On Fri, 2018-12-28 at 09:49 +0100, joe wrote: > Dear Cinelerra experts, > > I'm doing following: > > 1. Start Cinelerra GG official build on the Oct 31, 2018 10:50:41, > OS: Suse 15.0 > 2. Menu: Settings/Format: choose preset PAL 576I - DV(D) > 3. Menu: File/Load files (create new resources only) - choose an > arbitrary DV file (eg. one with length of ~5 secs, 20MByte), click on > OK > > then immediate crash. If I start cinelerra from a console, I see > following messages: > > > joe at 192:~> cin > > Cinelerra Unify - built: Oct 31 2018 10:50:41 > ------- > > lang changed from 'en_US.UTF-8' to '' > > init plugin index: /usr/lib64/cin/plugins > > init lv2 index: > > *** buffer overflow detected ***: cin terminated > > Aborted (core dumped) > > joe at 192:~> > > > The issue seems to be sprecific to DV, because I have no problems > with importing other formats.

2 1

Happy New Year at all
by Wolfgang Brunner 29 Dec '18

29 Dec '18

Ein Youtuber, mit dem ich in Kontakt bin, hat gelegentlich ein Video gepostet, das ich Ihnen zeigen möchte. Er ist kein Videokünstler, macht ganz andere Dinge, je beeindruckender das Ergebnis. Ich wünsche Ihnen allen viel Freude. https://www.youtube.com/watch?v=gPZ4N-ZEJhk&feature=em-uploademail -- Lg Wolfgang

1 1

Just checked into GIT a couple of things
by Phyllis Smith 29 Dec '18

29 Dec '18

- The phantom keyframes fix for issue 44 was fixed. - A new drag icon that Sam designed which lets you see behind is used in all themes except Bright and Blue Dot which had white backgrounds and Neophyte which already had a see through white/yellow icon. - But most importantly the labels, autos, and keyframes will be copied/pasted and dragged along with the clips. This capability has been missing for quite some time. gg/phyllis

3 5

Cinelerra crash when loading DV files
by joe 28 Dec '18

28 Dec '18

Hi CinGG experts, previously I sent my problem to the wrong list, now I'm coming to you. Since I have already a workaround (see below), my post below should rather be taken as a f.y.i. I appreciate your efforts very much, thank you - I wish you guys a happy new year for 2019! Bye, Joe -------- Forwarded Message -------- Date: Fri, 28 Dec 2018 11:07:45 +0100 Subject: Re: [CinCV TNG] Cinelerra crash when loading DV files To: cinelerra(a)lists.cinelerra-cv.org Reply-to: cinelerra(a)lists.cinelerra-cv.org From: joe <joe(a)fasor.hu> Hi all, meanwhile, I have a workaround, so it's not so critical for me any longer. However, the problem seems to be even more interesting with my new observations: If I change the container from DV to avi: ffmpeg -i {original.dv} -c copy -map 0 {newcontainer.avi} ... then cinelerra has no more problems with loading it! I'm sending this piece of info to you with the hope that it might help you guys, to improve cinelerra. Many thanks for your continuous efforts! Bye, Joe On Fri, 2018-12-28 at 09:49 +0100, joe wrote: > Dear Cinelerra experts, > > I'm doing following: > > 1. Start Cinelerra GG official build on the Oct 31, 2018 10:50:41, > OS: Suse 15.0 > 2. Menu: Settings/Format: choose preset PAL 576I - DV(D) > 3. Menu: File/Load files (create new resources only) - choose an > arbitrary DV file (eg. one with length of ~5 secs, 20MByte), click on > OK > > then immediate crash. If I start cinelerra from a console, I see > following messages: > > > joe@192:~> cin > > Cinelerra Unify - built: Oct 31 2018 10:50:41 > > git://git.cinelerra-cv.org/goodguy/cinelerra.git > > (c) 2006-2018 Heroine Virtual Ltd. by Adam Williams > > (c) 2007-2018 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. > > > > lang changed from 'en_US.UTF-8' to '' > > init plugin index: /usr/lib64/cin/plugins > > init lv2 index: > > *** buffer overflow detected ***: cin terminated > > Aborted (core dumped) > > joe@192:~> > > > The issue seems to be sprecific to DV, because I have no problems > with importing other formats. > In fact, if I convert this particular file to: > ffmpeg -i {input.dv} -c:v libx264 -preset slow -crf 23 -c:a copy > {output.mkv} > > Then it is imported to cinelerra without any problems. > Does anyone of you have an idea what migth be the problem, solution? > > Thanks, > Bye, Joe > > _______________________________________________ > Cinelerra mailing list > Cinelerra(a)lists.cinelerra-cv.org > https://lists.cinelerra-cv.org/cgi-bin/mailman/listinfo/cinelerra _______________________________________________ Cinelerra mailing list Cinelerra(a)lists.cinelerra-cv.org https://lists.cinelerra-cv.org/cgi-bin/mailman/listinfo/cinelerra

2 1

My messages in the forum are "awaiting moderation" any reason behind that?
by W P 28 Dec '18

28 Dec '18

Hi all, out of 5 messages sent 2 ended up being in "awaiting moderation", is it because of the content or??IP? I would imagine if the forum gets more users it will be a pain to review "suspicious" (mine weren't!) messages manually. Maybe an anti-bot/spam solution would be better? Also just in case someone was wondering, WPfilmmaker2 is me, apparently I had already registered in the forum (I don't remember at all! I always had issues signing-up) so I just made another account, so it is not someone tryng to impersonate me^^

2 2

Fwd: Fw: [CinCV TNG] Easiest way to remove plugins after new download of Cin-GG
by Phyllis Smith 28 Dec '18

28 Dec '18

Ed, > I installed cinelerra GG today in OpenSuSE Leap 15.0 and imported an old > project. I was surprised that it chewed up nearly all of the 12Gb of > memory. Cinelerra also reported (in red) that it had failed to load the > project. Now I did not check if it could be played from the beginning until > the end, yet I could play it for some time. Looks as if it did import the > project. > > Now I have installed OpenSuSE yesterday anew, but cannot remember I did > anything special. > > It is not the first time that Cinelerra uses a big amount of memory. > > What could be the reason? > Check to see what you have Cache set to and check memory usage as described below. It does not make sense that cin is using that much memory. "Cache" in Settings->Preferences, Performance tab is used to store images on the timeline. One 1080 frame uses about 10 MB. The default setting is 256 and this is enough for testing and running. However, why not use more memory if it is available. To experiment for testing a good number tuned to the way you use your computer, set the cache to 0, bring up cin5, load a typical media file, play it and run "top" on another terminal window to see how much memory is being used. In the "top" display, look at "free" memory. Whatever your computer is not using, is a good number to use for cache. If you start other programs, or change the design of the session so that it uses a lot of frame storage, you may need to re-experiment over time. " Cinelerra-gg is not using the cinelerra-cv mailing list but has its own you can get to at cinelerra-gg.org. If the above does not help, please reply to here instead. (P.S. I made a HUGE mistake by sending out email there that I meant to only send to WP.) Thanks, gg/Phyllis

1 0