You were correct, There was no problem with sox, it was with my daemon.
thanks,
On Mon, Nov 5, 2018 at 7:54 AM, Måns Rullgård <mans@xxxxxxxxx> wrote:
Rob Robinett <rob@xxxxxxxxxxx> 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
_______________________________________________ Sox-users mailing list Sox-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/sox-users
