• 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: Audio and MIDI Application Crashes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Audio and MIDI Application Crashes


  • Subject: Re: Audio and MIDI Application Crashes
  • From: Jeff Moore <email@hidden>
  • Date: Thu, 28 Jul 2005 12:07:23 -0700

As with anything crash, it helps a great deal to include the backtrace of all the threads in the process that crashed. It also doesn't hurt to file a bug about it.

At any rate, making your IOAudioEngine instance go away is equivalent to disconnecting the device to the HAL. This pretty much means that when the sample rate changes, any existing app is going to lose it's connection to your device due to the AudioDeviceID changing. This is probably a very bad and unpredictable user experience since some apps (namely the ones that don't track the default device) will recover using some other device (likely the built-in hardware).

I don't really know anything about your hardware, but I do know that this approach to your driver is really not a good one and is going to lead to trouble with your users. Can you elaborate on why you are doing it this way? Why can't you just re-use the existing IOAudioEngine instance?

Also, can you clarify whether or not you expect the input streams and the output streams to run and different sample rates? It seems that this may be the case from what you've said so far, but the IOAudio family doesn't work if they are different so maybe I'm misunderstanding?

On Jul 28, 2005, at 10:55 AM, BlazeAudio Developer wrote:

We have a case where Audio and MIDI Application crashes when used with our driver.

This happens when the sampling rate is changed. Our driver actually destroys the audio engine and creates a new one when the SR is changed.

The intersting part is, that if the SR for the output streams is changed, things work okay. But if the SR for the input stream is changed, A&M crashes.

Any idea on what might be causing this, or how we can prevent it from happening.

Every other application that we have used so far does not exhibit any problems with our approach of changing sampling rates.

--

Jeff Moore
Core Audio
Apple


_______________________________________________ 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
References: 
 >Data Source Confusion (From: Dominic Feira <email@hidden>)
 >Audio and MIDI Application Crashes (From: BlazeAudio Developer <email@hidden>)

  • Prev by Date: Re: Data Source Confusion
  • Next by Date: QT Instruments from CoreMidi
  • Previous by thread: Audio and MIDI Application Crashes
  • Next by thread: Re: Data Source Confusion
  • Index(es):
    • Date
    • Thread