Here’s a screengrab:
Looking at the log window, it is recognizing the individual patch as a sysex file ( yellow ) but when I send a bank afterwards ( blue, then purple ) it displays no sysex information.
And the purple text has nothing to do with any of the patches I have on the Voyager. It’s like a ghost bank, or some kind of default bank list?
I tried setting the buffer to 1024 instead of 512, but it made no difference.
It appears to be sending the data twice, on ports 3 & 4. Maybe because I have my interface ( Roland octa capture ) set as the midi device and also the CTRL device in MIDI-OX. But it wasn’t working with just one selected either.
I gave the Soundtower Voyager editor software a shot, and it is working fine saving entire banks. Maybe the Voyager doesn’t send bank data as sysex, thus MIDI-OX won’t recognize it?
I did sysex transfers of a whole bank with my Voyager. But according to the dates of these SysEx files, this was before 2017.
Have you tried it with other synth that send out data blocks of SysEx with this size (18734 Bytes of SysEx) or bigger? Many MIDI interfaces are known not wo work reliable with bigger sized SysEx data.
Hi, not yet. I just needed to archive all my patches as it’s been a few years & would suck if I lost them all.
The Soundtower software worked, so I’ve not bothered to mess around with it. I’ve got music to finish!
Interested if anyone else gets midi ox to work though.
edit
I did notice Soundtower appeared to be saving each patch individually, as a batch process when I saved a whole bank. And midi ox worked on individual patches, but it’d have taken far to long to manually export each patch, out of each bank