You mean 4GBs of RAM right? or that you only have 4MB of space left in your hard disk?
Is your disk faster than 4200 RPMs? Are there any background processes running ?
I have the same problem. 2.33 GHz Core 2 Duo, 2 GB RAM, 160 GB HD MacBook Pro. Lots of free HD space and no disk errors/issues. No other apps running. Recording quits after about 10 seconds with this error. -10005 is the error code.
Same for me, new (ok, not any more, bought too early) 17MBP (2,93/4GB, fast HD). Plus GB tells me there are too many open tracks (tracks? Spuren in German). But the same setting worked three years ago ...
I got those errors with my old 15MBP as well, once I changed to GB 09. Hoped it would stop with the new machine. Didn´t.
That is extremely annoying for me too.
MBP 2.53, 4 GB, 320GB 7200 HDD
One audio track is playing and it stops... While Cpu shows 80% idle, and 2,5GB of free memory.
What the ****. This is a serious issue and needs to be addressed.
It is not while playing, it is while recording my podcast. Just the basics are active, like the trailer. It does not matter, if I already imported background music, but normaly those tracks are empty. But recording stops, error too many tracks. (And sometimes I do not realize and keep reading ... 🙂
I think the key question here is what type of drive are you recording to? Is it the internal drive on your mac? or an external one? If external, is it USB2 or Firewire. I experienced this problem once on an external firewire drive when I was editing a massive (18+ track) project. I moved the project back to my system's internal drive, and the problem went away.
Also, if you look under Preferences in GB, what audio quality setting are you recording at? When this happens, are you recording multiple tracks at once? Do you have any plugins assigned to the track as you record live? Or, is the track completely dry?
Another thing to consider would be having Activity Monitor (Applications -> Utilities -> Activity Monitor) open while you are recording. It will show you your RAM, CPU, and Disk activity. Do you see one of these 3 things spike way up when the error occurs? That may help point to what in your system is the culprit.
Nothing special: I record on internal HD, 7200, on just one track, without any non GB-plugins, just some filters, and no suspicious spikes in Activity Monitor.
Do you have GB monitoring the output of the track back through speakers or headphones? Does the problem happen if you try recording without any of the GB plugins enabled and the track completely dry?
No monitoring, but I didn´t try "dry".
Good idea, seems I´m stubborn.
What amazes me is that a new, faster machine with all the updates plus a version of GB produces old troubles. How is life with Logic? Would you recommend it, just for podcasts?
