Currently Being ModeratedJan 7, 2013 3:21 PM (in response to plasticdemon)
Just out of curiosity, what happens when you use a small process buffer.
If it's no help go back to your original settings.
That's a hard drive "Use" meter, it's not unusual what you're seeing. When you start Logic it grab's the audio off the drive filling the buffers, this causes a spike in the drive use meter.
What's not normal is your comment: " It either just doesnt work or it leaves me with and audio block full of white noise." This should not happen.
Currently Being ModeratedJan 7, 2013 3:43 PM (in response to Pancenter)
Changing the process buffer to small didn't seem to make any difference.
I'm glad you said that what im seeing is normal cause i was beginning to worry. I did say when bouncing midi to audio late on in the project, i do get moments when it either just doesn't work or it leaves me with an audio block full of white noise. Its was kind of like Logic is saying to me.. " Im struggling " but the CPU doesn't move at all. ? However, it doesn't do it anymore since ive moved the project file to the external drive.
So thats fixed, i was now concerned about the clip on the HD monitor. But if you say its normal, i will leave it at that and keep my fingers crossed that I don't have any further issues.
Thank you very much for all your help.
Currently Being ModeratedJan 7, 2013 4:27 PM (in response to plasticdemon)
It's not really a "clip" meter, think of it as a hard drive access meter or hard drive use meter. What would be a sign of very heavy use is if it ran constantly red, then you might see some problems related to pulling all of the audio data off on time. A blip into the red is completely normal.
The "white noise" or "not working" problem was probably related to the operating system writing swap files to the same drive the audio was on, moving the project fixed that... I think you're ok. Go back to your original setting in Preferences/Audio.
Currently Being ModeratedJan 8, 2013 10:45 AM (in response to plasticdemon)
In case this was missed, as no one directly commented about your settings...
Assuming you are running Logic 9.x as I didn't see it mentioned specifically by the OP......
As you have 16GB of RAM you should run Logic in 64bit mode to properly benefit from that extra memory.
Otherwise you are limiting Logic to roughly 1.8GB of usable RAM once Logic is loaded and all the various overheads have been taken into account.
Also, if you are using Kontakt, make sure you then turn off Kontakt's memory server (See Kontakt's Preferences) as it is no longer needed when running Logic in 64bit mode...
Currently Being ModeratedJan 10, 2013 12:55 PM (in response to plasticdemon)
Quit Logic, now select the Logic program icon, press command-I and the info about Logic will pop up, here you will get the option to have 32 bit selected, if it ain't you're in 64 bit mode. Hope that's clear!
Currently Being ModeratedJan 10, 2013 1:06 PM (in response to kcstudio)
My system was working like a dream but now it's decided to start doing what it was doing before I got the new external HD and memory. I now keep getting " Disk is too slow or system Overload " (-10010 .. Message .. .
I'm running the project files from the thunderbolt and all the synths so my system should running perfect but it's started playing up ..
Currently Being ModeratedJan 10, 2013 1:29 PM (in response to plasticdemon)
Just a thought...
At this stage it may be worth checking the actual speed of your Thunderbolt external drive. Whilst the Thunderbolt interface should be capable of super high data rates, the drive itself may not.
As a free and quick method: