MMcL Mackie Driver with multiple units? Best way to set up?

[minminmusic]

This is a follow-up to my earlier post on the iCON P1 controllers. I thought I got things fixed but, while the 3 iCON controllers are displaying the the track order correctly and are banking...something about adding this 3rd controller and having to fiddle with things has made the display timecode counter on the P1-M extremely laggy.

Previously, I had the  P1-M (main unit) on MMcL Mackie Control #1 and the P1-X extender on MMcL Mackie Control XT #1. Everything worked well. Adding the additional P1-X, I thought it would be routed to the MMcL Mackie Control XT #2 but could not get it to pick up. Now...I have all 3 routed with MMcL Mackie Control #1 (using the correct midi routing). LIke I said, as far as I can tell this setup is working except for the extreme lagginess on the timecode bar. I also have the P1 series mapped to LUNA and Reaper and the timecode is working fine there.

If it's a 24 track project and I want the P1-X1 to be assigned to tracks 1-8, P1-X2 to 9-16 and the P1-M to 17 through 24...which is the nest configuration to use within the Control Surfaces menu? I've generally set it up in the order in the Control Surfaces menu...not because I think it's needed that way (if it's routed correctly) but from an organizational standpoint it makes more sense to my lizard brain.

[minminmusic]

For reference on how it's currently set up.

[minminmusic]

The attached setup seemed to fix the lagginess and all tracks on all three units are showing up correctly. Not totally sure if this is the correct way OR that there's benefits/differences between the Mackie Control driver or the MMcL.

Regardless with both, unless Cakewalk has no way of sending this data, I wish some of the limited tweakability of the "DrivenByMoss" Reaper and Bitwig driver could be added to Cakewalk. Realize their limits in the MCU protocol but squeezing the little but extra out of what's available is always nice.

Edited September 6 by minminmusic
Add Photo