Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

Weird copy and move behaviour in Logic 10.7.7

Hi guys,


Got a weird problem that might be two problems, which have only turned up since I updated my system in Dec 2022. Previously had a MacPro 5,1 running Logic 10.4.4 under OS10.12. Now running Logic 10.7.7 on a MacStudio under OS12.5.1.


I mention both systems because this never happened on the old system, and it’s driving me bonkers on the new system.


Sometimes, I record some midi, and the notes don’t play back. I open the piano roll, and they are there, but they don’t play. Other midi on the track plays as normal. I then go to another track at the same point in the song, and record the same notes…and it won’t play those either. If I go to elsewhere in the song, and drag-copy midi into the “dead zone”…those notes won’t play either, despite working in their original location. But…stuff that was already in the “dead zone” before it became “dead”…those regions continue to work as normal. This only happens with songs I’ve been working on for a while. I haven’t experienced it with a new file opened from my user template.


Now…the other thing that may or may not be related. Often, when the above behaviour is going on, I’ll find if I record midi onto a new track, that I can only drag that new region horizontally (ie, on the track on which I recorded it) but not vertically to another track.


What the heck am I doing wrong, guys? Is this a known bug? How do I fix it? I’ve been using Logic since version 1.0 (on an Atari!) and I’ve never seen this behaviour before!

2 replies

Hi guys,


Much faffing about later and I suspect that what happens is that the actual song file becomes corrupted...if that is possible.


Opened my default template this morning, copied all the tracks from the misbehaving song into a clean template, and everything now works. Takes about ten minutes to make the change (my songs are pretty minimalist for how big they sound), but it's not something that should happen...it's only midi data after all.

OK...the above was a temporary solution. Couple of hours of midi recording/arranging and the old problem is back.


What SEEMS to have fixed it is trashing 10.7.7 and reinstating 10.7.5.


Been working for six hours on a single song and everything APPEARS to be working perfectly.