Guys,
it's actually very easy to use the CS as a DAW controller without
any hassles. Let me explain how.
1. If you've got an audio/MIDI interface with native ASIO drivers,
then use that. That will give you the best performance. Forget
ASIO4ALL, because that is only useful for cards without native
ASIO driver, and only as an emergency substitute. ASIO4ALL
will tax your computer much more, and there's no advantage
if you've got a real ASIO driver.
2. Don't forget that latency is measured/displayed differently
by vendors. Each is right, but you have to know what the numbers
mean, to adapt your system and environment.
This applies to both audio and MIDI latency.
There are vendors which will indicate input or output latency, in which
case you have to duplicate that to calculate the roundtrip latency,
which is the true system latency. So if you set up 12 msec as input latency,
then it's no wonder, you are struggling at approx. 24 msec to keep the
tempo/feel.
3. There's no quality difference between ASIO interfaces regarding
latency time. Yes, the top of the line interfaces can probably go as low
as 64 samples or 1.5 msec or even lower, but say, 5msec is available
in all the interfaces. An expensive interface won't provide any extra
at 5 msec compared to a entry level one, that is, with native ASIO drivers.
4. If you experience excessive latency using an ASIO driver, then something's
set up wrong. If you checked everything and still there's too much latency,
then use the DAW as a muted recorder, that is, LOCAL ON on the CS,
muted tracks in the DAW. This way you'll get the instant feel on the CS,
and when you unmute/play the tracks from the DAW everything should
be OK.
Regards,
Zsolt | http://adsr.huMessage
Re: [xl7] CS as DAW midi controller
2010-12-18 by Zsolt Szabó