• 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
Multiple Instances, tied to one clock
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Multiple Instances, tied to one clock


  • Subject: Multiple Instances, tied to one clock
  • From: Devendra Parakh <email@hidden>
  • Date: Wed, 16 Oct 2002 16:15:29 -0700

Hi,

We are writing drivers for PCI audio adapters which can have their clocks tied to a single source.

Essetially, one can be made a master, and the rest slaves.

For our Windows and OS9 ASIO drivers, we present all the channels of the card as belonging to one "device".

This way, the applications don't have to do anything special to be able to treat the multiple cards as one device.

However, I'm not sure what the best approach would be on OS-X.

Should we be creating a single Audio-Engine which presents channels from all the (tied together) PCI cards?

Or can we just create multiple engines, and let applications use more than one devices simultaneously (without really knowing that the clocks are tied)?

I'm sure I'm not the first one to run into this problem!

Also, what's the best way for the driver to tell Core-Audio HAL that it's running on an external clock (and so the sampling rate might not be what CoreAudio tells the driver to use).

Thanks.

Devendra.
Devendra Parakh
Singing Electrons, Inc.
http://www.singingelectrons.com
425-889-2478
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: AU - more host callbacks - host name and version (From: Chris Rogers <email@hidden>)

  • Prev by Date: Re: Crashing when loading 3rd party AU
  • Next by Date: Re: 3rd party AU vendor info
  • Previous by thread: Re: AU - more host callbacks - host name and version
  • Next by thread: iMic rate change fails at first
  • Index(es):
    • Date
    • Thread