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

Parameters - Re: SDK Available


  • Subject: Parameters - Re: SDK Available
  • From: Urs Heckmann <email@hidden>
  • Date: Sat, 3 May 2003 12:00:22 +0200

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.

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.

Another suggestion: What about a void* usedata field in AUParameters that could be individually set and would be passed to SetParameter() ? - That way one could get rid of dual representation of parameters for formal AU support and internal dsp. Well, it would also enhance gui-dsp interaction possiblilities (while probably screwing up Marc's remote control idea). Of course, it'd be static only, but nontheless, it would help me a lot I think.

There are other ideas for metadata I had, but I havn't got them in my mind now...


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...

While we're at that, I'd appreciate to find a trigger type of parameter, one that could be represented as a push button and/or a on/off button. That'd be much better than a pulldown menue for indexed parameters with range 0-1.

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.

  • Follow-Ups:
    • AU Parameter metadata
      • From: Marc Poirier <email@hidden>
    • Re: Parameters - Re: SDK Available
      • From: Marc Poirier <email@hidden>
    • Re: Parameters - Re: SDK Available
      • From: "Chris Reed" <email@hidden>
References: 
 >Re: SDK Available (From: Bill Stewart <email@hidden>)

  • Prev by Date: Re: CoreFoundation (was DigitalCDSound)
  • Next by Date: Re: Emagic VST2AU SDK and multi-output MusicDevice
  • Previous by thread: Re: SDK Available
  • Next by thread: Re: Parameters - Re: SDK Available
  • Index(es):
    • Date
    • Thread