* Pytone users mailinglist pytone-users@luga.de [2006-09-04 13:39]:
Is this enough or do you need the whole debug.log?
Looks really the same. Can you try the patch I send concerning the byte-ordering problem. Maybe this fixes it for you. Funnily enough, for some devices the wrong byte-ordering works, but maybe it leads to other effects.
Hi Jörg,
the patch didn't help unfortunately :(
I tried "byte_format = 1" as well but it had the same effect: NULL ...
Anything else I can try?
Btw - before I add another ebuild to bugs.gentoo.org I'd like to know which prerequisites are *really* necessary nowadays:
pymad pyvorbis pyao (the ebuild requires python-2.3) libao vorbis-tools pyxmms
Greetz Stefan -- Stefan Wimmer swimmer@xs4all.nl
On 04.09.06, Stefan Wimmer wrote:
- Pytone users mailinglist pytone-users@luga.de [2006-09-04 13:39]:
Is this enough or do you need the whole debug.log?
Looks really the same. Can you try the patch I send concerning the byte-ordering problem. Maybe this fixes it for you. Funnily enough, for some devices the wrong byte-ordering works, but maybe it leads to other effects.
Hi Jörg,
the patch didn't help unfortunately :(
I tried "byte_format = 1" as well but it had the same effect: NULL ...
Anything else I can try?
I'm really a bit clueless. Now everything should be the same concering the player code.
Btw - before I add another ebuild to bugs.gentoo.org I'd like to know which prerequisites are *really* necessary nowadays:
pymad pyvorbis
Yes.
pyao (the ebuild requires python-2.3) libao
This depends. If you compile the C extension module, only libao (and its headers during the compilation process) are necessary.
vorbis-tools
Never was a prerequisite.
pyxmms
Not really at prerequiste but in principle still supported.
Jörg
* Joerg Lehmann joerg@luga.de [2006-09-05 00:35]:
I'm really a bit clueless. Now everything should be the same concering the player code.
Hmm - strange that I get it then :-/
Btw - before I add another ebuild to bugs.gentoo.org I'd like to know which prerequisites are *really* necessary nowadays: pymad pyvorbis
Yes.
... ok
pyao (the ebuild requires python-2.3) libao
This depends. If you compile the C extension module, only libao (and its headers during the compilation process) are necessary.
... oh - I never installed it with the C extension module. Will do that from now on :) (Installing it with the C extension module did not resolve the problem with the higher pitch btw.)
vorbis-tools
Never was a prerequisite.
... ok
pyxmms
Not really at prerequiste but in principle still supported.
... Even if you want to use xmms as a player?
Jörg
Greetz Stefan
========================================================= My very personal wishlist for Pytone - just ignore it ;-) ========================================================= * BPS recognition Show the bits per seconds from a song in the MP3 info window
* Pause between tracks
* Some sort of replaygain
* Extended search function -- Stefan Wimmer swimmer@xs4all.nl
* Joerg Lehmann joerg@luga.de [2006-09-05 00:35]:
I'm really a bit clueless. Now everything should be the same concering the player code.
Hi Jörg,
can it be because I use 'alsa09' instead of 'alsa'? I did not get 'alsa' working with this error msg:
Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/pytone/pytone.py", line 136, in ? playerids = [services.player.initplayer("main", config.player.main), File "/usr/lib/python2.4/site-packages/pytone/services/player.py", line 67, in initplayer raise RuntimeError("Cannot initialize %s player: type=internal, device=%s" % (id, config.device)) RuntimeError: Cannot initialize main player: type=internal, device=hw:0,0
Greetz Stefan
========================================================= My very personal wishlist for Pytone - just ignore it ;-) ========================================================= * BPS recognition Show the bits per seconds from a song in the MP3 info window
* Pause between tracks
* Some sort of replaygain
* Extended search function -- Stefan Wimmer swimmer@xs4all.nl
Hi Stefan,
On 14.09.06, Stefan Wimmer wrote:
can it be because I use 'alsa09' instead of 'alsa'? I did not get 'alsa' working with this error msg:
Maybe.
Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/pytone/pytone.py", line 136, in ? playerids = [services.player.initplayer("main", config.player.main), File "/usr/lib/python2.4/site-packages/pytone/services/player.py", line 67, in initplayer raise RuntimeError("Cannot initialize %s player: type=internal, device=%s" % (id, config.device)) RuntimeError: Cannot initialize main player: type=internal, device=hw:0,0
You could relace this raise by a plain raise to get more information on what's going on.
Jörg
* Joerg Lehmann joerg@luga.de [2006-09-14 21:30]:
You could relace this raise by a plain raise to get more information on what's going on.
Jörg
Hu?!? Please keep speaking english ;-)
Greetz Stefan -- Stefan Wimmer swimmer@xs4all.nl
Hi Stefan,
On 14.09.06, Stefan Wimmer wrote:
- Joerg Lehmann joerg@luga.de [2006-09-14 21:30]:
You could relace this raise by a plain raise to get more information on what's going on.
Hu?!? Please keep speaking english ;-)
Sorry, I meant that you could delete everything after "raise" in line 67 of src/services/player.py. This way, the reason for the driver not working would become clearer.
Jörg
* Joerg Lehmann joerg@luga.de [2006-09-14 22:00]:
Hi Stefan,
Sorry, I meant that you could delete everything after "raise" in line 67 of src/services/player.py. This way, the reason for the driver not working would become clearer.
Jörg
Hi Jörg,
I'm afraid I still do not know what you mean since I still get the same error msg after deleting all the other raises in src/services/player.py :-/
Greetz Stefan -- Stefan Wimmer swimmer@xs4all.nl
Hi Stefan,
On 14.09.06, Stefan Wimmer wrote:
I'm afraid I still do not know what you mean since I still get the same error msg after deleting all the other raises in src/services/player.py :-/
Are you sure. The error should persist but the message should not be the same.
Jörg
* Joerg Lehmann joerg@luga.de [2006-09-17 18:40]:
Hi Stefan,
On 14.09.06, Stefan Wimmer wrote:
I'm afraid I still do not know what you mean since I still get the same error msg after deleting all the other raises in src/services/player.py :-/
Are you sure. The error should persist but the message should not be the same.
Jörg
Hi Jörg,
no - I'm not sure at all since I'm not sure whether I understood very well what you tried me to say ;-) Can you provide me a patch? just to be sure ...
Greetz Stefan ;-) -- Stefan Wimmer swimmer@xs4all.nl
Hi Stefan,
On 17.09.06, Stefan Wimmer wrote:
no - I'm not sure at all since I'm not sure whether I understood very well what you tried me to say ;-) Can you provide me a patch? just to be sure ...
No problem, I've attached a patch.
Jörg
* Joerg Lehmann joerg@luga.de [2006-09-17 19:10]:
Hi Stefan,
On 17.09.06, Stefan Wimmer wrote:
no - I'm not sure at all since I'm not sure whether I understood very well what you tried me to say ;-) Can you provide me a patch? just to be sure ...
No problem, I've attached a patch.
Jörg
Thanks for the patch. As I was afraid already I did not understand what you wanted me to do ;-)
With your patch I get the following error msg: Traceback (most recent call last): File "src/pytone.py", line 136, in ? playerids = [services.player.initplayer("main", config.player.main), File "/home/swimmer/tmp/PyTone-2.3.1/src/services/player.py", line 64, in initplayer crossfadingduration=config.crossfadingduration, File "/home/swimmer/tmp/PyTone-2.3.1/src/services/players/internal.py", line 187, in __init__ self.audiodev = bufferedao.bufferedao(bufsize, self.SIZE, aodevice, rate=self.rate, options=aooptions) bufferedao.error: unknown driver_name
/etc/pytonerc -------------- [player.main] autoplay = true type = internal driver = alsa device = hw:0,0 bufsize = 100 crossfading = off
[player.secondary] autoplay = false type = internal driver = alsa device = hw:1,0 crossfading = off
Greetz Stefan -- Stefan Wimmer swimmer@xs4all.nl
On 17.09.06, Stefan Wimmer wrote:
- Joerg Lehmann joerg@luga.de [2006-09-17 19:10]:
Hi Stefan,
On 17.09.06, Stefan Wimmer wrote:
no - I'm not sure at all since I'm not sure whether I understood very well what you tried me to say ;-) Can you provide me a patch? just to be sure ...
No problem, I've attached a patch.
JörgThanks for the patch. As I was afraid already I did not understand what you wanted me to do ;-)
With your patch I get the following error msg: Traceback (most recent call last): File "src/pytone.py", line 136, in ? playerids = [services.player.initplayer("main", config.player.main), File "/home/swimmer/tmp/PyTone-2.3.1/src/services/player.py", line 64, in initplayer crossfadingduration=config.crossfadingduration, File "/home/swimmer/tmp/PyTone-2.3.1/src/services/players/internal.py", line 187, in __init__ self.audiodev = bufferedao.bufferedao(bufsize, self.SIZE, aodevice, rate=self.rate, options=aooptions) bufferedao.error: unknown driver_name
Ok, this means that alsa is not supported by your ao library. Do you link to the same version of that library as before?
/etc/pytonerc
[player.main] autoplay = true type = internal driver = alsa device = hw:0,0 bufsize = 100 crossfading = off
[player.secondary] autoplay = false type = internal driver = alsa device = hw:1,0 crossfading = off
Jörg
* Joerg Lehmann joerg@luga.de [2006-09-17 20:20]:
[...] With your patch I get the following error msg: Traceback (most recent call last): File "src/pytone.py", line 136, in ? playerids = [services.player.initplayer("main", config.player.main), File "/home/swimmer/tmp/PyTone-2.3.1/src/services/player.py", line 64, in initplayer crossfadingduration=config.crossfadingduration, File "/home/swimmer/tmp/PyTone-2.3.1/src/services/players/internal.py", line 187, in __init__ self.audiodev = bufferedao.bufferedao(bufsize, self.SIZE, aodevice, rate=self.rate, options=aooptions) bufferedao.error: unknown driver_name
Ok, this means that alsa is not supported by your ao library. Do you link to the same version of that library as before?
Hmpf - sometimes it's helpful if I could read :-(
/usr/share/doc/libao-0.8.6-r2/html/drivers.html ------------------------------------------------
alsa
Advanced Linux Sound Architecture. This driver borrows some code from Jaroslav Kysela's perex@suse.cz GPLed aplay that is included with the alsa-util distribution. It defaults to device 0 on card 0. Because of the way ALSA reads data, this driver packs sound from successive calls into a fixed size buffer (defaults to 32kB) and sends it to the card. Note that this driver only works with ALSA 0.5.x. You should use the alsa09 driver for the ALSA 0.9.x or 1.0.x series.
alsa09
Advanced Linux Sound Architecture, version 0.9.x and 1.0.x API. This is essentially the alsa driver modified to use the newer API.
Sorry that I wasted your time on that :(
Now I can go back to look why this pitch happens because this still remains :-/ Even if I switch the devices for secondary + main player the higher pitch comes out with the intel8x0 device?!?
Greetz Stefan -- Stefan Wimmer swimmer@xs4all.nl
On 17.09.06, Stefan Wimmer wrote:
Now I can go back to look why this pitch happens because this still remains :-/ Even if I switch the devices for secondary + main player the higher pitch comes out with the intel8x0 device?!?
I still don't understand why this doesn't happen with PyTone 2.3.0. The only change to the sound output is (as discussed before in this thread) the one related to the byte ordering.
Jörg
* Joerg Lehmann joerg@luga.de [2006-09-17 23:20]:
I still don't understand why this doesn't happen with PyTone 2.3.0. The only change to the sound output is (as discussed before in this thread) the one related to the byte ordering.
Me either - whatever I do (no patch, patch with format=4, patch with format=1) ... the pitch stays the same :-/
No idea what to do ...
Greetz Stefan
PS: Do you need some system information and if so which? The only thing I can say is that it happens on 2 Gentoo-machines (PC AMD64, Laptop i386) with different setups ... -- Stefan Wimmer swimmer@xs4all.nl
-
Joerg Lehmann -
Stefan Wimmer