• 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: New MusicDevice and PrepareInstrument
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New MusicDevice and PrepareInstrument


  • Subject: Re: New MusicDevice and PrepareInstrument
  • From: Airy André <email@hidden>
  • Date: Sun, 15 Jun 2003 10:26:40 +0200

Le dimanche, 15 juin 2003, ` 02:35 Europe/Paris, Urs Heckmann a icrit :

and it's coming along nicely, however because of what it's doing (it's actually glue to another sound generator rather than an independent AU) it seems to fit the Instrument model rather than the Preset model. In other words I've got a number of rather large backends from which to choose and they each need to be warmed up before anything happens.

My questions are: If I release a MusicDevice AU with Instruments will any hosts (other than my own - and even Rax doesn't grok it right now) actually be able to use it? Or should I switch to a "no presets or instruments mode" and handle it all through custom properties and a custom UI?

Thoughts?

Well, I see that we have some stuff that isn't supported widely nor really established within our thinking. The instrument paradigm is still far away from my understanding, as well as the bus stuff isn't exactly known how to handle.

For the current situation (uh, I get political here...), while we can't afford the luxury of saying "okay they won't buy it, because it doesn't run, but what gives, I do it the way it should be", I would pragmatically recommend sticking to what runs (uhm, former VST people have an advantage here...).

I have no idea what you do, but given that there are modular systems running halfways neatly (one isn't really modular, the other ones crash occasionally), there are quite simple solutions, even with parameters and presets. IIRC Airy's STK thing switches instruments as a parameter. In my own designs, I simply switch synthesis techniques by parameter and keep the stuff that's overall common the same.

Yes, AUStk uses a parameter to define instruments.
But mainly because, as far as a now, no host can use the MusicDevice API.
I've started to code my first AU by coding only the MusicDevice API, not the MIDIBase one and, suprise, no sound in Logic.
So, I've decided to learn writing AU by writing code I could test :-)

For current hosts, MusicDevices are nothing more than AudioEffects without input channels.

Any other host writer here ?

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

  • Follow-Ups:
    • Re: New MusicDevice and PrepareInstrument
      • From: Bill Stewart <email@hidden>
    • Re: New MusicDevice and PrepareInstrument
      • From: Philippe Wicker <email@hidden>
    • Re: New MusicDevice and PrepareInstrument
      • From: Urs Heckmann <email@hidden>
References: 
 >Re: New MusicDevice and PrepareInstrument (From: Urs Heckmann <email@hidden>)

  • Prev by Date: Re: Coalescing V1 & V2 MusicDevices
  • Next by Date: How to remember the MIDIEndpoint after reboot
  • Previous by thread: Re: New MusicDevice and PrepareInstrument
  • Next by thread: Re: New MusicDevice and PrepareInstrument
  • Index(es):
    • Date
    • Thread