• 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: Multitimbral Music Devices - Question and Proposal
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Multitimbral Music Devices - Question and Proposal


  • Subject: Re: Multitimbral Music Devices - Question and Proposal
  • From: Frank Hoffmann <email@hidden>
  • Date: Wed, 16 Jul 2003 09:35:14 +0200

Your example decribes the following scenario: a Audio Unit (Master) hosting Audio Units (Slaves).

1) One or more Slave Audio Units can again host Audio Units. I can not imagine a good UI for that, except complexity is something you prefer.
2) You actually describe building blocks. But every of these building blocks have parameters and many of these should not be altered or make only sense in conjunction with other parameters (dependencies). The Host has no knowledge about that and can not present any hint to the user. So the only Entity that can provide the knowledge required is the Master Audio Unit. There it belongs. The rest should be hidden as a black box.

Frank

On Mittwoch, Juli 16, 2003, at 08:24 Uhr, Jim Wintermyre wrote:

> Regarding Audio Units hosting Audio Units: There should be no need for
> that. Or how many layers of Audio Units inside Audio Units you want to
> support?

Isn't this basically what AUGraph is for? I'm completely naive about the
implications for plug-in development, but I think wrapping an AUGraph of arbitrary complexity in a single AudioUnit would be a really powerful feature.
(If that's a stupid comment please just ignore it :-) )

For hosts that just support the standard "x insert plugs in series per channel" plus "y parallel send plugs" model (which seems to be most of the standard DAW apps), it is definitely useful to have a "chainer" plug like this. For an example, check out the Spark FXMachine or Bias vbox plugins.

When might you want to use something like this? Say for example you want to "roll your own" multiband compressor, but you want to build it up using other plugins as components instead of trying to use a single MB compressor plugin. You might want to do this because you have EQ and compressor plugins that by themselves are each better than the EQ and compressor parts of the MB compressor plug. So, to do this in a traditional approach you'd make 2 (or more) copies of the source track. On the first copy, insert your ultra-cool EQ set to lowpass at the crossover point feeding your ultra-cool compressor with your low band compression settings. Do similar stuff for the second track to set up the high band. It sounds so good you decide you want to do the same thing to 10 other tracks, and you spend half an hour doing the busywork.

Or, you set up this particular plugin chain once in FXMachine, save it as a preset, then call it up instantly on any other track whenever you want.

Jim
_______________________________________________
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.


------------------------------------------------------------------------ --------------------------
frank hoffmann mailto: email@hidden
ableton ag http://www.ableton.com
_______________________________________________
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: Multitimbral Music Devices - Question and Proposal (From: Jim Wintermyre <email@hidden>)

  • Prev by Date: Where do AudioHardwarePlugIns go?
  • Next by Date: Re: Multitimbral Music Devices - Question and Proposal
  • Previous by thread: Re: Multitimbral Music Devices - Question and Proposal
  • Next by thread: Audio Units and sending Midi
  • Index(es):
    • Date
    • Thread