Ableton Forum

What can I do to avoid that? I rewire Live into Sonar. I play about 10 samples at the same time in Live. How can I avoid getting the "Hard Disk Overload Indicator" ?

Thanks for any advice.

what kind of specs does your harddrive have?

72000rpm and greater is a must (helps a LOT).

get more ram too.

Superchibisan wrote:what kind of specs does your harddrive have?

72000rpm and greater is a must (helps a LOT).

get more ram too.

I have a 7200 RPM hard drive. Live is using very little RAM. This does not seem to be the problem.
I also did a disk defrag. The problem seems to be between Live and its ReWire master (Sonar in my case).

Well, at least that's what I think. Because the problem barely occurs when playing the song.
But happens all the times when mixing down the song. Why would there be a hard drive overload when mixing down?
The applications should be taking the time it takes to mix down. Even if it means taking longer to read the HD.
So the HD should not be overloading when mixing down in my mind.

I sent an email to support.

yeah, not sure... sounds like you got yourself a bug

Superchibisan wrote:yeah, not sure... sounds like you got yourself a bug

I found this interesting thread on KVR.

To fix the problem, I could:

1. Select RAM on some clip so they are loaded in memory.
2. Freeze some tracks. (I found this suggestion somewhere else... not sure though?)



Since my clips are very big 32 bits WAV files, I decided to freeze the tracks.
I froze 1 track: it took about 15 seconds getting to 90% then another... 2 hours to finish!!!

I am not sure how ReWire works exactly, but in my mind, when mixing down, there should not be a "Hard Disk Overload". But it is possible that Live has no idea it is mixing down when used as a ReWire slave. Don't know.

Weird... I'll keep looking.

BB King wrote: I found this interesting thread on KVR.

To fix the problem, I could:

1. Select RAM on some clip so they are loaded in memory.
2. Freeze some tracks. (I found this suggestion somewhere else... not sure though?)

Nope. That didn't help in my case. I really don't get it.
I'm going to wait for a response from Ableton support.

In the end, what did work for me was to deselect the "Fast Bounce" option when exporting my track in Sonar.
(the problem was occurring when I was bouncing my track)