• 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: handing audio dropouts with synchronized input and output
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: handing audio dropouts with synchronized input and output


  • Subject: Re: handing audio dropouts with synchronized input and output
  • From: Brian Willoughby <email@hidden>
  • Date: Wed, 08 Aug 2012 10:45:58 -0700


On Aug 8, 2012, at 05:43, Paul Davis wrote:
On Tue, Aug 7, 2012 at 7:05 PM, Brian Willoughby <email@hidden> wrote:

On Aug 7, 2012, at 12:51, Paul Davis wrote:
On Tue, Aug 7, 2012 at 3:44 PM, Jeff Smith <email@hidden> wrote:
>Why are you using 2 different callbacks for input and output?
>What exact part of the CoreAudio API are you using?
>
>(duplex applications can perfectly be managed with a single
>callback that receive input buffers and have to produce output
>buffers... this is usually simpler to develop)

In order to that, doesn't it have to be a single device (PPC) or an aggregate device (Intel)?

there are plenty of duplex devices on Intel OS X, just not the builtin audio device. almost all pro- and prosumer audio interfaces ship with a duplex driver. its still a mystery to my why apple refused to provide this for the builtin HDA interface.

Apple have not "refused" to provide this; it's a matter of the nature of USB Audio.


The builtin Intel HDA conformant chipset has absolutely nothing to do with USB. I'm not sure what you're thinking here.
Many built-in chip sets are USB. If you are sure that this one isn't, then I assume that the only reason Apple have handled it the way they did is because the clock sources are separate for input and output. If one single clock were used for both, then they'd actually be forced by the CoreAudio design specifications to provide a duplex driver.

Read the rest of my email - the part you didn't quote. The crux of this matter is CoreAudio and the way Apple have designed it from the start. USB is just one example of where the actual hardware behavior might not be what an application wants, and thus somewhere the missing pieces must be supplied (even if the pieces come from CoreAudio itself, such as AudioConverter AudioUnits).

Brian Willoughby
Sound Consulting

_______________________________________________
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: handing audio dropouts with synchronized input and output
      • From: Paul Davis <email@hidden>
References: 
 >Re: handing audio dropouts with synchronized input and output (From: Jeff Smith <email@hidden>)
 >Re: handing audio dropouts with synchronized input and output (From: Paul Davis <email@hidden>)
 >Re: handing audio dropouts with synchronized input and output (From: Brian Willoughby <email@hidden>)
 >Re: handing audio dropouts with synchronized input and output (From: Paul Davis <email@hidden>)

  • Prev by Date: Re: handing audio dropouts with synchronized input and output
  • Next by Date: Re: handing audio dropouts with synchronized input and output
  • Previous by thread: Re: handing audio dropouts with synchronized input and output
  • Next by thread: Re: handing audio dropouts with synchronized input and output
  • Index(es):
    • Date
    • Thread