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

Re: Private Parameters


  • Subject: Re: Private Parameters
  • From: Urs Heckmann <email@hidden>
  • Date: Wed, 16 Jul 2003 01:54:22 +0200

Am Mittwoch, 16.07.03, um 01:05 Uhr (Europe/Berlin) schrieb Glenn Olander:

James Coker wrote:
On Tuesday, July 15, 2003, at 03:34 PM, Glenn Olander wrote:
I can live with that, but it seems like a narrow definition
of parameter, especially since only #3 will apply to the
majority of plugins. (can anyone seriously see a generic UI
for any major plugins which have been released in the past
year?)
In FinalCut you can. I think some other hosts (LIVE) allow
plugins (VST in that case) to be used w/ a generic UI.

:-). Trust me, a generic GUI has never and will never be used
for plugins like all the recent releases (Absynth, OhmBoyz,
Crystal, Zoyd, Mach 5, Kontakt, etc.)


Hehe. FCPro doesn't host Music Devices, right? - Maybe this is because MDs tend to blow up generic guis by their sheer average number of parameters?

Haha, could anyone do me the favour and send me a screenshot with FCPro's generic gui for More Feedback Machine? (Or better yet, an NFR of FCPro? 8-)

Alternatively, we could add a flag to
parameter info that says whether a parameter is automatable
or not. That would seem like a useful thing to have in the
long run.
I assume that if the parameter is readable and writeable,
I can (and will) send it automation data. I also use those
flags to determine which parameters to listen to for changes
so that I can capture 'scene' data separate from the normal
AU preset mechanism.

That's my point, we currently have to assume. But, if everyone
is happy with the narrow definition of parameter, then that
assumption is a safe one.

I think to remember that during the initial private parameters discussion some months ago, it was exactly defined that private params would just not be exposed via the parameter list. Hence they could be used to quickl'n'dirty do arbitrary, non-blocking gui <-> dsp communications, without needing to set up Properties stuff.

Furtherly, Marc provided us with an Audio Unit that made unequaled use of this mechanism. That was "RMS Buddy". You can look at the source via www.destroyfx.org - down in the cvs repository...

Hope this helps,

;) 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: Private Parameters (From: Glenn Olander <email@hidden>)

  • Prev by Date: Re: Private Parameters
  • Next by Date: Re: parameters, gui
  • Previous by thread: Re: Private Parameters
  • Next by thread: Re: Private Parameters
  • Index(es):
    • Date
    • Thread