Ableton Forum

Hallo,

This is my first post, so be kind :]

Well, my goal was to adjust lowest ASIO buffer size on my M-Audio 1814 (64 samples) on my Laptop (1.6 ghz, 2 GB ram)

I have stripped my services to bare minimum with help from http://www.blackviper.com/WinXP/servicecfg.htm (I have no internet connection on laptop so I was able to disable ~90% of it). I also tune up everything according to musicxp.net. I only have 1 program on that PC (Live 7.0). My disc is fully defragmented.

So when I start my project in live 7.0 with my soundcard at 64 samples, everything seems to be perfect at the begining, but after some time I start to hear random clicks (relatively rare, 1 click per 20 / 30 seconds). After some time I start to clearly feel delay between hitting my keyboard and hearing response.

I have like max 8 - 10 tracks, no vst/vsti, only Live effects (few), 2 midi tracks, the rest is audio clips. But even with 2 tracks I'm experiencing this.

When I rise ASIO buffer size to 256, clicks disappear.

Anyone have an idea what can be done to achieve minimum buffer size (with minimum latency) at this point? this is critical for my setup.

PS: sorry for my english

edit: sorry, I use 1 vsti - Novastion V-Station

anyone?

Maybe I should also post my setup.

I have Korg padKontrol connected by USB and M-Audio 1814 by firewire. DVD drive is not disabled, beside this every internet driver/service/hardware is disabled. Laptop is single core. I run audio at 44.1kHz sampling rate.

Also I think that dropouts occur more often when i play midi (if there's more notes)

yoyek wrote: Well, my goal was to adjust lowest ASIO buffer size on my M-Audio 1814 (64 samples) on my Laptop (1.6 ghz, 2 GB ram)

When I rise ASIO buffer size to 256, clicks disappear.

Anyone have an idea what can be done to achieve minimum buffer size (with minimum latency) at this point? this is critical for my setup.

You have your answer right there. 256 is the minimum buffer for your setup, and should be playable.

After some time I start to clearly feel delay between hitting my keyboard and hearing response.

Change your midi driver type in the preferences to mme if it's set to direct. It's in the preferences, press the little triangle next to your midi controller.

you'd probably need a faster processor to achieve lower-latency, though a faster processor would not guarantee this.

djgroovy wrote:Change your midi driver type in the preferences to mme if it's set to direct. It's in the preferences, press the little triangle next to your midi controller.

Thanks, I'll try that.

djgroovy wrote:You have your answer right there. 256 is the minimum buffer for your setup, and should be playable.

Well, for me it's not. It gives my about 20ms latency which is strongly noticeable when you play faster drum parts, it's little comfort to play at that latency (I'm a drummer). But I will definitely check that MME option.

pj_player wrote:you'd probably need a faster processor to achieve lower-latency, though a faster processor would not guarantee this.

Hmm... and what will?

RME soundcard!

Ok, I have checked everything, and it seams that my midi controller is the problem. I have preformed latency checks (following http://ntrack.com/wiki/index.php/Latency) and results where kind a strange.

I got 25ms latency with Alesis Control Pad, way too much for my needs. Then I checked my Korg padKontrol - 16ms. Repeated it few times. WTF?

Uh... So it seems that Alesis make some hardware delay effect for drummers. Stay away from this product.

Do you have any recomendation for midi drum pad like this one? (I need only midi controller, without buildin samples like Roland SPD-S)

And yes, I will look at RME soundard next time, probably Fireface 800.