sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: "Michael Dunston" <mdunston@music.vt.edu>
To: sox-users@lists.sourceforge.net
Subject: recording from firewire interfaces on MacOS?
Date: Sun, 19 Nov 2017 21:00:25 -0500	[thread overview]
Message-ID: <F68246EB-0AA5-4D7E-8583-165BF653B287@music.vt.edu> (raw)


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

Does anyone have any experience using SoX to record from firewire 
interfaces on MacOS X?  Searching the archives for “firewire” 
resulted in one post which mentioned a similar issue to what I am 
experiencing, however this post was from 2011 and there didn’t seem to 
be any resolution to the problem.  In this case I have a Mobile I/O 2882 
set as the system audio interface on a MacOS 10.12.6 system with 
sox-14.4.2, and although the interface has 18 inputs (with two channels 
enabled for sending audio to DAWs via coreaudio, which do show up in 
both Logic and ProTools), SoX only appears to see it as a 1-channel 
interface and at 32 bits (instead of 24) as other hosts see it:

	Input File     : 'default' (coreaudio)
	Channels       : 1
	Sample Rate    : 44100
	Precision      : 32-bit
	Sample Encoding: 32-bit Signed Integer PCM

And attempting to record a stereo file from this results in an error of 
“WARN formats: can't set 2 channels; using 1” and a file only 
containing clicks and silence.  I’ve tried setting the firewire 
interface as the system-default input device in the system preferences 
as well as naming it specifically using the “ −t coreaudio “ 
option (as found in Output and Input tabs of the System 
Preferences->Sound menu), but not yet had any success.  Based on the 
list archives it doesn’t seem like firewire interfaces are commonly 
used with SoX, but any suggestions would be appreciated.  Thanks in 
advance for any advice on where to look next.

[-- Attachment #1.2: Type: text/html, Size: 2085 bytes --]

[-- Attachment #2: Type: text/plain, Size: 202 bytes --]

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

[-- 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:[~2017-11-20  2:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=F68246EB-0AA5-4D7E-8583-165BF653B287@music.vt.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).