• 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: Urs Heckmann <email@hidden>
  • Date: Sun, 15 Jun 2003 02:35:22 +0200

Am Samstag, 14.06.03, um 23:43 Uhr (Europe/Berlin) schrieb Robert Grant:

I'm working on a MusicDevice AU

weeee. Everybody hide under yer desks....

(don't panic yet :-))

ah, okay.

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.

Well, and multitimbral stuff had been mentioned in the instrument's context. Ask Angus about that. He'll have nice words for it that do not exactly belong to my linguistic range, I think. - Can't find the mail now for a citation. However, I could contribute some nice episodes about that (multitimbral, not Angus).

And for all the good stuff that hasn't been explored, neither in hosts nor plugins, I think someone - if not Apple - should come up with an example. It should show the benefits and it should prepare the roadmap for the hosts to get there. In turn, the plugs will follow (I want to build a plug with flexible mono/stereo sidechains/inputs (plural here)!!!).

You asked for thoughts...

;) Urs


(I had Californian Merlot tonight, so don't blame German dialectics for anything scrambled here)
_______________________________________________
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: Airy André <email@hidden>
References: 
 >New MusicDevice and PrepareInstrument (From: Robert Grant <email@hidden>)

  • Prev by Date: Coalescing V1 & V2 MusicDevices
  • Next by Date: Re: Coalescing V1 & V2 MusicDevices
  • Previous by thread: New MusicDevice and PrepareInstrument
  • Next by thread: Re: New MusicDevice and PrepareInstrument
  • Index(es):
    • Date
    • Thread