• 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: Parameters - Re: SDK Available
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Parameters - Re: SDK Available


  • Subject: Re: Parameters - Re: SDK Available
  • From: "Chris Reed" <email@hidden>
  • Date: Sat, 03 May 2003 15:26:41 -0600

On Sat, 3 May 2003 12:00:22 +0200, "Urs Heckmann" <email@hidden> said:
> Am Freitag, 02.05.03, um 02:14 Uhr (Europe/Berlin) schrieb Bill Stewart:
>
> > Any other glaring or otherwise comments or concerns?
>
> Ah, an invitation! - Nothing glaring, but some sort of anti-headache
> agent...
>
> One old thing I'd like to bring up again is metadata for parameters.
>
> Something that could enhance user experience would the ability to build
> groups of parameters. - In an automation driven environment, these
> groups could be the organizing structure for hierarchical menues when
> selecting automation tracks. Furtherly, the generic view could adopt
> some strategies to seperate groups visualy. Obviously, this is
> important for plugins with many parameters.

I'd like this.. It'd make separation of parameters for each instrument in
Ritmo much easier, for one thing.

>
> Well, "groups" could have their own presets or at least settings could
> be loaded seperately from preset xy into current user preset (One could
> think of additionaly data keys in the settings for this). - Of course,
> one could do this anyway now, but a general way might be more
> consistent than isolated solutions. Some sort of discussion might be
> necessary. Example: The good old Ensoniq synths/samplers have presets
> for envelopes etc. Very useful.

Cool idea. But UI for this would probably be best implemented in the AU's
custom editor, which makes it questionable as to whether a generic API is
necessary. More talking about it needed :)

> [snip]
> One buggy thing I came across that's somehow related (Generic View):
>
> My current work has no custom gui yet, so the generic view jumps in.
> Half of the parameters disappear in nirvana below my monitor 8-)). The
> generic view should become a little smarter and waste less screen
> estate...

Already filed with Rader, although I couldn't tell you the bug number
now.. Also can't remember what state it's in.

-chris
_______________________________________________
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: 
 >Parameters - Re: SDK Available (From: Urs Heckmann <email@hidden>)

  • Prev by Date: Re: CoreFoundation (was DigitalCDSound)
  • Next by Date: Re: CoreFoundation (was DigitalCDSound)
  • Previous by thread: Parameters - Re: SDK Available
  • Next by thread: Re: Parameters - Re: SDK Available
  • Index(es):
    • Date
    • Thread