• 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: Reliably finding the binary for an audio unit from a host
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reliably finding the binary for an audio unit from a host


  • Subject: Re: Reliably finding the binary for an audio unit from a host
  • From: Stefan Gretscher <email@hidden>
  • Date: Sun, 10 Jul 2011 19:04:06 +0200

Am 09.07.2011 um 10:45 schrieb tahome izwah:
> That's quite easy, actually.
Well, I wish it was, but the code you provided only identifies the bundle where the Cocoa view for a given Audio Unit lives.
This may or may not be the same binary that the AU itself lives in, no assumption can be made about this.
For example, when a plug-in supports both Audio Unit and VST API, it is a common design choice to create a bundle with
shared code for both versions that is installed into the Application Support folder. The Cocoa view may likely live there too.

Furthermore, your suggestion requires the Audio Unit to provide a Cocoa view, which it may opt not to do.
Carbon/Cocoa discussions aside, many Audio Units that ship as part of Mac OS X don't provide any view at all.

So thanks for the suggestion, but this is not reliable in the way I need it to be. My question still stands unanswered.

-Stefan


> Check out -showCocoaViewForAU in CAUHWindowController.m that comes
> with the CocoaAUHost project. It shows you how to get the view factory
> and the path to the bundle:
>
>        AudioUnitCocoaViewInfo *cocoaViewInfo =
> (AudioUnitCocoaViewInfo *)malloc(dataSize);
>        if(AudioUnitGetProperty(		inAU,
>                                        kAudioUnitProperty_CocoaUI,
>                                        kAudioUnitScope_Global,
>                                        0,
>                                        cocoaViewInfo,
>                                        &dataSize) == noErr) {
>                 NSURL 	 *CocoaViewBundlePath	=
> (NSURL*)cocoaViewInfo->mCocoaAUViewBundleLocation;
>        }
>
> HTH
> --th
>
> 2011/7/7 Stefan Gretscher:
>> Am 07.07.2011 um 08:59 schrieb tahome izwah:
>>> - (NSString *)bundlePath gets you the path to the bundle, once you have identified it.
>> Sure, but the question actually is how do I identify it in first place?
>>
>> -Stefan

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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: Reliably finding the binary for an audio unit from a host
      • From: tahome izwah <email@hidden>
References: 
 >Reliably finding the binary for an audio unit from a host (From: Stefan Gretscher <email@hidden>)
 >Re: Reliably finding the binary for an audio unit from a host (From: tahome izwah <email@hidden>)
 >Re: Reliably finding the binary for an audio unit from a host (From: Stefan Gretscher <email@hidden>)
 >Re: Reliably finding the binary for an audio unit from a host (From: tahome izwah <email@hidden>)

  • Prev by Date: Re: Disturbing input gain problem
  • Next by Date: Re: Reliably finding the binary for an audio unit from a host
  • Previous by thread: Re: Reliably finding the binary for an audio unit from a host
  • Next by thread: Re: Reliably finding the binary for an audio unit from a host
  • Index(es):
    • Date
    • Thread