sasebastian

@Eric, on the second screen I typically have a mixer plus Reason or a couple plug-in windows. For plug-in instruments s I use a lot of Logic ones plus Kontakt, Reaktor, Massive, Absynth, BFD, Ethno, For FX on the inserts I use a lot of the Logic ones plus Amplitube and other IK stuff, Drumagog, DUY… Like I said above, I could have only Logic open on screen 1 with Safari on screen 2 and have this problem.

Yeah, it is weird. I work in FCP and Motion across the 2 monitors with no problem. Also Photoshop and Illustrator… all good. Just Logic that's a pain. updated original post with this... OSX 10.8.5 (also happened in 10.7.x) MOTU 896HD

In Logic 9.1.8 on my Mac Pro with dual monitors, Logic will freeze up and become non-responsive after I do anything in the secondary monitor. This has been happening since the first release of Logic 9. At first I thought it was because of a large project or a plug-in open or when Rewired in to Reason. Recently I found out that I can consistently reproduce this with a project with one track in the Arrange window. Example. SETUP 1) Monitor 1 has the main Logic window with the transport. Monitor 2 has a Mixer window. 2) The song can have as many as 24, 36, 48 (whatever) audio, MIDI or Software instrument tracks, or as few as 1 audio track. SCENARIO 1 3) Start the song. 4) Adjust the fader on any track in the Mixer on screen 2. 5) Press the space bar to stop the song. The song doesn't stop. 6) Press the space bar again. The song doesn't stop. 7) Wait several seconds. the song will stop and start again. 8) Click on stop in the transport in the primary monitor. The song will stop. SCENARIO 2 3) Start the song 4) Adjust the fader on any track in the Mixer on screen 2. 5) Click on Mixer in the main Logic window In the primary monitor. The mixer is not displayed. 6) Click on Scorein the main Logic window In the primary monitor. The score is not displayed. 7) Click on stop in the transport in the primary monitor. The song will not stop. 8) Wait several seconds. the Mixer will display, the Score will display and the song will stop. The second monitor could have anything there. I typically have Reason, a Mixer and Plug-ins in the secondary monitor. I could even have a Finder over there, and as long as I touch it with the cursor and go back to the primary monitor Logic will become unresponsive. Has anyone seen this behavior and know how to fix? I have been searching the boards forever and haven't seen anyone report anything similar. I have been using Logic since 5 and 9 is the only version I've seen this happen. Configuration: Early 2009 Mac Pro 2x 2.26 Quad Xeon 24 GB RAM Logic 9.1.8 Songs on dedicated drive for projects and audio. OSX 10.8.5 (also happened in 10.7.x) MOTU 896HD (added OS & Audio interface)

Thanks. I just discovered my problem was related to Novation Automap needing to be updated. Once I update to the latest version of Automap the slow disk errors went away. Maybe you have some older plug-ins that need to be updated.

My problem was related to Novation Automap needing to be updated. Once I update to the latest version of Automap the slow disk errors went away.

Having this same exact problem. New Quad 2.8 i7, 16GB, SDD. Press play and 2-3 seconds in I get the sam e message. I open the CPU/HD meter and the HD is pegged, CPU is fine. Is this an SDD issue?

Did you solve this problem? I just bought a Macbook Pro 2.8 Quad i7, 16GB with 512 SDD and have the same problem. CAn't get Logic to play. The song is really light, too. 8 tracks, a couple plug-ins. No mas.

I have been seeing this same issue, but when I edit across 8 or more tracks that are grouped with edit, phase lock enabled. I make the in/out cuts and move the regions to another later in the song. The error is thrown when the play head gets a bar or two before the copied region. I posted the details on the apple boards at http://discussions.apple.com/thread.jspa?messageID=10254723 Still not resolved