From: "Måns Rullgård" <mans@mansr.com>
To: Jeff Learman <jjlearman@gmail.com>
Cc: sox-users@lists.sourceforge.net
Subject: Re: Piping output of sox to a file produces empty text
Date: Mon, 27 Jul 2020 20:42:46 +0100 [thread overview]
Message-ID: <yw1xa6zk218p.fsf@mansr.com> (raw)
In-Reply-To: <CAGyjer6VRPtK4vWhH+oKhrhuyaoD=qF+jas4-+opn+oZf07ZJQ@mail.gmail.com> (Jeff Learman's message of "Mon, 27 Jul 2020 15:02:14 -0400")
Jeff Learman <jjlearman@gmail.com> writes:
>> On Mon, 27 Jul 2020 at 14:49, Ariel Elkin <ariel@arivibes.com> wrote:
>>
>>> Hello,
>>>
>>> I’d like to save the output of the stat command to a file.
>>>
>>> When I call
>>> sox file.mp3 -n stat
>>>
>>> The output is correctly displayed. But If I then do
>>> sox file.mp3 -n stat > file.txt
>>>
>>> file.txt is empty.
>>>
>>> Why?
>
> I didn't check, but perhaps sox text output is going to stderr. For
> Linux/UNIX, using many shells (sh, ksh, tsh, zsh, bash, but not csh),
> redirect stderr this way:
>
> sox file.mp3 -n stat > file.txt 2>&1
Per the man page, "The information is output to the `standard error'
(stderr) stream."
--
Måns Rullgård
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
prev parent reply other threads:[~2020-07-27 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 16:17 Piping output of sox to a file produces empty text Ariel Elkin
2020-07-27 19:02 ` Jeff Learman
2020-07-27 19:04 ` Jeff Learman
2020-07-27 19:42 ` Måns Rullgård [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=yw1xa6zk218p.fsf@mansr.com \
--to=sox-users@lists.sourceforge.net \
--cc=jjlearman@gmail.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).