Hello Jan,
thank you for the hint.
It is indeed a concurrency problem.
I got the problem once again and had a look at my process list.
There were two instances of aplay running, blocking the sounddevice.
Sending them SIGTERM solved the problem / freed it again.
Remains the question why sometimes
Hi Martin,
On Sat, Feb 02, 2013 at 02:22:07PM +0100, Martin Teufel wrote:
After some sound-notifications were played, the sounddevice somehow
breaks. I.e. no more sounds are played (of course psi tries to) and I
can't output any sound/music at all (e.g. with mplayer or something).
Psi just
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
On Mon, Feb 11, 2013 at 05:23:01PM +0100, Martin Teufel wrote:
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.)
Maybe some kind of concurrency problem? Psi may call aplay
Package: psi
Version: 0.14-2
Severity: important
Tags: upstream
After some sound-notifications were played, the sounddevice somehow
breaks. I.e. no more sounds are played (of course psi tries to) and I
can't output any sound/music at all (e.g. with mplayer or something).
Please feel free to mail
5 matches
Mail list logo
