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: Sat, 29 Mar 2008 03:20:38 -0700
That's a fair clarification. auval reports the version number as
0.0.0, but you enter it in your source code as 0x00000000. I was
merely referring to the human-readable interpretation of the value
returned by the Version() function of your AUBase subclass.
On Mar 29, 2008, at 03:06, tahome izwah wrote:
Just to clarify things, if I am not mistaken it's your #define
kPlugInNameVersion 0x00000000 that matters, NOT the CFBundleVersion
from your plist file as Brian's version number formatting would
suggest.
HTH,
--th
2008/3/28, Brian Willoughby <email@hidden>:
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.
_______________________________________________
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