32bit carbon GUIs are less efficient, since the whole GUI is continuously redrawn. Some carbon graphics functions were removed from 10.7 onwards which are used by iplug
So we are stuck with 10.6..? Does graphics depends on DAW where plugin is inserted?
I think that I somewhere read that some DAWs are using cocoa and some are using carbon graphics...
What exactly doesn't work with 10.7 SDK? I want to test something.
I have placed carbon framework from 10.5 SDK into a 10.9 SDK and I was able to build the example plugin correctly.
Maybe with this hack we could somehow use c++11 inside XCode...
32bit carbon GUIs are less efficient, since the whole GUI is continuously redrawn.
I have tested this and it seams that GUI is not continuously redrawn in Reaper64, Live 8, Live 9 when I load 32bit VST in them (10.9 SDK, 10.7 deployment target). Actually, Draw() is not called consistently. Also, CPU usage is very similar to 64bit versions...
So, am I missing something?
Reaper supports the Cockos VST extensions (naturally) . One of those allows 32bit vst2 plugins on mac to use a Cocoa GUI rather than a Carbon GUI. By default the VST2.4 sdk doesn't have cocoa support for 32bit. Ableton Live 8.4+ also supports this extension (probably also some other hosts).
10.7 or newer SDKs question
Linear Mode
