M32 Not Working After New Logic Update

dompurdie
dompurdie Member Posts: 6 Newcomer
in Komplete Kontrol

I recently updated Logic Pro and after doing so my M32 stopped integrating properly with Logic, so none of the transport controls seem to be working, and when I remove the device in the control surfaces setup and then unplug and plug the M32 (at which point Logic usually recognises it and adds it to the list) nothing happens, other than Logic saying more MIDI ports are now available. So it still works as a MIDI controller, and also it still integrates with Komplete Kontrol standalone, but in Logic it isn't integrating as before for some reason. Just wondering if this is something people are aware of already and trying to fix? Is it some bug introduced by the new Logic update? My OS version is Sequoia 15.5, and KO version is 3.5.0

Tagged:

Best Answer

Answers

  • Lolo13400
    Lolo13400 Member Posts: 27 Member

    Hello, following the Logic Audio 11.2 update (adding longer volume sliders), I also have the following problem with my Komplete M32, the volume potentiometers no longer work properly. They increase or decrease by 0.1 instead of 1. It is no longer usable (Thank you Apple), if you change the settings in the control surface menu: multiple x10, then the track names on the Komplete M32 are no longer displayed! Unfortunately, I don't have a solution.

  • Jeremy_NI
    Jeremy_NI Administrator, Customer Care Posts: 14,882 admin
    Answer ✓

    @dompurdie A few things to check.

    Do Logic and Komplete Kontrol have full disk access? How to Enable Full Disk Access on macOS

    Since you're on Sequoia, there are a couple of extra steps: How to grant audio apps access to your local network on macOS 15 Sequoia

    If that still doesn't work, please try the following: https://knowledge.apogeedigital.com/how-to-reset-logic-pro-trash-preferences

    Then try again.

  • dompurdie
    dompurdie Member Posts: 6 Newcomer

    Yessss I got it working now thank you :) I did all the steps you mentioned, and after trashing the preferences and restarting my machine it automatically recognised the M32 and installed it. I didn't actually restart the computer after doing the local network step or the full disk access step, so possibly those steps contributed to fixing it too, but I wasn't sure if a restart was necessary after those. The preference trashing did explicitly mention a restart so I did it for that step, and anyway it is all working now so thank you :)

Back To Top

Categories