Rajiv
Well, here is how you can compile Cinelerra on Fedora11. This a rough and ready workaround till they fix things and make the whole process a bit smoother.
Read the previous post here to install all the deps
now roll your sleeves and get going.
mkdir Cinelerra
cd Cinelerra
git clone git://git.cinelerra.org/j6t/cinelerra.git cinelerra
cd cinelerra
./autogen.sh
./configure --prefix=/usr --enable-opengl
Before you hit “make” you will need to compile the libmpeg3hv.la first
so do that
cd /home/rajiv/Cinelerra/cinelerra/libmpeg3
./configure
make
After this we need to compile libquicktimehv.la
cd /home/rajiv/Cinelerra/cinelerra/quicktime
./configure
make
Now its time to compile the heroine warrior.
cd /home/rajiv/Cinelerra/cinelerra
make -j3
sudo make install
Done :)
Sorry, wrong paste from Prior comment that is pending moderation.
That worked!! BUT..
When I go to record I see the following:
AVC1394Control::initialize(): couldn’t set port: Invalid argument
RecordMonitorCanvas::RecordMonitorCanvas 1 0 0 951 500
ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM Intel 82801DB-ICH4 #0
AudioALSA::open_input: No such file or directory
Device1394Input::open /dev/dv1394-0: No such file or directory
signal_entry: got SIGSEGV my pid=27637 execution table size=16:
canvas.C: create_canvas: 775
canvas.C: create_canvas: 778
canvas.C: create_canvas: 780
recordmonitor.C: recordmonitor.C: 69
recordmonitor.C: recordmonitor.C: 75
recordmonitor.C: recordmonitor.C: 77
recordmonitor.C: recordmonitor.C: 86
recordmonitor.C: recordmonitor.C: 94
recordmonitor.C: recordmonitor.C: 97
recordmonitor.C: recordmonitor.C: 99
recordmonitor.C: recordmonitor.C: 101
recordmonitor.C: recordmonitor.C: 998
record.C: run: 429
record.C: run: 432
record.C: run: 439
record.C: run: 450
signal_entry: lock table size=18
0x1b983c0 CWindowTool::input_lock CWindowTool::run
0x1bbd5e0 TransportQue::output_lock PlaybackEngine::run
0x1ca8aa0 TransportQue::output_lock PlaybackEngine::run
0x1ca9470 MainIndexes::input_lock MainIndexes::run 1
0x1d2af10 ResourceThread::draw_lock ResourceThread::run
0xb66b00 BC_Synchronous::next_command BC_Synchronous::run
0x1d65a80 BC_Repeater::pause_lock BC_Repeater::run
0x1bec5f0 BC_WindowBase::event_condition BC_WindowBase::get_event
0x19a54e0 BC_WindowBase::event_condition BC_WindowBase::get_event
0x1ae63f0 BC_WindowBase::event_condition BC_WindowBase::get_event
0x1d673d0 BC_WindowBase::event_condition BC_WindowBase::get_event
0x1bbefc0 BC_WindowBase::event_condition BC_WindowBase::get_event
0x1cd9100 Record::window_lock Record::run 3 *
0x7fbfc00347f0 RecordStatusThread::input_lock RecordStatusThread::run
0x1cab650 BC_WindowBase::event_condition BC_WindowBase::get_event
0x7fbfc00f7010 RecordMonitor::output_lock RecordMonitorThread::run
0x7fbfc00b73e0 BC_WindowBase::event_condition BC_WindowBase::get_event
0x7fbfc0100150 AudioDevice::buffer_lock AudioDevice::run_input 1 *
BC_Signals::dump_buffers: buffer table size=0
BC_Signals::delete_temps: deleting 0 temp files
SigHandler::signal_handler total files=0
Aborted
[leif@shadrack cinelerra-4]$
[leif@shadrack cinelerra-4]$
[leif@shadrack cinelerra-4]$ rpm -qa | grep 1394
libraw1394-2.0.1-2.fc11.x86_64
libdc1394-docs-2.1.2-1.fc11.x86_64
libdc1394-tools-2.1.2-1.fc11.x86_64
libdc1394-2.1.2-1.fc11.x86_64
libdc1394-devel-2.1.2-1.fc11.x86_64
libavc1394-devel-0.5.3-5.fc11.x86_64
libraw1394-devel-2.0.1-2.fc11.x86_64
libavc1394-0.5.3-5.fc11.x86_64
[leif@shadrack cinelerra-4]$
Hi Leif Ericksen
There are issues with Dv capture. But there are workarounds.
One you will need to patch your Kernel and use a low latency module.
Most of us these days use Kino for most of the capturing. Kino uses DvGrab which uses raw1394 and not the dv1394 kernel module.
These issues are being fixed as there is a new capture module now under development. It will be a year or so before the development sees any workable release, till then Kino is strictly advised.