Softube Fader 1 SysEx Messages moves Obsession Tuning Knob

[Spaceman Ted]

I purchased Obsession (1.0.2) yesterday and started going through the presets in Logic pro X on my Macbook Pro 16" and started to get annoyed that most sounds went out of tune after a few seconds.
Investigating further, I noticed that incoming Midi SysEx messages into Logic move the Tuning knob in Obsession in small, but clearly visible increments. The SysEx messages are coming from my Softube Fader when the Softube OSD control software is activated.
Not all of the messages cause the tuning knob to move, but most. The tuning knob keeps moving clockwise to 10, the jumps over to -10 and slowly makes its way around again.

Happens when using the stand-alone plugin of Obsession and also when using it inside Pluginguru Unify. Not having the problem when using Obsession inside Native Instruments Komplete Kontrol.

Examples of what those SysEx messages look like (recorded via Midi Monitor by snoize):

14:43:19.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 41 72 28 42 40 03 F7
14:43:20.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 4A 65 7A 1B 48 0C F7
14:43:21.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 53 01 11 33 08 0F F7
14:43:22.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 46 6C 4C 57 63 08 F7
14:43:23.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 4A 65 7A 1B 48 0C F7
14:43:24.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 46 6C 4C 57 63 08 F7
14:43:25.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 46 6C 4C 57 63 08 F7
14:43:26.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 4A 65 7A 1B 48 0C F7
14:43:27.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 4F 15 10 6F 47 0F F7
14:43:28.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 4A 65 7A 1B 48 0C F7
14:43:29.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 4F 15 10 6F 47 0F F7
14:43:30.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 46 6C 4C 57 63 08 F7
14:43:31.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 46 6C 4C 57 63 08 F7
14:43:32.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 46 6C 4C 57 63 08 F7
14:43:33.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 4A 65 7A 1B 48 0C F7
14:43:34.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 46 6C 4C 57 63 08 F7
14:43:35.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 4A 65 7A 1B 48 0C F7
14:43:36.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 46 6C 4C 57 63 08 F7
14:43:37.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 4A 65 7A 1B 48 0C F7
14:43:38.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 46 6C 4C 57 63 08 F7
14:43:39.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 46 6C 4C 57 63 08 F7
14:43:40.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 46 6C 4C 57 63 08 F7
14:43:41.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 3D 2B 1B 7F 57 07 F7
14:43:42.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 4A 65 7A 1B 48 0C F7
14:43:43.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 41 72 28 42 40 03 F7
14:43:44.708 From Console 1 Fader SysEx Non-Commercial 16 bytes F0 7D 53 00 00 00 02 00 40 3D 2B 1B 7F 57 07 F7



Macbook Pro 16" running Catalina 10.15
Logic pro X
Everything on my computer is completely up to date.

[Teksonik]

The question is why is your controller sending out sysex information from a Fader ?

One thing you can try is right clicking on the Tuning Knob on OBsession's GUI and selecting "Midi Forget".

There's really no way the knob should be set to receive sysex messages only Control Change messages but it can't hurt to try midi forget.

[Spaceman Ted]

Well, the SysEx gets sent to Logic when the Softube Fader unit is connected to the Softube Console plugin inside of the DAW. That happens after starting the Softube OSD (On Sreen Display) utility. I guess the hardware unit updates its knob and fader positions and sends that info to the Softube console plugin inside the DAW.

Tried the Midi Forget, but that didn't help.

Here's the link to a short video that shows a bit of what's going on: https://youtu.be/yD88LFyVBEs
Observe the Obsession Tuning knob moving a tick clockwise every so often (after a handful of SesEx messages)
If you let it go like this, it keeps on going round and round.

[Jouni]

You could try to debug a bit in the midi environment of Logic to see if something strange is happening. Afair sysex is sent differently to AU plugins so they should not be processed. How is the controller configuration in Logic now? Using some manufacturer mappings or generic?