Frustrated w. generic AUs not returning to settings
Frustrated w. generic AUs not returning to settings
- Subject: Frustrated w. generic AUs not returning to settings
- From: Chris Johnson <email@hidden>
- Date: Tue, 4 Sep 2007 23:03:02 -0400
So I'm not sure where exactly to turn here, but I've just seen the
9,000,000th example of one of my users being sad because Logic
doesn't retain their settings on my plugins after saving and
quitting. This makes me crazy because I'm using the generic interface
and to the best of my knowledge my AU code doesn't have ANY way to
remember or return to its own settings- it tells Logic what controls
are there and Logic saves them somehow and feeds the plugin back the
desired settings- or not.
Does anyone have any idea what's happening? Why can't Logic do this,
am I missing something? Why does Logic sometimes grab the control
(including on my Density plug which can put out dangerous levels of
boost) and, on click, slam it to full crank? Is there ANY way I can
control these things within my plugin? Is there any way I'm
inadvertently causing them through mistake or negligence? The generic
AU stuff looks pretty direct to me and I don't see any angle from
which I can attack the problems.
Help?
Chris Johnson
airwindows
_______________________________________________
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