Realgrey

@Eric Cardenas was correct ... working from the system drive (SSD) makes a huge difference. So I think I've narrowed the problem to the Lacie. I ran "First Aid" (system utility app) and it does seem to be performing a bit better. So ... I guess the conclusion is a dedicated SSD to record to. Thank's to all. Much appreciated.

I'm away from the studio currently, I'll know tonight ... I'll mark the conversation resolved after I test.

@Eric Cardenas Great suggestion ... I could even write a close script w/ Audomater that would move it for me post session. I will give that a try.

Jfever, Thanks for your reply ... My hard drive is a Lacie 2big 6TB. And yes, it is divided into a partitions ... It is connected via TB to my mac pro ... I don't have it configured as a raid, it's really 2 3TB drives side by side. The drive I record to does have partitions. Is that a problem? Thank you kindly for your questions. Hard drive spec http://www.sweetwater.com/store/detail/2bigTb2-6TB

============================== The System ============================== Mac Pro 3.7GHz Quad-Core 32GB RAM El Capitan OS X https://support.apple.com/en-us/HT206770 Logic Pro X 10.2.4 https://support.apple.com/en-us/HT203718 UAD Console 2.0 Interface Config + Silver Apollo Thunderbolt Card + ADAT to/from Focusrite Octopre Dynamics MkII + Apollo 16 MkII + Apollo Twin Duo Lacie 2big 6TB http://www.sweetwater.com/store/detail/2bigTb2-6TB ============================== The Problem ============================== “Disc too slow or system overload” issue w/ Logic has persisted since I bought the computer last year. What We’ve done: + Updated the RAM (32GB) in the Mac Pro + Optimized the processor allocation in Logic to use all 8 cores (actual & virtual) + We freeze all midi tracks + We save after every take What ha’happn ‘iz + Every time we start Logic the HD monitor spikes … it doesn’t always throw an error but it does spike every … Is that right? + The frequency of system error during playback and record has increased. More noticeable with bigger project files. + Increased occurrences when we updated to to El Capitan OS X Sometimes it seems like the HD goes to sleep and when it’s waking up the error occurs. Is that possible? How would I prevent that from happening? I’ve read that some just use a solid state drive as a recording disc … I’ve just invested a buttload in the 6TB 7200 RPM HD … I would have to buy separate controller to retrofit w/ SSDs … I’d want to prove that concept before investing. ============================== The Context ============================== We have a project recording studio and used logic. We have protools, and don’t seem to have issues w/ it but the bulk of our work is done in Logic. We are doing more and more live recording w/ paid artists so the loss of a take can be costly to the creative flow and financially too. I’ve have the configuration of how our gear is wired up and am glad to share that as need be. Any help would be greatly appreciated. System Config Illustration https://www.dropbox.com/s/7vr06yt8iz7hou2/RonFlack-TB-config.jpg?dl=0

Since upgrading from Snow leopard to Mavericks, Logic 9 seems sluggish but it's functional. After I used Mavericks for about a week I also upgraded to Logic X. Logic X has been unstable in the following ways: + Occasionally, recorded audio regions don't display visually but will playback. + I'm getting what sounds like syncing pops in both software instruments and recorded audio. My system is configured as follows: iMac, Mac OS X Mavericks, Core2 duo 2.66 8GB, Logic X My UA Apollo is slaved to a Focusrite Octopre MKII dynamics I'm committed to Logic X, I can't go back so any help would be greatly appreciated.

A kind thank you Jordi, Your suggestion to use the event editor was a quick solution. For reference sake, shift E is the key command for "Select Equal Events" once in the event list.

I've imported a Sonar MIDI file in Logic 9. The file opens in Logic and plays correctly ... except it appears that the sustain pedal data is inverted. When I open the midi editor and select sustain pedal it appears to be 0 when it should be 127 and 127 when it should be 0. Is there a way in logic to reverse the entire sustain performance in one pass? Any help would be greatly appreicated.