Ableton Forum

Timur wrote:If you can then use AERO Grobe, it's just an imperfect workaround, but better than nothing.

With aero enabled or disabled, the cpu usage of metters is absolutly high !!

has any still had crashes with Reaktor on 7.0.5???

Dj-Grobe wrote:

Timur wrote:If you can then use AERO Grobe, it's just an imperfect workaround, but better than nothing.

With aero enabled or disabled, the cpu usage of metters is absolutly high !!

Same happens for me with a combination of Vista, Nforce4, Fireface 400, Onboard Firewire and Live (6 or 7). I can't even play a single audio-clip without drop-outs and CPU-load increasing as soon as Windows is busy doing anything in the background (especially Windows Explorer).

But both the M-Audio Audiophile and Creative X-Fi have less of a hassle (still way more than I like, and they're only useable with AERO).

Using Reaper with the very same combination of hardware and Vista runs without any such obvious problems. Ableton wants to blame the NForce4 (since they can't think of anything else, which I tend to disagree because Live runs with XP via the same setup and Reapers runs with Vista, too), RME blames anything but the Fireface (since Reaper runs smoothly via the same setup, which I tend to agree to).

I'm with you Timur.

I wrote to Abe's Support and they basically imply that my card is the problem (PreSonus Firepod). Their response didn't even seem that they looked at the configuration or log files I sent them. Using Reaper there is no issue. Measuring the buffer requrements using the method outlined in the tutorial is not adequate to avoid the occasional dropouts and I've had to up my buffer by a factor of 3 (to 178 samples) to get reasonably clean MIDI operation. (It still has occasional dropouts).

If my hardware works fine with Reaper at very low latency, why can't I achieve this with Live 7?

Great update!
Loading time is much much faster on my Macbook Pro 1.87ghz