I'll admit that the description in the manual is possibly poorly phrased, in any case. My interpretation of that is more "if the keyboard isn't working and you are using a USB hub, try not using the USB hub" and not so much "the keyboard will not work with USB hubs". That bit about the USB hub appears to only be in the "Troubleshooting" part of the Q-series manuals, is that where you found it? I certainly didn't see it in the VI49, VMini, or V25 manuals. And in the end it turned out that I was running it against the wrong MIDI interface, and my device uses a slotted configuration and a byte-by-byte protocol for accessing the configuration data so it probably wouldn't've found anything anyway. For the VI49, it was formatted as though it were a sysex message (but not one that I expect would work: it's for a non-slotted configuration, and the stored message length was for the VI61), and it has the device ID in the header, and the length information is likewise obvious. I don't know if I want to improve this program, to write a new program, to merely document what I can about the VI61 in particular and the V series generally, or to give up and just use the given config editor in wine.įinding the headers required for a new device should be trivial: Get a save file from the configuration program. There's cleverness and some amount of magic in it, but overall it's prototype-quality code.
Everything else looks to be fragile relationships, tight coupling, and little-to-no parameterization. I suspect that the "easy to incorporate other models" bit is the way that the UI basically data-binds itself to the model (see ui/components.py and ui/values.py). My current belief, having examined the two variants of the alesisvsysex program, and having experimented a bit with my VI49 and the supplied editor, is that a program could be written to support all of the V25, the V49, the V61, the VI25, the VI49, the VI61, the V Mini, and possibly the Vortex Wireless and Vortex Wireless 2, with save files compatible with the windows configuration editors. Doesn't really help if you're on something fun like a PA-RISC, PowerPC, or ARM system, but should be good news for people with more-normal environments, and means that a full windows VM or dedicated machine isn't actually necessary to do the reverse engineering. I also found that the VI49 configuration editor works fairly well under Wine (modulo the usual font-related issues for tightly-constrained label controls). I'm still working (slowly) on reverse engineering the configuration encoding, but I do have the upload / download protocol bits worked out.
because it has multiple "preset slots", it uses a different (but related) protocol.
0 kommentar(er)
