Setting MIDI out to "-- None" makes CtrlrX crash (if switched from "Microsoft GS Wavetable Synth")

[dervur]

I wanted to try setting my MIDI output to none, but this made CtrlrX crash for some reason. Right now I only tried to switch from Microsoft GS Wavetable Synth because I have no MIDI device connected, later today I will try with my MIDI device connected to see if the issue persists. The error message is the following:

Once I try to do it from also physical MIDI device I will let you know of the outcome.

[dervur]

Just wanted to confirm that from other MIDI out this issue does not occur, but only from "Microsoft GS Wavetable Synth" to none for some reason... Earlier version did not show this behaviour and I don't understand it to be honest..

[dervur]

I was mainly using that Microsoft MIDI thing only to test my panels whenever I wasn't connected to my devices. If something needs to do the same use loopmidi instead (https://www.tobias-erichsen.de/software/loopmidi.html) as it works just fine. Maybe some people already knew of this software but I'm writing it here for future new users.

[damiensellier]

That would be nice to do a guide about how to deal with windows midi single client problem and the workaround with loopmidi or other virtual ports softwares. I posted about the midi thru from/to host in a plugin instance somewhere in a discussion.

[dobo365]

Hi, I tested this on my adapted 5.6.30.1 and it doesn't crash at all when changing from "Microsoft GS Wavetable Synth" to None back and forth.
I tried in the standalone editor and also in an exported panel. No issue at all.
@dervur which version of CtrlrX did you use to get this issue?
I don't think that we changed anything regarding Midi I/Os

[dobo365]

Hi again, I repeat here what I posted in the other thread...
Tbh, seeing the issue you have here with Ctrlr but also with CtrlrX when changing from "Microsoft GS Wavetable Synth" to None, I'm pretty sure, as Damien, that there is something wrong on your side as we are not experiencing those issues.
I'm also on Windows 10. Damien has also Win10.
If you have Win11, then that could be the culprit.
Do you have a chance to test the same on a Win 10 PC?

[dervur]

Hello there,
Yes I use Windows 11, I just repeated the error and it keeps occurring. Unfortunately I have no chance to test it on Win 10 so maybe win 11 is the culprit indeed. I think with older version I was able to do it because that is what I was doing. But anyway I guess for the purpose I was using it, loopMIDI does its job perfectly. There is not really a need for Microsoft GS Wavetable Synth within Ctrlr I think...

[dobo365]

Well, "Microsoft GS Wavetable Synth" is needed for exactly what you wrote: being able to test the Midi I/O of a panel without the actual synth. I have built many of my complex editors like that.

[dervur]

I know, but to be honest, having tried the combo of “loopMIDI” and “MIDI tools”, I would honestly not go back to use “Microsoft GS Wavetable Synth” even if this issue is fixed. The latter is only an output, loopMIDI can also create a virtual input, and MIDI Tools has a virtual keyboard that connects to the virtual port created by loopMIDI.
So now without connecting to any hardware I don’t only have an output, but an input as well, much better in my opinion.

Regardless, I will look more into this issue for sure.