• 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: Problem with Alesis MultiMix 8 USB 2.0 and kAudioDevicePropertyStreamConfiguration
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with Alesis MultiMix 8 USB 2.0 and kAudioDevicePropertyStreamConfiguration


  • Subject: Re: Problem with Alesis MultiMix 8 USB 2.0 and kAudioDevicePropertyStreamConfiguration
  • From: email@hidden (Stefan Haller)
  • Date: Fri, 31 Aug 2007 21:41:59 +0200
  • Organization: Ableton

Jeff Moore <email@hidden> wrote:

> Changing the format of the device (and in fact most other changes to
> device state) is an asynchronous operation. Always has been. That's
> why the HAL has so many notifications. You can't assume that an
> operation has succeeded just because you didn't get an error when
> setting the property. Your app has to pay attention to the
> notifications in order to know when the change has actually taken
> effect.

We are aware of this and plan to clean up our code accordingly in a
future version.  This didn't have high priority for us so far, because
our current code used to work fine with every device we tested.

And in fact, in this particular case I don't believe that this is the
problem either, or at least that listening for notifications would help:
when we register a device property listener for '****', it is not called
when we change the sample rate of the MultiMix from our code.  We do get
notifications when we set the sample rate of other devices, and we do
get notifications when another process changes the sample rate of the
MultiMix; just not when we do it.

The same behaviour can be seen in HALLab: when another process changes
the sample rate of the MultiMix, HALLab gets notifications about this,
but when you change the sample rate in HALLab itself, it doesn't.  For
other devices, it gets notificications in either case.

If you have an exemplar of this device and could have a look at this, it
would be greatly appreciated.


--
Stefan Haller
Ableton
http://www.ableton.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

  • Follow-Ups:
    • Re: Problem with Alesis MultiMix 8 USB 2.0 and kAudioDevicePropertyStreamConfiguration
      • From: Jeff Moore <email@hidden>
References: 
 >Re: Problem with Alesis MultiMix 8 USB 2.0 and kAudioDevicePropertyStreamConfiguration (From: Jeff Moore <email@hidden>)

  • Prev by Date: How to Get Started with CoreAudio Programming
  • Next by Date: System-wide access to Firewire DV Audio in/out
  • Previous by thread: Re: Problem with Alesis MultiMix 8 USB 2.0 and kAudioDevicePropertyStreamConfiguration
  • Next by thread: Re: Problem with Alesis MultiMix 8 USB 2.0 and kAudioDevicePropertyStreamConfiguration
  • Index(es):
    • Date
    • Thread