OzzCaesar Posted September 20, 2011 Share Posted September 20, 2011 Hey, I just started working on logic after many years of cubase, long story short, started this project, 17 channels, 16 bars. suddenly everything stops and this msg pops out saying: Disk is too Slow or System Overload the mac: MacBook Pro (13-inch, Mid 2009) 2.26GHz Intel Core 2 Duo 2GB (two 1GB SO-DIMMs) of 1066MHz DDR3 160GB Serial ATA; 5400 rpm OS X Lion 10.7.1 is there any reason for the system to overload? I know that 5400RPM is nothing nowadays, but still. Quote Link to comment Share on other sites More sharing options...
Rev. Juda Sleaze Posted September 20, 2011 Share Posted September 20, 2011 How many tracks are software instruments? What's your buffer set to? Quote Link to comment Share on other sites More sharing options...
OzzCaesar Posted September 21, 2011 Author Share Posted September 21, 2011 ur right, I did miss out a few crucial details. 5 virtual instruments, although they are all muted. everything is bounced down to audio. everything is recorded and running 24bit, 96K Also forgot to mention that i'm using a MOTU 8pre Sound card. and directly to your question Juda, 250 Quote Link to comment Share on other sites More sharing options...
fisherking Posted September 21, 2011 Share Posted September 21, 2011 24/96, so you're working things hard. reboot. open nothing BUT logic. should help a lot (works here when i get those error messages)... Quote Link to comment Share on other sites More sharing options...
jerzyb0rn Posted September 21, 2011 Share Posted September 21, 2011 I'm no logic expert, but when i record a virtual instrument to audio i always bypass that instrument not just mute. I believe it still sucks up cpu if its only muted, thats my personal experience though. Quote Link to comment Share on other sites More sharing options...
Rev. Juda Sleaze Posted September 21, 2011 Share Posted September 21, 2011 Yup, unless the regions are muted, the software instruments will still play. Try doing a "save as", delete all the software instruments and up the buffer. Quote Link to comment Share on other sites More sharing options...
lookatthisguy Posted September 21, 2011 Share Posted September 21, 2011 If memory serves, muting regions saves CPU, muting channel strips doesn't. Quote Link to comment Share on other sites More sharing options...
OzzCaesar Posted September 22, 2011 Author Share Posted September 22, 2011 first, thank you all for the replays. the regions are muted and the instruments and bypassed just for the point of it, about the 24/96, I'm not compromizing about that one. there is nothing on BUT logic, and still - same error. how could I identify which hardware is failing? oh, and how can I clean the buffer? Quote Link to comment Share on other sites More sharing options...
triplets Posted September 22, 2011 Share Posted September 22, 2011 Playing everything from the internal drive? At 96k? 5400 rpm? Maybe you're killing the HD. Put the project on an external FW800 drive, if you have one. If you don't, think about getting one, conceptually to take load off the internal HD. Quote Link to comment Share on other sites More sharing options...
lookatthisguy Posted September 22, 2011 Share Posted September 22, 2011 I can't say for sure, as I'm not using it, but I wonder if Lion is tasking your drive more than anyone would expect… I mean, a lot has changed since Leopard, which is what that model originally shipped with (whether you bought it then or not), and I can't imagine recording/streaming 96K prints from a 160 GB, 5400 rpm system drive. For the sake of experimenting, do you by any chance have an external FW drive you can move the project to, to see if that helps things out any? Quote Link to comment Share on other sites More sharing options...
Rev. Juda Sleaze Posted September 22, 2011 Share Posted September 22, 2011 first, thank you all for the replays.the regions are muted and the instruments and bypassed just for the point of it, about the 24/96, I'm not compromizing about that one. there is nothing on BUT logic, and still - same error. how could I identify which hardware is failing? oh, and how can I clean the buffer? Well, I'm not sure why anyone would bother with 96kHz, but if you're set on it, I think triplets is right about needing a better HDD. I wasn't talking about cleaning buffers, you said you had the I/O buffer set to 250, by which I presume you meant 256. Try increasing it to 512 or 1024 samples. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.