• 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: adding parameters to an Audio Unit
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: adding parameters to an Audio Unit


  • Subject: Re: adding parameters to an Audio Unit
  • From: William Stewart <email@hidden>
  • Date: Tue, 4 Mar 2008 14:55:14 -0800


On Mar 4, 2008, at 2:42 AM, Jankoen de Haan wrote:

Hi Bill

Indeed I'm adding a parameter at the lists, but it has an ID which is (if sorted numerically) somewhere in the middle of the list.
I was hoping that Logic would map the automation data uniquely to the parameter id, and did not use indexes.

It should - parameter IDs are not indexes, but IDs - but if you are using indexes, then you would end up using an index that was previously used for something else. If you aren't using indexes and logic is doing this as if it is, then that would indeed be bad and a bug Logic should fix. So, could you confirm this (you could just send me the auval report from your AU before and after and I can verify it too)


For now I removed the parameter from the parameter lists known to Logic and only store it in the bulk (Restore/SaveState).


I use OSType as parameter IDs for a little more easy debugging. This will get stored and sorted in the AUElemety::mParameters which is an std::map. Probably that is why the indexing goes wrong by Logic. I might want to set mUseIndexedParameters to true, so the parameters are added by index, not by ParmaterID ?

Maybe, but this would really be a bad bug in Logic if this were the case. Parameter IDs are not indexes and your usage sounds to me like it is correct.


I would like to file a bug report about this issue, but I'm unsure where to do that. Maybe somebody can point me to the right direction.

I think it might be worth doing (and attach the auval report as evidence that you aren't reusing the param ID) - I'll shepherd it through from there


Bill


JK

I don't think that is the problem.

Once you have published a parameter ID you really have to keep that ID - you can't change it as it will break all existing uses of your AU that are stored in presets and documents.

But, I don't think that is what he is doing, I think he is adding to the end - appending - or at least that is what i had assumed.

If however, you are adding the parameter ID into the middle of the list, then you need to change this in the AU and append it

Sorry if I am causing confusion!

Bill

On Feb 29, 2008, at 1:54 PM, Stefan Gretscher wrote:

Hi Jankoen,

sorry for the late reply, I was out of the office.
I looked into the issue you've reported and I assume that you've triggered a bug in Logic by inserting the new parameter somewhere in your exported parameter list instead of appending it at the end.
Due to legacy reasons, Logic relies on the order of parameters when storing its automation data. Please file a bug report about that.


Thank you,
Stefan

Am 21.02.2008 um 20:01 schrieb William Stewart:
From the sounds of it, what you have done is fine and seems to have triggered a bug in Logic; adding parameters should be supported by the hosts as long as the existing parameter IDs are kept the same. We'll need to wait and see what the Logic guys have to say

Bill

On Feb 21, 2008, at 4:19 AM, Jankoen de Haan wrote:

Hi

I'm creating a newer version of my Plugin with some new functionality. This means I did add one extra parameter to the parameter list. So far so good. All works fine, but now....

When I open an older session (created with a previous version of my plugin) that contains automation data in Logic, a lot of automation ramps are mapped to the wrong parameters. All AudioUnitParameterIDs are the same between the versions, there is only one parameter new. What is the right way to make sure, when I add a new parameter to en exisiting audiounit, the automation in Logic is mapped right ?

thanks,
Jankoen de Haan
Audio Ease BV
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden



------------------------------------ Stefan Gretscher plug-in development & 3rd party developer support

phone: (+49)-4101-495-586 (Central European Time)
AU developer support: email@hidden
TDM developer support: email@hidden

Apple GmbH
Geschäftsführung: Georges Guyon de Chemilly
Sitz der Gesellschaft: München
Amtsgericht München, HRB 66158



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: adding parameters to an Audio Unit
      • From: Stefan Gretscher <email@hidden>
References: 
 >Re: adding parameters to an Audio Unit (From: Jankoen de Haan <email@hidden>)

  • Prev by Date: Re: SupportedNumChannels problem
  • Next by Date: Re: Coreaudio-api Digest, Vol 5, Issue 76
  • Previous by thread: Re: adding parameters to an Audio Unit
  • Next by thread: Re: adding parameters to an Audio Unit
  • Index(es):
    • Date
    • Thread