• 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: Base classes for Music Device... so many choices!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Base classes for Music Device... so many choices!


  • Subject: Re: Base classes for Music Device... so many choices!
  • From: William Stewart <email@hidden>
  • Date: Mon, 26 Sep 2005 14:34:10 -0700

We provided AUInstrumentBase to give users a more complete level of support for writing instruments - similarly as we do with effects with AUEffectBase

AUInstrumentBase builds on the existing SDK classes - its a subclass of AUMusicDeviceBase (and actually uses the MIDI parsing - including support for automatically mapping midi messages to parameters - services of that class in its implementation). In fact (as AUEffectBase does with kernels), AUInstrument base takes the implementation completely away from the top-level AU interface, to an abstract concept of a note, with different phases of its envelope, etc.. Even note-dropping is handled in this abstract manner/

I think its fairly obvious by looking at the various implementations of these classes to see what functionality they give you. So, in short, the answer to your question is "it depends" - where "it depends" is on the level of sophistication of your implementation, etc.

If there are some questions you have (or areas we could clarify) about the set of base classes, I'd be happy to elucidate - but I think its more fruitful if you take a look through this yourself first.

Bill

On 26/09/2005, at 2:01 PM, Aurelio Ramos wrote:

Consider the scenario where an existing codebase for a software synthesizer is being ported from another platform / plugin-standard to Audio Units.

I have recently learned about all the options available to make an Audio Unit software synthesizer. It looks like many of the newer ones are very smart, but probably best left to those developing an instrument from scratch (AUMonotimbralInstrumentBase for example)

When porting a synthesizer whose interface is essentially MIDI input, Audio output and gui (already implemented under a different plugin standard) what would be the recommended AU base class to use as a starting point? MusicDevice? MusicDeviceBase?

Any help will be appreciated.

-Aurelio


_______________________________________________ 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


--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________ __
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________ __


_______________________________________________
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: 
 >Base classes for Music Device... so many choices! (From: "Aurelio Ramos" <email@hidden>)

  • Prev by Date: Base classes for Music Device... so many choices!
  • Next by Date: ioErr with AudioFileReadBytes?
  • Previous by thread: Base classes for Music Device... so many choices!
  • Next by thread: ioErr with AudioFileReadBytes?
  • Index(es):
    • Date
    • Thread