Tankfield

Thanks for the heads up. I'll watch out for that.

No, I was careful not to press SHIFT+[SELECT]. It's working now, but yesterday if I pressed Select to use the fader to change a parameter and then pressed Select again, the fader did not control the track's volume - it was controlling the Master Fader. And no matter what I did, including re-installing Core Control, re-starting Logic and re-starting the Mac, the ARM, MUTE, SOLO buttons were not working. Deleting Komplete Kontrol from the Controller Setup seems to have corrected it. NI KK was installed first, so that was top of the list. What happens if NI KK is not top of the list.

I think I have solved it, for now. @TChandler in a previous thread suggested accessing Controller Assignments and "locating the plugin parameter assignment on the control surface and ticking the 'exclusive' box". That worked at the time, but I could no longer find that control in Controller Assignments. I thought last time that it was in the Control zone, but it's not there. I found it in the Navigation zone and when I highlight 'parameter()' and then tick 'Exclusive' the CS12 behaves as expected. So it looks like operator error, compounding a mismatch between Komplete Kontrol and CS12.

In Control Surfaces > Setup I deleted my NI Komplete Kontrol keyboard and the CS12 started to behave as expected. When I turned on the NI KK keyboard and connected Logic to it, the problem returned where selecting a different track using the CS12's < > buttons opens either the track's instrument window or the first plugin window. However, the Arm, Solo and Mute buttons still work as expected.

The CS12 still misbehaves in a new user account, unfortunately.

Hi David I tried your suggestion (and also tried restarting Logic), but the CS12 is still the same.

My CS12 was working perfectly last week. My studio was powered down all weekend and today the gremlins have got into my CS12/Logic Pro. The Arm, Solo & Mute buttons are no longer working. If I press the Select button to control a parameter the fader does not return to controlling the selected track's volume when I press Select again. Instead it controls the Master fader. Selecting a different track with the < > buttons opens the first plugin's window, or if it's a software instrument track the instrument's window opens. I thought I had solved this issue last week, but it's back again. I've tried: Control Surfaces > Rebuild Defaults. Re-installing Control Core. Restarting the Mac. Any suggestions anyone? @TChandler?

Hi TChandler Thank you, ticking the 'exclusive' box seems to have worked. Yes, I will send my .cs file to Nectar support.

Hi Charlemagne, thanks for your help. I tried both Rebuilding Defaults and deleting com.apple.logic.pro.cs, but the behaviour is still the same: selecting a track with the CS12 also opens the instrument window or a plugin window.

When I select the next or previous track with the left or right buttons on the CS12, Logic opens the window of the first plugin on the new track. Or if the new track is an instrument rather than an audio track it opens the instrument's window. If I just want to change track to use the fader or pan I don't want a popup window opening. Is there a setting to turn this behaviour off?

Why?

I tried a new user account and the automation occurred on time. Good call, David. Comparing my settings with the default ones in the new account revealed that the critical parameter was Multithreading in the Devices tab in the Audio settings. Once I selected 'Playback & Live Tracks' the automation worked as expected.

Same thing happens on my MBP M1.

The automation happens early on my Mac Mini i7. Screen Recording 2024-03-19 at 13.45.44.mov

I just followed your video and my S61 Mk2 behaves like yours in Logic Pro. Shift-Play is the same as Play. However, Play (and Shift-Play) behave differently depending on whether Logic is already playing or if it's stopped. When Logic is already playing, clicking the Play button jumps the timeline back to where you last started playback and plays from there. Shift-Play does the same. So Restart does work, but only when Logic is already playing.