Cinelerra CV 2.2 (Pulled git 11/07/14) for Carolina

[battleshooter]

Unleash the 50,000 watt flamethrower of content creation in your Linux box. It's a movie studio with the efficiency of a box. Cinelerra is intended to be useful and fast, representing the most used features from 15 years of editing, but not compare to the leading commercial editors. By modern standards, it's probably minimalist.

- http://www.heroinewarrior.com/cinelerra.php

CV stands for Community Version.Cinelerra-CV is not a fork. We develop it in a direction not diverging from the original and we merge with all the new releases from Heroine Virtual. We apply our bug fixes, compiler compliance fixes, and enhancements to the git repository. Thus the CV has a number of features that the official version does not have. Cinelerra CV can be defined as the community's attempt to stabilise HV's release and to add enhancement in a community fashion.

- http://cinelerra-cv.org/about.php





I have a bit of history with Cinelerra, it was the first video editor I ever compiled and ya'll know how I love video editors However that first compilation was a mess, even worse so than normal so no links to that piece of "history".

Anyhow... I thought I compiled CV 2.2 wrong but a quick Google search showed the problems I encountered such as poor codec compatibility or refusing to stop playing were normal issues.

Just as a quick note, the fix to get Cinelerra to stop playing a video once started is Preferances > Playback > Audio Driver = ALSA check tab Stop playback locks up. I have to agree with this guy:

I've asked before, but why is this a configurable option? Is there some population of users out there who want lock-ups?

Download Cinelerra CV 2.2
Size: 18.7 MB
MD5: fe665faab207a57bbfdac47a2c1cc6e2

Download cinelerra_cv_NLS-git-11-07-14.pet
Download cinelerra_cv_DOC-git-11-07-14.pet

Where possible I used the dependencies found in the Carolina repository and if not, the same version.

Dependencies included in SFS
dvgrab-3.5
fftw-3.3.2
ilmbase-2.1.0
libavc1394-0.5.4-w5c
libdv-1.0.0
libquicktime-1.2.4
libiec61883-1.2.0
mjpegtools-2.1.0
opencv-2.4.6
openexr-2.1.0

Some comments:

Because of my unfamiliarity with Cinelerra I might not pick up on any bugs related to compilation. If you're familiar with Cinelerra and know a bug is in this SFS that isn't normally in other Cinelerra installations, please let me know.

Changelog:
13-07-14 - Added libdv and dvgrab to SFS

[davids45]

G'day battleshooter,

Tried this sfs in TahrPup-5.8.3 (new frugal) and via the console found libdv.so.4 was missing.
Installed a version of this lib for Tahr from a Ubuntu site and Cinelerra ran (played a .mpg file).
Haven't attempted any editing yet.
David S.

Just tried it in a Slacko-5.7 frugal - this time, console reported missing libx264.so.116; RPM archive had an .rpm version of this lib file which Pup installed and Cinelerra then opened. Still to put Cinelerra through any paces yet.

[RSH]

Hi.

This seems to work in Precise (complained missing libdv.so.4).

Grabbed those Files

libdv.a
libdv.la
libdv.so.4
libdv.so.4.0.3

from a kdenlive sfs and copied into the OS (for a quick test).

Successfully rendered a project similar like in Flowblade - rendered to .ogg Format.

Plays nice in gnome-player and vlc.

[battleshooter]

Tried this sfs in TahrPup-5.8.3 (new frugal) and via the console found libdv.so.4 was missing

This seems to work in Precise (complained missing libdv.so.4).

Bah, what a nuisance. Looks like libdv may be in Carolina so I didn't pick it up it up as an error in the terminal.

Nonetheless I'm reuploading the SFS with libdv and dvgrab for good measure, in case anyone like me is also stuck with an old DV tape camera.

Just tried it in a Slacko-5.7 frugal - this time, console reported missing libx264.so.116

Yeah, Carolina comes with libx264, but it's not a staple in a lot more simpler Pups. Still, besides these little dependencies issues, glad to hear the SFS is able to work in different pups.

Grabbed those Files
libdv.a
libdv.la

Shouldn't need those, *.a and *.la are only for compiling. Nevermind, I suppose you were being better safe than sorry.

Oh yes, NLS and DOC for Cinelerra's up as well.

[Pelo]

Cinelerra is for professionals. the harder in not to get it, however it's difficult. When the users wants to work his videos, then begins the chellenge. Perhaps i am a poor lonesome user here. No trace of success story in the forum. But our task is first to get it installed , for us, usarios.
I look after the links to the french forum. I wouldn't stop the matter. Don 570 provides pet click there
I was looking for libdv.so.4 , so i get here. Kino seems no more a good idea than cinelerra.
A brand new video editor has just arrived on the forum flowblade-0.12.0_precise.sfs: 24 M
Announced as the polyvalent one, ending our crisis with openshot, cinelerra, and others.
Sorry, i use now Windows Live Media Creator, i have it sold with windows 7, so the clever solution is to make it serve.
The poor Pelo was found lying on the ground, after a nervous breakdown here

[battleshooter]

The poor Pelo was found lying on the ground, after a nervous breakdown here

I'm sorry Pelo... Err, maybe you could just try using Carolina, with the video editors I packaged that you've been trying? They should work just fine as that's what I compiled them in and packaged them for.

[mikeslr]

Hi Pelo,

Which Puppy are you using? and on What computer? RAM? CPU? Video Card?

Battleshooter builds applications to run under Carolina. As Battleshooter suggested, the easiest way to get one of his applications to work as it's supposed to is to use it in the Puppy he created it in*.
I'm a tinkerer. Left to my own devises, with a lot of hard work, I can probably build a garbage heap. But I like to explore. So I try combinations of things which may not work to see if they actually do.
And while RG66, Geoffrey (and, I think, previously Elroy)'s combined efforts have resulted in a versatile pup, Carolina, with a slew of top-notch applications, I much prefer the Openbox-Lxpanel-rox environment to Carolina's Xfce-thunar. So when Battleshooter --or someone else-- makes an application available, regardless of what Pup it was created for, I'll try it in other Pups and post my experience.
Except, by now I know that:
Pets and SFSes built for Slacko will almost never run under Pups built using Ubuntu binaries --i.e., Lupu, Lucid, Precise, Raring, Tahr-- and vice-versa.
Pets built for Saluki or Carolina may run under any Puppy, although occasionally some libs have to be tracked down. And, as devs who create applications are constantly "improving" them by changing their libraries, older pets may sometimes function in a strange environment when newer pets won't.

If you open http://puppylinux.us/psearch.html, select Puppy Forum as Web Source, and type my handle "mikeslr" together with a video editor application --for example, "mikeslr openshot"-- into the Search box, you'll find the posts of my experiments with "mix and match".

Some version of openshot which will run under any Pup. But not necessarily the same version. And some version of Avidemux will also run under any Pup; as will some version ffmpeg/ffconvert or Winff, These form a powerful combination for video editing, assembly and format conversion.
Battleshooter's Flowblade-0.14 will run under Precise and Raring, but not tahr or Lucid/Lupu (these are Ubuntu based Pups employing older and newer libs, respectively) nor any Slacko. It is by far the most capable and easiest to use video editor. But, if you're working with a small screen, it may not suit you.
Battleshooter's Kdenlive will play-nice under the Slackos.
But if all else fails, since wine is independent of Puppy versions, you can try running Shotcut under Shinobar's Wine-portable. See http://murga-linux.com/puppy/viewtopic. ... 684#797684.

But again, Which Puppy are you using? and on What computer? RAM? CPU? Video Card?

mikesLr

* Not since before Barry K created woof has Puppy been a Linux distribution in the sense that Ubuntu or Slackware is a Linux distribution. When Ubuntu publishes a model, its binaries have been built against one kernel, and all the libs used in any application have been built to function with that model. Woof enables the building of a Puppy using the binaries of other Linux distributions, or from sources compiled via the T2 build kit. Trying to run applications built for one Pup in a different Pup is like merely dropping the motor of a Peugeot 207 into a Citreon Picasso and expecting it to run smoothly.

[Pelo]

pet version 2.2 needed here
No pet kept in my tool case, erased.