Can't plug-ins added when selecting output channel settings in Logic Pro 12.3.1

Hi

Seems like this has been fixed in 12.4

• "Adding a preset to Stereo Out channel now functions correctly."
• 
  

Logic Pro for Mac release notes – Apple Support (UK)

CCT

A plugin can be inserted in the Audio FX or in the Midi FX slot, but not in the output of a channel strip. Please post a screenshot if you still have problems

After a long week of troubleshooting, I reached the conclusion that the app pre-sets for the output channel have somehow become corrupted or broken. Since I could still insert plugins manually in all channels, including the output channel, I created a simple work around. I opened old projects which already had the output channel plugins already with the plugins I want. Then I saved the sets on each as user defined presets. Now I can use them the same as before without any issues. Now I have time to worry about fixing the problem at a later date.

Thanks to all who have responded,

JFA

Hi

josf wrote:

I haven't tried logging in as another user but I've tried just about everything else, including components, plugin manager. The behavior is like certain settings may behave correctly while others don't . . .

I'm considering uninstalling Logic and doing a clean re-install . . .

JFA

Before you go through all the hassle of deleting & re-installing, logging in to the Mac as a different user would test to see if there is a problem specific to the "primary" user account ( typically the Logic preferences file)

It'd take a minute or 2 to run the test

CCT

Hi

Not much help, but I can confirm that the Output 12 channel strip settings load correctly here.

Is this issue with one specific project or all (including a brand new empty project)?

If you log in as another User on your Mac, does the issue persist?

(Tested Logic 12.3.1 macOS 15.7.3)

CCT

Hi

So, the issue persists with a different user account:

Possibly an issue with the Logic Pro installation: you could try re-downloading the app

Possibly associated with a macOS(?) update... if this is the case you'd need to consider waiting for an update (OS or app), or perhaps downgrading your macOS ( this is a big job, not sure i'd do it just for this issue alone).

Would be loads easier to use a work around for the output channel plugins

Could you pls confirm the Mac specs, including the exact version macOS

CCT

Have you properly installed the legacy library/patches?

Yes. But it wouldn't matter. The problem is that even the modern app presets won't populate the channels plugin slots. But I've noticed that in some cases I noticed that, Setting> app presets> Knock A, creates a new channel strip with the plugin slots populated. ?!

In the output channel > Setting > (drop down) choose a preset such as Knock A Knock B . . . or a legacy preset such as Basic, Classical, Jazz, etc. / the slots fill with plugins . . . or at least they're supposed to.

When I choose Setting > Drop Down App Presets > Knock B, nothing happens. The slots are still empty . . .

[Edited by Moderator]

Thanks for jumping in on this . . . I'm really baffled by this issue . . . it's almost as if there's a virus.

It's with old projects that once opened and operated as expected, new projects from scratch.

I haven't tried logging in as another user but I've tried just about everything else, including components, plugin manager. The behavior is like certain settings may behave correctly while others don't . . .

I'm considering uninstalling Logic and doing a clean re-install . . .

JFA

CCTMusic wrote:

Hi

Possibly associated with a macOS(?) update... if this is the case you'd need to consider waiting for an update (OS or app), or perhaps downgrading your macOS ( this is a big job, not sure i'd do it just for this issue alone).

Could you pls confirm the Mac specs, including the exact version macOS

Mac mini M2

16 GB

Tahoe 26.5.2

But the recent update I was referring to was for Logic, which I updated on Sept. 8

Thanks for all your help . . .

JFA

Wow! So they actually put that in the release notes . . . so, apparently it was a bug? I wonder if calling Apple last week and pointing it out had anything to do with this. Hmmm . . .

Thanks for the heads up!

JFA

Ok, I’ll take your advice

JFA

I think the timing of the last update on Sept. 8 coincides with the emergence of this issue, but I'm not entirely sure . . . ?

JFA

Created a second user and logged in. Same issue . . .

JFA