• 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: Presets etc.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Presets etc.


  • Subject: Re: Presets etc.
  • From: "Michael Kleps [reFX]" <email@hidden>
  • Date: Tue, 27 Apr 2004 21:08:56 +0200

Hi Bill,

thanks for clarifiying this. Unfortunatly I have to support VST and AU
and for simplicity I don't want to do any major changes to either
implementation. In fact, I have not modified a single line of code in
the VST version to make the AU version work. I will hence lie to the
host and tell him that I have no factory presets at all. Then the user
is forced to use my internal preset-management that is a LOT more
flexible (IMHO) then the AU one (presets can be changed and organized
in banks). VST handles presets like a RAM bank, so the user, not the
host, can decide what to do with it.

Thanks for help.

Cheers,
Mike

Am 27.04.2004 um 21:01 schrieb William Stewart:

> These are different... The Present Preset is the name (and number for
> a factory preset) of whatever the current state of the AU is if it
> were to be saved.
>
> Factory Presets are a list of presets that you deliver to the
> application/host as a set of settings the user can apply to your AU...
> Our intention with Factory Presets is that these are fairly static
> (think of patches in a ROM bank on a Synth)... So, I don't believe
> that host's should really be required to adapt to any AU arbitrarily
> changing these. Its also a different property... The docs are I think
> reasonably complete when describing how this works
> (Developer/Documentation/CoreAudio/AudioUnits)
>
> I also like Urs' solution to this... he ships a bunch of user presets
> that you load into the correct location:
>
> ~ or / Library/Audio/Presets/u-he/Zebra
>
> and a host that is managing user presets correctly will find these
> presets...
>
> Bill
>
> On 27/04/2004, at 7:46 AM, Pavol Markovic wrote:
>
>> For notifying host I use this in AUBase subclass:
>>
>> PropertyChanged(kAudioUnitProperty_PresentPreset,
>> kAudioUnitScope_Global, 0);
>> PropertyChanged(kAudioUnitProperty_CurrentPreset,
>> kAudioUnitScope_Global, 0); // deprecated
>>
>> But works only in Rax... as I've tested...
>>
>> PM
>>
>> On 27.4.2004, at 15:13, Michael Kleps [reFX] wrote:
>>
>>> Hi all,
>>>
>>> when loading my AU, Logic asks for a list of AUPresets in
>>> "GetPresets"
>>> and I provide a list of 128 AUPresets. Works fine. I can choose a
>>> preset from within Logic.
>>>
>>> But how can I notify Logic that this list has changed? (new presets
>>> have been loaded by a plugin internal function).
>>>
>>> And how can I tell the host that the user selected another preset
>>> (out
>>> of the 128 list). I can select one of the 128 presets with Logic, but
>>> if the users uses e.g. a program-change I would like to notify Logic
>>> that the current preset changed. I tried:
>>>
>>> DispatchSetProperty (kAudioUnitProperty_CurrentPreset,
>>> kAudioUnitScope_Global, 0, &AU_Presets[i], sizeof (AUPreset));
>>> DispatchSetProperty (kAudioUnitProperty_PresentPreset,
>>> kAudioUnitScope_Global, 0, &AU_Presets[i], sizeof (AUPreset));
>>> SetAFactoryPresetAsCurrent(AU_Presets[i]);
>>>
>>> AU_Preset is an array of 128 "AUPreset"s.
>>> "i" is the current preset-number.
>>>
>>> I call all three functions (just to make sure) but Logic doesn't
>>> update it's display to reflect the change.
>>>
>>> Do I make any sense? Should I give up and lie to the host by telling
>>> him I have no presets, so the list isn't even displayed and so the
>>> user is forced to use my plugins internal preset-management? The
>>> downside would be that I would be forced to put in my own
>>> preset-management into every plugin I want to release as an
>>> AudioUnit...
>>>
>>> Hope somebody can help me.
>>>
>>> Cheers,
>>> Mike
>>> _______________________________________________
>>> 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.
>>
>> [demime 0.98b removed an attachment of type
>> application/pkcs7-signature which had a name of smime.p7s]
>> _______________________________________________
>> 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.
>>
>>
> --
> mailto:email@hidden
> tel: +1 408 974 4056
>
> _______________________________________________________________________
> ___
> Culture Ship Names:
> Ravished By The Sheer Implausibility Of That Last Statement
> I said, I've Got A Big Stick [OU]
> Inappropiate Response [OU]
> Far Over The Borders Of Insanity And Still Accelerating [Eccentric]
> _______________________________________________________________________
> ___
_______________________________________________
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: Presets etc.
      • From: William Stewart <email@hidden>
    • Re: Presets etc.
      • From: Marc Poirier <email@hidden>
References: 
 >Presets etc. (From: "Michael Kleps [reFX]" <email@hidden>)
 >Re: Presets etc. (From: Pavol Markovic <email@hidden>)
 >Re: Presets etc. (From: William Stewart <email@hidden>)

  • Prev by Date: Re: Presets etc.
  • Next by Date: Re: Presets etc.
  • Previous by thread: Re: Presets etc.
  • Next by thread: Re: Presets etc.
  • Index(es):
    • Date
    • Thread