I have one stange thing to add to the trouble.
I installed kaa base and mediainfo on my workstation with the following
result:
japie:~$ mminfo /dev/cdrom
kaa media metadata info
filename : /dev/cdrom
title: Seresta
artist: Rosenberg Trio, The
type: CD
subtype:
Another addition: with -d 2 I got:
DEBUG factory(290): Trying audio/cd
python: stack smashing attack in function PyEval_EvalFrame()
Aborted
But with plain -d I get:
kaa media metadata info
Traceback (most recent call last):
File /usr/bin/mminfo, line 84, in ?
a = max(0, min(int(a), 2))
Jaap Struyk wrote:
Another addition: with -d 2 I got:
DEBUG factory(290): Trying audio/cd
python: stack smashing attack in function PyEval_EvalFrame()
Aborted
But with plain -d I get:
kaa media metadata info
Traceback (most recent call last):
File /usr/bin/mminfo, line 84, in ?
You need to look at the logs /tmp/freevo/mplayer* or
/var/log/freevo/mplayer* and see what mplayer is telling you.
Duncan,
I looked at the /tmp/freevo/mplayer-stderr.log and found:
[AO OSS] audio_setup: Can't open audio device /dev/dsp: Device or resource
busy
Well, to get nearer to the
kaa.medata has changed from 0.5 to 0.6 and this means that some of the
calls in freevo rel-1 need to be changed.
I anybody is using the svn version of freevo rel-1 (*not* rel-1-6) you
will need to take certain steps to remove old kaa.metadata files before
updating freevo rel-1.
1) remove the
Roland Petera wrote:
You need to look at the logs /tmp/freevo/mplayer* or
/var/log/freevo/mplayer* and see what mplayer is telling you.
Duncan,
I looked at the /tmp/freevo/mplayer-stderr.log and found:
[AO OSS] audio_setup: Can't open audio device /dev/dsp: Device or resource
busy
Don't
Jaap Struyk wrote:
Another addition: with -d 2 I got:
DEBUG factory(290): Trying audio/cd
python: stack smashing attack in function PyEval_EvalFrame()
Aborted
But with plain -d I get:
Should be -d 1
kaa media metadata info
Traceback (most recent call last):
File /usr/bin/mminfo,
Duncan Webb a écrit :
Pascal Schirrmann wrote:
Hi,
One other very exciting new feature of freevo 1.7 is the encoding
server. As I use a Hauppauge PVR-350 card (connected on a cable
network), I obtain very good records, but somewhat too big.
Fixed in svn. I hope :)
Hi,
Pascal Schirrmann wrote:
Duncan Webb a écrit :
Pascal Schirrmann wrote:
Hi,
One other very exciting new feature of freevo 1.7 is the encoding
server. As I use a Hauppauge PVR-350 card (connected on a cable
network), I obtain very good records, but somewhat too big.
Fixed in
Op za 16-12-2006, om 13:39 schreef Duncan Webb:
Should be -d 1
That works.
To find out whats going on I tryed all the .py scripts in the
/usr/lib/python2.4/site-packages/kaa/metadata/disc manualy, none of them
triggers the stack smashing protector.
Neither did mediainfo.py
Am I right that info
Duncan Webb a écrit :
Pascal Schirrmann wrote:
branch/rel-1 it should be in src/helpers/encodingserver.py
HTH
Duncan
Ok,
First of all, i really thank you for your help.
I did a big download from the svn server (more tahn 1 gb !) :
svn co svn://svn.freevo.org/freevo rel-1
And yes,
Hi all,
at last I found the problem:
The KDE aRts soundserver was preventing mplayer from using the sound output.
(One does not get any informations about that with lsof /dev/dsp)
The KDE aRts soundserver releases the sound output when it was not in use for
60 seconds. Freevo was then able to
Pascal Schirrmann wrote:
Duncan Webb a écrit :
Pascal Schirrmann wrote:
branch/rel-1 it should be in src/helpers/encodingserver.py
HTH
Duncan
Ok,
First of all, i really thank you for your help.
I did a big download from the svn server (more tahn 1 gb !) :
svn co
Roland Petera wrote:
Hi all,
at last I found the problem:
The KDE aRts soundserver was preventing mplayer from using the sound output.
(One does not get any informations about that with lsof /dev/dsp)
The KDE aRts soundserver releases the sound output when it was not in use for
60 seconds.
14 matches
Mail list logo
