Protone Posted January 11, 2013 Share Posted January 11, 2013 Large project (120 tracks), but everything was smooth yesterday when I saved and quit. This morning I opened the project, and as soon as I hit play, cpu spikes and project stops! I have seen this before, but normally restarting logic solves it. Now I have rebooted several times, trashed preferences, tried different buffer sizes... Nothing helps! And I´m not on heavy VI-track when I try to play. Also, hd is fine, 300GB free space and other projects run ok. I have deadline today, so this is getting really scary now! Any ideas, anyone???? ps. Running 64bit. Link to comment Share on other sites More sharing options...
Eriksimon Posted January 11, 2013 Share Posted January 11, 2013 Have you tried freezing some tracks? You say this morning you opened the project - was that right after your Mac booted, or was it still on? Anyway, the very first thing I'd try is quit and reboot the Mac. After full startup, let it sit for 5 minutes, then start Logic. In your project, make sure you select an audio track or a frozen instrument track, not a live instrument track. You may have to hit play a few times to "educate" the buffers. Link to comment Share on other sites More sharing options...
Brendan Ross Posted January 11, 2013 Share Posted January 11, 2013 I have the same problem even if I have just 1 track of audio. (no fx, software instruments etc) I have to insert a external midi track and highlight that track before the project will play. This might get you through the day but it's a pain. Seems like a bug. Anyone out there have a more permanent fix? logic 9.1.8 3.4 GHZ intel Core i7 32GB ram mac OS 10.7.5 Link to comment Share on other sites More sharing options...
Eriksimon Posted January 11, 2013 Share Posted January 11, 2013 Well, this has been reported by a number of people, but there's an even greater number of people who have never had this issue and are not able to reproduce it (I haven't). All I get is a sometimes as long as two seconds latency (with buffer at 128), which always clears up by restarting coreaudio within Logic. I only ever get this when using other apps (that use coreaudio) while Logic is still open. Of course, this apparent random occurring of this issue makes it a lot harder to troubleshoot & solve. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.