Totalmix menu Options / Settings / Tab Midi / connections / Midi-output : none

Set the midi output to none for a test.

If you missing sync of the controller to Totalmix then re-enable the Midi-output, make sure Midi-thru is OFF in the Loupedeck.

The crash probably is caused by Midi feedback loop.

You are right, tonpalt.

Had no OSC related crashes since 1.96beta.

So, install 1.96beta, as it contains fixes regarding crashes caused by odd OSC messages.

See changelog for OSC:
- OSC crash fixed (no descriptor found)
- Cue via OSC restricted: does not allow switching to Main Out and Speaker B anymore
- OSC scaling now switchable to correct maximum value for Gain, EQ band type, Room EQ Scale, Expander Threshold,
- Conversion of page 4 for Room EQ (old page 4 invalid, not functional anymore)
- Sending of 0 for non-existent elements
- Increase crash safety for unexpected data
- Settings, OSC Tab: Added compatibility mode option to disable newer OSC functions of TM FX 1.96.

waedi, i think he uses the TM plugin for Loupedeck from here:
https://github.com/shells-dw/loupedeck-totalmix

So, i think it is not MIDI related.

You probably mean Totalmix 1.96 beta 7?

I am not familiar with Control Pilot, just quick overlooked the FAQs and Set up the trial version.

Totalmix itself does not lock or shows the beachball here.

Seems that in CP the Ports for connection2 are fixed to 7002/9002 and to "localhost".
CP seems to constantly toggle its connection if connection2 is enabled there. Switching the compatibility mode between 1.90/1.96 in TM seems to not have an affect.
I think its anyhow related with CP's handling of the page2 Params itself? (see the changes in OscTable provided with the beta). Maybe you could ask if felix could look into his code?

Yes, definitely 1.97 beta.
I was seeing connection 2 cut in and out in Control Pilot (Green, Red, Green etc etc. Mostly red).
I also tried the compatibility more (no effect)
Matthias, these were just lock ups, not hard crashes.
Should I send some logs?

Cheers,
Matt

i think, i got it.

In short:
mattrixx, You can switch to TM 1.96beta4 (or earlier) or ControlPilot should be updated.

Should mention, that in my case, although CP-Controller 2 toggles its state, it works at all. (receives/sends all commands Mute Groups, etc...). And TM itself does not freeze or locks..

long Version:

MC described the changes, introduced with TM 1.96beta5 here: https://forum.rme-audio.de/viewtopic.ph … 80#p221780
Especially this point is the reason, why ControlPilots Controller 2 toggles:
- the DURec buttons, state and record time information is no longer repeatedly sent, only on changes

Control Pilot recognizes the "alive" state of its controller 2 by periodically (every 2-3 seconds) switching to page 3. It sends  "/3" to TM, port 7002.
If Control Pilot  does not receive /3/recordRecordStart,/3/recordPlayPause,/3/recordStop as feedback on port 9002 from TM, it sends multiple new "/3" commands to TM - but with a time delta between 0 and 10 ms! (not good).
This is probably the reason why TM seems to "lock", as it gets flooded with "hey TM, switch to page 3" commands in a very short period.

Maybe an additional info for felix:
Since TM 1.96beta5 it sends about every 2 seconds the ping message (OSC address "/", float, val 0) to every active controller and its unique dst port, activated in TM.

Nice!

You can’t change the settings of Connection 2 while it is not checked ✅ to be used.
And there’s absolutely no need to make manual settings in system folders.

@maggie33: ControlPilot is meant to run on the same machine (computer) as TotalMix FX app does. It was never tested for anything else.

(Edit: Rephrased for clarification)