Logic Buggy - Inconsistent monitoring

Question

Level 1

8 points

Logic Buggy - Inconsistent monitoring

I've spent several hours with Apple tech support, shared my screen, tried dozens of suggestion (such as disabling all plugins) - they have no answer.

I use very simple audio tracks . Logic will arbitrarily stop showing any response on the output meter, even though audio is heard and main output slider will stop having an effect. Restarting Logic usually fixes. I assume restarting the coreaudiod might work but the point is, Logic should not be fighting itself requiring constant fixing to work.

Mac Studio, macOS 15.6

Posted on Aug 17, 2025 4:10 PM

Reply

Answer 1

EddieGrey

Level 4

2,000 points

Aug 18, 2025 7:32 AM in response to pslebow

Have you turned off Auto-Input Monitor? Also, give Logic Pro Full disc access.

Reply

Answer 2

yoyoBen

Level 4

3,403 points

Aug 18, 2025 12:54 AM in response to pslebow

You can send bug reports here:

Feedback - Logic Pro - Apple

You can access this link in Logic: Logic Pro > Provide Logic Feedback

Please always provide information about your computer model, Mac OS and Logic version.

Reply

Answer 3

pslebow Author

Level 1

8 points

Aug 18, 2025 8:17 AM in response to EddieGrey

Yes, autoinput monitoring has never been turned on. Apple support walked me through many diagnostics. One issue was that starting Logic with all plug-ins disabled seemed to prevent this from happening. Apple support seemed uncertain on how to troubleshoot plugins in the the ~Library folder and mistakenly believed disabling a plugin within Logic was the same as not loading it.

I will check Privacy and Security for full disk access, but Logic has never asked for it so I think it is enabled. If it truly is something needed to function properly, it seems odd that Logic would not enforce that permission.

Thanks

Reply

Answer 4

Pancenter

Level 6

14,782 points

Aug 18, 2025 4:54 PM in response to pslebow

This complaint has been around for ages. As far as I know, you have to live with it. It could be as simple as one 3rd party plugin causing the problem.

Reply