• 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 & scope/element
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: private parameters & scope/element


  • Subject: Re: private parameters & scope/element
  • From: Urs Heckmann <email@hidden>
  • Date: Mon, 18 Aug 2003 14:41:01 +0200

Hi Marc,

thanks, I now remember this stuff. Must have had a little power drop out somewhere in my memory...

I assume you used it successfully with notification scheme?

Side note: My multitimbral testing device had some problems with group scope parameters (which is obsolete now, anyway), maybe a bug on my side...

;) Urs



Am Montag, 18.08.03, um 14:48 Uhr (Europe/Berlin) schrieb Marc Poirier:

I think that using your own scope is the best way. Public scopes are a
known, fixed set (global, input, output, group) whereas elements (in this
context) are a variable array corresponding to each audio bus. So using
element 1 would I think imply that you have a second audio bus, in a way
at least, whereas using an open scope value doesn't do anything like that.
Maybe it doesn't matter, but that's just what I'm thinking.

I once asked the list if Apple reserved a range of scope values and Bill
said: "Not formally - but lets say we will reserve ID's up to 1024 - I'll
add that comment in the header" So you should use something 1024 or
higher.

Marc



On Mon, 18 Aug 2003, Urs Heckmann wrote:

Hi,

so, now my stuff has its public parameters and a whole lot of private
parameters (not reported in parameter list property), mainly for dsp
<-> view communication. They are all set up in global scope's element
0, with n public parameters going from id 0 to n-1 and the ids of m
privates from n to (n + m - 1).

Well, to get some more flexibility, I'd like to seperate these two
chunks physically (different enums, parameter info creation and stuff).
There are two options:

- Defining private parameters from id 0 to m-1 in global scope, element
1

- Defining private parameters from id 0 to m-1 in group scope, element 0

My questions:

Is any of these two solutions viable / hassle free? Which would be
better in regards of expectations?

Do I have to create elements physically (like setting number of group
scope elements 1 in AUBase constructor)?

Will ParameterListeners work properly /+ with every host?

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:
    • Re: private parameters & scope/element
      • From: Marc Poirier <email@hidden>
  • Prev by Date: Re: private parameters & scope/element
  • Next by Date: Connecting AU output to >1 destination -- PLEASE HELP!!!
  • Previous by thread: Re: private parameters & scope/element
  • Next by thread: Re: private parameters & scope/element
  • Index(es):
    • Date
    • Thread