Xpantastic! group photo

Yahoo Groups archive

Xpantastic!

Index last updated: 2026-04-28 23:44 UTC

Message

Re: [xpantastic] Xpander sysex patch spec- the Xplorer version

2018-05-22 by Tony Cappellini


>> 196 & 2 + 8 = 399 bytes, which is correct

I have to correct my own calculation, however it still doesn't add up from what i can see.
196 *2 = 392 bytes, including the patch name. Add the first 6 bytes for the sysex command, + 1 EOX, 399 bytes.


On Tue, May 22, 2018 at 1:46 PM, cappy2112@... [xpantastic] <xpantastic@yahoogroups.com> wrote:

I';m trying to understand the calculations that the single patch browser (included with Xplorer) ueses.

Looking at XpanderSysEx.h



// Single patch data sysex length is 399 bytes
// 6 bytes for sysex intro: F0 10 02....
static const int PRG_DUMP_DATA_FOLLOWS_INTRO_LENGTH = 6;
// 188 double bytes data for the values and 8 double bytes for the patch name
static const int PATCHNAME_LENGTH = 8;
static const int OBWORDS_DATA_LENGTH = 196 - PATCHNAME_LENGTH;
// 6 (intro) +196*2 (data+name) +1 (EOX) = 399


I understand that PRG_DUMP_DATA_FOLLOWS_INTRO_LENGTH is for the Sysex cmd overhead to request a single patch, however, I don't understand why he subtracts the patchname length from 196, when the patch name is part of each single patch.


196 & 2 + 8 = 399 bytes, which is correct


What am I missing?








Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.