Re: Logic, AU development and parameter scrambling
Re: Logic, AU development and parameter scrambling
- Subject: Re: Logic, AU development and parameter scrambling
- From: Brian Willoughby <email@hidden>
- Date: Fri, 28 Mar 2008 15:11:02 -0700
Ah, then you only have to follow a fraction of my suggestions.
Change the version number of your plugin each time you change the
param ID of an existing parameter. When Logic sees that the plugin
has a new version number, it will forget about the old one. As I
recently reminded this list, you have the option to set the version
number to 0.0.0 during development, and Logic will assume the plugin
is a new version every time it loads. Once you're ready to release,
you must change at least one part of the version number to be non-zero.
Brian Willoughby
Sound Consulting
On Mar 28, 2008, at 13:55, Mark Pauley wrote:
I absolutely understand that it's not up to logic to work this out
in the situation that I:
a) make a song and use my plugin and save the song
b) change the plugin's param layout
c) open the song again.
I'm fine with that... there's no possible way Logic could work with
that mess.
However I feel like this should work:
a) make a song and use my plugin and save the song
b) change the param layout
c) open the song (params are scrambled)
d) change the param settings and save the song
e) re-open the song
Here's what actually happened, I _strongly_ feel like this should
work:
a) make a song and use my plugin and save the song
b) change the param layout
c) open a _new_ song and use my plugin and save the song
d) re-open the song
This seems like it would clearly point to some sort of application-
wide (or possibly even system-wide) caching of parameter data... be
that parameter type information or index information or whatever.
Since I see my plugin's new parameters and the settings I give them
are obviously having the correct effect before I save / reopen, to
save the info and re-open in a scrambled state is at the least
inconsistent behavior.
Nobody's using my plugin but little old me... and I'm fine with
having to re-create my param settings if I want to change stuff,
the songs are sandboxes of the plugin anyhow... I am just wondering
if there's something more I can do than "reset and rescan" my
plugin that will allow a song to at least persist settings across a
save.
_______________________________________________
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