Re: Simulate HIView using NSView for AudioUnits?
Re: Simulate HIView using NSView for AudioUnits?
- Subject: Re: Simulate HIView using NSView for AudioUnits?
- From: Stefan Gretscher <email@hidden>
- Date: Wed, 11 Dec 2013 01:34:01 +0100
Same here - rather limited success with HICocoaViewCreate(), you'll likely be adding quite a few workaround of your own to get decent results in a plug-in context.
For the time being, we're sticking with Cocoa UI exclusively for Audio Unit, VST3 and AAX, and maintain a Carbon UI only for legacy RTAS and VST2, both based on our own custom frameworks.
This setup keeps debugging and testing efforts within reasonable limits and works well for the vast majority of our users.
And eventually we'll just drop Carbon, VST2 and RTAS all together - looking forward to this day, but it may not come so soon...
Best,
Stefan
Am 10.12.2013 um 10:00 schrieb Blue Cat Audio Dev <email@hidden>:
> We did use HICocoaViewCreate in the early days of Leopard, but it ended up being not very reliable in many cases. The worst case is if the app has been developed with Cocoa but still requires a Carbon UI from the AU (or VST). In this case, many events are just not forwarded properly to your cocoa NSView (Cocoa->Carbon->Cocoa tunnelling does not work) - for example you get no mouse events at all. There are lots of bugs with this Carbon/Cocoa wrapper that Apple will never fix anyway.
>
> So I think we now have a mix of HICocoaViewCreate when it is supposed to work, and fall back to the good old child NSWindow trick when we know it will be an issue. Honestly, I think it's not worth the trouble using the HICocoaView. The NSWindow trick has its own problems, but it's much easier to handle than the other one :-).
>
> For Audio Units, most hosts now look first for a Cocoa View, so it's not a big deal, but for VST, not many hosts implement the NSView Cockos extension - same for plug-ins - sor you're stuck with Carbon/Cocoa hacks :-(
>
> Looking forward to seeing all hosts migrating to 64-bit in the (near?) future...!
>
> Guillaume Jeulin
> Blue Cat Audio
> www.bluecataudio.com
>
> Quoting Vojtěch Meluzín <email@hidden>:
>
>> Well, that's arrogant and useless indeed :D. But you are right, Apple
>> clearly made it obvious many times, that they don't care about developers
>> and software and their customers should be teenagers with iPhones :D.
>>
>> For the rest of us, who understand the need for other plugin interfaces
>> (for example because these are more relevant than AU), the same questions
>> :) :
>>
>> Anyway any experiences with HICocoaViewCreate? So far it seems like nobody
>> used it successfuly.
>>
>> Or any other reasonable solution - e.g. embedding a NSView inside WindowRef?
>>
>> Cheers!
>> Vojtech
>> www.meldaproduction.com
>>
>>
>> 2013/12/9 Paul Davis <email@hidden>
>>
>>>
>>>
>>>
>>> On Mon, Dec 9, 2013 at 1:11 AM, Vojtěch Meluzín <email@hidden
>>> > wrote:
>>>
>>>> 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.
>>>>
>>>
>>> Your question began "when programming AudioUnits" so I chose to ignore the
>>> next parenthetical clause "(or other audio plugin interfaces)" ... pardon
>>> my arrogance but I don't see any point in supporting VST on OS X. Apple
>>> have made it clear that they don't want it around, and plugin developers
>>> have done a fine job making sure that the overwhelming majority of their
>>> quality plugins are available in AU format. And for actual AU plugins,
>>> there is no serious reason to offer a Carbon GUI at this time.
>>>
>>> Anyway, I'll you plugin folk carry on with the more useful discussion :)
>>>
>>> --p
>>>
>>>
>>>
>>
>
>
>
>
> _______________________________________________
> 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
_______________________________________________
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