• 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: Some more questions about sample rate notifications
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Some more questions about sample rate notifications


  • Subject: Re: Some more questions about sample rate notifications
  • From: Stéphane Letz <email@hidden>
  • Date: Mon, 14 Jan 2008 22:38:34 +0100


>It sounds to me like you are ending up with one very confused aggregate device. In fact, it also wouldn't surprise me if the instance of AUHAL you are >using thinks it is not actually attached to any devices any more after all the notifications have shaken out. You'd have to debug this more on your end to >know for sure why your instance of AUHAL is refusing to start.


Indeed, I am ending with a *very confused aggregate device* that "lost" it's output device!!
What am I supposed to do in this situation??


>So, what you are saying is that because some other app thinks it owns the hardware and is slamming settings that it is causing trouble for your app? >Really? I never would have guessed that something like that could happen =)

>This is exactly the sort of chaos that will ensue when apps start thinking they own the hardware settings and among the reasons we give the advice we >do about hardware settings (even to Apple apps like GarageBand). Repeat after me: you cannot control the format of the hardware absolutely. You >have to be able to adapt to what it gives you. There is no middle ground where you can slam the sample rate like you are trying to do.

OK, that is good to know. But if even Apple GarageBand does not do the *right thing* ??

Sorry but you do not anwer the basic question:

- an application (like Max/MSP or Ableton Live) or even the user using Audio Midi Setup is changing the SR of a *real* device used in an aggregate one.

- the aggregate device get confused: it's output part (for example) just disappear .

- the aggregate device then is not "duplex" anymore!!

- trying to setup back the current SR is not a good strategy OK, OK

- what I am I supposed to do in my application? (which is actually a server that cannot warn the user so easily). Just fail??

I understand that maybe a lot of applcations are not doing the right thing. The question is WHAT TO DO NOW?

Thanks again

Stephane Letz
_______________________________________________
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: Some more questions about sample rate notifications
      • From: Jeff Moore <email@hidden>
  • Prev by Date: Re: Some more questions about sample rate notifications
  • Next by Date: Re: Some more questions about sample rate notifications
  • Previous by thread: Re: Some more questions about sample rate notifications
  • Next by thread: Re: Some more questions about sample rate notifications
  • Index(es):
    • Date
    • Thread