Apple Logic Pro 10.7.9 is released

[chagzuki]

Chagzuki as a result of the separation of Logic from the AUs in the latest versions of MacOS LOgic doesn’t know anymore which plugin caused the problem. If it happens you need to look in the Console’s crash logs for AUSevices (or AUHosting - I’m not at my computer right now to check exactly what it’s called) and that threads info should tell you which plugin is causing the problem.

Thing is, Logic has a dialogue box in which you either select recover or quit, so it rare to have a crash proper. There's a lot of references to Sonarworks Sound ID in the logs, but not the crash reports. In the crash reports I see references to the thread which crashed but this doesn't appear to point directly to a plugin, unless one should assume that the process which failed is connected to whatever plugins happen to also be in that thread?

[rACatkvr]

Chagzuki have a look at this thread https://www.logicprohelp.com/forums/top ... ent-876480

I think it may help you.

[stoopicus]

I'm seeing a maddening bug in Logic 10.7.9 right now. Basically if a plugin ever resizes, from then on all keystrokes get stolen by Logic even if the plugin is focused. So, you can't type in plugin fields, for example - including (say) to save the preset you are editing. This is on Ventura 13.3.1 running on a M2 Pro.

Restarting logic fixes it. Happens regardless of plugin. Reproducible 100% of the time.

Anyone else see this? Meanwhile I have Reaper just sitting there in my dock, taunting me for betraying it

[aMUSEd]

I'm seeing a maddening bug in Logic 10.7.9 right now. Basically if a plugin ever resizes, from then on all keystrokes get stolen by Logic even if the plugin is focused. So, you can't type in plugin fields, for example - including (say) to save the preset you are editing. This is on Ventura 13.3.1 running on a M2 Pro.

Restarting logic fixes it. Happens regardless of plugin. Reproducible 100% of the time.

Anyone else see this? Meanwhile I have Reaper just sitting there in my dock, taunting me for betraying it

Yes I found this too, in some plugins such as Kontakt the behaviour persists between sessions and the only way to fix it is to reset the size in Kontakt standalone then make it the size you want again before opening Logic.

What other plugins are you seeing this with?

[stoopicus]

What other plugins are you seeing this with?

Drumazon 2 just now. Pretty sure I saw it in another earlier. Seems to happen when the plugin resizes itself (i.e. you do not change the window size, it does.)

[aMUSEd]

What other plugins are you seeing this with?

Drumazon 2 just now. Pretty sure I saw it in another earlier. Seems to happen when the plugin resizes itself (i.e. you do not change the window size, it does.)

Yeah I just found the same problem with Phaseplant - it may well be the case that any plugin with resizing elements triggers this (whether done manually or by itself). afaik Apple are aware of it but they seem to be slower than usual with releasing a fix, perhaps they are building up to Logic 11?

[stoopicus]

Maybe yeah. Didn't happen for me in Phase Plant but just did in Arturia SQ-80 V too. Very unfortunate, makes plugins pretty clunky.

[LoveEnigma18]

A quick question on Logic Pro major versions: If I have a major version 10, after version 11 comes out, will 10 be replaced with 11 or I will have access to both version 10 and 11 Logic Pro apps?

Any suggestions based on history of version 9 to 10 transition would help.

The thing is I am still on Logic Pro 10.7.9 demo. I would like to buy it next month once I have the money, so just in case Apple decides to drop version 11 in the meantime, I wanted to understand the above since I would love to buy version 10 and use it in case 11 isn't the ideal transition, at least immediately. Hope I made it clear enough.

[aMUSEd]

With Phaseplant I dragged the corner to resize then tried entering text into a preset description and keystrokes were passed to Logic.

[rACatkvr]

A quick question on Logic Pro major versions: If I have a major version 10, after version 11 comes out, will 10 be replaced with 11 or I will have access to both version 10 and 11 Logic Pro apps?

Any suggestions based on history of version 9 to 10 transition would help.

The thing is I am still on Logic Pro 10.7.9 demo. I would like to buy it next month once I have the money, so just in case Apple decides to drop version 11 in the meantime, I wanted to understand the above since I would love to buy version 10 and use it in case 11 isn't the ideal transition, at least immediately. Hope I made it clear enough.

I think it’s been over 10 years since Logic Pro X was released - the one purchase has got you all the updates through until Logic Pro 10.7.9. Which is pretty good value.

Anyone who knows anything about Apple’s plans for Logic 11 will be under a strict nondisclosure agreement. Some have speculated that 11 will be a subscription model like Logic for iPad, others that 11 will never come the 10 will just disappear like the X did. No one really knows. Seems to be pointless to speculate.
Logic 9 could co-exist with Logic Pro X when it was released.
If your happy with Logic as it is now then I suggest you buy it - holding off because something unannounced maybe just around the corner would mean you never buy.

[stoopicus]

Some have speculated that 11 will be a subscription model like Logic for iPad, others that 11 will never come the 10 will just disappear like the X did.

The former seems like pure speculation. And if it happens, I'm out, along with many many others. Too many excellent (arguably even better) alternatives to put up with a sub (which is not true on iPad).

[syntonica]

A quick question on Logic Pro major versions: If I have a major version 10, after version 11 comes out, will 10 be replaced with 11 or I will have access to both version 10 and 11 Logic Pro apps?

For the most part, you can run any number of versions of Logic on the same machine. However, I believe they will still share all of the same preferences files, which could potentially cause a problem.

Just make a copy of your current version of Logic outside of the Applications folder. When you update, it will be left alone.

[Johnnyjohn]

I'm seeing a maddening bug in Logic 10.7.9 right now. Basically if a plugin ever resizes, from then on all keystrokes get stolen by Logic even if the plugin is focused. So, you can't type in plugin fields, for example - including (say) to save the preset you are editing. This is on Ventura 13.3.1 running on a M2 Pro.

Restarting logic fixes it. Happens regardless of plugin. Reproducible 100% of the time.

Anyone else see this? Meanwhile I have Reaper just sitting there in my dock, taunting me for betraying it

Yep that bug is pretty annoying .. hope there's a fix on the horizon soon

[nordickvr]

Same thing happening over here.
Annoying. yes.
Report over here.
https://www.apple.com/feedback/logic-pro.html

[oneway]

Logic is not perfect but I've never encountered any of these issues. Sounds to me like you may need to blow away your preferences and possibly check all of your plugins to see what's happening there.

I was running into the same auto save freezing issue and after some googling and troubleshooting I realized it’s an M1 Native only problem. Intel Logic or Rosetta Logic doesn’t have the issue.

It’s pretty easy to test. You take a demo project, add 30 tracks with an instance of a third party plugin, twist a knob in the GUI and immediately hit save. After doing this 4 or 5 times it will beachball for 20 seconds or so. In a large project this freeze can take 4 minutes.