sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: "Michael Cottle, (David)" <D.Cottle@utah.edu>
To: "sox-users@lists.sourceforge.net" <sox-users@lists.sourceforge.net>
Subject: Re: Set input channels
Date: Thu, 10 Feb 2022 12:59:36 +0000	[thread overview]
Message-ID: <C7943FAB-2919-49E2-85A5-4FEB26D2145E@umail.utah.edu> (raw)
In-Reply-To: <5047D403-69F8-40B7-9BDE-9F508A29C673@umail.utah.edu>


Oops. Never mind. I see you’ve already answered this. 

> On Feb 10, 2022, at 5:15 AM, Michael Cottle, (David) <D.Cottle@utah.edu> wrote:
> 
> Hi all,
> 
> Sorry if this is a simple question, but I’ve been looking through the manual and searching online for about an hour and can’t see an answer. How do you set the input channels from a multi-channel interface? 
> 
> Specifically: This is a music school where we record 6 rehearsal spaces all day. We currently are using Logic Pro to record CAF files, then split them up using SoX. We have two Focusrite preamps with 8 inputs connected to two work stations. (We started this about 10 years ago, and though there was some initial push back faculty and students love it.) It occurs to me we could just do this with SoX. I would need to set up four processes on each of our machines, each with a different output file and a different input from the interface, such as: 
> 
> rec hall1.caf <input 1-2>
> 
> rec hall2.caf <input 3-4>
> 
> etc. 
> 
> Any help would be appreciated. 
> 
> 
> 
> _______________________________________________
> Sox-users mailing list
> Sox-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sox-users


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

      reply	other threads:[~2022-02-10 13:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 12:15 Set input channels Michael Cottle, (David)
2022-02-10 12:59 ` Michael Cottle, (David) [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=C7943FAB-2919-49E2-85A5-4FEB26D2145E@umail.utah.edu \
    --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).