You are not logged in. Please login or register.
RME User Forum → TotalMix FX → TotalMix crashes when using OSC (with Loupedeck)
Hello,
TotalMix crashes when I have OSC enabled. I am using a Loupedeck controller and everything works beautifully for several minutes, but then TotalMix crashes and needs to be restarted. I am on MacOS Sonoma 14.5, TotalMix v 1.95 (but the problem was the same with earlier versions), RME Babyface Pro. What could be causing this issue?
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.
Hello
I don't know if will be helpful for you but there is a new version TotalMix 1.96 Beta
https://forum.rme-audio.de/viewtopic.php?id=39809
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.
I have been having some OSC related issues in Totalmix beta 1.97 and OSC in Control Pilot.
If I enable the second connection (for Automating Mutes etc in Control Pilot) I am get Totalmix lock with there spinning beachball.
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?
In TM FX beta 7 mac? Any crash reports you can share?
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 updated to TM 1.96 beta 7 and no crushes yet. Thank you for all answers!
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.
Sorry for the confusion! I had a few weeks break and missied those newer developments.
I just distributed an update for ControlPilot which should fix the issue with TotalMix 1.96 beta5+.
@maggie33, very good debugging, it's all true. Thanks for the tip with ping/pulse.
Btw., ControlPilot's Connection 2 ports and host can be set freely, 7002/9002 "localhost" is just the default.
Nice!
Btw., ControlPilot's Connection 2 ports and host can be set freely, 7002/9002 "localhost" is just the default.
Was not possible to set sth in the UI, while it was toggling...
But - ok, i found the ~/Library/Preferences/com.soundflix.ControlPilot.plist next day after i posted my first post here.
Btw., ControlPilot's Connection 2 ports and host can be set freely […]
Was not possible to set sth in the UI, while it was toggling...
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.
You can’t change the settings of Connection 2 while it is not checked ✅ to be used.
Thats not what i meant. I posted this, while i was on the old version of CP. Of course, Connection 2 was checked.... Because the connection 2 was toggling there, it was not possible to set the ports in the UI (in my case). Every time when CP switched back from active/inactive, the old ports (7002/9002) reappeared there.
---
And there’s absolutely no need to make manual settings in system folders.
...Connection 2 ports and host can be set freely, 7002/9002 "localhost" is just the default.
Did i overlook sth? I did not find where i could change the target host in the CP UI.
I was needed to alter these settings, because i usually test SW in a VM (different IP/Network than the host, TM is running on). So localhost or 127.0.0.1 did (of course) not work...
@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)
whatever you mean with that. I was able to run it in a VM.
Edit:
Anyhow, it tends to drift offtopic... We had direct contact, longer time ago. Feel free to ping me if you want.
And CP works now, since your update - so - everything is ok...
Edit 2:
as Response to your modified post (Edit: Rephrased for clarification)
-> OK, sounds different now.
So, if i may to share what just comes in my mind - maybe an idea for improvement? As it seems to be not a problem to make it work stable between different TM and CP hosts. But i do not know if there would be users, with such a use case... Its on your own.
RME User Forum → TotalMix FX → TotalMix crashes when using OSC (with Loupedeck)
Powered by PunBB, supported by Informer Technologies, Inc.