After the latest update, Proclaim no longer recognizes rtpMIDI or loopMIDI network MIDI controllers. These have worked for years, and now no MIDI controller appears in the SETTINGS->LIGHTING/MIDI except "Microsoft GS Wavetable Synth". All the MIDI controllers we have used are gone.
- I have used NONE of this capability, but thank you for your post. It has reinforced that we MUST NOT do a relaunch on a Saturday evening/Sunday morning, even though that is a quite natural time to do so ... when we see the alert. On the one hand I am pleased that Logos is continually responding to the needs for updates and upgrades, but with the sheer volume of these upgrades it appears as though more and more unintended consequences are finding their way into Proclaim updates. Fortunately none have impacted our use of this service ... but obviously it has impacted others!
- This happened to us, Haverhill Church Tech. I found a solution online. This is a bug with the way Windows handles MIDI. https://devblogs.microsoft.com/windows-music-dev/windows-midi-services-rollout-known-issues-and-workarounds/ Until Microsoft gets around to fixing it, the solution is as follows: Stop all MIDI services (if you use RTPMIDI I found that you just need to open it and uncheck the Enabled checkbox and make sure to disconnect all participants > 1st screenshot). With loopMidi right click the icon in the SysTray and then click Stop LoopMIDI. 2nd screenshot Open the Command prompt as Administrator (Win key > type cmd then choose run as Administrator). 3rd screenshot. In the command prompt box type > net stop midisrv Restart loopMIDI In the command prompt box type > net start midisrv If you are only using loopMIDI to send and receive internal MIDI signals, I would recommend downloading LoopBe1 as it doesn't seem to have been affected by this issue: https://www.nerds.de/en/loopbe1.html
