• 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
kAudioUnitProperty_AUHostIdentifier
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

kAudioUnitProperty_AUHostIdentifier


  • Subject: kAudioUnitProperty_AUHostIdentifier
  • From: Nathaniel Perez <email@hidden>
  • Date: Wed, 30 Apr 2014 10:29:45 -0400
  • Acceptlanguage: en-US
  • Thread-topic: kAudioUnitProperty_AUHostIdentifier

Hi,

We have a crash in an audio-unit plug-in failing Auval validation.

After some investigation we have found out that there is a need to know if the plug-in is in Auval 'test' mode in order to perform tests such as Set Bypass immediately, and not run them in a low priority thread as we do when running under AU hosts.

Do you know of a way to identify if an AudioUnit is running in 'test' mode?
If not, is it possible to know we are running in Auval?

We tried  AudioUnitGetProperty
with kAudioUnitProperty_AUHostIdentifier
but it appears not to work at all..

Thanks,
Nathaniel

 _______________________________________________
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: kAudioUnitProperty_AUHostIdentifier
      • From: Kyle Sluder <email@hidden>
  • Prev by Date: Re: No sound output with userland driver, multiple output device and audio units. Probably a bug in core audio.
  • Next by Date: Re: kAudioUnitProperty_AUHostIdentifier
  • Previous by thread: Re: No sound output with userland driver, multiple output device and audio units. Probably a bug in core audio.
  • Next by thread: Re: kAudioUnitProperty_AUHostIdentifier
  • Index(es):
    • Date
    • Thread