Re: Coreaudio-api Digest, Vol 2, Issue 67
Re: Coreaudio-api Digest, Vol 2, Issue 67
- Subject: Re: Coreaudio-api Digest, Vol 2, Issue 67
- From: Stephen Martin <email@hidden>
- Date: Fri, 4 Mar 2005 03:06:50 -0600
Hello, I am a Nuendo user that has been severely missing the feature of
Direct Monitoring (ASIO style) ever since the introduction of Core
Audio and OSX.
Now I realize that it is possible to get pseudo-style direct
monitoring by implementing a third party mixer (in my case , RME) that
controls the hardware interface and will allow you to mix between input
and output sources as well as input to the software for recording. This
works fairly well for some users especially those that mix "in the box"
or those that are unaware that there once was a better alternative.
I choose to employ an analog mixing console in my setup to bypass
digital summing and to allow for adding analog effects (which a lot of
pro users do these days). This requires that I use a lot of software
audio output busses which often get assigned to different hardware
outputs before going to the mixing console.
This arrangement (although great for sound) makes it very complicated
to monitor while recording via the third (RME Hardware) mixer as buss
assignments need to be reassigned constantly for punch ins etc. On
complicated projects it always comes down to dealing with that mess or
attempting to subject my clients to latency delays or take chances on
pops and clicks showing up on the recordings.
With ASIO style Direct Monitoring, this was never a problem for within
it there was a protocol that would communicate between the application
and the audio interface and make the appropriate switches between
incoming and outgoing signals on the hardware device in the background
without screwing up the buss assignments. Besides the bussing issue, it
was just a much cleaner and elegant way of monitoring that didn't
require a bunch of extra steps that all users would appreciate.
Surely, there must be a way to get this sorely missed feature back into
Mac DAWs again.
I used to blame Steinberg or RME for resenting CoreAudio and not
writing the appropriate software or drivers for I read here that Direct
Monitoring was written into the CoreAudio spec and that developers
needed to catch up but now I see the same type of complaints on the
MOTU and Apple's own Logic Forums so that leads me back here.
Is it Apple's stance that Direct Monitoring implementation is fine at
it's current state and users get to choose between kludgy hardware
device mixers and latency issues?
Or are the software and hardware manufacturers too busy putting the
bells and whistles in their souped up new revs or gizmos to write some
code for something that's been in CoreAudio ever since pootty cat was
released.
I'm not trying to put the blame on anybody in particular especially
since I do not know all the details involved, I'm just a very
frustrated end user that has waited over three years to see this basic
feature re-implented.
I'm wondering if the companies involved understand that a problem even
exists as everyone seems to be ignoring this.
My hope is that there are already steps being taken to solve it.
(Tiger, perhaps?)
If not what can be done to open a dialog between the parties involved
to take care of this once and for all?
Thanks, Stephen Martin
_______________________________________________
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