January 2023 - Cin - Cinelerra-GG Mailing Lists

history for ffmpeg.C
by Andrew Randrianasulu 05 Jan '23

05 Jan '23

I was puzzled by this https://github.com/cinelerra-cv-team/cincv-exp-akirad-paolo/commits/master/… at very start it says r413: Add a wrapper class for ffmpeg/libavcodec routines, with examples of use in fileyuv. Still in progress, but works for what it does so far. author: nkurz on Sep 7, 2004 I *guees* nkruz = nate=Nathan Kurz <nate(a)verse.com> from CinelerraCV AUTHORS we can see familiar #include <string.h> #include "filebase.h" #include "quicktime.h" #include "ffmpeg.h" #include "guicast.h" FFMPEG::FFMPEG(Asset *asset) { this->asset = asset; codec = 0; context = 0; picture = 0; got_picture = 0; } int FFMPEG::init(char *codec_string) { avcodec_init(); avcodec_register_all(); compare with code merged by William ===== @@ -0,0 +1,393 @@ +#include <string.h> + +#define HAVE_SWSCALER + +#ifdef HAVE_SWSCALER +extern "C" { +#include "libswscale/swscale.h" +} +#endif + + +#include "filebase.h" +#include "quicktime.h" +#include "ffmpeg.h" +#include "guicast.h" + + +FFMPEG::FFMPEG(Asset *asset) { + this->asset = asset; + codec = 0; + context = 0; + picture = 0; + got_picture = 0; +} + +int FFMPEG::init(char *codec_string) { + + avcodec_init(); + avcodec_register_all(); + + CodecID id = codec_id(codec_string); + codec = avcodec_find_decoder(id); + if (codec == NULL) { + printf("FFMPEG::init no decoder for '%s'", codec_string); + return 1; + } + + context = avcodec_alloc_context(); + + if (avcodec_open(context, codec)) { + printf("FFMPEG::init avcodec_open() failed\n"); + } + + picture = avcodec_alloc_frame(); + + + return 0; +} so I think we can relatively accurately conclude ffmpeg.C comes from cinCV development tree. So, I think, license header for this specific file should include all contributors listed in github history Paolo Rampino xiphmont = Monty Montgomery petterreinholdtsen (I think he still around! http://people.skolelinux.org/pere/blog/) Simeon Voelkel Plus, of course, William!

1 0

guicast/vicon.C history
by Andrew Randrianasulu 05 Jan '23

05 Jan '23

https://git.cinelerra-gg.org/git/?p=goodguy/history.git;a=history;f=cineler… So, correct line probably should be + * CINELERRA + * Copyright (C) 2016-2020 William Morrow + * because work on this file (and corresponding h/inc) was done over more than just year 2020 ?

1 0

fileffmpeg.C history digging
by Andrew Randrianasulu 05 Jan '23

05 Jan '23

So, it seems file was already present in CinHV 4.0 from around aug 2008 https://sourceforge.net/projects/heroines/files/releases/081108/cinelerra-4… same file present in 4.1 So I guess Monty only noticed it in 4.1 because 4.0 was "hiding" in 081108 folder. https://cinelerra.skolelinux.narkive.com/zRx84EEA/cincv-ffmpeg-based-file-r… this specific archive does not show exact date, but I guess 12 years ago will give us 2010 or so https://www.mail-archive.com/[email protected]/msg12045.html https://www.mail-archive.com/[email protected]/msg11759.html date is [CinCV] FFMPEG-based file reader for cinelerra [link to patch] Monty Montgomery Tue, 13 Jul 2010 02:00:23 -0700 sooo ... I think correct author lines will be 1) Adam's (c) 2008 2) Monty's (c) 2010 3) Paolo Rampino (2012-2014) 4) W.P.Morrow (2015-2020) 3) based on https://github.com/cinelerra-cv-team/cincv-exp-akirad-paolo/commits/master/… 4) based on https://code.google.com/archive/p/cinelerra/source/default/commits?page=2 "Good1.2Guy 2015-02-20 11:21:11 -0700 bf3a568a7ce3 CV file codec mods + a few fixes " bootstrap.c seems to be part of CinCV build system since initial commit in 2003: https://github.com/cinelerra-cv-team/cinelerra-cv/commit/696d7a41ec6bc52473… Because fileffmpeg.c/ffmpeg.C history is very convolved may be we should put 'evidence' links in header too? (because current CinHV fileffmpeg says 2016-2022 by Adam, I guess it was rewrite of 2008 code ..?)

2 2

AUTHORS file for cinelerra-GG?
by Andrew Randrianasulu 02 Jan '23

02 Jan '23

Because cinelerra-gg is merge of cin hv, cin-cv, various recent contributors on this list and Bill's own work I thought having AUTHORS file in sorce tree root will be good idea. Right now Cin-CV AUTHORS look like this (some emails outdated) hv=Adam Williams <broadcast(a)earthling.net> j6t=Johannes Sixt <johannes.sixt(a)telecom.at> minmax=Andraz Tori <Andraz.tori1(a)guest.arnes.si> herman=Herman Robak < herman(a)skolelinux.no> baver=Richard Baverstock <baver(a)thebeever.com> einar=Einar Runkaru <einarry(a)smail.ee> pere=Petter Reinholdtsen <pere(a)hungry.com> tfheen=Tollef Fog Heen <tollef(a)add.no> andreask=Andreas Kielb <andreaskielb(a)web.de> theraz=Tyler Geddes <tgeddes(a)wgeddes.com> dyce=Gergely Erdelyi <dyce(a)rovidzar.hu> dreamlx=David Arendt <admin(a)prnet.org> ga=Gustavo Iniguez <ga(a)kutxa.homeunix.org> memenk=Michael Eric Menk <meklev(a)osys.grm.hia.no> benjif=Benjamin Flaming <cinelerra(a)solobanjo.com> cobra=Kevin Brosius <cobra(a)compuserve.com> taraba=Mark Taraba <m_taraba(a)yahoo.com> nate=Nathan Kurz <nate(a)verse.com> mammique=Camille Harang <mammique(a)garbure.org> kbielefe=Karl Bielefeldt <uhauufo02(a)sneakemail.com> alexf=Alex Ferrer <alex(a)ftconsult.com> pmdumuid=Pierre Dumuid <pierre.dumuid(a)adelaide.edu.au> giskard=Riccardo Setti <giskard(a)autistici.org> jstewart=Joe Stewart <jstewart(a)lurhq.com> doudou=Sylvain Joyeux <doudou(a)melix.net> rafael2k=Rafael Diniz <rafael(a)riseup.net> nicolasm=Nicolas Maufrais <e.conti(a)gmx.net> raffa=Raffaella Traniello <raffaella.traniello(a)livecom.it> feranick=Nicola Ferralis <feranick(a)hotmail.com> akirad=Paolo Rampino <tuttoainternet(a)gmail.com> All in all 30 authors Cin-CV did a lot of bugfixing, build system , internationalization work, some plugin work. Also IIRC ffmpeg support appeared in some branch of cv "fork" while may be Adam and Bill come up with similar file on their own? cinelerra/cinelerra-5.1/cinelerra/ffmpeg.C contain no attribution ... guess we should track this down in history and fix CinHV aboutperfs.C contain this list (Myself only send literally few oneliners, but I guess my work on cingg merges into it) credits.append(new BC_ListBoxItem("Richard Baverstock")); credits.append(new BC_ListBoxItem("Karl Bielefeldt")); credits.append(new BC_ListBoxItem("Kevin Brosius")); credits.append(new BC_ListBoxItem("Jean-Luc Coulon")); credits.append(new BC_ListBoxItem("Jerome Cornet")); credits.append(new BC_ListBoxItem("Pierre Marc Dumuid")); credits.append(new BC_ListBoxItem("Nicola Ferralis")); credits.append(new BC_ListBoxItem("Alex Ferrer")); credits.append(new BC_ListBoxItem("Gustavo I<C3><B1>iguez")); credits.append(new BC_ListBoxItem("Tefan de Konink")); credits.append(new BC_ListBoxItem("Nathan Kurz")); credits.append(new BC_ListBoxItem("Greg Mekkes")) credits.append(new BC_ListBoxItem("Jean-Michel Poure")); credits.append(new BC_ListBoxItem("Monty Montgomery")); credits.append(new BC_ListBoxItem("Bill Morrow")); #ifdef X_HAVE_UTF8_STRING credits.append(new BC_ListBoxItem("Einar R<C3><BC>nkaru")); #else credits.append(new BC_ListBoxItem("Einar R\374nkaru")); #endif credits.append(new BC_ListBoxItem("Paolo Rampino")); credits.append(new BC_ListBoxItem("Andrew Randrianasulu")); credits.append(new BC_ListBoxItem("Petter Reinholdtsen")); credits.append(new BC_ListBoxItem("Eric Seigne")); credits.append(new BC_ListBoxItem("Johannes Sixt")); credits.append(new BC_ListBoxItem("Joe Stewart")); credits.append(new BC_ListBoxItem("Dan Streetman")); credits.append(new BC_ListBoxItem("Mark Taraba")); credits.append(new BC_ListBoxItem("Andraz Tori")); credits.append(new BC_ListBoxItem("Jonas Wulff")); 25 authors. (with overlap) Tefan de Konik looks like typo? Stefan, may be? https://lists.cinelerra-gg.org/pipermail/cin/2022-January/004602.html I think for cingg specifically we should add Bill, Sergey at very least and Andrea, Phyllis, Terje, IgorB, and other *testers* because without your work we newer had chance to move anywhere near our current state. (i guess we should say list is incomplete in first edition, because fishing out all contributor's names out of mail list archive will take time) I think we can go with second form of list, without emails? Usually email is useful if someone want to ask few questions, but because someone contribute to various cinelerra branches does not mean they are still on it ... So I guess leaving remark about incompleteness and links to current email archive is best we can do?

2 6

Fwd: Manual Appendix: Keyframes and Plugins
by Andrew Randrianasulu 01 Jan '23

01 Jan '23

---------- Forwarded message --------- From: Andrew Randrianasulu <randrianasulu(a)gmail.com> Date: Sun, Jan 1, 2023 at 7:23 PM Subject: Re: [Cin] Manual Appendix: Keyframes and Plugins To: Phyllis Smith <phylsmith2017(a)gmail.com> forwarded ... (I send image to Phyllis as attach, then tried to sent link to webhosting to list, forgot to check send to header ...) On Sun, Jan 1, 2023 at 6:32 PM Phyllis Smith <phylsmith2017(a)gmail.com> wrote: > Seems like it could be done - I hope someone who really knows responds. > But I will try to test it. The user sounds like he wants it to be totally > automated so even just adding keyframes in the right place may be more > effort than he wants. > https://freeimage.host/i/HuV62jf (f_stereotools apparently can do cingg keyframes ) stereotools suggested over pan filter by ffmpeg dev Paul Mahol > > On Sat, Dec 31, 2022 at 11:40 PM Andrew Randrianasulu < > randrianasulu(a)gmail.com> wrote: > >> >> >> сб, 31 дек. 2022 г., 05:11 Phyllis Smith via Cin < >> cin(a)lists.cinelerra-gg.org>: >> >>> I proofread and checked into GIT with only a minor change or 2. Wanted >>> to get this in for the builds tomorrow. Thanks to all. >>> >> >> >> I just saw question on libav-user list about virtual audio source. I >> thought pan filter from ffmpeg can do this, but at least in ffmpeg 5.1 it >> lacks runtime parameters tweaking, so your audio source can't travel from >> one side to another as track plays. I thought may be our key frames can do >> this? Anyone with two speakers to test? ( I have one, shame on me) >> >> I'll fwd full letter. >> >>> >>> On Fri, Dec 30, 2022 at 1:44 PM Andrea paz via Cin < >>> cin(a)lists.cinelerra-gg.org> wrote: >>> >>>> I have added a new section to the "Real-World" appendix. It is about a >>>> workflow on "Keyframes and Plugins" and is written by DeJay as a post >>>> in our forum. See if it is okay. >>>> >>>> @Dejay >>>> I've made minor changes, see if they work for you. If you have other >>>> changes or additions let me know. >>>> >>>> In addition to the .tex files I also attach the .txt file for everyone >>>> to read and review. >>>> -- >>>> Cin mailing list >>>> Cin(a)lists.cinelerra-gg.org >>>> https://lists.cinelerra-gg.org/mailman/listinfo/cin >>>> >>> -- >>> Cin mailing list >>> Cin(a)lists.cinelerra-gg.org >>> https://lists.cinelerra-gg.org/mailman/listinfo/cin >>> >>

1 0

Manual Appendix: Keyframes and Plugins
by Andrea paz 01 Jan '23

01 Jan '23

I have added a new section to the "Real-World" appendix. It is about a workflow on "Keyframes and Plugins" and is written by DeJay as a post in our forum. See if it is okay. @Dejay I've made minor changes, see if they work for you. If you have other changes or additions let me know. In addition to the .tex files I also attach the .txt file for everyone to read and review.

3 3

Fwd: [Libav-user] Creating Panned MP3 Clips
by Andrew Randrianasulu 01 Jan '23

01 Jan '23

---------- Forwarded message --------- От: Terry Corbet <tcorbet(a)ix.netcom.com> Date: вс, 1 янв. 2023 г., 09:10 Subject: [Libav-user] Creating Panned MP3 Clips To: <libav-user(a)ffmpeg.org> I have recently discovered how to use the Audacity Envelope Tool to turn a standard stereo MP3 file into a modified one in which throughout the entire duration of the clip the apparent source of the sounds will traverse from left to right. While I could use that workflow to manually perform the same transformation on multiple files, for my own use as well as to help other family members [who generally have limited computer skills] I want to automate that workflow. Over the past four days I have played as much catch-up on the many topics and toolkits which appear might permit me to engineer a software solution to this requirement. As a newbie, I probably will not correctly summarize what I believe to be the possible tools and approaches, so please forgive any misuse to the correct terminology. I hope/believe that I might be able to state my concepts/questions in a manner which will be most considerate of the time of those who participate in this mailing list and most quickly help me move closer to a good approach to the challenge. 01. I have managed to download the libraries which are used for the maintenance of the ffmpeg, ffprobe and ffplay triumvirate of tools. 02. I have managed to successfully build some sample C programs [taken from the doc\examples sub-directory and other miscellaneous snippets found by following the wonderful links from your Wiki] using the CodeBlocks IDE framework. 03. I have squirreled my way through the parts of the Doxygen documentation which seem like they would be most apropos. What I did not discover was any functions or examples of what I assumed I would be needing to do, which essential would be to process the audio frames of the FrontLeft [FL] and FrontRight [FR] channels of coming out of a stream of packets. That caused me to think that perhaps I would find examples of that processing by searching the Audacity sources to learn when and how they use the ffmpeg libraries. And somewhere between the Audacity and FFmpeg sites I stumbled upon some sources and some documentation concerning what I suppose are two reasonable libraries devoted to "resampling" -- soxr and swr. It was about at that point that I concluded that my modification of the sampled frames probably does not fall within the ambit of what is meant by resampling at all and that led to an investigation of what Nyquist was all about. Wow, what a guy Mr. Dannenberg must be. The 2007 Nyquist Reference Manual is a jaw-dropping read. I think that is enough background/context. Here's were I would appreciate any suggestions: A. Would it be possible to accomplish the steps necessary to achieve the desired result just using ffmpeg.exe? I imagine that, using the command line tool and an appropriate shell scripting language, it might be necessary to make multiple passes of the original .mp3 file and/or the two separate channels. I am not concerned about that loss of throughput; it will always be far faster than any manual procedure. B. Nonetheless, there are some advantages that would accrue from accomplishing the work entirely in an application .exe with a little GUI glitter to help the user be able to attempt some trial-and-error [preview] with slight changes in some of the parameters of the task depending upon the nature of the audio content and the manner in which the user will eventually play the output on different devices in different environments. Since I will not have the capabilities for building an Envelope in the manner that Nyquist [Lisp] accomplishes that, can anyone point me to any sample code doing that in C with the eight ffmpeg .dll libraries? C. Or -- and I appreciate that it is not fair to ask this of this mail group -- but I would appreciate any experience/advice as to whether the solution really ought to be accomplished by some scripting and/or macro facilities wrapped around Audacity? Thank you so much for the fantastic capabilities you have provided with the entire FFmpeg effort and for your patience in reading through my questions as the bell is about to strike on the New Year. _______________________________________________ Libav-user mailing list Libav-user(a)ffmpeg.org https://ffmpeg.org/mailman/listinfo/libav-user To unsubscribe, visit link above, or email libav-user-request(a)ffmpeg.org with subject "unsubscribe".

1 0