sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Rob Robinett <rob@robinett.us>
To: "Måns Rullgård" <mans@mansr.com>
Cc: sox-users@lists.sourceforge.net
Subject: Re: sox won't write output file when run in spawned shell
Date: Mon, 5 Nov 2018 16:27:22 -0800	[thread overview]
Message-ID: <CADO0Qia+Yzui5XnUXE1YMW5Rbjh6p2bQKa=kjMOHTXmQQT+fQQ@mail.gmail.com> (raw)
In-Reply-To: <yw1xo9b3o6yd.fsf@mansr.com>


[-- Attachment #1.1: Type: text/plain, Size: 1228 bytes --]

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@mansr.com> wrote:

> Rob Robinett <rob@robinett.us> 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
>



-- 
Rob Robinett
AI6VN
rob@robinett.us
mobile: +1 650 218 8896

[-- Attachment #1.2: Type: text/html, Size: 2469 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



[-- Attachment #3: Type: text/plain, Size: 158 bytes --]

_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users

      reply	other threads:[~2018-11-06  0:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05  1:25 sox won't write output file when run in spawned shell Rob Robinett
2018-11-05 15:54 ` Måns Rullgård
2018-11-06  0:27   ` Rob Robinett [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.sourceforge.net/lists/listinfo/sox-users

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADO0Qia+Yzui5XnUXE1YMW5Rbjh6p2bQKa=kjMOHTXmQQT+fQQ@mail.gmail.com' \
    --to=sox-users@lists.sourceforge.net \
    --cc=mans@mansr.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/sox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).