• 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: Channels, Busses and I/O Configurations
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Channels, Busses and I/O Configurations


  • Subject: Re: Channels, Busses and I/O Configurations
  • From: William Stewart <email@hidden>
  • Date: Mon, 27 Oct 2003 12:18:11 -0800

I agree whole-heartedly, and we'll do our best to ensure this is fixed.

To help that, can those who have an interest in this write me a list of the problems they currently have with host apps? (Sooner than later would be better) - just send it to me privately (doesn't have to be exhaustive - just short notes, and if there's something I don't understand I can ping you - that would help a lot I think - and I'll present the info to the appropriate companies...

Bill

On 27/10/2003, at 6:57 AM, Glenn Olander wrote:

I have to agree with Art. The problem posed by Urs is interesting, but only
in an academic sense. Meanwhile, back here in the real world, we don't
have any major hosts (or plugins?) which properly implement multiple stereo outs.

What's the problem? Is there confusion about the current spec? Does that
indicate that we should be simplifying the API, not making it more complex?

One of the things we're all proudest of in AU is the ability to have one plugin
support multiple I/O configurations, but the reality is that all we've achieved
the the absence of multiple stereo out plugins. From the user's point of
view, there is currently a distinct disadvantage to AU vs. VST. Let's first focus
on fixing that problem.

- Glenn


Art Gillespie wrote:
FWIW, I'm not nearly as interested in solving this theoretical 'problem' as I
am in some sort of advocacy to encourage host developers to support the API as
it's written now. I'm not sure if adding more complexity to the API while
nobody has yet managed to get the 'simple case' right is the solution.
_______________________________________________
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.


-- 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
________________________________________________________________________ __
_______________________________________________
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: Channels, Busses and I/O Configurations (From: Glenn Olander <email@hidden>)

  • Prev by Date: Re: AUValidation tool availability for the rest of us?
  • Next by Date: Re: kAudioHardwareIllegalOperationError
  • Previous by thread: Re: Channels, Busses and I/O Configurations
  • Next by thread: some new developer info at ADC
  • Index(es):
    • Date
    • Thread