Built in click or clicktrack? Stability? "DIsk Too Slow"

Question

Level 1

0 points

Built in click or clicktrack? Stability? "DIsk Too Slow"

I've had a lot of issues with "disk too slow" messages while tracking through Amplitube or Waves SSL. And when I got these messages I've used the built in click/metronome (klopfgeist).

But then I started using an audio clicktrack by bouncing out klopfgeist to a seperate audio track and then using that in the project. Thus NOT using the built in click. And since then I haven't got any "disk too slow" messages.

I'm wondering if anyone else have experienced this, and if others could try this. I have now been running for half a day with several Amplitube tracks and NO "disk to slow" messages what so ever (know on wood).

Mac Pro Quad 2.66 2009, Mac OS X (10.6.4), 6GB RAM

Posted on Oct 18, 2010 5:22 AM

Reply

Answer 1

gardinen Author

Level 1

0 points

Oct 25, 2010 11:43 PM in response to gardinen

Thought I'd bump this thread since it's quite a big deal for me.

I've had the "disk too slow" issues for about a year now using Logic 9 and Amplitube 2 and 3 about every day. And since I've starting too export the click and use it as an ordinary audio track, I've not seen the "disk too slow" message once.

And it's been two weeks now. Would be nice if someone else could "create" this issue.

Reply

Answer 2

Eriksimon

Level 6

15,416 points

Oct 26, 2010 5:10 AM in response to gardinen

Try making a clicktrack using a different instrument (any EXS24 drumset using a sidestick or rimshot-like sound, for instance), see what happens. Klopfgeist is a Software Instrument, and if it drives your system into overload, it tells me that your setup is already close to overloading anyway. However, if it is the case that the Klopfgeist Instrument is drawing more CPU than the EXS24, something isn't right with Klopfgeist.
I hardly ever use it, I just choose an appropriate (drum- or percussion-) loop to play along to.
So what do the CPU meters indicate when you run your overloading projects with Klopfgeist bypassed? Big difference?
I cannot "create" the issue because I do not have Amplitube. But if it is comparable to other Amp sims, they can be CPU hogs, depending on how heavily you use them and which parameters are active.

Reply

Answer 3

gardinen Author

Level 1

0 points

Oct 26, 2010 7:30 AM in response to gardinen

Well, I'm using a Mac Pro 2.66 (2009) so Amplitube 3 draws about 25% on one core in LIVE mode (64 samples buffering with RME AIO)

One track of Amplitube 3 and the Klopfgeist running would cause "disk to slow". It can happen within 5 minutes or 50 minutes, but it WILL happen. And the CPU meter (in Logic) is still at 25%.

Using an AUDIO clicktrack however, I'm able to run like 5 Amplitube's plus a sixth LIVE one, together with Superior Drummer and various other software instruments running all day long. No "disk too slow" messages at all whatsoever.

I'm a very happy guy now since I've manage to find a solution to this problem, because I've been looking for one the past 12 month or so. But it would be nice if this "bug" could be solved.

Reply

Answer 4

Eriksimon

Level 6

15,416 points

Oct 26, 2010 7:57 AM in response to gardinen

There could be something wrong with Klopfgeist here. I hardly ever use it though, and imho the "disk too slow" error makes no sense, since Klopfgeist is not reading anything from disk, it ain't a sampler! "Disk too slow" is always related to (the inability to) reading audio files, be it samples or recordings or Apple loops. So I somehow am sceptical about Klopfgeist being to blame, however, if you can reproduce the error consistently and only with Klopfgeist, I'ld have to review my scepsis...

Reply