Sorry ... in your first post I didn't notice that you'd already been tweaking your buffers/ latency. 12ms is right about the borderline for 'live' feel play. ASIO4All might get you down to around 7ms with your current hardware.
At any rate, at 12ms there shouldn't be that degree of delay you described. Maybe it is a midi latency as opposed to audio latency problem? I can only say that I don't experience that when I trigger my command station with my master keyboard.
DF
CONFIDENTIALITY NOTICE: This communication with its contents may contain confidential and/or legally privileged information. It is solely for the use of the intended recipient(s). Unauthorized interception, review, use or disclosure is prohibited and may violate applicable laws including the Electronic Communications Privacy Act. If you are not the intended recipient, please contact the sender and destroy all copies of the communication.
--- On Fri, 12/17/10, James Ulibarri <jamesulibarri@gmail.com> wrote:
From: James Ulibarri <jamesulibarri@...>
Subject: Re: [xl7] CS as DAW midi controller
To: xl7@yahoogroups.com
Date: Friday, December 17, 2010, 12:57 PM
I'm using the Native Audio 8 interface. I guess latency is 12ms verses its 5ms ASIO. I am not sure if the Native interface works with ASIO drivers.
I may switch to the Hercules Deejay Trim 4+6. But here is no point for "me" to buy a RME or Apogee or something terribly expensive since the computer is not my cup of tea as a sampler/sound module. It sounds way too clean and thin for me. There is something majorly lost in the conversion along the line verses old dirty samplers (something major). In fact I have to sample hardware when even firing off clips so my ears don't freak out when I hear those glistening clean VST's taking over.
On Fri, Dec 17, 2010 at 1:49 AM, D F Tweedie <bienpegaito@...> wrote:
Hmmm ... what type of audio interface are using and does it have ASIO drivers? If you are using standard Windows drivers with an onboard soundcard you will get about that much latency.
What you are hearing as you tweak your knobs could have actually been buffered for several hundred millisecs.
If you don't have a fancy, schmantzy interface, you can download Wunsch's ASIO4All. It is free and it gives you the ability for super low latency if you aren't using softsynths or a lot of plugins in your DAW since sequencing midi puts very little load on your computer.
DF
CONFIDENTIALITY NOTICE: This communication with its contents may contain confidential and/or legally privileged information. It is solely for the use of the intended recipient(s). Unauthorized interception, review, use or disclosure is prohibited and may violate applicable laws including the Electronic Communications Privacy Act. If you are not the intended recipient, please contact the sender and destroy all copies of the communication.
--- On Fri, 12/17/10, James Ulibarri <jamesulibarri@...> wrote:
From: James Ulibarri <jamesulibarri@...>
Subject: [xl7] CS as DAW midi controller
To: xl7@yahoogroups.com
Date: Friday, December 17, 2010, 12:21 AM
i've felt the CS makes a great Ableton/Kontakt controller since it throws CC's, etc
But is it me and just my PC's and/or interface... but is there latency there for you also?
I mean i've tried with the Motu Ultralite, Emu Midi X 2x2, and Native Audio 8 cards,
and it seems as if the CS is about a whole whole note step behind sometimes on knob movements.
Twisting a knob sometimes is really when it shows. In Ableton it's more apparent thank Kontakt because
I think Ableton is a bit bloated and requires more CPU usage. It's definately not instant like hardware.
Is it the CS or my old ass computers? I've tweaked the latency in my interfaces software and it's all the same accept
for less and more dropouts. Anyone else feel there is something to be desired or is it just me?
This is where I think the Command Station excels.Message
Re: [xl7] CS as DAW midi controller
2010-12-17 by D F Tweedie