[CinCV] News statement regarding domain change
Hi Einar, as you were the by far most active cinelerra-cv developer during last year, I would highly appreciate your opinion on the current situation with cinelerra-cv.org and the reregistration of cinelerra.org. Are there indeed any plans to shift development back to cinelerra.org, as they claim? I haven't seen any such announcement on our mailinglist... Have you been contacted by the new registrant of cinelerra.org, Michael Collins? If both is not the case, I strongly suggest to update our news page. @All: As nobody responded to my call for statements on Mar 7 2014, I prepared some suggestion for a news update myself, see below. Comments and improvements are highly appreciated. If there are no objections, I push the news statements to our website. Regards, SimAV Proposed news statements: Mar 7, 2014 Our Bugtracker on bugs.cinelerra-cv.org and gitweb on git.cinelerra-cv.org/gitweb are back. Mind the -cv in the domain name! All git users should update their remote URL to the new domain git.cinelerra-cv.org. Feb 23, 2014 Our obsolete domain cinelerra.org was reregistered by someone else and currently shows an outdated and modified, static website copy. For verifying future news statements, please refer to our mailing list cinelerra@skolelinux.no Jan 20, 2014 Cinelerra-CV has moved to cinelerra-cv.org. Our new domain name reflects how cinelerra is named in several popular distributions and clarifies that it is the home of the community version of cinelerra. ___ Cinelerra mailing list Cinelerra@skolelinux.no https://lists.skolelinux.org/listinfo/cinelerra
[CinCV] news statement?
Hi all, any volunteers (or even better: suggestions ;) ) for a news statement on cinelerra-cv.org regarding the domain move? I think an announcement would be an appropriate way of avoiding confusion... SimAV ___ Cinelerra mailing list Cinelerra@skolelinux.no https://lists.skolelinux.org/listinfo/cinelerra
[CinCV] apache config updated, irclog and trac are back.
Hi all, while investigating the whereabouts of irclog.cinelerra-cv.org I recognized that the apache configs still use cinelerra.org as ServerName and inside RewriteRules. @Metta (and everyone else who has root on the server): You find a diff of my changes in /root/docs/apache2_sites-available_update_to_cinelerra-cv.SimAV.* irclog.cinelerra-cv.org and bugs.cinelerra-cv.org are back now. Please note that my changes can't fix the tons of hardcoded bad/outdated links on the website. That needs separate manual/scripted fixing and might be done best after moving the website to git, so all changes get documented automatically? SimAV ___ Cinelerra mailing list Cinelerra@skolelinux.no https://lists.skolelinux.org/listinfo/cinelerra
Re: [CinCV] Cinelerra crashes on using SVG filter
Hi Einar! I hit that bug somewhen back in 2009 and found a workaround: http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=commit;h=99bb78bb86b43f127c95b2261817637d106cff9a http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=commit;h=ca17d38b8bb89895af4e711ebb9e3856e8e80d3a http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=commit;h=1f107bba0eec5d994990610336a521439aceaa85 http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=commit;h=6f6ec2ac194fc5e6a3acd6fc2bc5f84fc4b8d485 http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=commit;h=592673a39d3ddb1ba66a087c09362ecebab0d6a4 http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=commit;h=081cb8f33400011b6f05e6fea7ebe6f0dbee89ec I don't know whether these commits still work with Cin2.2CV, but they should give at least a hint how that problem can be worked around... :) With best regards, Simeon ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] Cinelerra on >=2.6.38 (patch removing buzz and v4l1 support)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, today i updated my kernel to 2.6.39 and was able to compile cinelerra after applying Nicola's patch from bugs.cinelerra.org to j6t's repo. In my opinion we should support recent kernels rather soon. So i wonder whether we have to keep v4l1 and buzz supported or whether removing support therefore (what Nicola's patch does) is fine, too. Personally speaking i would vote for the second choice as we have extremely limited resources for maintenance. However, if (and only if) this hardware should be still in use by Cinelerra users (please speak up if that's the case for you!) we should consider adding an option to configure. Regardless wheter we want to make support optional or remove it completely, i suggest to release a new version of cinelerra (2.1.6?) supporting linux kernels >=2.6.39 as soon as possible. What is you opinion on that? Regards, Simeon -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3f378ACgkQph/voQkhF7wY2QCfbmllYDUFhhQALALNdzJJT642 2YEAoMa4VCHslFLFwMqp7aN6/WeeoqqX =4oJ+ -END PGP SIGNATURE- ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] Re: Release of Cin2.1.5CV?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/20/10 11:19, Einar Rünkaru wrote: > May be someone has time to look at libmpeg3 from my tree and consider > including it in the new release. I have fixed > toc file generation, decoding subtitles... The toc-file is much > shorter and has right offsets, so seeking in mpeg is quicker and > error-free. > > Einar Hello Einar, libmpeg3 is already on my list, however I doubt that I'll have any time soon for reviewing your commits (does anyone else have?). But of course libmpeg3 fixes have a high priority for the next release (2.1.6 i guess), which shouldn't take too much time anymore. With best regards, Simeon -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkznojkACgkQph/voQkhF7yNGACgjFEdUyI1hm2ClVZk2CzKmKB9 vAUAnjrCUyvTU8buEFMk7Qn1esrLU9Ue =lhdU -END PGP SIGNATURE- ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] Release of Cin2.1.5CV?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Hannes, I just wanted to inquire when we finally increase the version number to 2.1.5 as I couldn't see any changes on the git repos for about two weeks now. I conclude that there is obviously no work for Cin2.1.5CV still going on and thus a release might stimulate some further contributions, in particular by distros shipping cinelerra. If I should update the appropriate files (mainly configure.in, mwindow.inc and possibly as well aboutprefs.C) and create a commit for you please notify me. With best regards, Simeon -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzmwlgACgkQph/voQkhF7xY6QCePnEoGEOAwtqdsFLanoX4/3QV MrEAn1YWZdNxQo8g+fa6K0Tcyqo6O9k2 =acLu -END PGP SIGNATURE- ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] Re: Cinelerra CinCV merge request / Cin2.1.5CV
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Hannes, thanks for pushing out the latest changes. If i remember correctly we have now merged nearly everything that was intended to be merged, except for one of Monty's alsa fixes, that caused serious playback problems for Hannes. So what do we still want to merge before releasing Cin2.1.5CV? (except for an update of the about page / version variable ;)) Personally speaking I would prefer a release rather soon for the following reasons: 1. a "new version" should encourage distributions to build new packages which should decrease the time that has to be spend for answering "where can i get (the latest) packages for XY" 2. a "new version" should encourage users to look for "new (old) bugs", hopefully resulting in new tickets on bugs.cinelerra.org. Adding a new version there makes it easier to keep track of what is still an issue. (I'm aware that many old bugs aren't fixed yet, but we won't fix them all in finite time, so waiting for all bugs being fixed would prohibit the release of > 2.1 forever ;-)) 3. a "new version" might encourage someone to contribute again some patches, as he/she sees that something is going on with cinelerra. (e.g. gentoo's patches weren't forwarded to our ML at some point as nothing happened) 4. releasing other bugfix releases (e.g. 2.1.6) should become "easier" to do when a first step is done. Hannes, Monty, Einar, what do you think? (as you've contributed most of the new patches) With best regards, Simeon On 11/04/10 21:08, Johannes Sixt wrote: > On Mittwoch, 3. November 2010, Simeon Völkel wrote: >> I've just reformatted Monty's three patches you hadn't committed yet due to >> their formatting. They are now available in my git repo, together with an >> extended commit message written my Monty. I hope you can merge them now >> into your repo, so that we get a step closer to the release of Cin2.1.5CV. > > Thanks, I appreciate it. > > I pushed out these patches, but I substituted Monty as author. (I hope you > don't mind.) nope, just wasn't aware of how to do that :) > > -- Hannes -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzTKmEACgkQph/voQkhF7wnswCgiMqOwHb4qG8q3Q0Tktqx46AK NcoAn35VTNpfweWfTefdsB8Gup9Vpkao =027Z -END PGP SIGNATURE- ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] Re: Cinelerra CinCV merge request / Cin2.1.5CV
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Hannes, I've just reformatted Monty's three patches you hadn't committed yet due to their formatting. They are now available in my git repo, together with an extended commit message written my Monty. I hope you can merge them now into your repo, so that we get a step closer to the release of Cin2.1.5CV. With best regards, Simeon -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzRxeQACgkQph/voQkhF7wHvACgmlcOMPDtMQ8n/PcRp2OnHGms 9FIAn2ero6ya+KrWl4L84Jyn6xEOxrj8 =GYWq -END PGP SIGNATURE- ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] Re: Compositor keyframing and scene change
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Ivan, Cinelerra uses a maybe not too intuitive interpolation strategy: If the value can't change between two keyframes (or "imaginary keyframes" that were created by interpolation between existing ones) it uses the value of the preceding (imaginary) keyframe until the new keyframe is reached. > It seems in cinelerra that means that I should have zoomed in > projection parameters [0,0, 3] after the last frame in first scene. I > also need default projection [0,0, 1] before the first frame of > second scene. I think you want to have [0,0,3] *at* the last frame in first scene and [0,0,1] *at* the first frame of the second scene. That would make the Timeline look as follows (zoom in in order to see the single frames in cinelerra's timeline) F|K L|k f|S where: F = First clip K = Keyframe [0,0,3] at beginning of L = Last frame of first clip k = keyframe [0,0,1] at beginning of f = first frame of second clip S = Second clip | = Tick/border between two frames, however Keyframes are shown as sitting on the preceding border. I hope that explanation was sufficient :) With best regards, Simeon -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzRUIoACgkQph/voQkhF7xtawCgk1WSwOMo3cL09i4XdYFzJml+ qPIAn2KpJt8Pm1KKjtOBRQIc/HqghKHa =Ctr7 -END PGP SIGNATURE- ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] Re: Cinelerra CinCV merge request / Cin2.1.5CV
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Hannes, I've received the following answer from aballier, explaining the libavutil50 and x264 patches by gentoo. In my opinion both changes are fully justified, and _now_ as well sufficiently explained. So what is currently still pending / not merged yet (that should be included in Cin2.1.5CV)? With best regards, Simeon - Original Message Subject: Re: gentoo's cinelerra patches Date: Thu, 28 Oct 2010 11:00:43 -0300 From: Alexis Ballier Organization: Gentoo To: Simeon Völkel Hi, > we are currently working on Cin2.1.5CV and now collecting patches from > distributions to be included in the next release. However, only very few > have any explanation with them, but for the git repos we would like to > have a at least somewhat expressive commit message. > > When asking today in #gentoo-media about gentoo's patches for cinelerra > ssuominen told me to ask you for the following two patches: Glad to hear cinelerra is moving again :) I was bored of sending patches that were lost in the abysses of the cincv ml so I stopped forwarding them at some point... Anyway, about these two patches, its been so long that I don't remember but let's try. in any case, you can see the cvs log here: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/media- video/cinelerra/files/ > > cinelerra-libavutil50.patch > > This patch seems to be quite destructive, as it replaces RGBA with RGB > color models. Is that really a proper solution or just a workaround that > does not mind loosing the alpha channel? Could you please explain this > patch? cvs log says: Fix build with libavutil 50 by not using pixel formats that have been deprecated for years. libavutil/pixfmt.h says: * PIX_FMT_RGB32 is handled in an endian-specific manner. An RGBA * color is put together as: * (A << 24) | (R << 16) | (G << 8) | B * This is stored as BGRA on little-endian CPU architectures and ARGB on * big-endian CPUs. #define PIX_FMT_RGB32 PIX_FMT_NE(ARGB, BGRA) #define PIX_FMT_RGB32_1 PIX_FMT_NE(RGBA, ABGR) #define PIX_FMT_BGR32 PIX_FMT_NE(ABGR, RGBA) #define PIX_FMT_BGR32_1 PIX_FMT_NE(BGRA, ARGB) so at least the remark of it being destructive is wrong iirc the only thing this patch changed is the name: the two pixel formats were #defined one onto the other but with libavutil 50, the one cinelerra was using was gone. You'll have to check libavutil/pixfmt.h svn history in ffmpeg svn if you want a 100% accurate answer there I'm afraid. > > cinelerra-x264.patch > > What does this patch solve? 9 +#if X264_BUILD >= 76 10 + int size = nals[i].i_payload; 11 + memcpy(codec->work_buffer + codec->buffer_size, nals[i].p_payload, nals[i].i_payload); 12 +#else I guess you can infer the obvious answer :) Again, don't ask me to explain more: it's been so long that I forgot. This API change in x264 was well documented though: http://mailman.videolan.org/pipermail/x264-devel/2009-September/006337.html http://mailman.videolan.org/pipermail/x264-devel/2009-September/006353.html Regards, Alexis. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzNvxEACgkQph/voQkhF7yzqwCbBqAWlMPkHqo8mmJ63iljdA+r u1QAnRwKjuwYmAMWR/HYf1G3SirDbmTM =Leyp -END PGP SIGNATURE- ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] Re: Cinelerra CinCV merge request / Cin2.1.5CV
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 oh, forgot cinelerra ML :-/ - Original Message Subject: Re: Cinelerra CinCV merge request / Cin2.1.5CV Date: Tue, 26 Oct 2010 22:39:57 +0200 From: Simeon Völkel To: Johannes Sixt CC: Monty Montgomery On 10/26/10 22:12, Johannes Sixt wrote: > On Sonntag, 24. Oktober 2010, Simeon Völkel wrote: >> today Monty and I worked out which of his changes are independent from his >> ffmpeg loader project and fix bugs of CinCV. >> >> I've merged these commits over into my repo[1] and would like to ask you to >> pull these changes (everything from october, starting with [2], except for >> the one commit[3] which states that it is not for CinCV) over into the >> official CinCV repo. > > I didn't take these: > > - f4b7d222 apply gentoo libavutil50 patch > This substitutes RGBA* by RGB color codes. How can this be good? > Please explain. I just took over the patch which is applied by gentoo when compiling cin using emerge, as otherwise it does not compile here. If i've got some time tomorrow, I'll have a look at what actually changed in libavutil and whether RGBA color codes are still supported. > > - b789d4ff fix background rendering crash on >=jpeg-7 > This doesn't compile here. It needs version checks around uses of > do_fancy_upsampling. I'll add them. Didn't recognize that as background rendering was broken for almost one year on my boxes, however not on others, obviously due to jpeg-7/8. Haven't tested it on a not-jpeg-7/8 installation. > > - 8aa33e3e Rwrite the latency timing/calculation for the OSS backend > There is parctically no explanation why the change is good and why > a new mutex is needed. It looks dangerous. How extensively has the > code been excercised? Why is a change needed at all? I am not aware > of people complaining that the OSS driver does not work. But I > might be missing something. > > - e0569663 Actually check for error return codes in OSS > This does not adhere to the coding standard that is used in surrounding > code. Fixing that would take too much of my time. Remember that it is > good tone to copy the coding style that you find rather than to force > your own style onto existing code. This includes white-space style. > (IOW, please use tabs, not 8 spaces.) > Monty will explain the need and purpose of the two OSS changes in more detail. > - 48e292ec Add ArchLinux x264-quicktime build patch > This does in no way explain what the patch solves. I cannot judge why > the change would be good. > This was taken over from Monty's repo, however it seems to be applied as well by gentoo without explanation. I'll try to figure out where this patch comes from. > - 64e8022f Eliminate the YUV file loader's wont > Before I merge this change, I'd like to know why the patch solves a > problem (and what the problem exactly is). "It happens more often > than you think" is a bit too much hand-waving. Can I easily reproduce > the bug? (Oh, and the commant about coding style applies, too.) Monty will explain in detail; It seems as if YUV frames can't differ in size, thus creating an index is wasting resources. > > - e40c03ad remove hardcoded cinelerra/versioninfo.h and add README.Cin2.1SV > What is this about? I'm sorry, didn't recognize that commit when writing the mail, that commit does not apply to CinCV, just to my repo (CinSV). It was not intended to be merged into CinCV :D > > I pushed out my state to > > git://git.cinelerra.org/j6t/cinelerra.git sv/gentoo-fixes > Thanks! > This state doesn't work for me (it crashes on the first playback of DV), > hence, I didn't push it to master right away. I'll investigate. Ok, i haven't used DV yet in my latest version, but edited and rendered already a small test project in HDV. Maybe you could paste a backtrace to bugs.cinelerra.org or so. With best regards, Simeon -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzHPocACgkQph/voQkhF7yzagCgyBaGTeHyqpF9W4jno7nbIzxY tpsAoKwBAYOvzydXKbz2GwxSFfyDMKjX =PwyK -END PGP SIGNATURE- ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] Cinelerra CinCV merge request / Cin2.1.5CV
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Hannes, today Monty and I worked out which of his changes are independent from his ffmpeg loader project and fix bugs of CinCV. I've merged these commits over into my repo[1] and would like to ask you to pull these changes (everything from october, starting with [2], except for the one commit[3] which states that it is not for CinCV) over into the official CinCV repo. Furthermore, we (Monty and I) would like to increase CinelerraCV's version counter to 2.1.5 to reflect these sometimes very fundamental bugfixes (mainly audio- and rounding-related). As soon as we can merge Monty's ffmpeg-loader, something from Cin4.xHV or any change that goes beyond pure bugfixing the version number shall be increased to 2.2 (as long as nobody demurs ;-)). Many thanks in advance! With best regards, Simeon References: [1] http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=shortlog;h=refs/heads/cin2.1sv [2] http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=commit;h=1be5df4199e5cb23dbfb2768d9661e7bc392c043 [3] http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=commit;h=8c77c96e6dae6c0d8259cc9b8beffb226315030c -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzEWXUACgkQph/voQkhF7z7gwCeJIkrkPSh0ICFD2KpCsYN4ILE a/cAn34KdLYgTS/tKOkAaSdzw37pTVpD =5anh -END PGP SIGNATURE- ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] Cin4.2HV
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello everybody, I just wanted to notify you that HV released his 4.2 version of cinelerra[1] some days ago (15 October 2010). I'm currently walking through (and producing git commits in my personal repo[2]) the patches gentoo applies to a CinCV git-snapshot for successful compilation (I suggest to merge them asap into CinCV. J6t, your opinion?). After finishing that I'll have a look at HV's latest changes. With best regards, Simeon References: [1] http://heroinewarrior.com/cinelerra.php [2] http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=shortlog;h=refs/heads/cin2.1sv -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzCrX8ACgkQph/voQkhF7xeFwCeO2n8sMbxBvgsLvoN8Pu+syjj 8BEAoIMllSbQ/tJJuOj0v0uNf8pGlhCl =8dMF -END PGP SIGNATURE- ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] making Einar's git repo compile on Gentoo (64 bit)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Einar,
Today I tried to compile your git repo on my gentoo box (64 bit) and
succeeded only after the following steps:
1. Fixing admin/nasm script
Line 29 causes trouble as there is an unexpected "$". In my git repo I
resolved this problem by removing the dollar sign,[1] however escaping it
("\$") works as well.
Currently I have no idea what this file actually is required for,
especially the fact that it is unchanged since 2003 and contains mainly
hardcoded output created by libtool 1.5.0a (I'm on 2.2.10 here!) makes me
wonder. In case anyone knows, please speak up!
2. Fix shapewipe / libpng 1.4.x incompability.
libpng 1.4 does not define png_voidp_NULL, png_error_ptr_NULL and
png_infopp_NULL anymore. They have to be replaced by plain NULL, as already
fixed in my git repo.[2]
It is extremely likely that everyone trying to compile cinelerra against a
libpng 1.4 will run into these troubles.
3. Update po/POTFILES.in
A commit from August 2010 [3] removed cinelerra/assetremove.* from your
repo. However cinelerra/assetremove.C is still listed in po/POTFILES.in
which causes compilation to fail. However, this is not the only file which
has been forgotten to be commented out in po/POTFILES.in, for me
compilation of a fresh "git clone ..." worked after removing/commenting out
the following files from po/POTFILES.in:
cinelerra/assetremove.C
cinelerra/avc1394transport.C
cinelerra/confirmquit.C
cinelerra/labelnavigate.C
cinelerra/messages.C
cinelerra/recconfirmdelete.C
cinelerra/threadindexer.C
plugins/blurzoom/blurzoom.C
plugins/blurzoom/blurzoomwindow.C
plugins/interpolateall/interpolateall.C
plugins/quark/quark.C
plugins/quark/quarkwindow.C
I have attached the corresponding commit.
I would really appreciate if you could merge these fixes into your git repo.
Regards,
Simeon
References:
[1]
http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=blobdiff;f=admin/nasm;h=4ff0a9d21e28ce2eb454f568ff9e57e2e75a6b33;hp=108f79dfeab4a790f0f3a0f90fc34953725cf1f7;hb=b14a3274c06b2a35e8f7c0aa3d7057e6992f0369;hpb=2f323240bd9bfb8cf44cebf5c4380df133b6ace2
[2]
http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=blobdiff;f=plugins/shapewipe/shapewipe.C;h=fc8c7377477f6af5208af1cd6b34a7b207986aff;hp=2032aaa3eae38c78c9cf7338cc34771e2a44685d;hb=2f323240bd9bfb8cf44cebf5c4380df133b6ace2;hpb=86062fa76144e1ed04f55d8223dbd70db3707b95
[3]
http://git.cinelerra.org/gitweb?p=einar/cinelerra.git;a=commit;h=994d2d09912798dd3520da35f9037be40268b2df
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkzB1BgACgkQph/voQkhF7yAlACgiwkHHYzZYnsPyVGYJsEIkc9D
IdMAn20wjOOXPERbeYUdXk4i/69oXrV8
=SJ9l
-END PGP SIGNATURE-
commit 35f6cf8362d7f4c5716e5e15cc580f87db012599
Author: Simeon Voelkel
Date: Fri Oct 22 19:59:08 2010 +0200
update po/POTFILES.in to reflect deletion of files
diff --git a/po/POTFILES.in b/po/POTFILES.in
index 05cb819..099588c 100644
--- a/po/POTFILES.in
+++ b/po/POTFILES.in
@@ -6,9 +6,9 @@ cinelerra/apatchgui.C
cinelerra/assetedit.C
cinelerra/assetedit.h
cinelerra/assetpopup.C
-cinelerra/assetremove.C
+# cinelerra/assetremove.C
cinelerra/atrack.C
-cinelerra/avc1394transport.C
+# cinelerra/avc1394transport.C
cinelerra/awindowgui.C
cinelerra/awindowmenu.C
cinelerra/batch.C
@@ -20,7 +20,7 @@ cinelerra/channeledit.C
cinelerra/channelpicker.C
cinelerra/clipedit.C
# cinelerra/compresspopup.C
-cinelerra/confirmquit.C
+# cinelerra/confirmquit.C
cinelerra/confirmsave.C
cinelerra/cpanel.C
# cinelerra/cropvideo.C
@@ -56,7 +56,7 @@ cinelerra/indexfile.C
cinelerra/indexthread.C
cinelerra/interfaceprefs.C
cinelerra/keyframepopup.C
-cinelerra/labelnavigate.C
+# cinelerra/labelnavigate.C
cinelerra/loadfile.C
cinelerra/loadmode.C
cinelerra/main.C
@@ -65,7 +65,7 @@ cinelerra/mainmenu.C
cinelerra/mainprogress.C
cinelerra/manualgoto.C
cinelerra/menueffects.C
-cinelerra/messages.C
+# cinelerra/messages.C
cinelerra/meterpanel.C
cinelerra/mwindow.C
cinelerra/mwindowedit.C
@@ -86,7 +86,7 @@ cinelerra/pluginpopup.C
cinelerra/preferencesthread.C
cinelerra/question.C
cinelerra/quit.C
-cinelerra/recconfirmdelete.C
+# cinelerra/recconfirmdelete.C
cinelerra/record.C
cinelerra/recordaudio.C
# cinelerra/recordengine.C
@@ -95,7 +95,7 @@ cinelerra/recordmonitor.C
cinelerra/recordprefs.C
cinelerra/recordtransport.C
cinelerra/recordvideo.C
-cinelerra/recordwindow.C
+# cinelerra/recordwindow.C
# cinelerra/reindex.C
cinelerra/render.C
cinelerra/renderfarm.C
@@ -109,7 +109,7 @@ cinelerra/setformat.C
cinelerra/sharedlocation.C
cinelerra/splashgui.C
cinelerra/statusbar.C
-cinelerra/threadindexer.C
+# cinelerra/threadindexer.C
cinelerra/tipwindow.C
# cinelerra/toggleauto.C
cinelerra/trackcanvas.C
@@ -135,8 +135,8 @@ plugins/bandslide/bandslide.C
plugins/bandwipe/bandwipe.C
plugins/blur/blur.C
plugins/blur/blurwindow.C
-plugins/blurzoom/blurzoom.C
-plugins/blurzoom/blurzo
[CinCV] gcc 4.4 issues
Hello,
einar's repo doesn't compile anymore using gcc 4.4:
../../cinelerra/yuvstream.C: In member function 'int
YUVStream::open_write(const char*, char*)':
../../cinelerra/yuvstream.C:85: error: invalid conversion from 'const
char*' to 'char*'
make[3]: *** [yuvstream.o] Error 1
According to http://gcc.gnu.org/gcc-4.4/porting_to.html const-ness is now
more strictly handled.
The attached patch should resolve that problem in yuvstream.[hC].
Simeon
diff --git a/cinelerra/yuvstream.C b/cinelerra/yuvstream.C
index e4244ca..1fb7936 100644
--- a/cinelerra/yuvstream.C
+++ b/cinelerra/yuvstream.C
@@ -77,12 +77,12 @@ int YUVStream::open_read(const char *path)
}
// NOTE: path is opened as a pipe if contains '|'
-int YUVStream::open_write(const char *path, char *pipe)
+int YUVStream::open_write(const char *path, const char *pipe)
{
if (pipe && *pipe)
{
// skip over the '|' if present
- if (char *p = strchr(path, '|'))
+ if (const char *p = strchr(path, '|'))
{
pipe = p + 1;
}
diff --git a/cinelerra/yuvstream.h b/cinelerra/yuvstream.h
index 404e073..048bbb7 100644
--- a/cinelerra/yuvstream.h
+++ b/cinelerra/yuvstream.h
@@ -38,7 +38,7 @@ public:
~YUVStream();
int open_read(const char *path);
- int open_write(const char *path, char *pipe);
+ int open_write(const char *path, const char *pipe);
void close_fd();
int read_frame(uint8_t *yuv[3]);
[CinCV] libpng1.4
Hello, it seems as if shapewipe does not compile anymore using libpng1.4. I've pushed a possible patch to git, however I'm not sure whether this is the best solution though. http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=commit;h=2f323240bd9bfb8cf44cebf5c4380df133b6ace2 Simeon ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCV] Director's Cuts
Hello Keith, I'm sorry, but this workflow as described isn't implemented in Cinelerra yet. I used once a workaround to build a kind of multicam-sync editing which gives you nearly the same comfort, if you don't mind pressing more than just one key. Therefore I added a 'h' shortcut some time ago. ( http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=commit; h=fb5f5f6bd84332805a54772296eec188ef18f98f ) The idea was to _copy_ parts of one of the lower tracks to the most upper track. However, I really used that only once or twice. My efforts to implement real multicam clips got stuck and were dropped as Cinelerra got just even more unstable. Thus I'm sorry I can't deliver working(TM) solutions (e.g. how to implement such an workflow), but if you are interested in what didn't work as expected for me, you could try to contact me on IRC (#cinelerra @ freenode). If you feel like you could get it working, just have a go! I'm sure I'm not the only one who would like to see such an feature implemented, too ;-) With best regards, Simeon aka SimAV ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCV] My little project!
Hello Akirad, nice to hear that you could make use of my highly experimental patch for the SVG plugin. By the way, "SV" in CinelerraSV doesn't stand for my name. Internally I'm using the "S" in order to distinguish the version on my laptop "sigma" (32bit) from the version on "mue", maintained on a machine running 64bit Gentoo but in praxis identical. I personally would prefer letting the "SV" just be "SV" instead of giving it an unintentional meaning. Concerning your changes from CinelerraCV to cinecutie, I wonder whether you could push your changes to git.cinelerra.org or make at least some patches available for download in order to simplify merging your work back into CinCV when time permits. Regards, Simeon ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCV] cin 2.1 and cin-sv xml compatibility
Hello Klemen, if CinCV and CinSV .xml should be compatible that's rather by accident. To stay on the safe side, please use CinCV. CinSV is just a kind of personal playground. If you need some of the features of CinSV for production, I'd recommend to help merging Cin4HV into CinCV, after that, merging SV into CV should be easy - if still required. Simeon ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCV] yuv4mpeg ffmpeg presets don't work anymore
Hello Rafael, please feel free to share any tested ffmpeg pipe presets with the community! For some examples, you might be interested in http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=blobdiff;f=cinelerra/fileyuv.C;h=666b3396ebd377e02b357bba5eb9049f3cc0b55e;hp=a255e183cb1011c5dcc7b5638e6007687b319dea;hb=06d5df2349ae94a70e8857dda53d522ed017643a;hpb=5c4e79be801f969dff994124ce49b4dee624b262 regards, Simeon ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCV] Cinelerra Plugin - Dip2Black
Hello Keith, of course we would like to have a fade to black transition in our repositories. Therefore I suggest that you proceed either as cehteh suggested, or that you simply join our IRC Channel #cinelerra on freenode. There we can help you interactively if necessary. Regards, Simeon ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCV] Cinelerra crash when load SVG
Hello Artenaut, as Roland pointed out, there was some work going on concerning the SVG plugin. If you want to test the most recent version, get a copy from git://git.cinelerra.org/sv/cinelerra and checkout branch cin2.1sv. The workaround lets inkscape export a png and uses convert from the imagemagick package to generate a rgba image. As cinelerra currently requires a file with a valid RAWC-header, a small binary rawc-convert will be installed in tandem with cinelerra which adds the RAWC-header where needed. For a final version of this workaround one should possibly add some additional error checks, e.g. whether inkscape and convert are available and worked as expected. Greetings, Simeon ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] update for Cin2.1CV / merge with Cin4HV
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello everybody, this year's summer vacation allowed me to work a bit on Cinelerra and the Cin4HV merge. * Renovation of SVG plugin As Artenaut mentioned some days ago, the current SVG plugin is broken. I implemented a workaround using - a standard inkscape version (not patched, just using inkscape's png-export function in contrast to the former RAWC-export which had been written for cinelerra), - convert from the imagemagick package (using the rgba export) - rawc-convert, a program written for this workaround, shipped with the SVG-plugin code (rawc-convert.C) (for creating a valid RAWC header, which cin expects to be in front of the rgba data) This workaround is still experimental and lacks still several error checks. It would be brilliant if this workaround could be tested under several distros / setups. Help for various checks (e.g. whether a working inkscape / convert is available and produced valid output) is greatly appreciated. * New feature: move selection It is often required to have a selection with the length of a specific part of the timeline at another position in the timeline. This is easily possible with this feature: Just create the selection with the desired length, place the cursor somewhere else by clicking and holding down at the same time either just alt or alt and shift. This will create a new selection at the desired position with the desired length either starting or ending at the current position of the cursor. * New feature: horizontal scrolling for timeline with touchpad Scrolling horizontally on a touchpad may produce mouse events like button number 6 or 7 clicked. These are now used for scrolling th timeline horizontally, while 4 and 5 remain for the vertical scrolling. * Bugfix: (horizontal) scrolling is sometimes interpreted as clicks * Merge from Cin4HV: - synchronize faders only if track is armed - 'x' and backspace function in Compositor window. - 'asynchronous decoding debugged' It seems as if this line in HV's Changelog.4 refers only to two small changes, however this can't be said for sure yet. Nevertheless these changes could at least theoretically prevent Cin from segfaulting. Please see http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=shortlog;h=refs/heads/cin2.1sv for a complete list of commits. Checkout branch cin2.1sv from git://git.cinelerra.org/sv/cinelerra to get the latest source code. NOTE: this is not the official Cin2.1CV git repo. Greetings, Simeon -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkq2YH8ACgkQph/voQkhF7zMygCff+hV2FtUtQpvyjCvDt2Y8Oni T4gAoJmdoDWYLIfgiCYN+KtuqU0Kac+2 =cnuU -END PGP SIGNATURE- ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] add multiple uniform transitions at once to a track
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi August, you can add fades to the audio section as well if you arm only your audio tracks, jump from one edit to the next by using Alt+right or left arrow and insert the fade by pressing u. For setting the type and duration of the fade I recommend either experimenting around or the usual RTFM ;-) Hope this helps... Simeon -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpTohwACgkQph/voQkhF7zZDACfRjLFWs0LO3at2pWeoKYiTYg1 OAAAoMClWa8rcxszpb5p6+/6k4esS+YF =EuyE -END PGP SIGNATURE- ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCV] Howto produce HD mpg 1080 from Cinelerra
Hello Ed, Nice to hear that you finally got your rendering working. It would be great if you could add your experiences and gained knowledge to the Cinelerra Wiki in order to share it with the other users of Cinelerra! http://cvs.cinelerra.org/docs/wiki/doku.php can take some additinonal information, especially http://cvs.cinelerra.org/docs/wiki/doku.php?id=english_manual:cinelerra_cv_en_20 in this case. For example a section titled "One way to produce a FullHD mpg in Cinelerra" would be nice to have :) Simeon ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCV] Howto produce HD mpg 1080 from Cinelerra
Hello Ed, I did just try some HDV footage (1440x1080 not FullHD), exported the assembled clips using the ffmpeg command i posted earlier and couldn't see any gaps when playing the video in mplayer or vlc. Simeon ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCV] Howto produce HD mpg 1080 from Cinelerra
Hello Ed, I can't really speak out of experience but I would try the following: To export the video through "YUV4MPEG Stream" use the following pipe command: ffmpeg -f yuv4mpegpipe -i - -y -r 25 -b 2800 -f mpeg2video % As Cinelerra Format settings i would suggest a frame rate 25. fps and 1920x1080 as size of your canvas. Export your audio as MPEG Audio, select Layer II and 384 kbit/s. Then mux your video and audio together using a command like ffmpeg -i foo_video.m2v -i foo_audio.mp2 -acodec copy foo_muxed.mpg Hope that helps... Simeon ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] mods for cinelerra-4, if you are still interested.
Hello Agent Smith, I do have to endorse my previous posters: pushing your cinelerra source code to git.cinelerra.org would be great step to start with. This way everyone can dip into your version of cinelerra and enjoy your improvements. Personally speaking I'm especially interested in the MPEG TS stream capturing. Did you integrate that into Cinelerra's Recording-dialog? Nevertheless I can assure you that we will try to merge as much as possible from your work. In order to make that as easy as possible it would be great to have each small change as a single commit. This way more people could work in parallel. >From my point of view, the best (of the "not so great") alternatives could be to make a diff between your version and Cin4HV. As I had no glance at your code yet I can't assess which of the Cin branches has the smaller differences or at least easier-to-understand ones. Regardless of which option we have to choose it would be great if you could help us further while merging your changes. I guess you are the person who knows the new code best and would be a valuable help in both cases. As you might have already noted, there is as well an IRC channel #cinelerra on freenode. I'm sure there are several people out there who would be pleased about seeing you there. On that note, I'm looking forward to hearing from you. Simeon ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCV] about cinelerra 4 import
Hello Rafael, That's the current status: http://git.cinelerra.org/gitweb?p=sv/cinelerra.git;a=shortlog;h=refs/heads/cin2.1sv I've imported two single features of Cin4HV into Cin2.1CV as merging the whole Cin4HV into Cin2.1CV at once ended up in a big mess and merging Cin2.1CV into Cin4HV wasn't better. (They simply differ too much) Thus the best way seems to be to merge one small feature after another. It would be great if anyone could help there a bit. Simeon ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCV] Cinelerra won't stop play once started
Hello Matthew Just a quote from cinelerra/audioalsa.C : // Interrupts the playback but may not have caused snd_pcm_writei to exit. // With some soundcards it causes snd_pcm_writei to freeze for a few seconds. if(!device->out_config->interrupt_workaround) snd_pcm_drop(get_output()); This option is a workaround, not a normal 'feature'. Simeon ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] bug fix for mpeg3cat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello David,
I wasn't able to test my patch as i didn't have appropriate footage here,
but i guess that commenting the lines out is not the optimal way to go.
My patch replaces the printf( with fprintf(stderr, in order to let the
messages appear on the terminal but not on the stream. If it should work,
this could be a better solution.
Simeon
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAklZKtsACgkQph/voQkhF7ycUQCfd55SoOuaKi9VAeyZPd+Riq5D
RNkAn3nRkkwdjSYvHbyEuctqcK7lZ/no
=4tjA
-END PGP SIGNATURE-
diff --git a/libmpeg3/mpeg3demux.c b/libmpeg3/mpeg3demux.c
index a7ec1f8..f68bc91 100644
--- a/libmpeg3/mpeg3demux.c
+++ b/libmpeg3/mpeg3demux.c
@@ -1903,10 +1903,10 @@ int mpeg3_read_prev_packet(mpeg3_demuxer_t *demuxer)
/* Transport stream or elementary stream case */
if(file->packet_size > 0)
{
-printf("mpeg3_read_prev_packet 1 result=%d title=%d tell=%llx
program_byte=%llx\n", result, demuxer->current_title, mpeg3io_tell(title->fs),
demuxer->program_byte);
+fprintf(stderr, "mpeg3_read_prev_packet 1 result=%d title=%d tell=%llx
program_byte=%llx\n", result, demuxer->current_title, mpeg3io_tell(title->fs),
demuxer->program_byte);
demuxer->program_byte -= file->packet_size;
result = mpeg3_seek_phys(demuxer);
-printf("mpeg3_read_prev_packet 100 result=%d title=%d tell=%llx
program_byte=%llx\n", result, demuxer->current_title, mpeg3io_tell(title->fs),
demuxer->program_byte);
+fprintf(stderr, "mpeg3_read_prev_packet 100 result=%d title=%d tell=%llx
program_byte=%llx\n", result, demuxer->current_title, mpeg3io_tell(title->fs),
demuxer->program_byte);
}
else
{
[CinCV] Cinelerra-4: Merge has started and needs helpers
Hanno Böck wrote: > Is there any statement from HV if there'll be any back-merging? > HV stated quite clearly that they don't want to spent much bandwidth to do that, as they want to focus on their interests which shifted a bit. > It's probably not the best idea to keep two completely separate trees and try > to merge stuff in rare cases. Though isn't there a chance to coordinate > development again? Their interest in having one single tree is quite small, as they don't want to focus on patches, bugfixes or just minor improve- ments they don't need at the moment. According to Adam the best option to contribute at the moment is to copy their work into Cinelerra CV instead of the other way round. I haven't found a definite statement whether there will be a larger back-merging or not. In recent years a few fixes have been merged back while a lot were either ignored or rejected. There are some statements from HV which express as well, that there is no close co-operation, but rather a loose connection between them and Cinelerra CV. Simeon ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] Cinelerra-4: Merge has started and needs helpers - update
Sorry, I forgot some crucial commands in my last mail, thus here again the whole git part, this time hopefully complete: Download it using (Please replace $foo with the name your local copy should receive. Just choose any name for $foo) > git clone git://git.cinelerra.org/c4/cinelerra $foo Go into your repository. (Please replace $foo with the name your local copy has received due to the last command) > cd $foo You should be on branch master at the moment. Check that using > git branch There should be an asterisk (*) in front of master. The branch master contains at the moment nothing else than Cin2.1Cv (r1061). But all the work is done in a branch called cin4merge. To work on a local copy, which is recommend, do the following: (Please replace $cin4merge either with cin4merge, or, at your option, with another name for the branch on which you want to work on) > git checkout -b $cin4merge origin/cin4merge This will bring you to the branch which contains the dirty work, as the name should tell you. If you have already cloned this repo according to the preceding descriptions and want to get the latest changes from the public repo: (Please replace $cin4merge with the same name you chose for the last command) > git pull origin/cin4merge $cin4merge If you need further information, or find any errors please catch me on IRC. Simeon (SimAV) ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] Cinelerra-4: Merge has started and needs helpers
To Whom It May Concern :-) Fortunately I can announce herewith, that there is an urgent need for people assisting in fixing all the errors the merge of Cin2CV and Cin4HV introduced in order to be able to release a working Cin4CV before the next HV version has been released. Anyone's help is greatly appreciated, but first of all we need Someone(TM) who is capable of fixing errors in the build-system and volunteers for that job. (I don't know that part at all, sorry) At the same time we need people who fix C/C++ errors which somehow went into the code. I tried to fix as many as I could, but as there is no working build- system at the moment available, thus spotting mistakes takes quite a long time. I'll keep on looking for them and update the public repo asap. Here again: Anyone who knows a bit about programming is welcome to join the dash for errors. I've pushed the current status of the merge to a git- repo on git.cinelerra.org. Download it using (Please replace $foo with the name your local copy should receive) > git clone git://git.cinelerra.org/c4/cinelerra $foo If you have already cloned this repo and want to get the latest changes: > git pull There is a file called TODO.cin4merge in the repo with some tasks in it, but there are for sure more. All contributors are invited to join #cinelerra on freenode in order to arrange the work with the others. For pushing your work back on cinelerra.org please ask there as well for write access to that repo. Simeon (SimAV) ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCV] Cinelerra4: first hints and patches for compiling
Hello,
I've just compiled Cinelerra Version 4 on my Gentoo Linux.
I'd like to share my changes I had to make to make cin4
compile for me in the hope someone else finds the following
information useful.
I didn't succeed in compiling cin4 without corrupting
quicktime/thirdparty/faad2-2.0/plugins/mpeg4ip/faad2.cpp
That's why I split up the second diff: The first version
seems to be crucial to compile cin4 on a 32bit (Gentoo?)
Linux, the second file contains the first one plus a work-
around to make cin4 actually compile for me.
Both files are outputs of diff -u.
=== Annotations for compiling ===
Obviously, with version 4, a new dependency was introduced:
mpeg4ip. Without having the (devel-!) package installed,
you are likely to run into errors like
faad2.h:28:26: error: codec_plugin.h: No such file or directory
On Gentoo you'll just have to emerge mpeg4ip of course.
Secondly: Errors like
faad2.cpp:86: error: invalid conversion from 'long unsigned int*' to 'uint32_t*'
should be solved by applying my patches. Just as e.g.
faad2.cpp:242: error: too few arguments to function
and others.
Unfortunately I wasn't able to fix the errors in line 370 of faad2.cpp
Example:
faad2.cpp:370: error: cannot convert 'codec_data_t* (*)(const char*, int, int, format_list_t*, audio_info_t*, const uint8_t*, uint32_t, audio_vft_t*,
void*)' to 'const char*' in initialization
Maybe Someone(TM) can solve that. I worked around by commenting
the call to makro out. (see faad2.cpp.2.patch)
=== Annotations for running cinelerra-4 ===
Paradoxically sudo make install didn't install (here) cinelerra in
/usr/local/bin but inside the local directory. Start cin4 by typing
./bin/cinelerra in cinelerra-4 (where you just typed make).
Monitoring audio when playing video in the record-dialog and Video-in
does not work for me 'out of the box', even if the checkbox is marked.
The audio-settings work for normal playback. If I find out how to get
this working here, I'll tell you. ;-)
Finally I'd like to say "Thank you for Cinelerra-4" to Adam Williams.
SimAV
--- aa_file.cpp 2008-05-31 11:25:31.0 +0200
+++
/static/cinelerra/cin4/quicktime/thirdparty/faad2-2.0/plugins/mpeg4ip/aa_file.cpp
2008-08-12 15:33:10.0 +0200
@@ -56,7 +56,7 @@
aac->m_buffer_size_max,
aac->m_ifile);
- unsigned long freq;
+ uint32_t freq;
unsigned char chans;
faacDecInit(aac->m_info, (unsigned char *)aac->m_buffer,
--- faad2.cpp 2008-05-31 11:25:31.0 +0200
+++
/static/cinelerra/cin4/quicktime/thirdparty/faad2-2.0/plugins/mpeg4ip/faad2.cpp
2008-08-12 16:59:50.0 +0200
@@ -76,7 +76,7 @@
}
aac->m_info = faacDecOpen();
- unsigned long srate;
+ uint32_t srate;
unsigned char chan;
if ((userdata == NULL && fmtp == NULL) ||
(faacDecInit2(aac->m_info,
@@ -97,7 +97,7 @@
aac->m_output_frame_size = 960;
}
}
- aac->m_freq = srate;
+ aac->m_freq = srate;
aac->m_chans = chan;
aac->m_faad_inited = 1;
aac->m_msec_per_frame = aac->m_output_frame_size;
@@ -188,7 +188,7 @@
* If not initialized, do so.
*/
abort();
-unsigned long freq;
+uint32_t freq;
unsigned char chans;
faacDecInit(aac->m_info,
@@ -237,9 +237,9 @@
aac->m_vft->audio_configure(aac->m_ifptr,
aac->m_freq,
aac->m_chans,
- AUDIO_S16SYS,
+ (audio_format_t) AUDIO_S16SYS,
aac->m_output_frame_size);
- uint8_t *now = aac->m_vft->audio_get_buffer(aac->m_ifptr);
+ uint8_t *now = aac->m_vft->audio_get_buffer(aac->m_ifptr, aac->m_freq,
aac->m_current_time);
aac->m_audio_inited = 1;
}
/*
@@ -322,7 +322,7 @@
}
if (userdata != NULL) {
mpeg4_audio_config_t audio_config;
-decode_mpeg4_audio_config(userdata, userdata_size, &audio_config);
+decode_mpeg4_audio_config(userdata, userdata_size, &audio_config, false);
message(LOG_DEBUG, "aac", "audio type is %d",
audio_config.audio_object_type);
if (fmtp != NULL) free_fmtp_parse(fmtp);
--- faad2.cpp 2008-05-31 11:25:31.0 +0200
+++
/static/cinelerra/cin4/quicktime/thirdparty/faad2-2.0/plugins/mpeg4ip/faad2.cpp
2008-08-12 16:59:50.0 +0200
@@ -76,7 +76,7 @@
}
aac->m_info = faacDecOpen();
- unsigned long srate;
+ uint32_t srate;
unsigned char chan;
if ((userdata == NULL && fmtp == NULL) ||
(faacDecInit2(aac->m_info,
@@ -97,7 +97,7 @@
aac->m_output_frame_size = 960;
}
}
- aac->m_freq = srate;
+ aac->m_freq = srate;
aac->m_chans = chan;
aac->m_faad_inited = 1;
aac->m_msec_per_frame = aac->m_output_frame_size;
@@ -188,7 +188,7 @@
* If not initialized, do so.
*/
abort();
-unsigned long freq;
+uint32_t freq;
unsigned char chans;
faacDecInit(aac->m_info,
@@ -237,9 +237,9 @@
aac->m_vft->audio_configure(aac->m_ifptr,
aac->m_freq,
[CinCV] More playback speeds for Cinelerra
Hi all,
I have attached a patch i did this morning as i think that it could be
interesting to some other people as well:
The patch adds 8 additional playback speeds which are accessible via
ALT+NUMPADKEY. So just hold down ALT to get faster playback. This is
a somewhat convenient feature when rushing through about 2 hours of
video as you don't have to move the mouse but can let your fingers on
the keyboard.
Nevertheless i haven't tested the speeds thoroughly, so you might
want to find out what the best speed is for you by editing
cinelerra/transportque.C and change the returned values of
float TransportCommand::get_speed()
NOTE: you should not select the option play every frame. I doubt
that cinelerra will handle 160 fps ;-)
If the playback is accelerated by more than 2 no sound should be
played due to the limits of alsa i found on my laptop. If you want
to change that, edit line 247 in cinelerra/virtualaconsole.C
Simeon
diff --git a/cinelerra/playbackengine.C b/cinelerra/playbackengine.C
index 6ca11e0..a88b15c 100644
--- a/cinelerra/playbackengine.C
+++ b/cinelerra/playbackengine.C
@@ -295,6 +295,7 @@ double PlaybackEngine::get_tracking_position()
if(command->get_direction() == PLAY_FORWARD)
{
// Interpolate
+//printf("playbackengine.C:
command->get_speed() returned %f\n",command->get_speed());
result = tracking_position +
command->get_speed() *
tracking_timer.get_difference() /
diff --git a/cinelerra/playtransport.C b/cinelerra/playtransport.C
index 05d7f8e..a066028 100644
--- a/cinelerra/playtransport.C
+++ b/cinelerra/playtransport.C
@@ -192,32 +192,54 @@ int PlayTransport::keypress_event()
}
subwindow->unlock_window();
-
- switch(subwindow->get_keypress())
+ if (subwindow->alt_down())
{
- case KPPLUS:handle_transport(FAST_REWIND, 0,
use_inout);result = 1; break;
- case KP6: handle_transport(NORMAL_REWIND, 0,
use_inout); result = 1; break;
- case KP5: handle_transport(SLOW_REWIND, 0,
use_inout);result = 1; break;
- case KP4: handle_transport(SINGLE_FRAME_REWIND, 0,
use_inout);result = 1; break;
- case KP1: handle_transport(SINGLE_FRAME_FWD, 0,
use_inout); result = 1; break;
- case KP2: handle_transport(SLOW_FWD, 0, use_inout);
result = 1; break;
- case KP3: handle_transport(NORMAL_FWD, 0, use_inout);
result = 1; break;
- case KPENTER: handle_transport(FAST_FWD, 0, use_inout);
result = 1; break;
- case KPINS: handle_transport(STOP, 0, use_inout);
result = 1; break;
- case ' ': handle_transport(NORMAL_FWD, 0, use_inout);
result = 1; break;
- case 'k': handle_transport(STOP, 0, use_inout);
result = 1; break;
- case END:
- subwindow->lock_window("PlayTransport::keypress_event
3");
- goto_end();
- result = 1;
- subwindow->unlock_window();
- break;
- case HOME:
- subwindow->lock_window("PlayTransport::keypress_event
4");
- goto_start();
- result = 1;
- subwindow->unlock_window();
- break;
+ printf("received numpad-hit with hold alt! %i\n",
subwindow->get_keypress());
+ switch(subwindow->get_keypress())
+ {
+ case KPPLUS:
handle_transport(SHIFTED_FAST_REWIND, 0, use_inout);result = 1;
break;
+ case KP6:
handle_transport(SHIFTED_NORMAL_REWIND, 0, use_inout); result = 1;
break;
+ case KP5:
handle_transport(SHIFTED_SLOW_REWIND, 0, use_inout);result = 1;
break;
+ case KP4:
handle_transport(SHIFTED_SINGLE_FRAME_REWIND, 0, use_inout);result = 1;
break;
+ case KP1:
handle_transport(SHIFTED_SINGLE_FRAME_FWD, 0, use_inout);
result = 1; break;
+ case KP2: handle_transport(SHIFTED_SLOW_FWD,
0, use_inout); result = 1; break;
+ case KP3:
handle_transport(SHIFTED_NORMAL_FWD, 0, use_inout);
[CinCVS] Cinelerra3
Hi all, to shorten the endless suggestions (and discussions) of new Names for Cinelerra3 (cin3) I have started a compilation of suggestions at http://pipapo.org/pipawiki/Cinelerra3/Names . You are welcome to post your ideas there instead using the ML. But: PLEASE, write only SERIUOS and SUSTAINABLE suggestions to not fill up the wiki with spam. Thank you. Simeon ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
