• 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
Re: Hardware Monitoring (Was: I/O Latency (Was: Layman with a mission))
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Hardware Monitoring (Was: I/O Latency (Was: Layman with a mission))


  • Subject: Re: Hardware Monitoring (Was: I/O Latency (Was: Layman with a mission))
  • From: John Pitcairn <email@hidden>
  • Date: Fri, 15 Oct 2004 10:50:49 +1300

From: Jeff Moore <email@hidden>
Hardware monitoring has been supported since the very first release of
Mac OS X (actually it was supported even before that) and was improved
greatly in 10.3 with the addition of more kinds of controls the driver
can provide that modify the monitor signal path.

Thanks Jeff. Can you clarify - does this allow for full matrix mixing under the control of the (hypothetical) app if the hardware/driver supports a full matrix mixer, or is it restricted to some kind of simpler many-to-two, or direct one-to-one input->output scheme (the latter being worst-case, a la the old ASIO Direct Monitoring scheme)?


Apps and drivers have yet to catch up with what the system supports in
this area.

Indeed - a chicken and egg situation it seems. At least the next time someone points the finger at CoreAudio, I'll have some information to refute that.


--
John Pitcairn

--------------------------------------------------------------------------
    Revolver Design  |  Opus Locus  |  Auckland, New Zealand
--------------------------------------------------------------------------
_______________________________________________
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


  • Follow-Ups:
    • Re: Hardware Monitoring (Was: I/O Latency (Was: Layman with a mission))
      • From: William Stewart <email@hidden>
    • Re: Hardware Monitoring (Was: I/O Latency (Was: Layman with a mission))
      • From: Jeff Moore <email@hidden>
  • Prev by Date: Re: Find out all IOProcs attached to an Audio device in a Process
  • Next by Date: Re: Hardware Monitoring (Was: I/O Latency (Was: Layman with a mission))
  • Previous by thread: Re: AUGraphGetCPULoad() info?
  • Next by thread: Re: Hardware Monitoring (Was: I/O Latency (Was: Layman with a mission))
  • Index(es):
    • Date
    • Thread