Apple Logic Pro 10.7.9 is released

[ozinga]

Curious if I update Logic via App store and want to revert to the previous version, where I can download the previous version ?

Zip the current one as back up before updating

[roman.i]

Zip the current one as back up before updating

Yep, that seems to be the simplest solution.

[Tj Shredder]

Or get it out of your timemachine…

[LoveEnigma18]

They haven't updated the Logic Pro trial version from 10.7.8 to 10.7.9 yet. Is this common for Logic Pro trials or does it indicate something?

I guess one reason is reinstalling a new version probably resets the trial period, but I haven't experienced it myself yet as 10.7.8 is the first version for me.

Just a heads-up: The Logic Pro 10.7.9 trial is now up. Simply redownload from https://www.apple.com/in/logic-pro/trial/. It also resets the trial period back to 90 days, which is very generous of Apple.

[roman.i]

I had a major issue, not specific to this version of Logic, but it's interesting it's not mentioned a lot on the internet.
When working with plugins and turning knobs, suddenly everything freezes for a few seconds, except playback. This is caused by auto-save.
To disable this you need to run in termial:

Code: Select all

defaults write com.apple.logic10 DisableAutoSave YES

or configure a longer auto-save periods

Code: Select all

defaults write com.apple.logic10 AutoSaveInterval 7200

[BoogerSnot]

Anyone else having 3rd party plug in windows bug out after the update?

A lot open up to the wrong size window, or just freeze so I can't edit.

Reported it to Apple, which means it will probably be fixed in 12-14 months.

Had to move on to another DAW.

[LoveEnigma18]

I have a couple of questions if someone can please help:

1. Are Logic Pro projects backwards compatible? I mean if I saved a project with 10.7.9, will I be able to open it with a previous version ( let's say 10.7.8 )? If not, could it be browsed instead via the browser "Projects" tab to use the contents that way?

2. Is it possible to disable an entire row of Audio FX (first, second, etc., - one row at a time) for the selected Channel Strips in the Mixer?
-> Figured this out. Works by selecting the required number of Channel Strips and then clicking bypass button on any effect plugin of the desired plugin slot and it will disable the effect plugins on that row.

[ansolas]

I had a major issue, not specific to this version of Logic, but it's interesting it's not mentioned a lot on the internet.
When working with plugins and turning knobs, suddenly everything freezes for a few seconds, except playback. This is caused by auto-save.
To disable this you need to run in termial:

Code: Select all

defaults write com.apple.logic10 DisableAutoSave YES

or configure a longer auto-save periods

Code: Select all

defaults write com.apple.logic10 AutoSaveInterval 7200

Thank you for this, will try it for sure

[chagzuki]

I had high hopes for Logic when I started using it 3 or so years ago. It worked well for about 6 months, and since then various updates have broken things, either on the OS side or Logic itself. If the problems are ever fixed something new breaks.

I've been on apple support phone calls for quite a while and I'm still stuck with this nonsense of projects taking forever to load. An OS update seemed to introduce instability into the current and older version of Logic (which I kept), so it crashes a lot. Actually, on that note the error message says that a plugin has caused an error/or system instability, or something along those lines, but for some reason it doesn't tell you which plugin.

Any yes, autosave has been causing hangs for about a year and a half.

I've not had these sorts of stability issues with either Waveform, or my brief tests with Reaper. The whole point of the closed hardware system is supposed to be to ensure stability, but I have the opposite experience.

[apoclypse]

I had high hopes for Logic when I started using it 3 or so years ago. It worked well for about 6 months, and since then various updates have broken things, either on the OS side or Logic itself. If the problems are ever fixed something new breaks.

I've been on apple support phone calls for quite a while and I'm still stuck with this nonsense of projects taking forever to load. An OS update seemed to introduce instability into the current and older version of Logic (which I kept), so it crashes a lot. Actually, on that note the error message says that a plugin has caused an error/or system instability, or something along those lines, but for some reason it doesn't tell you which plugin.

Any yes, autosave has been causing hangs for about a year and a half.

I've not had these sorts of stability issues with either Waveform, or my brief tests with Reaper. The whole point of the closed hardware system is supposed to be to ensure stability, but I have the opposite experience.

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.

[chagzuki]

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.

So far I'm aware of the audiounit cache file, and the plist file, which I'm told stores the preferences. I don't know if there's any difference in deleting the audiounit cache and just doing a total rescan from the plugin manager? Based on what I've seen so far, Logic must access a list of audiounits from somewhere beyond just those files. I saw mention of an audiounit sandbox cache file but I can't find it on my system. There must be some other files... I may be forgetting the steps I've tried going through already, but if I remember correctly, if one removes all component files from the audiounit folder, and then does a complete rescan, Logic still detects the audiounits despite there being none in the folder...? I'm confused. Or does it use the list in the cache to try to rescan the listed files... in which case would deleting the audiounit cache and removing all component files result in Logic no longer detecting any audiounits?

If I run Logic in rosetta mode projects load quickly, as they do in version 10.7.4 in native mode. So after 10.7.4.

[machinesworking]

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.

So far I'm aware of the audiounit cache file, and the plist file, which I'm told stores the preferences. I don't know if there's any difference in deleting the audiounit cache and just doing a total rescan from the plugin manager? Based on what I've seen so far, Logic must access a list of audiounits from somewhere beyond just those files. I saw mention of an audiounit sandbox cache file but I can't find it on my system. There must be some other files... I may be forgetting the steps I've tried going through already, but if I remember correctly, if one removes all component files from the audiounit folder, and then does a complete rescan, Logic still detects the audiounits despite there being none in the folder...? I'm confused. Or does it use the list in the cache to try to rescan the listed files... in which case would deleting the audiounit cache and removing all component files result in Logic no longer detecting any audiounits?

If I run Logic in rosetta mode projects load quickly, as they do in version 10.7.4 in native mode. So after 10.7.4.

Do you have any AU3 instruments or FX? I recently had issues with Logic and some AU3 plugins that were crashing and hanging AU scan. Took forever to solve.

[chagzuki]

Do you have any AU3 instruments or FX? I recently had issues with Logic and some AU3 plugins that were crashing and hanging AU scan. Took forever to solve.

I have 2 Moog plugins, and I seem to recall something vague about them employing a wrapper to enable them to be accessed within Mac OS hosts... but I have no idea if that's a standard feature of AU3 plugins, or something specific to the Moog ones. I think in some hosts a workaround was required to use them, but perhaps that's simply to do with certain hosts not having AU3 implementation? They appear to work fine in Logic. I see in plugin manager there are extra items associated with them, an audiobridge insert and audiobridge trunk.

[rACatkvr]

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.

[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.

Thanks. I did skim through the logs but couldn't see anything... I'll have another go following your advice. Apple support are supposed to contact me in a day or two and hopefully they'll dig properly into the loading times weirdness, but on top of that the plugin-causing-instability issue inevitably happens, whether it's as soon as a project loads or 20 minutes after, so I have to save constantly. But saving while a GUI is open can cause hanging so I have to constantly close plugin windows and save. It's not a workable workflow right now, so if there's a particularly plugin that I can track down that would make an enormous difference.