MTIN/MIDI module crashes the SSP if change in preset

Bug description (state clearly and simply):

Add MTIN to new preset without setting the midi in/out/channel, now switch to a preset that has a MIDI module and all is good and normal.

If however, you assign the MTIN to your controller you will get this error when changing to a preset with a MIDI module…

Software version: latest

this is a known issue …

This is fixed in the next SSP firmware update. (and no, there is no release date for this yet)

unfortunately, in the current firmware I cannot really fix/workaround in within the VST.

just noticed, that when I moved to the wiki format, this ‘warning’ has been lost on some of the MT* modules… I’ll fix that.

edit: ok, updated all the MT tools with this warning

anyway, workaround in this current firmware, unfortunately, is to unplug your midi device and plug it in again.

Ahh thanks… thought the midi bug was limited to changing to juce…

Anyway… not a big deal… it will be fixed as you say…

no,
the issue stems from synthor connecting to any ‘new device’ that gets connected…
unfortunately, alsa creates an ‘internal device’ when you connect to a physical device.
so whats happening is my module connects to a physical device, then synthor connects to that internal device… then gets ‘upsets’ when that device is closed.

the fix is simply we make synthor not connect to the internal devices in the first place … which also prevents other ‘issues’ :wink:

2 Likes