One of my steps in moving my home workstation to a GNU platform is to find a replacement for Vegas Video under Windows.
Starting out with my stock Fedora Core 1 system, I first downloaded the RPM for Cinelerra. This installed without incident and ran on the first try!
Not only this, but with a little tweaking (setting the recording preference to Firewire) I was able to open the capture tool and record some video off of my digital camcorder.
This was going amazingly well!
Of course, it was too good to be true. As soon as I added the clip to the timeline and attempted to play it back, it was nothing but garbage.
Ok, maybe I was getting ahead of myself with something as heavy-duty as Cinelerra. Let’s take a step back and try to get something more basic running, Kino.
Kino is not avaliable as a binary RPM, so we’re going to do this the old fashion way and download the source. The source is built using the typical configure, make, make install cycle, but I immediately ran into a snag running the configure script; libdv is required.
No matter, we download libdv and follow the same process (configure, make, make install)…wait a minute, there is an RPM, cool!
I want to mention that Fedora has a nice pretty GUI that comes up when you double-click an RPM. So far I’ve used it twice and it’s been nice to me.
Ok, libdv installed from RPM, let’s try to configure Kino again…
Hmm…same problem. Oh wait, we need libdv-devel, not just libdv (silly me!). That’s OK, we have an RPM for that as well, so let’s just down that and see what happens…
…ok, now we need libraw1394-devel (I’ll get the devel package the first time this time around…) Oh boy, the link from Kino’s site is 404, but we can still get to linux1394.org. More bad news, no RPM, and no source for “libraw1394-devel”, just the source for libraw. Ok, we’ll try that.
./configure (ok)
make (ok)
make install (ok)
Now, let’s try configuring Kino again…sonofabitch; now we need libavc1394-devel…
Another tarball, another configure, another make, another make install…
Ok third time’s the charm (this is only the third time, right?). No, libsamplerate is next up to bat.
(on an unrelated note, I like seeing things like “fortran compiler” when a ./configure script runs, it’s just entertaining).
…and wouldn’t you know that my damn camera battery just died…
Anywhoo, libsamplerate configures, makes and make installs without error, but Kino’s configure script still can’t find it. It’s looking for samplerate.pc and suggests adding it’s directory to PKG_CONFIG_PATH. Ok I have a crazy idea; this file exists in the directory where I un-tared samplerate; what if I ran the Kino configure script from this directory?
no dice.
OK I’ll add this directory to the path…swing and a hit!
So now we’re configured, let’s try to make kino! (for every compilation, churn, churn churn). Holy crap this is taking a long time…Ok, make is done, now make install!
Ok, now that we’re installed…what? Well, let’s start the app by typing kino. Frak.
“error loading shared libraries”; it can’t find libsamplerate, christ. It’s in /usr/local/lib, wtf?
OK, maybe when I set the PKG_CONFIG_PATH to the directory where I un-tared the thing I broke something. Let’s switch it to /usr/local/lib, reconfigure and see what happens.
Nope.
So off to google and what do I find? Someone posted the exact same problem on the kino message board, last night.
I think this is a sign, it’s time for bed.