Voyager transposing issue

[Tim Webster]

Hello. New to the forum. Thanks for having me.

I am encountering an issue with a Moog Voyager and transposition, and thought sharing the info I have might help someone else.

I am currently touring with a band, and we run two Voyagers on stage, both of which are played "by hand", and triggered via midi (from an A&B rig running Ableton Live 10, via a MIDI Solutions midi switcher) at various points in the set. One is set to midi ch1, and the other to ch2. The one on ch1 has twice now detuned all 3 oscillators by -2 semitones. Both the midi and keyboard transposition menus show 0 transposing, yet a D key sounds a C note, and so on. Nothing seems to fix this, apart from powering off, disconnecting everything and leaving it 5 mins or so. Obviously non-ideal mid-set.

Whilst troubleshooting this today I established that when I discovered that when I eject an external hard-drive from computer B in my rig it sends a sysex message and 3 pitch messages on ch1. Perhaps this is the cause.

I have now moved the offending Voyager to run on ch3 (hopefully thereby avoiding the sysex), and have taken to unplugging the midi cable when editing on the computers. Obviously, this is a bit of a fudge-fix, but fingers crossed it will stop any nasty surprises. I will report on this if anyone is interested.

As I said, hopefully this info might help someone.

Cheers

Tim

[till]

...
I discovered that when I eject an external hard-drive from computer B in my rig it sends a sysex message and 3 pitch messages on ch1. Perhaps this is the cause.

I have now moved the offending Voyager to run on ch3 (hopefully thereby avoiding the sysex), ...

SysEx is send global, not per MIDI channel. So using a different channel won't help here.
But why does your computer send MIDI when ejecting a hard-drive?

[MC]

Voyager does have device ID parameter for sysex, but that won't solve the problem.

The best way to solve the problem is a MIDI filter on the output of the computer.