Once I got frustrated over the small buttons on the module enough to chart out the contents of a user kit syx file. So it's not encoded. The file has distinct blocks of data for every pad and so on. Finding out the structure of the file was quite a pain in the butt though, fiddling with a kit parameter and dumping the file to a computer to check out with a hex editor which byte has changed. I got it charted out pretty nicely though, except that there's this one byte that just changes between 0 and 1 and doesn't seem to represent any real setting. Oh well... :) And as every parameter except the kit name is just a numerical value it was at times a bit puzzling to connect it with the setting value that's visible on the module. Didn't get around to coding a software for it yet though. Harri --- In DTXpress@yahoogroups.com, rdamon@m... wrote: > On the software topic, it has been over tens years since I did any VB > programming. But it would seem to me that if the kits data file of 972 bytes > (typical size) could be broken down into it's basic information (user kit > no., pad type,voices) that a simple windows interface could be written to > access/modify perimeters from some simple pulldown menu's. Has anyone tried > to tackle this?? Or is the data stream "encode/encripted" to prevent direct > manipulation?? Just curious. >
Message
Re: new product
2003-04-24 by Harri Ohra-aho
Attachments
- No local attachments were found for this message.