• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Unusual AU initialization behavior in Digital Performer?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unusual AU initialization behavior in Digital Performer?


  • Subject: Re: Unusual AU initialization behavior in Digital Performer?
  • From: William Stewart <email@hidden>
  • Date: Thu, 15 Feb 2007 12:54:06 -0800

Just have your kernel constructor call the Reset method, presuming that that sets the values to what should be their initial values.

You should always make sure that your intial values are correct

Bill

On 14/02/2007, at 4:22 PM, Chris Johnson wrote:


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

--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________ __
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________ __


_______________________________________________
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


References: 
 >Unusual AU initialization behavior in Digital Performer? (From: Chris Johnson <email@hidden>)
 >Re: Unusual AU initialization behavior in Digital Performer? (From: Chris Johnson <email@hidden>)

  • Prev by Date: Re: Audio problem
  • Next by Date: Re: AU parameter names and units
  • Previous by thread: Re: Unusual AU initialization behavior in Digital Performer?
  • Next by thread: AU parameter names and units
  • Index(es):
    • Date
    • Thread