SynthMaker

SysEx tools.

Archive · 2011 12 old posts

From the original SynthMaker forum (2004–2014), with its members’ names and dates.

trogluddite ·

Following Power Chord's recent request for help with checksum calculation, here are a some little SysEx helper modules...

There are checksum generators for a couple of the most common methods - Roland ( 128 - SUM % 128 ) and Parity ( XOR all values together ). The inputs and outputs are all Hex strings - except that the outputs will send the string 'ERROR' if the input is not valid (it checks that the string is pairs of hex digits, and that values are in the range 0x00-0x7F). There's also a little module to separate a 14bit (0 to 16383 range) integer into 7bit MSB and LSB - also handy if you use the MIDI 'Fine' continuous controllers.

trogluddite ·

Checksum generators upgraded to version 2 (download in top post).

No change in function - The body of the checksum loop is a little more efficient, as checking for a valid SysEx string is now done entirely with the custom parser (hooray, I'm finally getting the hang of it!) inside the initialise module. If there are out of range numbers in the string, the loop doesn't even have to run - and if it does run, it doesn't have to look for invalid numbers on every iteration.

sunsynth ·

Awesome work trog... 😀

Like the MSB/LSB part and especially the custom parser thingy (never get it 😊 )

keep on doing! Walter

trogluddite ·

sunsynth wrote: custom parser thingy (never get it 😊 )

Well, to be honest, lots of trial and error - I don't think I could make one 'to order'. Maybe this will help a little...

sunsynth ·

That looks like even i can understand it 😉

cheers

DigitalWhiteByte ·

trogluddite wrote: sunsynth wrote: custom parser thingy (never get it 😊 )

Well, to be honest, lots of trial and error - I don't think I could make one 'to order'. Maybe this will help a little...

Taking the results directly from the parse, so you can eliminate the loop to extract characters from hex string. To get the parameters read in sequence you can use the "Rule Action". As in this pseudo optimization.

trogluddite ·

Wow, that's really nice DWB. 🙂 Now I see you can get many triggers from the parser 'extract bits' blocks I have a much better understandng. Many thanks.

sunsynth ·

Yeah - well done...

Thanks Andrea!

DigitalWhiteByte ·

mmm... Andrea? 😝 PARSE - ERROR 🙂 hehehe

sunsynth ·

Sorry - getting old... 😊 😈

...but i dragged it into the correct Toolbox group 😉

Neptune ·

Great work guys! But btw. where are those Rule modules coming from?

DigitalWhiteByte ·

Neptune wrote: Great work guys! But btw. where are those Rule modules coming from?

MENU->OPTION->[TAB]ADVANCED-> Checkmark [on] R&D ... and voilà you can find it in Group Other 😉

Wrote something here? To have a post removed or your name hidden, write to [email protected].

Before your first post

A few rules keep this a friendly place. You agree to them once.

Shown next to what you post, here and in the app. It doesn’t have to be your real name: 3–24 lower-case letters, digits or _ (capitals become lower case, spaces become _).

    Then your post goes up straight away.

    Delete this reply?

    Open it in SynthMaker?

    It goes on the track you’re editing there, in place of that track’s sound, and into My sounds. Your other tracks stay as they are.

    Want to keep that track’s sound? Start a new song in SynthMaker first (Song › New song), then open this.

    Report this reply?

    Only the developer reads reports. The person isn’t told who reported them.

    What’s wrong with it?

    Block this person?

    You won’t see their posts and replies here any more. They aren’t told, and you can unblock them at any time.

    People you’ve blocked

    Their posts and replies are hidden from you. Unblock someone to see them again.

    The community rules

    A few rules keep this a friendly place. Everyone agrees to them once, before their first post.