Anyone making "Sandbox-Safe" Audio Units?

DSP, Plugin and Host development discussion.
Post Reply New Topic
RELATED
PRODUCTS

Post

George wrote:Edit: Sean, security warning dialog still triggers if your AU is code signed but it's not sandbox ready.
Yes, and if your plug-in does not use the 10.7 APIs, it will be flagged as "not sandbox ready" anyway (got the info straight from Apple).

Post

Just checked and as long as you validate lower security settings, it works fine.
I was quite afraid it was not possible at all.
Olivier Tristan
Developer - UVI Team
http://www.uvi.net

Post

Blue Cat Audio wrote:
George wrote:Edit: Sean, security warning dialog still triggers if your AU is code signed but it's not sandbox ready.
Yes, and if your plug-in does not use the 10.7 APIs, it will be flagged as "not sandbox ready" anyway (got the info straight from Apple).
I assume it forces you to use XCode 4 then :?

Post

George wrote:
Blue Cat Audio wrote:
George wrote:Edit: Sean, security warning dialog still triggers if your AU is code signed but it's not sandbox ready.
Yes, and if your plug-in does not use the 10.7 APIs, it will be flagged as "not sandbox ready" anyway (got the info straight from Apple).
I assume it forces you to use XCode 4 then :?
That would suck...

Post

I assume it forces you to use XCode 4 then
Probably. Not a big deal though... Are you guys aware that XCode 5 has now been released? :-)

Post

It is a big deal in some cases. Fortunately sandbox bypass is easy enough for the end user right now.

Post

Blue Cat Audio wrote:
I assume it forces you to use XCode 4 then
Probably. Not a big deal though... Are you guys aware that XCode 5 has now been released? :-)
Honestly if they force everyone to upgrade their OS version that would be great.
I would be happy to only support min 10.7 and use Xcode 5
It's great compare to 3.2.5 and we would be able to use C++11 but we still need to use it in order to support 10.5
Olivier Tristan
Developer - UVI Team
http://www.uvi.net

Post

It is possible to use XCode 4 with the 10.5 SDK if you do not need PPC support (haven't checked with XCode 5 yet but I guess it should work).

I agree it would be great to get rid of older versions! However, we still have a very large Snow Leopard user base... :-(

Post

Further experimentation report: the plug-in can _not_ see the user Library/Application Support.

HOWEVER!!!!

It _can_ see the root Library/Application Support. This may make things very easy for some of us. Use this info at your own risk.

Post

Blue Cat Audio wrote:It is possible to use XCode 4 with the 10.5 SDK if you do not need PPC support (haven't checked with XCode 5 yet but I guess it should work).

I agree it would be great to get rid of older versions! However, we still have a very large Snow Leopard user base... :-(
Question is, why do they keep snow leopard.
Is this because of Mavericks requirements or some other reason ?
Olivier Tristan
Developer - UVI Team
http://www.uvi.net

Post

otristan wrote:
Blue Cat Audio wrote:It is possible to use XCode 4 with the 10.5 SDK if you do not need PPC support (haven't checked with XCode 5 yet but I guess it should work).

I agree it would be great to get rid of older versions! However, we still have a very large Snow Leopard user base... :-(
Question is, why do they keep snow leopard.
Is this because of Mavericks requirements or some other reason ?
It's because Snow Leopard WORKS for these clients, for whatever reason.

Most people I know that work with audio for a living would prefer to work with Snow Leopard, as it is very stable on their machines. Plus, many DAWs don't perform well on the cutting edge of Mac OS upgrades (Pro Tools in particular).

Sean Costello

Post

For some reason, Snow Leopard seems to be the system people tend to prefer (maybe because it's the last non-full-64-bit OS?). Pro Tools runs perfectly on 10.7 or 10.8, but I can understand that people just don't want to bother upgrading if they do not absolutely need it: it's just a waste of time and a risk to break things...

Post

Crandall1 wrote:Further experimentation report: the plug-in can _not_ see the user Library/Application Support.
Our plug-in Corona can access ~/Library/Application Support/

Post

Be aware that you might be able to access some specific paths because the app may have "bookmarked" them (if you chose a path, opened a file...). It may not be reliable in all situations...

Post

Ok, thanks.

Post Reply

Return to “DSP and Plugin Development”