- Cin - Cinelerra-GG Mailing Lists

Curiosity: Android Studio
by Andrea paz 05 Jan '19

05 Jan '19

Curiosity: why Android Studio? Isn't it just Java and just for android?

3 2

Ungrouping of video and audio clips after some edits
by Xing Tu 05 Jan '19

05 Jan '19

It'd probably be easier to just show what's going on. Here's a short video https://youtu.be/QOSCdSH4Szc. Would this be considered a bug? Maybe there's some way around it... but it shouldn't be the default behavior.

4 10

Forum registration - Key is invalid
by Jedi Knight 03 Jan '19

03 Jan '19

Hello I'd like to register to Your forum, but after registration/password change i see only message "Key is invalid" or something like that. Please, help. P.S. I have also this situation on two another WordPress-based websites forums. Awful CMS ... Happy new year with Cinelerra.

2 1

Re: [Cin] Cin Digest, Vol 3, Issue 5
by Wolfgang Brunner 03 Jan '19

03 Jan '19

https://www.youtube.com/watch?v=kXdCBwWy2TY Reframe Rt I had already as a topic Am Mi., 2. Jan. 2019 um 21:51 Uhr schrieb < cin-request(a)lists.cinelerra-gg.org>: > Send Cin mailing list submissions to > cin(a)lists.cinelerra-gg.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.cinelerra-gg.org/mailman/listinfo/cin > or, via email, send a message with subject or body 'help' to > cin-request(a)lists.cinelerra-gg.org > > You can reach the person managing the list at > cin-owner(a)lists.cinelerra-gg.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Cin digest..." > > > Today's Topics: > > 1. Re: Cinx - 10-bit h264 and/or h265 (Terje J Hanssen) > 2. Re: Ungrouping of video and audio clips after some edits (Xing Tu) > 3. ReframeRT, Interpolate Video (Andrea paz) > 4. Re: ReframeRT, Interpolate Video (Xing Tu) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 2 Jan 2019 19:46:55 +0000 > From: Terje J Hanssen <terje(a)nordland-teknikk.no> > To: "cin(a)lists.cinelerra-gg.org" <cin(a)lists.cinelerra-gg.org> > Subject: Re: [Cin] Cinx - 10-bit h264 and/or h265 > Message-ID: <ebc8550e-c8db-75c2-6ee9-96c5b5539eb4(a)nordland-teknikk.no> > Content-Type: text/plain; charset="utf-8" > > Is Cinelerra10bit (Cinx) based on 10-bit x264 or 10-bit x265? > It is based on x265 BUT there is a enable flag in the build scripts for > anyone doing there own build to use x264 instead. > > Thank you for clarifying and confirming that, which was what I initially > thought. > > The confusion and uncorrected manual resulted in falsely believing that > the maintainers of x264 included the possibility of having both 8/10 bit > working without having to make a special compile. We were fooled for a > month or so and I had updated the manual and did not correct it > > Yes, I remember that (refer your previous mail 07.06.2018). > > But as Cinelerra (Cin) then is based on x264, I wonder if the following > reference below is something that has been incorporated later in x264 and > possibly yet change that "Cin" has the opportunity to work with both 8-bit > and 10-bit x264? > > x264 supports both 8-bit and 10-bit outputs, and you don't have to do > anything special. > ffmpeg -h encoder=libx264 > ...... > Previously you had to compile x264 with --bit-depth=10, and then link your > ffmpeg to either an 8-bit or 10-bit libx264, but that is now unnecessary. > See Unify 8-bit and 10-bit CLI and libraries for more info. > > https://video.stackexchange.com/questions/13164/encoding-422-in-10-bit-with… > See Unify 8-bit and 10-bit CLI and libraries for more info. > > https://git.videolan.org/?p=x264.git;a=commit;h=71ed44c7312438fac7c5c5301e4… > > > Very interesting and promising signals regarding better help and > documentation, if this succeed to make things easier for new users to start > with and next continue with Cinelerra. It is known this has been an > Achilles heel and has caused the impression of a steep learning curve. > > Terje > > > Den 02.01.2019 18:02, skrev Phyllis Smith: > Is Cinelerra10bit (Cinx) based on 10-bit x264 or 10-bit x265? > It is based on x265 BUT there is a enable flag in the build scripts for > anyone doing there own build to use x264 instead. > The confusion and uncorrected manual resulted in falsely believing that > the maintainers of x264 included the possibility of having both 8/10 bit > working without having to make a special compile. We were fooled for a > month or so and I had updated the manual and did not correct it > > GG is doing a Leap15 cinx experiment right now so I can get the wording > correct in the manual since we have not re-tested it in quite some time. > And I will try to be consistent in the terminology as you suggested too. > > A single, updated manual for "Cinelerra-GG Infinity" sounds to be to the > 'right time', and yes, I will report typos/faults/RFEs on areas I see the > demand for more detailed explanations or procedures. > > In general a 'single manual' needs to fill the demand for a combined > "Users Guide" beside a "Reference or Feature Guide", maybe also as a online > html and pdf print. And especially the new "gui ease of use" with the new > "Cinfinity plugins icon set" compared with the original default icons or KB > shortcuts as a reference. > Issue #77 in MantisBT is planned to be used to get reviewers help on the > manual. > > Maybe this is a possibility to create a more integrated Help-system for > Cinelerra-GG Infinity? > > I.e a "Help" menu with > > - link to the online manual > - context sensitive Help? > - the "About" button > Believe it or not we actually have 2 shortcut single letters left in the > english alphabet for use on the main window. One of these is "h" and we > are saving it for Help ! The other letter is "p" which I think should be > saved for "p-hyllis". > > P.S. gg's experiment was done faster than I could finish this email due to > interruptions. With CINX, you can ONLY create 10-bit output when you > render. gg/phyllis > > > >

1 0

ReframeRT, Interpolate Video
by Andrea paz 03 Jan '19

03 Jan '19

I don't understand how these two plugins work. The explanations on manual-cv are not clear (for me, of course). Can someone who knows how to use them explain how they work? (it's used to make the new unified manual). GG/Phyllis you can't answer, it's just to make sure you don't waste your time :-)

2 5

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