Closed mark-epstein closed 10 months ago
Also, Companion v3.1.0 doesn't seem to connect to midi-relay. The log shows this if I stop and start the connection, but the Connections page never advances past "Connecting"
system: ** Connection stopped **
system: ** Starting Connection from "/opt/companion/bundled-modules/techministry-midirelay/main.js" **
system: ** Connection started **
Starting up module class:
Sentry disabled
Module-host accepted registration
info: Verbose mode enabled. Log entries will contain detailed information.
debug: Using protocol for midi-relay v2
sorry last comment of the night. Same Pi, same USB-MIDI hardware, works fine with an older SD card that has Companion v2.3.1 on it. I don't know how to determine the midi-relay version, I lost the SSH credentials.
Maybe this info is useful
OK, I just saw this.
If I can't run midi-relay at all with Companion v3 that will make me very sad. I have invested tons of time researching and planning a move to v3. But the option to select lower (2.x) protocol versions confuses me if this is the case; I'm hoping the "only compatible with midi-relay v3.0 or greater" is incorrect?
At some point if I can find the time (or if someone hires me to find the time) I will make the current midi-relay v3.x codebase be able to run on a Pi. And eventually I will deprecate and remove the v2.x functionality within the companion module entirely.
Unless you particularly need this to run on a Pi, just download midi-relay v3.x and run it on a desktop computer with that USB midi interface.
Describe the bug
To Reproduce installed mid-relay v2.0.1 also occurred on 2.0
I got midi-relay to run by running
npm install request
but I have no idea if that's right. midi-relay seems to be running but won't recognize my MIDI hardwareos: Debian GNU/Linux 11 (bullseye) Raspberry Pi 4 Model B Rev 1.4