sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Jeff Learman <jjlearman@gmail.com>
To: sox-users@lists.sourceforge.net
Subject: Re: Piping output of sox to a file produces empty text
Date: Mon, 27 Jul 2020 15:02:14 -0400	[thread overview]
Message-ID: <CAGyjer6VRPtK4vWhH+oKhrhuyaoD=qF+jas4-+opn+oZf07ZJQ@mail.gmail.com> (raw)
In-Reply-To: <1FEAF281-437D-429D-9859-BE883905CB8A@arivibes.com>


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

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

Jeff

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?
>
> Thanks
>
> Ariel
>
> _______________________________________________
> Sox-users mailing list
> Sox-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sox-users
>

[-- Attachment #1.2: Type: text/html, Size: 1314 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:[~2020-07-27 19:02 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 [this message]
2020-07-27 19:04   ` Jeff Learman
2020-07-27 19:42   ` Måns Rullgård

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='CAGyjer6VRPtK4vWhH+oKhrhuyaoD=qF+jas4-+opn+oZf07ZJQ@mail.gmail.com' \
    --to=sox-users@lists.sourceforge.net \
    /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).