- Cin - Cinelerra-GG Mailing Lists

two more patches
by Andrew Randrianasulu 29 Jan '23

29 Jan '23

One alter bsd.bld for telling configure to use clang (on freebsd), so build spew less warnings there. Second patch raises libvpx limit for internal ffmpeg, so you can test it on monster machine (do not forgot to alter vp9 profile a bit so it will try to use more threads)

2 1

CinCV early history (2003-2011)
by Andrew Randrianasulu 28 Jan '23

28 Jan '23

Well, our link [0] only gives access to late CinCV TNG (?) archives since 2014 There was more history. Currently i tried to wget -m https://web.archive.org/web/20110511132711/https://init.linpro.no/pipermail… and got 100 Mb big mbox! (2003-2011) I also try to archive this one https://web.archive.org/web/20200710015535/https://lists.skolelinux.org/pip… (2003-2019) I do not know how to get full archive from narkive or mail-archive.com [0] https://lists.cinelerra-cv.org/pipermail/cinelerra/ - linked as "Cin-CV email archive complete Here you can find the complete Cinelerra-CV email archive." I think we have bug in bugtracker about this .... https://www.cinelerra-gg.org/bugtracker/view.php?id=132 ah, lol, Terje pointed cin-cv archive was just under different directory "old Cin-CV(S) email Archive: 2001 (mainly 2003) - 2016 https://lists.cinelerra-cv.org/pipermail/cinelerra-skolelinux/" always nice to have more than one archive

1 2

Revision Proxy section on Manual
by Andrea paz 27 Jan '23

27 Jan '23

IgorBeg did a great job of revising the Proxy section of the manual. I have put it in Latex, see if that works for you. I take this opportunity to remind you that the CinGG manual is a "work in progress", if you would like to help revise and improve it, you are welcome. PS: I am also attaching Igor's odt version so you can all read it and see the nice work done and also propose changes.

4 21

NetBSD fixes
by Andrew Randrianasulu 27 Jan '23

27 Jan '23

I tried to fix NetBSD build without breaking FreeBSD, Linux and termux.. It seems I successed! Attached patches builds (and runs) on NetBSD 9.2 I386 FreeBSD 12.3 amd64 Slackware 15.0 i586 Termux aarch64 all without-thirdparty for saving build time. Can you test them on your usual systems?

2 3

Fwd: oh, my fix for nested edl undo crash regressed video!
by Andrew Randrianasulu 27 Jan '23

27 Jan '23

---------- Forwarded message --------- От: Андрей Рандрианасулу <randrik(a)mail.ru> Date: пн, 14 нояб. 2022 г., 04:37 Subject: oh, my fix for nested edl undo crash regressed video! To: randrianasulu <randrianasulu(a)gmail.com> better (?) fix (tested with video this time) -- Андрей Рандрианасулу

3 12

libvpx via ffmpeg on high-cpu machines
by Andrew Randrianasulu 26 Jan '23

26 Jan '23

I think this one can be safe to test, if you have >16 cpu/thread machine ... https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/c13d95934327ddad4db30f6aee9…

3 7

Complete system hangs (likely out of memory)
by Stefan de Konink 25 Jan '23

25 Jan '23

Hi, When editing with Cinelerra (current git) I experience frequently that my entire system hangs after scratching through either the timeline or the viewer. As experienced before I have noticed that Cinerella eats a lot of memory. The total amount of assets I have currently in my project is about 70GB, my system memory is 16GB, and yesterday I have added 8GB of swap (normally no swap). It seems that with every video that I preview my memory usage significantly increases, but is never released. I think we have discussed this behavior on the mailinglist before being that the indices never get released. But still the amount does not make sense to me. As user my expectation would be that when I would close the *viewer*, the memory would get released, especially when the content is not placed on the timeline. Are there any statistics available on the memory usage what goes where? Practical question: is it possible to have a different path for the emergency backups than /tmp? -- Stefan

5 26

Re: [Cin] Cin Digest, Vol 51, Issue 40
by Richard Nolde 25 Jan '23

25 Jan '23

Regarding memory leaks: > 1. Re: Complete system hangs (likely out of memory) > (Stefan de Konink) > 2. Re: Complete system hangs (likely out of memory) > (Stefan de Konink) > 3. Re: Complete system hangs (likely out of memory) > (Andrew Randrianasulu) The following tool has been instrumental in finding memory leaks and/or peaks of usage in a large graphically intensive program that I have helped another developer with from time to time. https://apps.kde.org/heaptrack/ https://github.com/KDE/heaptrack It comes with text and GUI analyzer tools to allow you to see which functions allocate/release/leak memory during the run of a program and it does not slow down the execution nearly as much as valgrind. It uses a replacement version of malloc and the LD_PRELOAD option to redirect system calls into its own instrumented versions of memory related system calls. Originally written by Millan Wolff in Berlin, it has now become a part of the KDE development environment but it does not require you to run a full KDE desktop. I run in with XFCE on Fedora 36 without any problems. Richard Nolde

2 1

Re: [Cin] Complete system hangs (likely out of memory)
by Andrew Randrianasulu 24 Jan '23

24 Jan '23

пн, 23 янв. 2023 г., 18:45 Stefan de Konink <stefan(a)konink.de>: > Hi Phyllis, > > With the suggestion of Richard Nolde, I decided to do a day of work in > Cinerella with heaptrack enabled in the background. It was a pleasant > surprise how well it performed. (And no crashes ;) > > And I am also surprised how functional Heaptrack itself has been designed, > I'll forward this application to my peers. To screenshots attached. > Thanks for being curious, Stephan! I looked at attached screenshots and I found it strange how Peaked and Leaked basically stays very near each other for each function line? > If anyone is intested in my heaptrack file, I can obviously make it > available. But I would really recommend adding this tool to your toolbelt! > > -- > Stefan

3 24

Re: [Cin] Complete system hangs (likely out of memory)
by Stefan de Konink 23 Jan '23

23 Jan '23

Hi Phyllis, With the suggestion of Richard Nolde, I decided to do a day of work in Cinerella with heaptrack enabled in the background. It was a pleasant surprise how well it performed. (And no crashes ;) And I am also surprised how functional Heaptrack itself has been designed, I'll forward this application to my peers. To screenshot attached. If anyone is intested in my heaptrack file, I can obviously make it available. But I would really recommend adding this tool to your toolbelt! -- Stefan

1 0