Read-only parameters
Read-only parameters
- Subject: Read-only parameters
- From: Chris Rogers <email@hidden>
- Date: Wed, 27 Nov 2002 12:10:52 -0800
Marc,
My thinking about parameters that are readable but not writable when
I was designing the flags was to provide a way for an AudioUnit
to report back dynamically changing values relating to the internal
state of the DSP. Some examples would be: dynamic compression amount
in dB, peak signal level, average power level in dB, pitch (for a
pitch tracker) in hertz or absolute cents, tempo in BPM for a
tempo detector, etc. Thus the UI would be able to dynamically
display the value of these types of parameters to provide feedback
to the user of what the DSP is doing. This is critical for setting
the threshold on compressors and this sort of thing...
To me it seems like parameters which are neither readable nor writable
make no sense at all. Writable but not readable also seems a bit
suspect but a bit of creative thinking could probably come up with some
arcane uses for it.
Chris Rogers
Core Audio
Apple Computer
Now imagine a parameter that is readable but not writable. This is
simpler to conceptualize. The parameter values are shown to the user, but
the user is given no means to alter them. The values are locked. But if
the values are unchangeable, then what the hell does the user care about
what the values are? They might as well not be shown. They're only
useful internally to the plugin itself, no one else cares about them.
Marc
_______________________________________________
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.