• 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: AUMultibandCompressor and factory presets?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AUMultibandCompressor and factory presets?


  • Subject: Re: AUMultibandCompressor and factory presets?
  • From: Robert Grant <email@hidden>
  • Date: Mon, 15 Mar 2004 19:33:54 -0500

The problem with the generic UI is compounded by the fact that if the users sets a custom preset (with a name) there is no way for the generic UI to show that preset name.

The generic UI needs to be fixed IMHO.

Sounds like a good bug to file. :-)

Robert.

On Mar 9, 2004, at 3:10 PM, Jeremy Sagan wrote:

That is very confusing then because when a user selects the factory preset from the menu it changes but it does not change if the plug-in is sent a factory preset via a set property call on current preset. Seems a tad inconsistent to me. Perhaps it should always just say "Factory Presets" in that menu then and not reflect the users selection?

Jeremy

On Tuesday, March 9, 2004, at 01:28 PM, William Stewart wrote:

This is a vagary of having a preset menu in the Carbon View... Its not
great UI design, but that menu is not meant to reflect the "Current
Preset" of the AU, just the collection of factory presets that are
available to the user to choose.

Bill

On 09/03/2004, at 7:34 AM, Jeremy Sagan wrote:

If I set the current preset of the AUMultibandCompressor to a factory
preset, the plug-in does not update the factory preset setting at the
top of the edit window.

err = AudioUnitSetProperty(m_audioUnit,
kAudioUnitProperty_CurrentPreset,
kAudioUnitScope_Global, 0, &m_preset, sizeof(m_preset));

where for example, m_preset = {1, CFSTR"Subcontrol") which was
directly extracted from the factory_preset array.

I do not know if I have to, but I am calling AUParameterListenerNotify
after setting this property.

Is this not working because I should be using the property
PresentPreset and not CurrentPreset? Shouldn't CurrentPreset still
work?
_______________________________________________
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.
_______________________________________________
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.
_______________________________________________
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: AUMultibandCompressor and factory presets? (From: Jeremy Sagan <email@hidden>)

  • Prev by Date: Midi Plugins like MFX in Logic Audio Pro???
  • Next by Date: Re: Stereo Mixer oddity.
  • Previous by thread: Re: AUMultibandCompressor and factory presets?
  • Next by thread: CoreMIDI: problem connecting MIDI I/F after app launch
  • Index(es):
    • Date
    • Thread