• 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: Simulate HIView using NSView for AudioUnits?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Simulate HIView using NSView for AudioUnits?


  • Subject: Re: Simulate HIView using NSView for AudioUnits?
  • From: Christopher Johnson <email@hidden>
  • Date: Tue, 10 Dec 2013 17:32:38 -0500

Brian Willoughby <email@hidden> wrote:
> At least for AudioUnits, you're not actually required to provide any
> UI at all. My free AUs are all without UI, and the AU spec allows the
> host to create the UI on the fly. This works great in Logic, Ableton
> Live, etc.
>
> In the case where you provide a Cocoa view, but the host only
> supports Carbon, there's still the option for the host to build a UI
> from the AU parameter descriptions. Granted, there are a rare few
> types of plugs that can't be used effectively without a custom UI,
> but not very many at all.
>
> Brian Willoughby
> Sound Consulting

	Sure. All of my commercial plugs as well as my freebies are without UI, and it's been a huge help in weathering host changes.

	There are some circumstances where it gets awkward: for instance, the video editor ScreenFlow allows Audio Units to be used in processing, but doesn't always display control values properly. However, it won't open Audio Units with GUIs at all, and mine remain completely functional. (So do the Sound Consulting plugs, other than Bit Meter)

	My concerns lately haven't been GUI-related, they have to do with Mavericks. Is anyone working with sandbox-safe code (as I think mine is, since I don't read or write files in any way and let the host manage any presets) and setting that resource flag that tells the OS that the plugin's safe?

	Disregard things like installers (I don't use 'em, though I understand there may be issues with the .dmg files I do use?) and talking just about the plugin itself, can I future-proof my stuff on my existing build platform by adding some resources to my projects?

	I shudder to ask this as the last time Apple needed such a thing, I had to rebuild about 150 past and present plugins to run 64-bit. But then when the guy from Apple called me up to ask how I was doing, he was pretty thrilled to hear Airwindows had been 64-bit for a year. I knew in my bones they were going to ditch 32-bit in the next Logic, I just didn't know when.

	I think we're looking at sandbox/security troubles and I might be able to get through unscathed, so I've got to ask :)

	Chris Johnson
	airwindows
 _______________________________________________
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


  • Prev by Date: Debug audio unit with xcode 5
  • Next by Date: Re: Simulate HIView using NSView for AudioUnits?
  • Previous by thread: Re: Simulate HIView using NSView for AudioUnits?
  • Next by thread: Only one module for 2 Mac plugin bundles (AU, VST) gets loaded
  • Index(es):
    • Date
    • Thread