Re: Sound Output Components for OS X???
Re: Sound Output Components for OS X???
- Subject: Re: Sound Output Components for OS X???
- From: Jeff Moore <email@hidden>
- Date: Mon, 6 Jan 2003 15:32:58 -0800
On Monday, January 6, 2003, at 01:51 PM, Mark Coniglio wrote:
Dear
On Saturday, January 4, 2003, at 06:49 AM, Mark Coniglio wrote:
Hi,
For my real-time video and audio app Isaodra. I've written an OS 9
Sound Output Component that talks to an ASIO handler within my app,
and routes the audio from a Sound Manager channel to any pair of
channels on an external, multi-channel interface. It works great on
my
MOTU 828. So far so good...
But now, I'd like to pull off the same trick for OS X. My question
is,
does OS X recognize a Sound Output Component? Where do I put it?
Yes sdevs are still supported, but the Sound Manager is not the way to
do what you are doing. It is not even the primary API for doing audio
on X. The right way is to just use the native multi-chanel APIs found
in Core Audio.
But if you insist, I would manually register and unregister your
component when your app launches and quits using the appropriate
Component Manager routines. I would keep your component in your app's
bundle in the Resources or Plug-Ins folder.
I understand that what I'm doing is a bit unorthodox. My ultimate goal
is to get the sound from multiple QuickTime movies playing on
different pairs of outputs on the 828 or other multi-channel output
device.
Though Apple folks on the QuickTime API list are hinting that there
will be a way to do this using CoreAudio the future, there doesn't
seem to be a way to get QT movie sound separated out without using a
sound output component.
Am I wrong? If there's a simpler way to do this I'd be happy to know
it.
QT is still mired in the Sound Manager, so an sdev will be required.
All the APIs involved are the same. This is why I suggested registering
and unregistering your component dynamically and storing it in a folder
inside your application's bundle. That way, you're not publishing your
component to the whole system when just your app is going to be using
it.
You will have to talk to the HAL to implement your sdev, regardless of
where your component lives. So you will necessarily be using Core Audio
APIs, hence my other advice about getting with the current APIs.
--
Jeff Moore
Core Audio
Apple
_______________________________________________
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.