• 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: AudioHardwarePlugIn vs AudioServerPlugIn
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AudioHardwarePlugIn vs AudioServerPlugIn


  • Subject: Re: AudioHardwarePlugIn vs AudioServerPlugIn
  • From: Jeff Moore <email@hidden>
  • Date: Mon, 12 Aug 2013 13:33:48 -0700

On Aug 12, 2013, at 1:26 PM, Bertrand Van Kempen <email@hidden> wrote:

> Hi Jeff,
>
> Now, it is clear; if coreaudiod likes my plugin then all applications will like it too.
> Our QA will love that ;-)

It does tend to simplify things a bit.


> Now, for debugging, I suppose I have to restart coreaudiod each time I modify the plugin or is there another way to ask coreaudiod to update/restart the plugin?

Coreaudiod is a proper launchd-managed daemon. So, when you need coreaudiod to reload your driver, the easiest thing to do is to just kill it: “sudo killall coreaudiod”. Launchd will take care of relaunching the daemon for you.


> Best regards,
>
> Bertrand van Kempen
>
> -----Original Message-----
> From: coreaudio-api-bounces+bvankempen=email@hidden on behalf of Jeff Moore
> Sent: Mon 8/12/2013 20:32
> To: email@hidden; API
> Subject: Re: AudioHardwarePlugIn vs AudioServerPlugIn
>
> Just to be clear: it does't matter whether Logic or MainStage are sandboxed or not as far as an AudioServerPlugIn is concerned. The reason why is that AudioServerPlugIns are only ever loaded by coreaudiod. They are never loaded into the app's process. So, the only sandbox that matters with respect to proper functioning of the AudioServerPlugIn is coreaudiod's. Further, the AudioServerPlugIn API has a mechanism that allows the plugin to tell the system about the resources it needs so that coreaudiod can adjust its sandbox accordingly.
>
>
> -
>
> Jeff Moore
> Core Audio
> Apple
>
>
>
>
>
> On Aug 12, 2013, at 11:24 AM, Markus Fritze <email@hidden> wrote:
>
>> On Aug 12, 2013, at 8:28, Bertrand Van Kempen <email@hidden> wrote:
>>
>>> [Bertrand] Is Logic Pro X allow AudioServerPlugin with custom IOKit driver?
>>
>> Yes, because Logic Pro X and MainStage 3 are not sandboxed. That said, I would expect that this is going change at some point (including future releases of GarageBand), so it makes sense to avoid sandbox issues as soon as possible. You probably want to avoid issues like some AudioUnit developers who didn't update their plugins to 64-bit within the past 3-4 years and are now struggling to catch up.
>>
>>
>> Best regards,
>> Markus Fritze
>> Apple Inc. <http://www.apple.com>
>> Sr Software Engineering Manager - Audio/Music Applications
>>
>


 _______________________________________________
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: 
 >AudioHardwarePlugIn vs AudioServerPlugIn (From: Bertrand Van Kempen <email@hidden>)
 >Re: AudioHardwarePlugIn vs AudioServerPlugIn (From: Jeff Moore <email@hidden>)
 >RE : AudioHardwarePlugIn vs AudioServerPlugIn (From: Bertrand Van Kempen <email@hidden>)
 >Re: AudioHardwarePlugIn vs AudioServerPlugIn (From: Markus Fritze <email@hidden>)
 >Re: AudioHardwarePlugIn vs AudioServerPlugIn (From: Jeff Moore <email@hidden>)
 >RE: AudioHardwarePlugIn vs AudioServerPlugIn (From: Bertrand Van Kempen <email@hidden>)

  • Prev by Date: RE: AudioHardwarePlugIn vs AudioServerPlugIn
  • Next by Date: Re: AudioUnit : Audio playback too fast and too high on iOS 7
  • Previous by thread: RE: AudioHardwarePlugIn vs AudioServerPlugIn
  • Next by thread: Audio Units fail validation, result: -50.0 & sudden problems with AUCarbonViewBase
  • Index(es):
    • Date
    • Thread