Hi Bill. I've built cinelerra on my powerbook G4 with altivec. It's
not that difficult, but you should be aware that currently you cannot
edit .dv files natively in cinelerra on PPC because of a "big-endian"
problem in libdv (as far as I understand it, others may correct me on
this). Also, since there are no proprietary drivers for ppc graphics
acceleration (unless you count the intel open source project...) you
won't be able to get opengl accelation on playback because mesa
doesn't support opengl version 2. That said, cinelerra seems to run
fairly well for me, as long as I don't try native hdv. (HDV doesn't
have the libdv problem, but it's far too big for my processor).
After my exams are over I'm going to look into getting cinelerra to
work with ffmpeg's dv codec instead of libdv. The mjpeg guys are
fairly certain ffmpeg's dv codec is pretty superior to libdv in
general, so that should be a boost for cinelerra all around.
Additionally, ffmpeg's codec supports dv50, which is a codec that was
requested on this list.
As a general question to this list: I can't find cinelerra on the
google SoC mentor's page. Was cinelerra accepted this year or not?
Bill: if you would like me to walk you through it I can. Please let me
know if cinelerra is still useful to you without .dv support
You can get started by checking out from svn (you may need to apt-get
subversion):
svn checkout svn://svn.skolelinux.org/cinelerra/trunk/hvirtual
I would recommend you do this in a "src" directory. On my xubuntu box,
I have /home/[username]/src/ for packages I build from scratch.
There's also /usr/src, but I like to build packages in my home
directory, and save big system-wide things (like kernels and drivers)
in /usr/src. Also saves me typing sudo :).
The svn command above will create a folder called hvirtual in your
current working directory (I presume it is /some/path/src). At this
point, given you're on Ubuntu, you're gonna want to make sure you have
installed the "build-essentials" package, since ubuntu doesn't install
a compiler by default.
Presuming you've done that, go into the hvirtual directory and type:
./configure.
This should run the configure script, which should go through and
prepare the package for building. If you get a "No such file or
directory" error, email this list again and I will tell you how to
create your own ./configure script (it just means you have to run
another script first, no actual work).
Once ./configure does work, you can run it with ./configure --help to
see various options. You're gonna want to --enable-altivec at least.
All the options have explanations, but if you're not sure about
something, ask.
Presuming ./configure started running, you should notice it failing
and complaining about various things you don't have. Each time, find
the relevant ubuntu package and install it, and if there is a "-dev"
version you'll probably need to install that too. Each time you
install a new package run the ./configure script again and see if it
gets farther (as in, fails on a different required package, aka
"dependency"). If it actually finishes, it prints out all the varioius
things it wanted and whether you had them. Mine looks like this:
Summary of mandatory components:
libogg found
libvorbis found
libvorbisenc found
libvorbisfile found
libtheora found
OpenEXR found
libdv found
libpng found
libjpeg libraries found
libjpeg headers found
libtiff libraries found
libtiff headers found
FreeType 2 found
libx264 libraries found
libx264 headers found
libuuid libraries found
libuuid headers found
mjpegtools found
libfftw3 libraries found
libfftw3 headers found
liba52 libraries found
liba52 headers found
libmp3lame libraries found
libmp3lame headers found
libsndfile libraries found
libsndfile headers found
libfaac libraries found
libfaac headers found
libfaad libraries found
libfaad headers found
Summary of optional components:
ESD subsystem found
ESD (Enlightenment Sound Daemon) is enabled
ALSA subsystem found
ALSA is enabled
libraw1394 found
libiec61883 found
libavc1394 libraries found
libavc1394 headers found
librom1394 libraries found
librom1394 headers found
Firewire is enabled
OpenGL 2.0 libraries missing
Hardware acceleration using OpenGL 2.0 is disabled
Now type
make
to start compilation.
"Founds" are good. Everything in the top section is required, so you
could start by installing all of those packages before trying
./configure, to save yourself some time. In the optional section,
you're definitely gonna want ALSA, though you might not have ESD
(because you use KDE).
NB: I hand compiled a few packages because I don't like the ubuntu
defaults, particularly with fffmpeg (which doesn't include x264 when
last I checked). I also used a few packages from debian SID (the
unstable version of debian) because I wanted things that were newer,
or because the packages I hand compiled requested them. I don't think
any of that is actually necessary, (meaning you can probably get away
with just the standard ubuntu repositories) but if you run into
problems just ask.
Once you've got all your "founds". I would recommend installing a
package called "checkinstall". Once that is done, you can type
"sudo checkinstall" in the hvirtual directory to build your very own
cinelerra .deb, which will then be installed for you. It may fail on
the package building section at the building section at the bottom
(which is what always happens to me), but if that happens search for a
".spec" file in the hvirtual folder, and try messing with that. You
won't have to wait so long (since it will retain the compiled binary)
and then just keep trying checkinstall until it works. I'm not quite
sure how to do this properly, but since I don't care that much I
haven't looked it up.
The point is: you will have a debian package which you can install and
remove at will (which is the whole point of a package management
system) using "sudo dpkg -i [name of package]" and "sudo dpkg -r [name
of package]" respectively. So if you want a newer version (go to the
hvirtual folder and type "svn update" to download any recent changes)
you can remove the old one, and install the new one without much
trouble.
As a final note, apt-get may complain about an "out of date" cinelerra
package. This is fine: your package isn't the ubuntu package, so it
thinks it's out of date. Just ignore those warnings.
Hope this was helpful. I'm going back into study mode now, so I'm
sorry if I'm not able to answer questions right away. I haven't looked
this over so there may be an error or two, but hopefully this should
get you pretty far.
good luck.
-griff
PS, if you find this too much of a hassle, I'm pretty sure ubuntu has
a (fairly old) version of cinelerra for you to install.
On 3/23/07, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
Send Cinelerra mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Cinelerra digest..."
Today's Topics:
1. I could try building a ppc altivec version on my mac mini (Bill Heinz)
I'm bill. I have Kubuntu Edgy installed on a 1.25ghz G4 Mac mini. I
wouldn't mind building it from source if you walk me through it. I'm
pretty good at following instructions. I managed to get IBM Java going
on it. Let me know. --Bill Heinz
_______________________________________________
Cinelerra mailing list
[email protected]
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
_______________________________________________
Cinelerra mailing list
[email protected]
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
