• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Identifying matched ins and outs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Identifying matched ins and outs


  • Subject: Identifying matched ins and outs
  • From: Mark Gilbert <email@hidden>
  • Date: Sun, 12 Sep 2004 09:58:23 +0100

Folks,

Does anyone know if there is a way to identify inputs and outputs which 'match'.

I use the example of a MOTU 896HD.

It has lots of inputs, but the first 8 are 8 microphone inputs (it them goes onto ADAT and AES EBU i/ps)

On the output side, it also has 8 outputs which seem to correspond to the 8 mic inputs (they are next to them on the box). However in Core Audio, the 896's Main Stereo out are indexed as 1 and 2 in the stream descriptor.

So, if you flatten all the streams (as we do) into one family of 20 ins and however many outs, input and output 1 are NOT the 'same'

Our app tries to avoid the need for a complex cross point setup matrix, and in our playback/echo mode, we loop inputs to outputs by index.

So, recording input stream channels 1-8 then playing back through output stream channels 1-8 actually sends 1,2 to the Main outs and then 3-8 to outputs 1-6

Can anyone advise whether coreaudio has a solution to this conundrum, in the way of an information selector to 'identify' associated ins and outs ?

Cheers

Mark Gilbert.
--
email@hidden
Tel: +44 208 340 5677
fax: +44 870 055 7790
http://www.gallery.co.uk
http://www.mtools.info
http://www.metaflow.info
http://www.virtualvtr.com
http://www.libraryloader.com
New Product !!!
http://www.pictureready.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Next by Date: Re: Where is the AudioDeviceSetProperty() API Reference?
  • Next by thread: Re: Where is the AudioDeviceSetProperty() API Reference?
  • Index(es):
    • Date
    • Thread