AudioUnits, sandbox and preferences
AudioUnits, sandbox and preferences
- Subject: AudioUnits, sandbox and preferences
- From: Pavol Markovic <email@hidden>
- Date: Tue, 26 Nov 2013 15:41:13 +0100
Hello,
this might not be the most appropriate forum to ask in, however this problem covers only very specific area of interest and seems to be omitted in general guides.
We have been using CFPreferencesCopyValue/CFPreferencesSetValue mechanism for setting user preferences (stored in ~/Library/Preferences folder) which could be shared among various audio hosts and plugin architectures (AU/VST/RTAS). Settings set for our plugin in one audio host have been retained in other hosts and also migrated on system upgrades/changes.
Sandbox technology now isolates application storage space and preferences as well. This also means that we cannot set plugin preferences based on user choices during installation process. Is there a way how to share preferences and not to break compatibility with future system releases and migration technology? Should we just drop the CFPreferences framework and use own hacks?
Thanks for any ideas.
Pavol Markovic
_______________________________________________
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