sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: "Måns Rullgård" <mans@mansr.com>
To: Noah Essl <arche1@gmx.at>
Cc: sox-users@lists.sourceforge.net
Subject: Re: playing more than 2 sounds with synth option
Date: Mon, 10 Aug 2020 18:36:32 +0100	[thread overview]
Message-ID: <yw1x364uwggv.fsf@mansr.com> (raw)
In-Reply-To: <301f169b-bcd4-0c13-fcf9-9780bd30d8b7@gmx.at> (Noah Essl's message of "Mon, 10 Aug 2020 17:57:17 +0200")

Noah Essl <arche1@gmx.at> writes:

> Hi!
>
> I am playing 2 frequencies like this:
>> play -qn synth $a_number_variable sine $sound_1 sine $sound_2 fade h
> $some $random $numbers
>
> and I am trying to play even more sounds like:
>> play -qn synth $a_number_variable sine $sound_1 sine $sound_2 sine
> $sound_3 sine $sound_4
> or like:
>> play -qn synth $a_number_variable sine $sound_1 sine $sound_2 synth
> sine $sound_3 sine $sound_4
>
> but that doesn't work. How would I do it to play 4 frequencies parallel
> with the same command? Is there no support for that and if so, why limit
> it to 2?
>
> Thanks in advance for any help!

Your commands create a new channel for each tone.  If you want to mix
them you can do that in a few ways.  One is like this:

$ play -n synth 10 sine 1k synth sine mix 2k synth sine mix 3k

Another way:

$ play -n synth 10 sine 1k sine 2k sine 3k remix -

If that's not what you're looking for, you'll have to describe in more
detail what you're trying to achieve.

-- 
Måns Rullgård


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

  reply	other threads:[~2020-08-10 17:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 15:57 playing more than 2 sounds with synth option Noah Essl
2020-08-10 17:36 ` Måns Rullgård [this message]
2020-08-11 12:34   ` Noah Essl
2020-08-11 14:02     ` Måns Rullgård
2020-08-10 19:03 ` Jan Stary

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=yw1x364uwggv.fsf@mansr.com \
    --to=sox-users@lists.sourceforge.net \
    --cc=arche1@gmx.at \
    /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).