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-28

; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
; 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>.
; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

0xF0h - sysex start
0x42h - Korg
0x21h - Poly 800
0x0Fh - HAWK parameter data value change in the running patch
parameter number (0x00-0x7Fh) - 0x00-0x3Fh P1 11-88 and 0x40h-0x7Fh P2 11-88
parameter value (0x00-0x7Fh) - paramater data value (either absolute or ranged - see owners manual)
0xF7h - EOX

Does this give you the detail you need for now?

/mike



From: "domgoold@... [korgpolyex]" <korgpolyex@yahoogroups.com>
To: korgpolyex@yahoogroups.com
Sent: Saturday, January 28, 2017 5:04 AM
Subject: Re: [korgpolyex] hawkmod sysex data format?

 
i also think absolute is best, as a default.
but generally you have to offset -1 with editors anyway
ie: a list going 1,2,3,4 is 0-3
as is the case with the Remote.

ok, so i'll wait for your new version; i can start the layout anyway.
sysex can mess up midi timing if overused, and nrpn is really
unintuitive to implement without a Novation Remote, as far as i can
work out.

so you say the parameter numbers will be the same whether it's
for NRPN(midiCC) or sysex? pretty sure lots of devices do not have
same nrpn number and sysex parameter, so that's easier.

if you have any clue as to what the sysex data format is now, and
the header .. :) i can at least copy that in ...