Korg Poly800/EX800 Users

Mike,
It took me a while to get my PC to communicate with the Hawk800, but finally made it with NRPNs. I'm trying to get a software editor going.

However I have the following problem:
In sending the NRPN code I see the the correct numbers are going to the Hawk, for instance:
99,0,
98,24 (for filter cutoff),
6,0

However, that last 0 is being read by the synth as a zero, and I find that I can't vary that figure. My software allows me to create a GUI with sliders, and whilst the slider does show the number changing, the synth remains fixed on 0. This is msb_value I guess, but what can I do to turn that 0 into a variable "x"? I have also contacted the developers of my software with the same question.
Thanks

Thanks for your reply, Mike. Yes I had already changed global parameter to 0 and got communication with the synth, but I can't see an obvious solution to this, it may lie with the software I'm using??
Dan

--- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote:
>
> The NRPN MSB must be equal to global parameter 16.
>
> The default value for global parameter 16 is 1 (not zero).
>
> So perhaps you need to set NRPN MSB to 1 or change global 16 to zero.
>
> Mike
>
>
> ________________________________
> From: dpaulo2 <dpaulo@...>
> To: korgpolyex@yahoogroups.com
> Sent: Sunday, August 5, 2012 8:57 AM
> Subject: [korgpolyex] question about NRPNs
>
>
> Â
> Mike,
> It took me a while to get my PC to communicate with the Hawk800, but finally made it with NRPNs. I'm trying to get a software editor going.
>
> However I have the following problem:
> In sending the NRPN code I see the the correct numbers are going to the Hawk, for instance:
> 99,0,
> 98,24 (for filter cutoff),
> 6,0
>
> However, that last 0 is being read by the synth as a zero, and I find that I can't vary that figure. My software allows me to create a GUI with sliders, and whilst the slider does show the number changing, the synth remains fixed on 0. This is msb_value I guess, but what can I do to turn that 0 into a variable "x"? I have also contacted the developers of my software with the same question.
> Thanks
>

Mike,
I finally gave up on NRPNs, they were just not going to work for me. However I've managed to break through with CCs so at last am making progress.
One thing bugs me though, which is the MIDI scaling from 0-127, so instead of sending, say, 0 and 1, for an on/off switch, it has to be 0 and 127. It means that all parameters on the GUI will be seen to go up to 127, even if they go up to only 15. Whilst my program will work fine, it would be more appropriate if the slider was shown to go up to the number that is the particular parameter's highest point. Could there be any workaround to this??
Thanks
Dan

Dan: do you have to show the values? can you have just
a graphic of a button with a LED? don't know what you are
using for this...
trying to remember what happened with the tx81z: a lot of
its values go 0-99. this was cubase mixer map..i think you
could limit the fader range.

Mike - i KNOW you've been asked this before, maybe even by
me(...) - but can we have a repeat runthrough on sending a
NRPN CC message (if that's the right description)? BECAUSE:
i know you have to send the nrpn and msb(though i'm well hazy
on this: having been put off by failure, i wrote it off too)
and then you have to select data entry #6 and then the value...

so.. step by step: ...given a novation remote controller, for
example, and i wanted to whack up the cutoff a bit, then the res,
in quick realtime succession, how would this be done? could i
program each knob to send the required series of messages, (as with
regular CCs?)or do i need a button to select this, then select parameter, then send data values?
in essence, i'm really more interested in progging up patches
fairly quickly, than in realtime control (eg as with an editor),
or tweaking a patch without having to push a load of buttons.
(although that really isn't so bad on simple old machine like this: there are mid90s machines that require much more button presses,
although they claim to be 'realtime control' machines...pffff)

--- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote:
>
> I added this to the sourceforge feature requests list.
>
> Since I have slowed down development, I add these to the feature list so that I can get to them in one go when i block some time out for HAWK.
>
> Mike
>
>
> ________________________________
> From: dpaulo2 <dpaulo@...>
> To: korgpolyex@yahoogroups.com
> Sent: Friday, August 10, 2012 2:40 AM
> Subject: [korgpolyex] Re: question about NRPNs
>
>
> Â
> Mike,
> I finally gave up on NRPNs, they were just not going to work for me. However I've managed to break through with CCs so at last am making progress.
> One thing bugs me though, which is the MIDI scaling from 0-127, so instead of sending, say, 0 and 1, for an on/off switch, it has to be 0 and 127. It means that all parameters on the GUI will be seen to go up to 127, even if they go up to only 15. Whilst my program will work fine, it would be more appropriate if the slider was shown to go up to the number that is the particular parameter's highest point. Could there be any workaround to this??
> Thanks
> Dan
>

I'm using a Renoise tool called Guru which does most of the work for me. The result will hopefully be a very easy to use editor for the Hawk. I have had to fiddle a bit with Guru's own code to accommodate Hawk's CC requirements. On Guru's GUI each slider is shown to reflect the MIDI value sent, so all sliders will show 0-127 even if they only have 15 steps. It's not a big deal as everything will still work fine, but it does mean that when you drag the slider you'll have to look at the synth if you need to know what the actual received value is.
Dan

--- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@...> wrote:
>
> Dan: do you have to show the values? can you have just
> a graphic of a button with a LED? don't know what you are
> using for this...
> trying to remember what happened with the tx81z: a lot of
> its values go 0-99. this was cubase mixer map..i think you
> could limit the fader range.
>
> Mike - i KNOW you've been asked this before, maybe even by
> me(...) - but can we have a repeat runthrough on sending a
> NRPN CC message (if that's the right description)? BECAUSE:
> i know you have to send the nrpn and msb(though i'm well hazy
> on this: having been put off by failure, i wrote it off too)
> and then you have to select data entry #6 and then the value...
>
> so.. step by step: ...given a novation remote controller, for
> example, and i wanted to whack up the cutoff a bit, then the res,
> in quick realtime succession, how would this be done? could i
> program each knob to send the required series of messages, (as with
> regular CCs?)or do i need a button to select this, then select parameter, then send data values?
> in essence, i'm really more interested in progging up patches
> fairly quickly, than in realtime control (eg as with an editor),
> or tweaking a patch without having to push a load of buttons.
> (although that really isn't so bad on simple old machine like this: there are mid90s machines that require much more button presses,
> although they claim to be 'realtime control' machines...pffff)
>
> --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> wrote:
> >
> > I added this to the sourceforge feature requests list.
> >
> > Since I have slowed down development, I add these to the feature list so that I can get to them in one go when i block some time out for HAWK.
> >
> > Mike
> >
> >
> > ________________________________
> > From: dpaulo2 <dpaulo@>
> > To: korgpolyex@yahoogroups.com
> > Sent: Friday, August 10, 2012 2:40 AM
> > Subject: [korgpolyex] Re: question about NRPNs
> >
> >
> > Â
> > Mike,
> > I finally gave up on NRPNs, they were just not going to work for me. However I've managed to break through with CCs so at last am making progress.
> > One thing bugs me though, which is the MIDI scaling from 0-127, so instead of sending, say, 0 and 1, for an on/off switch, it has to be 0 and 127. It means that all parameters on the GUI will be seen to go up to 127, even if they go up to only 15. Whilst my program will work fine, it would be more appropriate if the slider was shown to go up to the number that is the particular parameter's highest point. Could there be any workaround to this??
> > Thanks
> > Dan
> >
>

I'm using a Renoise tool called Guru which does most of the work for me. The result will hopefully be a very easy to use editor for the Hawk. I have had to fiddle a bit with Guru's own code to accommodate Hawk's CC requirements. On Guru's GUI each slider is shown to reflect the MIDI value sent, so all sliders will show 0-127 even if they only have 15 steps. It's not a big deal as everything will still work fine, but it does mean that when you drag the slider you'll have to look at the synth if you need to know what the actual received value is.
Dan

--- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@...> wrote:
>
> Dan: do you have to show the values? can you have just
> a graphic of a button with a LED? don't know what you are
> using for this...
> trying to remember what happened with the tx81z: a lot of
> its values go 0-99. this was cubase mixer map..i think you
> could limit the fader range.
>
> Mike - i KNOW you've been asked this before, maybe even by
> me(...) - but can we have a repeat runthrough on sending a
> NRPN CC message (if that's the right description)? BECAUSE:
> i know you have to send the nrpn and msb(though i'm well hazy
> on this: having been put off by failure, i wrote it off too)
> and then you have to select data entry #6 and then the value...
>
> so.. step by step: ...given a novation remote controller, for
> example, and i wanted to whack up the cutoff a bit, then the res,
> in quick realtime succession, how would this be done? could i
> program each knob to send the required series of messages, (as with
> regular CCs?)or do i need a button to select this, then select parameter, then send data values?
> in essence, i'm really more interested in progging up patches
> fairly quickly, than in realtime control (eg as with an editor),
> or tweaking a patch without having to push a load of buttons.
> (although that really isn't so bad on simple old machine like this: there are mid90s machines that require much more button presses,
> although they claim to be 'realtime control' machines...pffff)
>
> --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> wrote:
> >
> > I added this to the sourceforge feature requests list.
> >
> > Since I have slowed down development, I add these to the feature list so that I can get to them in one go when i block some time out for HAWK.
> >
> > Mike
> >
> >
> > ________________________________
> > From: dpaulo2 <dpaulo@>
> > To: korgpolyex@yahoogroups.com
> > Sent: Friday, August 10, 2012 2:40 AM
> > Subject: [korgpolyex] Re: question about NRPNs
> >
> >
> > Â
> > Mike,
> > I finally gave up on NRPNs, they were just not going to work for me. However I've managed to break through with CCs so at last am making progress.
> > One thing bugs me though, which is the MIDI scaling from 0-127, so instead of sending, say, 0 and 1, for an on/off switch, it has to be 0 and 127. It means that all parameters on the GUI will be seen to go up to 127, even if they go up to only 15. Whilst my program will work fine, it would be more appropriate if the slider was shown to go up to the number that is the particular parameter's highest point. Could there be any workaround to this??
> > Thanks
> > Dan
> >
>