Re: DefaultAudioUnit and Digidesign 001
Re: DefaultAudioUnit and Digidesign 001
- Subject: Re: DefaultAudioUnit and Digidesign 001
- From: Brian Willoughby <email@hidden>
- Date: Tue, 21 Oct 2003 15:36:48 -0700
Your application cannot have a Creator Code of '????'
If it does, the Digi drivers will ignore it.
As someone else pointed out, command-line programs won't work, either.
Probably because they have no bundle or Creator Code.
P.S. It seems to me that all Digidesign needs to do is bite the bullet and
write a "real" CoreAudio driver (that does not sit on top of their archaic and
monolithic driver). This would, however, require that they update Pro Tools to
access their hardware via CoreAudio rather than directly. I have no idea
whether there are any special features or super low latency performance that
would be lost if CoreAudio were inserted between Pro Tools and their hardware,
but apparently Digidesign are having a harder time getting on board with
CoreAudio than the rest of us. NOTE: I'm hoping such comments will embarrass
Digi into fixing these issues - as if massive complaints from their paying
customers aren't enough already. Do we need to boycott Pro Tools? I'm
certainly suggesting this to everyone who asks my advice on Mac OS X audio.
Brian Willoughby
Sound Consulting
Begin forwarded message:
My app uses the DefaultAudioUnit.
A user claims that it impossible to get any sound from it after installing the
most recent CoreAudio driver for Digidesign 001
Is there a known problem with this driver and the DefaultAudioUnit or is it
just a system setting he is missing?
Thanks for any help
Rolf Nilsson/Roni Music
_______________________________________________
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.