Re: Jack and CoreAudio (was Mirroring Audio Output)
Re: Jack and CoreAudio (was Mirroring Audio Output)
- Subject: Re: Jack and CoreAudio (was Mirroring Audio Output)
- From: "Andy O'Meara" <email@hidden>
- Date: Sat, 20 Jan 2007 18:23:51 -0500
Peter, great post -- very well expressed. As you probably already
know, the response (or lack thereof) on these issues isn't very
encouraging. Here's some correspondence when I was asking about
getting an audio feed from apps and/or Mac OS -- it's same sort of
frustration:
http://lists.apple.com/archives/coreaudio-api/2006/Jan/msg00097.html
http://lists.apple.com/archives/coreaudio-api/2006/Jan/msg00101.html
http://lists.apple.com/archives/coreaudio-api/2006/Jan/msg00102.html
Andy
On Jan 16, 2007, at 4:01 PM, Peter Kirn wrote:
I wrote the story Dan pointed to arguing for better integration of
JACK with the operating system; let me elaborate.
An open, universal platform for interconnecting applications is not
the same as vendor-specific driver mixing capabilities. Look at the
utility of the existing inter-app audio and MIDI functionality of the
Core Audio API. These benefit all applications equally (including
Apple's own pro apps). And when routing sound, MIDI, and sync data,
all applications and users have the same fundamental set of needs, not
needs specific to a certain app or device (as with vendor-specific
functions).
The problem is that the current interconnects are insufficient for
many users' needs. This isn't just an advanced feature, either -- I
regularly get questions from beginners about how to sync up different
apps. Unfortunately, the answer has usually been ReWire. Because
ReWire is proprietary to a separate developer, it's been difficult to
develop for, it's often out of step with the OS, and it's really
outdated in terms of its what people want to do. The host/client model
confuses a lot of users, depends on ReWire implementation in the apps,
and won't allow many of the real-world inter-app situations for which
it's needed. Add to that the support costs of dealing with proprietary
interconnects; even Logic suffered in ReWire implementation prior to
the most recent updates. Current inter-app audio and MIDI features in
OS X are great, but they don't do everything and they're not
completely transparent to the end user without additional work.
Ideally, the ability to connect audio and MIDI between applications
should be part of the operating system. We already have these benefits
in a limited way with OS X; JACK simply goes further. And it's not
unprecedented to have a virtual patch bay inside an OS, as any BeOS
user will tell you. Imagine if OS X had those advantages and more. The
has a huge edge over Windows XP and Windows Vista here already; JACK
could widen that gap just as Microsoft is catching up as far as
low-latency driver models.
And if it's impractical for Apple to integrate JACK fully, the next
best thing would certainly be to provide the necessary source code and
documentation for the JACK community to develop it further.
Peter Kirn
http://www.createdigitalmusic.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40soundspectrum.com
This email sent to email@hidden
_______________________________________________
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