Korg Poly800/EX800 Users

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

yes > remote25. that's it. i've got a remoteSL, Zero, without keys.
it's probably got a completely different layout but i was able to open
it in the RemoteSL mk1 editor. i think the SL is more common the
the 25 which came before.

yours relies on calling the parameter via P1-8, banks of parameters.
and then adjusting the value, inc dec, like on the panel.

what about just having analog controls for each parameter?
NRPN - i think - adjusts 1 parameter at a time, and needs to be
nulled after each 'burst' of messages - i haven't used nrpn before,
i'm used to midi cc and sysex.

so, for example, you map out a page dedicated to an envelope and
have all the controls displayed simultaneously with names. - you
can have multiple pages linked with the SL, and it holds 40 user
templates in memory. you can have series of templates, <name>1/2/3 etc.
referred to as 'a' template, and link these via buttons assigned to template
numbers, ie: use the drumpads for this, so you can navigate easily between
sections. i've been messing around with this making maps for multitimbral
blackbox rack units with button menus. transfer via usb, and updating of
the remoteSL works really well, and the editor software works really well.

so the sysex document 'sysex reference 2.5.5' says
'byte' above what appears to be the parameter number list.

if a sysex parameter change message can be received by hawk800,
it should go F0,xx,xx,...,parameter, <variable value>, F7

so that's the question really: how to address those parameter numbers
and send them a value. is it sysex or nrpn ;-) ?

tbh, my hawkmod kit is still sitting in a little box waiting for me to have
the time and guts to fit it. i'm going to have to take photos and everything
to show you what version i have... : - / and i'm seeing stuff like the
circuitbenders rotary pots as well. i need to pull myself together and just
get stuck in lol

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

I saw the mention of defaulting to Absolute CC/NRPN controller values.


I prefer the Ranged values. 

First since the GUI I am making has all been set up for Ranged values..  not only the actual GUI knobs, but also all the LUA scripting that fetches every pair of bytes in a patch dump and then converts the values from absolute to ranged.

Second.  Most controllers I have are sliders/pots with endpoints vs. endless encoders.  Plus there are toggling momentary switches.
Most controllers want to set a ON/OFF parameter to be 0/127 values.


PS-
Getting VERY CLOSE to updating the GUI I had partially working a few years ago.
Updates include MkII effects controls, Atomahawk controls, dynamic Envelope Generator graphics with Inverted EG3 display and a COPY DCO1 EG to DCO2 EG feature.

The cool part is it will automatically set all the controls every time you change the patch by selecting the number via the GUI console.   Very quickly you can see what waveform goes to which modulator/LFO, SLFO, DCO, etc..    It just about eliminates the need to look up the parameter reference since most controls are self explanatory.


/Blaine

Hi Mike
thanks for that;, i'm checking it out.
i can't see MIDI Channel in that - is that necessary?
i'm pretty sure all previous sysex i've dealt with had a midich byte.

if we call this the 'header':

F0 42 21 0F

i'm expecting to see midiCH ..between the 21h and 0Fh, or maybe after.
maybe it isn't needed with monotimbral devices that don't have a Basic Channel.

looks pretty straightforward anyway.
so i could also call a parameter with NRPN by addressing it with MSB=0,
LSB=(param#), using the same parameter numbers?

Bimmerfan: 'LUA' ? are you making Ctrlr panels? i could do with some tips
on how to use Lua, absolutely clueless. i have some panels on the go but
can't get any further with them until i suss out Lua scripts.

On Sun, Jan 29, 2017 at 06:49:59AM +0000, domgoold@... [korgpolyex] wrote:

> Hi Mike
> thanks for that;, i'm checking it out.
> i can't see MIDI Channel in that - is that necessary?
> i'm pretty sure all previous sysex i've dealt with had a midich byte.

Sysex messages only specify that the start with $f0 and then the manufacturer and product code, and end with $f7 - there's nothing in the spec about sysex but that doesn't mean a particular manufacturer hasn't used a byte that specifies it.

There are good reasons not to, for example if you want to distribute patches using sysex and you want people to have to change channel on their instrument.

There are good reasons to use them, for example if you have a bunch of identical instruments and only want to change parameters on one of them.

--
Gordonjcp MM0YEQ

no problem, i can get started with that.
i've just done something with something like 400-500 parameters,
so this one will be a doddle :-) the extra byte doesn't take long
to add.

i'll be interested to see what happens if i do it with NRPN. i've
never used those successfully. last time i tried it was from an
atari and i cound't figure out how it was all sent 'simultaneously'
from a cubase mixermap; but the RemoteSL seems like an
opportunity to use them sensibly.

HEHE...you're going to have ot help me with some of the
abbreviations ;-) i have 8 characters to work with per param title/label:

'sequencer clock random sample and hold increment' ...mmm
and
'sustain decay release eg offset' ...'offset' is always a pita, 6 characters,
and doesn't abbreviate well.

'DCO1 trem off, LFO1/2 select' ...

vcf mg modulator waveform...etc.

i think also there's an erratum: LFO3 Wave appears twice, at 70 and 78

i'm just filling in slots atm, follwing the chart order, to see how many pages
it will need. first stage. looks like three, maybe four, depending on how it
looks.i might split out modulation destinations to several momentary buttons,
so i can name them for more clarity.

yeah, if you can paraphrase some of those lol
i usually abbreviate something like 'LFO1' to 'L1' if needed.(so LFO1Rate,
can become L1R at a push)