Over the weekend I experimented with doing patch dumps from my JD990 to Tracktion, and it's not working well at all. JD800/990 programming is something I'm intimately familiar with, so please bear with the technical explanation here;
When dumping a patch, the JD990 sends three sysex packets, consisting of 129, 267 and 123 bytes respectively (including sysex headers) for a total of 519 bytes.
Tracktion is recording these as three packets of 126, 126 and 121 bytes - not including F0/F7.
Further investigation reveals that what Tracktion is doing is taking the first 126 bytes of each sysex packet and discarding everything beyond that until the start of the next packet.
Obviously, this means that some of the patch data is simply getting ignored. Not good!
So -- is there a setting in Tracktion that allows me to increase the size of a single sysex packet that Tracktion will record? Or is this a "bug" (more likely, a programming oversight) that needs correcting?
The ability to save sysex dumps of patches or banks inside songs is really important for archival purposes - you don't want to open a song a year from now only to find you can't locate the correct patches, so it's safer to store them as sysex dumps inside the track (not to mention a hell of a lot more convenient). Therefore, I'd rate this issue as being of medium to high priority.
Thanks,
Gwydi
Bug? Tracktion and Sysex dumps
-
- KVRAF
- 4644 posts since 28 Nov, 2002 from Chicago
sysex is barely supported in tracktion at all as far as I can tell.
I'm hoping some degree of full sysex support will come with v2, but I'm not totally convinced it will, TBH.
I'm hoping some degree of full sysex support will come with v2, but I'm not totally convinced it will, TBH.
Someone shot the food. Remember: don't shoot food!