• 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: Audio Units - newbie questions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Audio Units - newbie questions


  • Subject: RE: Audio Units - newbie questions
  • From: "Muon Software Ltd - Dave" <email@hidden>
  • Date: Tue, 11 Oct 2005 08:16:09 +0100
  • Importance: Normal

Bill

Thanks for your response, my comments in the text below:-

> I'd probably just create the AU with the 4 outputs, all stereo, and
> leave it at that. You should then also accept a mono or stereo output
> on any of the outputs.

So in the constructor I pass in 0 inputs, 4 outputs, and leave it at that?
do I need to check what outputs and buffers I have been given in Render? do
you have any example code I could look at for that?

> That's incorrect - it calls Initialize everywhere - You can easily
> see this if you use the DebugDispatcher AU in the SDK and run it
> through auval.

It isn't hitting breakpoint in Initialize, and my implementation sets a bool
flag to say it has been called which I evaluate in Reset and other
functions. This flag is false during the first call to Initialize.


> That's not mandatory. In fact, all of the mandatory properties are
> fully supported in AUBase,  so subclasses are only required to
> support the features that they want to add.

Where are the Apple-defined properties (<64000) documented?


> GetParameterValueStrings is designed to provide support for indexed
> parameters where each param value is a string - in a generic view
> this allows the parameter to be represented as a menu list.

Which I guess is why it returns an array, understood.

> Then we added generic values/strings services - that would also allow
> just some specific values to have strings, otherwise its a literal
> translation - for instance, a dB parameter where values below -120dB
> should be presented as -inf

OK - since the underlying code is shared with a VSTi I'll stick to the value
strings I understand. I'll have more questions about parameters later no
doubt!

> optional

Are scheduled parameters and slice based rendering easy to implement if I
did decide I wanted to go there? any example code around?

Regards
Dave

 _______________________________________________
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

  • Follow-Ups:
    • Re: Audio Units - newbie questions
      • From: William Stewart <email@hidden>
    • RE: Audio Units - newbie questions
      • From: "Muon Software Ltd - Dave" <email@hidden>
References: 
 >Re: Audio Units - newbie questions (From: William Stewart <email@hidden>)

  • Prev by Date: Re: USB vs. FireWire
  • Next by Date: RE: Audio Units - newbie questions
  • Previous by thread: Re: Audio Units - newbie questions
  • Next by thread: RE: Audio Units - newbie questions
  • Index(es):
    • Date
    • Thread