From: "Måns Rullgård" <mans@mansr.com>
To: "Dr. Thomas Tensi" <t.tensi@gmx.de>
Cc: sox-users@lists.sourceforge.net
Subject: Re: Reason for sox mix restriction to two or more input files?
Date: Mon, 12 Aug 2019 10:29:23 +0100 [thread overview]
Message-ID: <yw1xtvamd958.fsf@mansr.com> (raw)
In-Reply-To: <97a81d26-ff35-2af7-3872-af34ae20af6a@gmx.de> (Thomas Tensi's message of "Sun, 11 Aug 2019 21:22:28 +0200")
"Dr. Thomas Tensi" <t.tensi@gmx.de> writes:
> Hello Måns,
>
> thanks for your effort!
>
> I have the same opinion: mixing should be possible for
> a single input.
>
> Nevertheless be careful with your patch: one has to
> check whether other operations (like multiply) are
> still meaningful for a single input. I think so,
> but I have not looked deeply into that.
I tested the merge, mix, and multiply options with a single input, and
it came out unchanged. Seems like reasonable behaviour to me.
--
Måns Rullgård
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
next prev parent reply other threads:[~2019-08-12 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-11 19:22 Reason for sox mix restriction to two or more input files? Dr. Thomas Tensi
2019-08-12 9:29 ` Måns Rullgård [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-09 19:42 Dr. Thomas Tensi
2019-08-10 9:52 ` Jeremy Nicoll - ml sox users
2019-08-10 12:06 ` Dr. Thomas Tensi
2019-08-10 17:28 ` 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=yw1xtvamd958.fsf@mansr.com \
--to=sox-users@lists.sourceforge.net \
--cc=t.tensi@gmx.de \
/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).