sox-users@lists.sourceforge.net unofficial mirror
 help / color / Atom feed
From: Måns Rullgård <mans@mansr.com>
To: Toru Yagi <yagitohru@yahoo.co.jp>
Cc: sox-users@lists.sourceforge.net
Subject: Re: sox can't encode to 16-bit
Date: Fri, 18 Jan 2019 21:44:35 +0000
Message-ID: <yw1xy37h1vzw.fsf@mansr.com> (raw)
In-Reply-To: <2995b4a4-8938-e015-1d1f-d55a018c8f23@yahoo.co.jp>

Toru Yagi <yagitohru@yahoo.co.jp> writes:

> On 1/18/19 9:54 PM, Måns Rullgård wrote:
>>> $ rec -c 2 -b 16 -r 48000 -p trim 0 20 |
>>> sox -V3 -c 2 -b 16 -r 48000 -p test.wav trim 0 10 : newfile : restart
>>>
>>> I want to record 16-bit wav files, but the files generated are 32-bit ones.
>>
>> Put the "-b 16" option immediately before the output file argument.  You
>> can also drop all the format options preceding the -p since the pipe
>> format already includes all information.
>
> $ rec -c 2 -r 48000 -b 16 -p trim 0 20 | sox -p test.wav trim 0 10 : newfile : restart
> rec WARN formats: sox can't encode to 16-bit
>

[...]

> Is the position of "-b 16" option okay?

No, it needs to go immediately before the "test.wav" argument.

>> That said, why don't you do the splitting directly with the rec command?
>> This should work:
>>
>> $ rec -c 2 -b 16 -r 48000 test.wav trim 0 10 : newfile : restart
>
> I understand it, but I have to save test.wav first.
> I just want to split into wav files while I record from the line input.

The command I suggested does exactly that.

-- 
Måns Rullgård


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

  reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 13:41 Toru Yagi
2019-01-18 12:54 ` Måns Rullgård
2019-01-18 14:47   ` Toru Yagi
2019-01-18 21:44     ` Måns Rullgård [this message]
2019-01-19 15:58       ` Toru Yagi

Reply instructions:

You may reply publically 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=yw1xy37h1vzw.fsf@mansr.com \
    --to=sox-users@lists.sourceforge.net \
    --cc=yagitohru@yahoo.co.jp \
    /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

sox-users@lists.sourceforge.net unofficial mirror

Archives are clonable: git clone --mirror https://public-inbox.org/sox-users

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.audio.sox
	nntp://ou63pmih66umazou.onion/inbox.comp.audio.sox
	nntp://news.gmane.org/gmane.comp.audio.sox

 note: .onion URLs require Tor: https://www.torproject.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox