Play/playhead issue with Logic Pro X 10.5

Happens to the artist Jacob Collier here @43:30 https://www.youtube.com/watch?v=sRIjprauHgk&t=2629s

He's using a Mac Pro with 384 Gigs of RAM (but is also churning through a ~700 track Logic file, lol)

I just spent 2 and a half hours with Apple support and I spoke with several really nice guys. We did some tests and it seems like creating a new user will "fix" the issue. Obviously it isn't ideal, but I was able to replicate the bug on my main user with him but I was not able to do so on a new test administrative user we created. It could be coincidence but I wanted to post this as a potential temporary solution.

The problem for me seems to happen when "play from Marquee selection" is checked. When I unchecked that the problem went away. You can access this by control clicking on the play button. Is this a new Logic option? I remember when I started on Logic long before Apple this behavior wasn't available so I always used a key command to take the playhead to where the marquee is. At the very least this could be a workaround for everybody that this is driving crazy. That said I only tested for 5 minutes but the problem seemed to be gone.

Catalina 10.15.5 “supplemental update” just released. Gonna try it. Nothing has worked for me regarding this issue yet, so why not. NOTE: after updating, Logic took a very long time to first load up 🤔. Testing now.

Yes, the bug is still ongoing unfortunately. The only workaround seems to be using the "record" button on a midi track, which will then playback normally. We're all still crossing our fingers for a patch ASAP. Keep filing those bug repots!

I have 10.4.8 which is the last stable release. If you contact me on Discord at vissequ#1301 we can talk about that.

I got an update from Apple today and they said the engineers have been informed of the bug and are working on it. Even though people posted here and submitted reports they seemed to not be aware of it until I called. I'll have another update from Apple this Saturday.

I know we are all annoyed with this bug but just on the positive side it seems like Apple is actually taking this seriously. They were very knowledgeable and spent a lot of time with me and I could tell they wanted to help. They said they'd call me back at a certain time and they did exactly that. So the good news is I do think we will get a fix relatively soon.

Thanks for the update. I have submitted 2 very detailed bug reports and have not had a response. In the past, my logic bug reports have always been followed up to some degree. I know many others that have submitted reports and haven’t heard anything.

You're very welcome. I would recommend calling in the future. I thought I would get somebody reading from a script but if you tell the robot you're calling about Logic they actually connect you to a bunch of very knowledgable musicians which is super dope.

Really appreciate the offer! Deleting the app, /Library/Application Support/Logic, and /Library/Audio/Apple Loops solved the issue for me. Re-downloaded from the App Store and re-downloaded the loops. No stutters in 6 hours!

That's correct. Init key commands will not help. The benefit he or she is experiencing is simply from restarting the program. With the 10.5 bug there is really no correlation to any user action that we have been able to detect and it appears to be purely random. When it doesn't work all you can do is restart it and hope it works the next time. The odds are it will but obviously this is terrible for any artistic workflow and untenable for any producer.

I do not think this is an effective solution to the problem. I'm not an engineer so honestly I don't know, but when I was on the phone with Apple we tried various play settings and none of them helped. If you continue to have success with this please let us know as it could be a temporary fix for the bug.

I had the exact same problem as you described. Woke up one morning the update was there and that’s what all this mess started for me! I posted what works for me. Others are saying that they’re having it with new projects at the start in 10.5. But this works for me if you can see my post I don’t know if you can see it? -it’s been running really well now. Better than the previous version ever ran on the same computer.Try my fix see if that works for you just got a clean up all the existing data that’s not being used is what I believe that was written in the previous version before 10.5

You may be right however I don't think that's the case, regardless I really appreciate the advice. I would definitely try it right now but I've already switched back to 10.4.8 and I'm not touching 10.5 until engineering has fixed the bug lol