Re: [PyTone-users] [pytone] pytone causes 100% CPU usage
Hi Claudio, On 21.02.08, Claudio Pascalis wrote:
On Thu, 21 Feb 2008 09:06:17 +0100 [player.main]
# This player will be used for playing of the songs in the playlist.
autoplay = true
type = internal driver = oss device = /dev/dsp bufsize = 100 crossfading = on crossfadingstart = 5 crossfadingduration = 6
Ok. Looks fine. But let's see what happens with the 3.0. branch.
I would test alsa but I can't start pytone anymore..see below
I also tried to install the version 3.0.1 of pytone but there some errors I don't understand
(buildbufferedaoext = False and True have the same errormessage)
$ python setup.py build_ext -i running build_ext building 'pytone.pcm' extension gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.5 -c src/pcm/pcm.c -o build/temp.linux-i686-2.5/src/pcm/pcm.o src/pcm/pcm.c:35:20: Fehler: Python.h: No such file or directory [snip] Die Fehlermeldungen sind jetzt natürlich auf Deutsch...wie kann ich das ändern, damit alle Menschen auf der Mailinglist das verstehen? :)
By setting LANG=C :-)
Anyway, you need to install the python-dev package in order to be able to build the neede Python extension modules.
Ok, I installed the python-dev package (and libao-dev just to test it with the C extension), but I only get more errors :(
$ pytone Traceback (most recent call last): File "src/pytone.py", line 57, in ? config.processconfig() File "/home/dio/Linux/programme/PyTone-3.0.1/src/config.py", line 935, in processconfig processstandardconfig() File "/home/dio/Linux/programme/PyTone-3.0.1/src/config.py", line 800, in processstandardconfig readconfigsection(section, eval(section)) File "/home/dio/Linux/programme/PyTone-3.0.1/src/config.py", line 740, in readconfigsection raise ConfigError("Unkown configuration option '%s' in section '%s'" % config.ConfigError: Unkown configuration option 'playlistdir' in section 'general'
That's probably because you have a pytonerc file lying around in /etc. So just delete /etc/pytonerc and this problem should disappear. I actually think that putting the pytonerc file distributed with PyTone in /etc is not a good idea.
Both $ python setup.py install and $ python setup.py build_ext -i are running fine except for a warning with build_ext: ... src/pcm/pcm.c: In Funktion »py_rate_convert«: src/pcm/pcm.c:260: Warnung: »last_r« könnte in dieser Funktion uninitialisiert verwendet werden src/pcm/pcm.c:259: Warnung: »last_l« könnte in dieser Funktion uninitialisiert verwendet werden ...
Im really tired of trying to installing it but I really want this program :(
The warnings are no problem, so everything should be fine. Cheers, Jörg
On Thu, 21 Feb 2008 22:55:37 +0100 Joerg Lehmann <joerg@luga.de> wrote:
Hi Claudio,
On 21.02.08, Claudio Pascalis wrote:
On Thu, 21 Feb 2008 09:06:17 +0100 [player.main]
# This player will be used for playing of the songs in the playlist.
autoplay = true
type = internal driver = oss device = /dev/dsp bufsize = 100 crossfading = on crossfadingstart = 5 crossfadingduration = 6
Ok. Looks fine. But let's see what happens with the 3.0. branch.
I would test alsa but I can't start pytone anymore..see below
I also tried to install the version 3.0.1 of pytone but there some errors I don't understand
(buildbufferedaoext = False and True have the same errormessage)
$ python setup.py build_ext -i running build_ext building 'pytone.pcm' extension gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.5 -c src/pcm/pcm.c -o build/temp.linux-i686-2.5/src/pcm/pcm.o src/pcm/pcm.c:35:20: Fehler: Python.h: No such file or directory [snip] Die Fehlermeldungen sind jetzt natürlich auf Deutsch...wie kann ich das ändern, damit alle Menschen auf der Mailinglist das verstehen? :)
By setting LANG=C :-)
Anyway, you need to install the python-dev package in order to be able to build the neede Python extension modules.
Ok, I installed the python-dev package (and libao-dev just to test it with the C extension), but I only get more errors :(
$ pytone Traceback (most recent call last): File "src/pytone.py", line 57, in ? config.processconfig() File "/home/dio/Linux/programme/PyTone-3.0.1/src/config.py", line 935, in processconfig processstandardconfig() File "/home/dio/Linux/programme/PyTone-3.0.1/src/config.py", line 800, in processstandardconfig readconfigsection(section, eval(section)) File "/home/dio/Linux/programme/PyTone-3.0.1/src/config.py", line 740, in readconfigsection raise ConfigError("Unkown configuration option '%s' in section '%s'" % config.ConfigError: Unkown configuration option 'playlistdir' in section 'general'
That's probably because you have a pytonerc file lying around in /etc. So just delete /etc/pytonerc and this problem should disappear.
I actually think that putting the pytonerc file distributed with PyTone in /etc is not a good idea.
Both $ python setup.py install and $ python setup.py build_ext -i are running fine except for a warning with build_ext: ... src/pcm/pcm.c: In Funktion »py_rate_convert«: src/pcm/pcm.c:260: Warnung: »last_r« könnte in dieser Funktion uninitialisiert verwendet werden src/pcm/pcm.c:259: Warnung: »last_l« könnte in dieser Funktion uninitialisiert verwendet werden ...
Im really tired of trying to installing it but I really want this program :(
The warnings are no problem, so everything should be fine.
Cheers,
Jörg
It is running now but it nevertheless keeps my CPU at 100% :( When pytone starts it is complaining: PyTone-3.0.1/src/services/players/internal.py:25: RuntimeWarning: Python C API version mismatch for module pcm: This Python has API version 1012, module pcm has version 1013. import pcm PyTone-3.0.1/src/services/players/internal.py:32: RuntimeWarning: Python C API version mismatch for module bufferedao: This Python has API version 1012, module bufferedao has version 1013. import bufferedao O_o I also tried alsa but it didn't change anything Claudio
On 21.02.08, Claudio Pascalis wrote:
It is running now but it nevertheless keeps my CPU at 100% :(
Well, I have to admit that's kind of hard to debug. One of the threads seems to make a problem. Just a question: Are you sure that the database rebuild has already finished?
When pytone starts it is complaining:
PyTone-3.0.1/src/services/players/internal.py:25: RuntimeWarning: Python C API version mismatch for module pcm: This Python has API version 1012, module pcm has version 1013. import pcm PyTone-3.0.1/src/services/players/internal.py:32: RuntimeWarning: Python C API version mismatch for module bufferedao: This Python has API version 1012, module bufferedao has version 1013. import bufferedao
That happens because the Python version you used to compile the extension modules needed by PyTone (i.e., when running setup.py) is not the same as the one used when running PyTone. Probably you have two different versions installed and the shell script distributed with PyTone 3.0.1 is hardcoded to use a non-default one. So you might want to change that. But it should not be a problem, anyway. Jörg
On Fri, 22 Feb 2008 09:10:22 +0100 Joerg Lehmann <joerg@luga.de> wrote:
On 21.02.08, Claudio Pascalis wrote:
It is running now but it nevertheless keeps my CPU at 100% :(
Well, I have to admit that's kind of hard to debug. One of the threads seems to make a problem. Just a question: Are you sure that the database rebuild has already finished?
Yes, I'm sure.
When pytone starts it is complaining:
PyTone-3.0.1/src/services/players/internal.py:25: RuntimeWarning: Python C API version mismatch for module pcm: This Python has API version 1012, module pcm has version 1013. import pcm PyTone-3.0.1/src/services/players/internal.py:32: RuntimeWarning: Python C API version mismatch for module bufferedao: This Python has API version 1012, module bufferedao has version 1013. import bufferedao
That happens because the Python version you used to compile the extension modules needed by PyTone (i.e., when running setup.py) is not the same as the one used when running PyTone. Probably you have two different versions installed and the shell script distributed with PyTone 3.0.1 is hardcoded to use a non-default one. So you might want to change that.
But it should not be a problem, anyway.
Jörg
I will try to delete everything and build it again in the next days... Thanks so far for your help Claudio
Teilnehmer (2)
-
Claudio Pascalis -
Joerg Lehmann