Re: Unusual AU initialization behavior in Digital Performer?
Re: Unusual AU initialization behavior in Digital Performer?
- Subject: Re: Unusual AU initialization behavior in Digital Performer?
- From: Chris Johnson <email@hidden>
- Date: Wed, 14 Feb 2007 19:22:51 -0500
On Feb 14, 2007, at 6:06 PM, Chris Johnson wrote:
I'm going to try defining the values in Channel.h and also
assigning them to 0.0 there- not just in the Reset. I had this idea
that everybody would call Reset *ROFL* imagine that, such an
idea... looks like I have an entire product line to overhaul and
put in redundant initial values, IF this workaround bails DP out.
I've got a followup which is obvious to anyone more masterful at C++
than me (i.e. everyone ;) )
Can't do that- I simply cannot find where to initialize the class
members. I've been trying things I find on google searches with no
joy, and the more it fails the more concerned I become that I'm
attempting something that may cause problems elsewhere.
Anyone CoreAudio- is this a bad idea that I'm doing, trying to load
variable initializations into the ChannelKernel constructor rather
than letting it live or die by ChannelKernel::Reset() as it was
designed to do?
What I have in mind is to try and get the variables defined
redundantly for DP or anything else that is not actually calling Reset
() for some reason.
If it is okay to attempt this, can anyone tip me off how I would do
it in AUs built from the template code? I strongly prefer writing in
redundant code to telling my user it's the host's fault. Or rather,
I'd like to tell him what's happening _and_ be able to fix it even if
it's not my fault.
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