Archive of the former Yahoo!Groups mailing list: Korg Poly800/EX800 Users

previous by date index next by date
previous in topic topic list next in topic

Subject: Re: [korgpolyex] hawkmod sysex data format?

From: Michael Hawkins <korgpolyex800@...>
Date: 2017-01-26

Correction...
; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
; Patch parameter value change (affects running patch only)
; F0 42 21 0F 0x 0y F7
; Change the current patch parameter x (0-127) to value y (0-127).
; Where current sysex patch parameter values 0-63 are for parameters P1 <11-88) and...
; Where current sysex patch parameter values 64-127 are for parameters P2 <11-88>.
; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

/Mike

From: "Michael Hawkins korgpolyex800@... [korgpolyex]" <korgpolyex@yahoogroups.com>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com>
Sent: Thursday, January 26, 2017 9:17 AM
Subject: Re: [korgpolyex] hawkmod sysex data format?

 
I created the Novation Remote template. Not sure what you mean by stripped down since I used just about every slider, knob and button on the SL25.

I would recommend using the latest version of software. Why are you using 2.55 instead of 2.59?

Each paramater data value is sent in a sysex message as two consecutive sysex bytes. This was not really necessary because no HAWK parameter is larger than 127, so I could have formed the sysex data bytes by mapping one parameter data value to one sysex data byte. But I used two sysex data bytes so that if there was ever a day where I needed more than 127 in the sysex messages, I could do it. So the 'byte' is really just a sequence number. And yes, the byte/sequence no. is one higher than the actual MIDI CC parameter numbers. I shall update the sysex doc to reflect that.

The new version of code to come out soon is 2.65. And it has a sysex parameter set function as shown below.

; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
; Patch parameter value change
; F0 42 21 0F 0x 0y F7
; Change the current patch parameter x (0-63) to value y (0-127).
; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The above sysex acts just like a CC change in that it modifies the running patch data but does not change the stored patch at all. If you want to save the change then you can either request a patch dump of the running patch and then send it back to a specific patch. Also, when you see the sysex message above, the display briefly shows CC xx yy just like it was a MIDI CC message.

You probably need version 2.65 which I'll be posting next week.

/mike

From: "domgoold@... [korgpolyex]" <korgpolyex@yahoogroups.com>
To: korgpolyex@yahoogroups.com
Sent: Thursday, January 26, 2017 2:48 AM
Subject: [korgpolyex] hawkmod sysex data format?

 
hi,

thinking of making a Novation Remote mapping for Hawkmod+atomahawk

i'm looking at the sysex reference v2.55
and see the 'byte' column - are these the parameter numbers/addresses?

is it possible to send it sysex parameter change messages?
ie: F0 (manuf) (deviceID)(etc) <param> <value> F7

>>what is the hawkmod sysex data format?(plz)
------------------------------------------------------------------------------
or are these for NRPN ? (no, it's the 'sysex reference'...)
don't 100% know if there is a distinction between sysex parameter number
and NRPN parameter number.

i've had a look at the NovationRemote25 syx file - which is quite stripped
down, and am thinking of doing a full layout with the remoteSL editor.
haven't done a NRPN mapping before, just sysex - but it looks like the
Remote handles it all automatically.
(still not sure what Rel1/Rel2/APot do, exactly..)

one thing i noticed with NRPNs on another device was that edits were
'temporary', and not changing the stored parameters - but that was
Yamaha XG, where you can 'edit' setting with sysex, but nrpns+cc
get cleared each time you restart song/machine and aren't stored.

have to have another look at that Remote25.syx ...