• 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: Noob question: sending button clicks to AudioUnits?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Noob question: sending button clicks to AudioUnits?


  • Subject: Re: Noob question: sending button clicks to AudioUnits?
  • From: William Stewart <email@hidden>
  • Date: Mon, 9 May 2005 15:37:44 -0700

And in fact in Tiger, the generic views we publish will see that this is a write-only boolean parameter and will give you a standard button to press (that doesn't retain state)

Bill

On 08/05/2005, at 2:34 PM, Chris Rogers wrote:

Sure, just define your parameter to be write-only (there's a flag for this in AudioUnitProperties.h).
Then, if you're not already doing so, you'd have to override the SetParameter() method and handle
the parameter set there. Your code can completely ignore the parameter value....


Chris Rogers
Core Audio
Apple Computer



On May 8, 2005, at 4:53 AM, Oli Donald wrote:


I'm porting an old AudioUnit plugin forwards to support a nice Cocoa interface. 99% of the work is done, I've got sliders and text fields and on/off buttons doing there thing and the AU Kernel responding correctly. But there is one thing I can't work out - how do I make my AU Kernel respond to a button click?

I have one button in the GUI that is supposed to clear a buffer. In the button's action method, if I do AUParameterSet() with 'true' for the button being pressed, then when my AU Kernel comes to get that parameter, then from the first click onwards it will *always* be True. What I've done to get around this is to have the action method send a toggling value to AUParameterSet(), and the AU Kernel responds to a change in that parameter. This seems like a horrible kludge. Is there a more elegant way for an AU Kernel to respond to a button click?

Thanks,
Oli
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com


This email sent to email@hidden



_______________________________________________ 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: 
 >Noob question: sending button clicks to AudioUnits? (From: Oli Donald <email@hidden>)
 >Re: Noob question: sending button clicks to AudioUnits? (From: Chris Rogers <email@hidden>)

  • Prev by Date: Custom MIDI driver does not appear in Audio MIDI Setup
  • Next by Date: Re: Calculating AU latency
  • Previous by thread: Re: Noob question: sending button clicks to AudioUnits?
  • Next by thread: Re: Noob question: sending button clicks to AudioUnits?
  • Index(es):
    • Date
    • Thread