• 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: Control value passing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Control value passing


  • Subject: Re: Control value passing
  • From: Urs Heckmann <email@hidden>
  • Date: Mon, 30 Sep 2002 20:21:41 +0200

For a control, you have an integer range from the control's min and max
value - so when displaying a floating point parameter value you have to
scale this to the resolution of the control itself.

Unless you're showing a lot of pixels! I doubt that you'd need the 32bit
version. - This is why the AU view provides an enter text box for values,
because a slider cannot provide the resolution the parameter can represent
in most cases.

SetControlValue should fire the value changed callback if the value is
actually changing - the AUView code relies on this behaviour between the
slider and the text box to keep them in sync

Bill


Hi Bill,

setting the range from min to max in 100 steps == 100 pixels is not quite sufficient for some parameters. That's why default controls in Logic can be adjusted in a "fine mode" when holding down option (or was it shift?). My knob control can be modified very fine when you drag the mouse far from the control's center, even without wasting much screen estate. I think a range of about 12 - 16 bits is sufficient for any case, so I'll try to get something like that working.

In my opinion, if your primary contrrol (slider) is too coarse, the secondary control (edittext) becomes to important and needs to be displayed in a too dominant manner ( == big). The primary control should provide a sufficient resolution whereas the editable control should be used to enter values that are absolutely certain to the user (i.e. delay times, frequencies).

Day by day we get more light into the framework, so please be patient with those of us who used simplified frameworks and are now quite overwhelmed by the strength and complexity of the OS ;-)

Cheers,

;) Urs
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: Control value passing (From: Bill Stewart <email@hidden>)

  • Prev by Date: Re: more AudioUnitRender Errors
  • Next by Date: Re: graphics in AU
  • Previous by thread: Re: Control value passing
  • Next by thread: IOAudioStreamFormat.fIsMixable
  • Index(es):
    • Date
    • Thread