Hi Jan, > Psi just calls an external program to play sounds. You can configure > the command to use in general/options/sound/player. that's interesting, but makes sense.
> Do you have a player manually configured? No, I don't have a player configured manually. The configuration is empty. > If the configuration is empty, psi autodetects if it should use "play" > or "aplay". (aplay in case /proc/asound exists, play otherwise). Yes, /proc/asound/ exists. It should use aplay then, assuming you're right. > Does the same problem occur if you play sounds by manually calling > 'aplay' (or 'play')? I'm testing it at the moment, but not so far. My problem with the situation: What _if_ aplay plays correctly all the time, but in psi it breaks the sound after a while? (At the moment, for me, it seems to be the case.) Best regards, Martin On Mon, Feb 11, 2013 at 04:39:57PM +0100, Jan Niehusmann wrote: > Psi just calls an external program to play sounds. You can configure the > command to use in general/options/sound/player. > > If the configuration is empty, psi autodetects if it should use "play" > or "aplay". (aplay in case /proc/asound exists, play otherwise). > > In any case, I don't see how the behaviour you describe could be a psi > bug. (Of course, I could be wrong.) > > Do you have a player manually configured? > > Does the same problem occur if you play sounds by manually calling > 'aplay' (or 'play')? > > Regards, > Jan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
