|
From: Jan S. <ha...@st...> - 2010-05-28 09:23:06
|
On May 28 19:09:01, pj...@pj... wrote:
> Pascal Giard wrote:
>
> > FWIW, `play -q backing.wav &` works as expected here i.e. does play.
>
> Great :-) ; I'll assume that (perhaps because it was noticed by
> Rob 26jul2009 ?) it got into the sox TODO list and was fixed.
I don't think so. Running 'play -q file.wav &' works as expected
for me using 14.2.0 here, too; it's not something that 'got fixed'.
Show me the ps(1) output that shows the play/sox process as stopped
after you start it like that.
> Yes, the xterm is started with the command (I abbreviate the font...)
> exec xterm -geometry 80x36+2-0 -bg 'old lace' +sb -e bash &
>
> > What is your $SHELL? (echo $SHELL)
>
> /bin/bash
>
> > Have you tried starting some other processes like this?
>
> Of course, all the time.
I still think this is a shell problem and is not related to sox.
Anyway, is the 'play' command you are using really sox's play?
('play --version')
Can you ktrace/systrace/whatever the shell process to see
where exactly did the STOP signal come from? Because them
there processes don't just STOP themselvses ...
|