Apple

It isn't correct to say that VST does not allow Cocoa interfaces in 32-bit.

When using VSTGUI 3.6 your interface will be implemented as Cocoa if you are targetting OSX 10.5 or better, or you can manually define MAC_COCOA in your prefix header. Take a look at vstgui.h

#ifndef MAC_COCOA

#define MAC_COCOA (MAC_OS_X_VERSION_MIN_REQUIRED >= MAC_OS_X_VERSION_10_5)

Last time I checked, JUCE used Cocoa windows on all Mac audio plugin platforms as well. Non-composited windows? haven't had to worry about those since the days of Protools 7.

Kind regards
Dave

From: coreaudio-api-bounces+dave=email@hidden [mailto:coreaudio-api-bounces+dave=email@hidden] On Behalf Of Vojtech Meluzín
Sent: Monday, December 09, 2013 6:11 AM
To: Paul Davis
Cc: coreaudio-api
Subject: Re: Simulate HIView using NSView for AudioUnits?

Paul, I'm afraid you do have to. Your host may be able to handle Cocoa, but others may not and VST doesn't even allow it in 32-bits. So you really have to use the Carbon even if there would be just a few remaining hosts asking for it. After all many customers still use some ancient versions or both OS and host. I still get questions about supporting Tiger... Unfortunatelly Apple made compatibility such a pain...

Cheers!
Vojtech
www.meldaproduction.com

2013/12/7 Paul Davis <email@hidden>

On Sat, Dec 7, 2013 at 10:38 AM, Vojtěch Meluzín <email@hidden> wrote:

Hi,

when programming AudioUnits (or other audio plugin interfaces) one has to implement 3 GUI interfaces - embedded, composited and cocoa.

This language is wierd. You do not *have* to do this. You can choose which to support. Given that Carbon has been deprecated for over 10 years and is finally vanishing, one choice is to just focus on Cocoa.

I am a host author and our life is made MUCH easier when a plugin offers a cocoa GUI. Using the Carbon ones in a Cocoa-based host requires some really awful hacks.

--p