I wonder if the SysEx specs are available for the Taurus 3?
I would like to be able to see where a sound stored as sysex will go. Or if it is possible to load a sound into the edit buffer first. Or to program a tiny app to change the sound names via the QWERTY keyboard of a computer.
Haven’t seen them published. I suppose you could ask.
Otherwise, why not spend a few hours (days?) starting with a default patch, modify one parameter, do an octal dump followed by compare of the SysEx dumps and document it for the curious out there.
Phatty’s patch is 383 bytes which includes a series of values which are 12 bit (0..4095) and likely packed into 2 bytes, plus the text of the patch name, etc.
Shouldn’t be too difficult; maybe I’ll decent into the laboratory and do this if you’re not interested.
I have not heard of a Taurus editor coming along so I wouldn’t expect Moog to NOT provide this detail for you/us.
This reverse engineering technique would be a way to go. But it does take plenty of time to do so. I am not sure when I could start such a project with so many other interesting things to do.
Well, my wife is going out of town on business in a few weeks. If you haven’t gotten to it by then, I’ll put in some late night hours to document anything I can find out.