Kino crashes in FC8

RossClement · #1 16th December 2007, 10:40 AM

Hi all. I'm having trouble running kino. On my previous FC4 laptop, I couldn't install any video editing software apart from kino. Now with my new (PlanetCCRMA and Livna backed) FC8 install on a new computer, I've got cinelerra, kdenlive, Lives, avidemux, and kino installed. I haven't used the other software, and one or more of these may be an alternative to fixing kino. But at this precise second, kino is the only one of these packages that I know how to use.

When I start kino, everything seems fine. But as soon as I try to render ANY video (e.g.. with Titler) kino crashes. When I run kino in a terminal, this is the output I get:

Code:

>>> Trying /home/ross/001.kinofx.dv
>>> Trying /home/ross/002.kinofx.dv
[dv @ 0x41ae0f04]Can't initialize DV format!
Make sure that you supply exactly two streams:
     video: 25fps or 29.97fps, audio: 2ch/48Khz/PCM
     (50Mbps allows an optional second audio stream)

Kino experienced a segmentation fault.
Dumping stack from the offending thread

Obtained 10 stack frames.
kino [0x8074431]
[0xb7ff2420]
/usr/lib/libavformat.so.51 [0x41a9cd74]
/usr/lib/libavformat.so.51(dv_assemble_frame+0x23) [0x41a9d393]
/usr/lib/libavformat.so.51 [0x41a9d898]
/usr/lib/libavformat.so.51(av_write_frame+0x3d) [0x41a87b9d]
kino(_ZN5Frame9EncodeRGBEPh+0x17f) [0x80a81bf]
kino(_ZN10PageMagick11StartRenderEv+0x77c) [0x80e3d0c]
kino(on_togglebutton_magick_start_toggled+0x2d) [0x80e455d]
/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x49) [0x4ec6a409]

Done dumping - exiting.

I've attached the full output as a text file.

Runnin kino as root makes no difference.

I don't have 1394 on this laptop, and hence am not affected (I presume) by the current problems with 1394 libraries that seem to be the main kino discussion topic on this forum.

I have FFMPEG installed from svn installed over the top of the livna rpm version as I couldn't compile kdenlive from source without swscaler installed. Also, since kino was crashing in libaviformat, I thought that might be something to do with ffmpeg. But no change.

Any hints as to what might be wrong?

RossClement · #2 16th December 2007, 11:01 AM

This is getting weirder. It seems that this is a widespread problem where a DV file is created without having an audio track. I tried taking an avi file with no sound and ffmpeg'ing it to a DV file. It wouldn't work, and it produced a file with 0 bytes.

Given that this appears to be a widespread problem, I thought I'd find a solution. Or at least a statement that there isn't one. But so far, no luck.

Code:

ffmpeg -i untitled.avi -target pal-dv test.dv

... produces the output: .... oops too long, I've attached it.

RossClement · #3 16th December 2007, 11:35 AM

Apologies to everyone for "talking to myself", but I found that there is a new version, kino-1.2.0, on the main kino site. I compiled this from source, using default configure options, installed it over the top of the kino-1.1.1 from livna, and this fixes the problem. There are some display problems when playing back video, but the bottom line is the software is now usable.

http://www.kinodv.org/article/static/1

orsula · #4 18th December 2007, 05:22 AM

I was able to configure Kino 1.2.0 but I am getting this when I try to compile:

Code:

[gideon@qsp kino-1.2.0]$ make
make  all-recursive
make[1]: Entering directory `/home/gideon/Desktop/kino-1.2.0'
Making all in po
make[2]: Entering directory `/home/gideon/Desktop/kino-1.2.0/po'
file=`echo ca | sed 's,.*/,,'`.gmo \
          && rm -f $file &&  -o $file ca.po
/bin/sh: line 1: -o: command not found
make[2]: *** [ca.gmo] Error 127
make[2]: Leaving directory `/home/gideon/Desktop/kino-1.2.0/po'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/gideon/Desktop/kino-1.2.0'
make: *** [all] Error 2

It happens if I try 'sudo make' as well. Anyone have any debugging ideas?
Thanks

RossClement · #5 18th December 2007, 09:59 PM

Quote:

Originally Posted by orsula

I was able to configure Kino 1.2.0 but I am getting this when I try to compile:

Code:

[gideon@qsp kino-1.2.0]$ make
make  all-recursive
make[1]: Entering directory `/home/gideon/Desktop/kino-1.2.0'
Making all in po
make[2]: Entering directory `/home/gideon/Desktop/kino-1.2.0/po'
file=`echo ca | sed 's,.*/,,'`.gmo \
          && rm -f $file &&  -o $file ca.po
/bin/sh: line 1: -o: command not found
make[2]: *** [ca.gmo] Error 127
make[2]: Leaving directory `/home/gideon/Desktop/kino-1.2.0/po'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/gideon/Desktop/kino-1.2.0'
make: *** [all] Error 2

It happens if I try 'sudo make' as well. Anyone have any debugging ideas?
Thanks

I just did a make clean, and then another make in my kino-1.2.0 directory. Worked fine.

Looking in the makefile in the kino-1.2.0/po directory, I note this:

Code:

.po.gmo:
        file=`echo $* | sed 's,.*/,,'`.gmo \
          && rm -f $$file && $(GMSGFMT) -o $$file $<

That seems to be the source of the line in your makefile that causes the error. I presume that you don't have $(GMSGFMT) set properly in your make. I note that further up in that makefile I have:

Code:

GMSGFMT = /usr/bin/msgfmt

so in my case I don't get the syntactically incorrect line that you do as the variable has a non-empty value.

So, the best I can do in terms of suggesting what to try next is for you to check your kino-1.2.0/po make file and see what (if anything) GMSGFMT is set to. Do you have /usr/bin/msgfmt on your computer?

Hoping this is something vaguely approximating useful information.

Edit: What do you get if you issue the command:

Code:

$ rpm -q --whatprovides /usr/bin/msgfmt
gettext-0.16.1-12.fc8
$

ryptyde · #6 19th December 2007, 03:33 AM

Using Kino 1.1.1 from Livna and haven't exp any crashes rendering .dv or .avi but then I haven't mixed 3rd party repos which can cause unexpected problems and elusive solutions.

RossClement · #7 19th December 2007, 10:00 AM

Quote:

Originally Posted by ryptyde

Using Kino 1.1.1 from Livna and haven't exp any crashes rendering .dv or .avi but then I haven't mixed 3rd party repos which can cause unexpected problems and elusive solutions.

The only other repo I use apart from livna is planet ccrma, and ccrma is vital to me. I haven't just mixed repos for the sake of it.

orsula · #8 19th December 2007, 03:50 PM

Hi Ross,
You were right!! I had nothing for GMSGFMT in the Makefile. I installed gettext and added the /usr/bin/msgfmt to the Makefile. Installed perfectly. That was a great tip!!
Thanks

5ElementsFist · #9 19th December 2007, 11:15 PM

Hey Ross,
I was having the same problem mentioned earlier: kino works fine except when rendering certain fx. I tried installing kino-1.2.0 over top of kino-1.1.1, like you said. When I tried to configure kino-1.2.0, I ran into this:

Quote:

checking for LIBDV... configure: error: Package requirements (libdv >= 0.103) were not met:

No package 'libdv' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables LIBDV_CFLAGS
and LIBDV_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

How do I get this new install to recognize that libdv is already installed?

Thanks in advance,
Tim

orsula · #10 20th December 2007, 01:03 AM

Quote:

Originally Posted by 5ElementsFist

Hey Ross,
I was having the same problem mentioned earlier: kino works fine except when rendering certain fx. I tried installing kino-1.2.0 over top of kino-1.1.1, like you said. When I tried to configure kino-1.2.0, I ran into this:

How do I get this new install to recognize that libdv is already installed?

Thanks in advance,
Tim

You probably need to do this:

Code:

sudo yum install libdv-devel

Also, anything else you think you already have installed but seems to be preventing configure from doing its thing - can many times be solved by installing the devel package, which is needed if you are compiling from source.
Hope it helps

5ElementsFist · #11 20th December 2007, 02:00 AM

Ahh...of course. Thanks orsula.

rapiddescent · #12 20th December 2007, 09:43 PM

I've just encountered this problem as well in FC8 on a non-ieee1394 laptop. Luckily I didn't upgrade an FC7.ez workstation.

it's easy to reproduce -
1. just create a new kino project
2. go to FX
3. create a 25 frame black to black
same error as RossClement above.

I've yum'd libdv-devel and got the latest ffmpeg and checked that dv is a supported format. at a loss really. I suppose a build from src is the next step?

RossClement · #13 21st December 2007, 01:26 PM

rapiddescent, what happens if you try and create dvvideo from a source movie with no sound, or mono sound, just using ffmpeg?

wt6g · #14 24th December 2007, 04:04 PM

I'm having the same problem of Kino crashing in FC8. Checked the makefiles etc. as above, no joy. It seems from the number of pointer warnings, incompatible assignments, deprecated functions, and undefined variables that make spews out there's far more wrong here than a simple fix going to address. (Kino 1.2.0)

/Len

wt6g · #15 24th December 2007, 04:17 PM

I found the problem of crashes on my system. Its related to audio. If I disable audio output kino works fine.

Edit/Preferences/Audio

Enable Audio Output is checked and the device is set to default. Unchecking stops the crashes. I'm going to look at my audio setup and see if there is anything obvious.

/Len