Re: sox won't write output file when run in spawned shell
Måns Rullgård <[email protected]>
| Newsgroups | gmane.comp.audio.sox |
|---|---|
| Message-ID | <[email protected]> |
Rob Robinett <[email protected]> writes: > Hi, > > I am trying to us sox as part of an RF signal processing daemon on a > Raspberry Pi 3B Stretch. When I execute sox from a terminal command line > the output file is created, but when I spawn the command it runs but > doesn't create the output file: > > runs and creates '0.wav': sox -r 32k -t raw -e s -b 16 -c 1 > 0.raw -r 12k 0.wav > runs but doesn't create '0.wav': sox -r 32k -t raw -e s -b 16 -c 1 0.raw > -r 12k 0.wav > redirecting stdin/out/err and it still doesn't create '0.wav': sox -r > 32k -t raw -e s -b 16 -c 1 0.raw -r 12k 0.wav &> out.log < /dev/null & > > the sox output seems the same in all cases and echo $? print 0 == success. > What am I missing? The daemon is probably running in a different directory than you're expecting. Use full path names in the sox command and see if that helps. -- Måns Rullgård