• 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: Recommended way to classify AU categories on the UI?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Recommended way to classify AU categories on the UI?


  • Subject: Re: Recommended way to classify AU categories on the UI?
  • From: "Ross Bencina" <email@hidden>
  • Date: Sun, 1 Aug 2010 05:42:25 +1000

I wrote something along the lines of the following (I've added the AU type constants):
At the moment I have all AUs listed in a single tree by category:

Instruments > Manufacturer (kAudioUnitType_MusicDevice)
Instrument/Effects > Manufacturer (kAudioUnitType_MusicEffect)
Effects > Manufacturer  (kAudioUnitType_Effect)
Generators > Manufacturer (  kAudioUnitType_Generator)
Panners > Manufacturer ( kAudioUnitType_Panner )

A lot of the confusion seems to stem from this:
Instrument/Effects > Manufacturer (kAudioUnitType_MusicEffect)

I take kAudioUnitType_MusicEffect to be ambigous about being an Instrument with audio input, or an Effect with MIDI input, but Sophia Poirier wrote off list:
Actually it is not supposed to ever mean "instrument which takes audio input", just "effect that takes MIDI input". I remember asking once about it long time back on the CoreAudio email list and being told this by Apple folks. So my thoughts are that something like "MIDI-controlled effect" might be a less confusing label, in my opinion.

Can anyone else confirm this please? Is anyone using kAudioUnitType_MusicEffect for "instrument which takes audio input". Otherwise I will just put kAudioUnitType_MusicEffect plugins in my Effects category and delete the "Instrument/Effects" category from my UI entirely.



Thanks!


Unlike some hosts, all AUs are available in the same list (ie context
doesn't provide implicit filtering to only instruments/only effects, etc).

Some of my users are finding this classification confusing. I suspect this
is largely because the whole Instruments, Instrument/Effects, Effects
classification is artificially based on i/o topology rather than functional
role -- so you can end up with variants of the same AU in different
categories (e.g. what the user expects to be an instrument is in
Instrument/Effects for example).


I'm considering removing the top level categories entirely and listing all
AUs only by manufacturer, or flipping the hierarchy thus:

Manufacturer > Instruments
Manufacturer > Instrument / Effects
Manufacturer > Effects
Manufacturer > Generators
Manufacturer > Panners

Is there a recommended Apple way of representing the AU list?

Thanks

Ross.


_______________________________________________ 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
References: 
 >Recommended way to classify AU categories on the UI? (From: "Ross Bencina" <email@hidden>)

  • Prev by Date: Re: multichannel mixer render callback problems
  • Next by Date: Formatting a time signature for MusicPlayer
  • Previous by thread: Re: Recommended way to classify AU categories on the UI?
  • Next by thread: Feedback between external speaker and microphone on iPhone3G
  • Index(es):
    • Date
    • Thread