Re: Save audio unit presets with Digital Performer as host
Re: Save audio unit presets with Digital Performer as host
- Subject: Re: Save audio unit presets with Digital Performer as host
- From: John McAuliffe <email@hidden>
- Date: Tue, 15 Mar 2011 20:03:23 +0000
- Importance: Normal
Hi Stephen,
Thanks for the suggestion, however I finally figured out what was wrong and
it was a problem with my Mac setup. I found from reading through at the DP7
help that plugin presets are stored in the folder
/Library/Audio/Presets/Digital Performer/...
I noticed that this folder didn't exist on my Mac, but
/Library/Audio/Presets/MAGIX did and the plugins that I could create presets
for were from MAGIX. I then found that the folder permissions settings on
/Library/Audio/Presets were somehow set to read-only and so DP couldn't
create the Digital Performer folder in which to put the presets.
Unfortunately DP doesn't say 'Can't create folder' or any useful error, it
just doesn't put up the file dialog.
Having sorted the folder permissions, I can now happily save presets :-)
Thanks for everyone's input on this.
John.
--------------------------------------------------
From: "Stephen Blinkhorn" <email@hidden>
Sent: Tuesday, March 15, 2011 5:25 PM
To: "CoreAudio API" <email@hidden>
Subject: Re: Save audio unit presets with Digital Performer as host
Hi John,
On 15 Mar 2011, at 06:52, John McAuliffe wrote:
Digital Performer has a preset menu on the plugin frame and within this
there is a 'Save Settings' option. On one plugin that I have (an amp
sim), when I click on this, a dialogue appears to select the
name/location of the preset to be saved. On other plugins (including my
own and all the MOTU ones that came with DP), no such dialogue appears.
Audio
Is it possible that some plugins use the SaveState() method to throw up a
file dialog in an attempt to override the AU preset mechanism? If this is
true then you'd expect to see the dialog when saving a session too I
imagine.
Stephen | AudioSpillage
I'm trying to figure out why this is the case. You mention being asked
for a filename - do you mean some call into the plugin that asks for
this?
I have implemented SaveState() and RestoreState() within my AU and I
just expected this to be called from the host with a buffer in which to
save the preset info to.
Thanks,
John.
--------------------------------------------------
From: "Paul Davis" <email@hidden>
Sent: Tuesday, March 15, 2011 12:37 PM
To: "John McAuliffe" <email@hidden>
Cc: <email@hidden>
Subject: Re: Save audio unit presets with Digital Performer as host
On Tue, Mar 15, 2011 at 6:44 AM, John McAuliffe <email@hidden
> wrote:
Hi,
I'm new here and looking for information on saving an AU plugin user
preset.
I'm using DP7 as a host. If I load my plugin to a track and I click on
the
"Save Settings .." menu, I would expect a dialog to appear to allow me
to
select where to save to. However nothing appears. I've noticed this
behaviour is the same for many other AU plugins, however some plugins
do
seem to allow me to save settings to a preset file.
AU preset saving is handled by CoreAudio and not by the host. The
presets are in a standard format and are usable by all AU hosts via
mechanisms offered in the CoreAudio API. as a result, no individual
host gets to decide their format or where to put them. this is why you
can use presets you created in logic with mixbus or DP or .....
what is the flow when you get asked for a filename?
_______________________________________________
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
_______________________________________________
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