Play/playhead issue with Logic Pro X 10.5

Apple .... HELLO?! Earth to Apple?!! Middle of an economic collapse and my method of revenue generation has been taken from me by this bug. What's really annoying is that my system updated without a prompt overnight while I had a current project running. It'd be great to see someone from Apple support say something and give an ETA for a fix or offer a refund since they like being so politically correct. ...Yes I'm ******. sorry.

I also have this problem. It can appear from anywhere between 10 seconds to an hour into work, usually closer to the former. I have no Spectrasonics products installed and this appears to occur randomly.

Definitely did that on the form. Maybe its time someone at apple was assigned to watch the forums, not necessarily to comment, but since a multibillion dollar company just broke one of their flagship apps - maybe would be a nice idea. Bit shocking to see how many people are affected. We cant pinpoint the cause, but its definitely a thing. This is going to scare people off the DAW. In terms of my own case I'm a Live user mainly for the last 5 years (after being with logic for over 10 years) and due to this update I was totally debating coming back to use logic as the main, but now Apple's absence of responsibility and support on this is truly shocking.

I'm sure people from Apple Support read the forums. Just not in any official capacity. It remains true, though, that the best way to get this problem fixed is to file a bug report. And call Support on Monday morning. Just be patient and compassionate. It's not the support team's fault, that's for sure.

jsdigital wrote:

I'm sure people from Apple Support read the forums. Just not in any official capacity. It remains true, though, that the best way to get this problem fixed is to file a bug report. And call Support on Monday morning. Just be patient and compassionate. It's not the support team's fault, that's for sure.

Yes, well said.

The more people that file a bug report and call Apple the sooner a fix will arrive.

My personal feeling is, it's a bit amateurish to use your User base as a Beta Test team.

Same issue here. It happens very randomly but has a tendency to get worse over the days/hours.

I'm working on a big orchestral project with lots of midi tracks, on a MBPr 15" late 2013, OSX Mojave.

I've submitted a bug report.

Meanwhile, I'll restart my machine and switch back to 10.4.8 if it happens too frequently.

Fingers crossed for a fix, my friends...

Apparently apple knows about it! I found this video on youtube: https://www.youtube.com/watch?v=TtkJ1Iiyxuo&feature=youtu.be&t=1214 (20:20 min). The guy has the same issue and said, he received a mail directly from the logic team.

Hopefully we will get the update soon but maybe it's pretty complicated to fix this...

Interesting. That particular midi pattern issue he’s showing in the video doesn’t always apply to me. Once the issue starts, even if I move the play head to an empty part of the project, it still won’t play.

Could it be key command corruption?

Perhaps some midi data is being interpreted as a stop command. Logic can send midi reset data or note start data for long notes even when there are no new notes sounding.

That's a great thought. I did play around with some midi settings last week when this problem kicked off. I've also tried disconnecting/uninstalling all midi controllers with no luck. It does behave somewhat like a hung "stop" command. Then again, this problem has been arising often between pressing "play" and doing almost anything else. There's no common denominator or unique key command involved, other than the spacebar.

A hint : it seems that the playhead bounces a little frame back and only plays the portion between this start frame and the initial position.

This bouncing back is driven by a general parameter : Preferences > Audio > General > Compensation (all) & Playback pre-roll (ticked)

I have unticked pre-roll and switched compensation to Audio & Software instrument track setting.

Since then, LPX crashes at playback (it says the culprit is Orchestral Tools’ Sine engine). Yet again, it’s a big project I’m working on at the very limits of my machine.

I’d like to know if this setting fixes your issues.

I had copied the previous LPX in a separate applications subfolder before updating ; so I’ve switched back to 10.4.8, was able to reopen my project (forward compatibily is nice !). I only lost my Quick Sampler track... not totally since I froze it. So I’m able to complete my project with 10.4.8 and will keep an eye on a possible fix (yes you can have 2 versions of LPX running on the same machine).

The bouncing back itself isn't an issue. It happens, but that's a symptom, not the problem. It's critical for most of us to keep our plug-in latency accurately compensated for. Otherwise things start to get out of sync with busses and auxes.

I’m experiencing this big across 2 different Macs on 2 seperate projects. Both projects are entirely different, different plugins and even deleting all tracks and leaving a blank audio or midi tracks still causes this issue. Once it’s in the project, it seems to be baked in! Thankfully, The only 10.5 features I’m using is step sequencing that can be converted to midi. These projects can then be opened fine in 10.4.8. I’ve submitted feedback. I first thought, like many of you it was related to midi inputs or possibly key commands but after many different tests, it is not. It also has nothing to do with resource heavy plugins - it’s happened on projects with 2-3 tracks.

Quick update: after following Apple's advice to update to OS 10.15.5 from Mojave, reinstalling LPX and all of my third-party plugins, the bug is still persisting. I have followed up again with Apple support this morning. I'm willing to bet all the money I've been losing over the past two weeks that they won't have anything substantial to say - no ETA, nothing; just "wait".

Add me to the list. Logic 10.5, Catalina 10.15.5. Exactly as you’ve described; start-then-stops, record will get it to play back, nothing resolves it but a restart. I had high hopes for 10.15.5 Catalina update To fix this, but it’s definitely still happening. Do something soon please Apple, this is debilitating.