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

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


  • Subject: Base classes for Music Device... so many choices!
  • From: "Aurelio Ramos" <email@hidden>
  • Date: Mon, 26 Sep 2005 17:01:08 -0400

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
  • Follow-Ups:
    • Re: Base classes for Music Device... so many choices!
      • From: William Stewart <email@hidden>
  • Prev by Date: linked Cocoa-Carbon windows for AUCarbonViews
  • Next by Date: Re: Base classes for Music Device... so many choices!
  • Previous by thread: Re: linked Cocoa-Carbon windows for AUCarbonViews
  • Next by thread: Re: Base classes for Music Device... so many choices!
  • Index(es):
    • Date
    • Thread