HAWK-800 Sysex Patch Dump format
2010-11-30 by tim.tashpulatov
Mike, Could you please shed some light on Hawk-800's patch dump format? I am thinking of some external way to tweak patch parameters and to send changes back via sysex. Regards Tim
Thread
HAWK-800 Sysex Patch Dump format
Re: [korgpolyex] HAWK-800 Sysex Patch Dump format
2010-11-30 by Michael Hawkins
Tim, You might be interested in looking at the JsynthLib editor/librarian that I have been working on. If you're interested I can post it. Meanwhile, I'll get the other group members here to chime in with their own templates. And I will get the patch sysex table put together over the next couple of days. Mike ________________________________
Show quoted textHide quoted text
From: tim.tashpulatov <tim.tashpulatov@...> To: korgpolyex@yahoogroups.com Sent: Tue, November 30, 2010 2:25:07 AM Subject: [korgpolyex] HAWK-800 Sysex Patch Dump format Mike, Could you please shed some light on Hawk-800's patch dump format? I am thinking of some external way to tweak patch parameters and to send changes back via sysex. Regards Tim
Re: [korgpolyex] HAWK-800 Sysex Patch Dump format
2010-11-30 by Michael Hawkins
Well, here is the raw format of the data. See the MIDI implementation for the precise format of the sysex message. In order, from patch byte 0 through to patch byte 127 (which takes two bytes each in the patch sysex dump itself). The left hand is the maximum value for the parameter. If you exceed the value then when the patch is selected the parameter that has the invalid value will be set to half of the maximum for that parameter. Let me know if you have any questions at all. 2 , 11 DCO1 Octave 1 , 12 DCO1 Waveform 15 , 13 DCO1 harmonics 12 , 14 DCO1 harmonic modulator waveform 3 , 15 DCO1 harmonic modulator source 15 , 16 DCO1 harmonic modulator depth 31 , 17 DCO1 Level 1 , 18 DCO mode single or double 2 , 21 DCO2 Octave 1 , 22 DCO2 Waveform 15 , 23 DCO2 harmonics 12 , 24 DCO2 harmonic modulator waveform 3 , 25 DCO2 harmonic modulator source 15 , 26 DCO2 harmonic modulator depth 31 , 27 DCO2 Level 0 , 28 Not used 12 , 31 Interval 3 , 32 Detune 15 , 33 Noise 99 , 34 Delay Time 15 , 35 Delay Feedback 31 , 36 Delay Modulation Frequency 31 , 37 Delay Modulation Intensity 15 , 38 Delay Effect Level 99 , 41 VCF cut off 2 , 42 Keyboard Track 1 , 43 Polarity 15 , 44 EG3 VCF cutoff influence 1 , 45 EG3 Trigger 12 , 46 EQ treble 12 , 47 EQ bass 1 , 48 Chorus 31 , 51 EG1 Attack 31 , 52 EG1 Decay 31 , 53 EG1 Break Point 31 , 54 EG1 Slope 31 , 55 EG1 Sustain 31 , 56 EG1 Release 0 , 57 Not used 0 , 58 Not used 31 , 61 EG2 Attack 31 , 62 EG2 Decay 31 , 63 EG2 Break Point 31 , 64 EG2 Slope 31 , 65 EG2 Sustain 31 , 66 EG2 Release 0 , 67 Not used 0 , 68 Not used 31 , 71 EG3 Attack 31 , 72 EG3 Decay 31 , 73 EG3 Break Point 31 , 74 EG3 Slope 31 , 75 EG3 Sustain 31 , 76 EG3 Release 0 , 77 Not used 0 , 78 Not used 4 , 81 Velocity operator 1 intensity 1 , 82 Velocity operator 1 invert 11 , 83 Velocity operator 1 target 4 , 84 Velocity operator 2 intensity 1 , 85 Velocity operator 2 invert 11 , 86 Velocity operator 2 target 6 , 87 VCF velocity sensitive intensity 5 , 88 VCF velocity sensitive response shape 15 , 11 LFO1 frequency 15 , 12 LFO1 delay 1 , 13 LFO1 free running 1 , 14 LFO1 delay type 62 , 15 LFO1 square wave PWM ratio 12 , 16 LFO3 waveform select 15 , 17 LFO3 modulation depth of SLFO1 0 , 18 Not used 15 , 21 LFO2 frequency 15 , 22 LFO2 delay 1 , 23 LFO2 free running 1 , 24 LFO2 delay type 62 , 25 LFO2 square wave PWM ratio 12 , 26 LFO3 waveform select 15 , 27 LFO3 modulation depth of SLFO2 63 , 28 LFO2 sync driven 0=original oscillator, 1-63 sequencer clock driven 12 , 31 DCO MG 1st modulator waveform 3 , 32 DCO MG 1st modulator source 15 , 33 DCO MG 1st modulator depth 0 , 34 Not used 1 , 35 DCO MG EG invert 15 , 36 DCO MG EG depth 0 , 37 unused 2 , 38 DCO MG mode 12 , 41 VCF MG 1st modulator waveform 3 , 42 VCF MG 1st modulator source 15 , 43 VCF MG 1st modulator depth 12 , 44 VCF MG 2nd modulator waveform 3 , 45 VCF MG 2nd modulator source 15 , 46 VCF MG 2nd modulator depth 0 , 47 unused 1 , 48 12/24db filter cutoff select 99 , 51 Resonance set point 12 , 52 Resonance MG waveform 3 , 53 Resonance MG source 15 , 54 Resonance MG depth 0 , 55 Not used 15 , 56 Resonance EG depth 1 , 57 Resonance EG invert 1 , 58 Resonance mode 99 , 61 FM-800 set point 12 , 62 FM-800 MG waveform 3 , 63 FM-800 MG source 15 , 64 FM-800 MG depth 0 , Not used 15 , 66 FM-800 EG depth 1 , 67 FM-800 EG invert 2 , 68 Noise mode 15 , 71 SLFO3 frequency 62 , 72 SLFO3 square wave PWM ratio 1 , 73 SLFO3 free running 98 , 74 sequencer clock random sample and hold increment 15 , 75 SLFO4 frequency 62 , 76 SLFO4 square wave PWM ratio 1 , 77 SLFO4 free running 31 , 78 sustain decay and release EG offset 2 , 81 DCO1 tremolo off, LFO1/2 select 15 , 82 DCO1 tremolo depth 2 , 83 DCO2 tremolo off, LFO1/2 select 15 , 84 DCO2 tremolo depth 63 , 85 Bend depth 63 , 86 Portamento slide rate 0 , 87 unused 3 , 88 Operating Poly Mode All parameter values start at zero. For example, waveform is displayed as 1 or 2 but is stored as 0 or 1. This applies to all parameters that start at one. They are in fact stored as one less than the display shows. Please also keep in mind that I plan to rewrite the sysex patch dumps so that they use a single MIDI byte instead of two per value. However, when I do that, I will use a new sysex message ID number so that the existing patch dump sysex commands still work. Ask as many questions as you wish. Mike ________________________________
Show quoted textHide quoted text
From: tim.tashpulatov <tim.tashpulatov@...> To: korgpolyex@yahoogroups.com Sent: Tue, November 30, 2010 2:25:07 AM Subject: [korgpolyex] HAWK-800 Sysex Patch Dump format Mike, Could you please shed some light on Hawk-800's patch dump format? I am thinking of some external way to tweak patch parameters and to send changes back via sysex. Regards Tim
Re: HAWK-800 Sysex Patch Dump format
2010-12-01 by tim.tashpulatov
Mike, Yes please, I'd love to take a look at JSynthLib. The last one I have checked in the Files section of the group missed actual parameter editing stuff. Regards Tim --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote:
Show quoted textHide quoted text
> > Tim, > > You might be interested in looking at the JsynthLib editor/librarian that I have > been working on. If you're interested I can post it. > > Meanwhile, I'll get the other group members here to chime in with their own > templates. > > And I will get the patch sysex table put together over the next couple of days. > > > Mike > > > > ________________________________ > From: tim.tashpulatov <tim.tashpulatov@...> > To: korgpolyex@yahoogroups.com > Sent: Tue, November 30, 2010 2:25:07 AM > Subject: [korgpolyex] HAWK-800 Sysex Patch Dump format > > > Mike, > > Could you please shed some light on Hawk-800's patch dump format? I am thinking > of some external way to tweak patch parameters and to send changes back via > sysex. > > Regards > Tim >
Re: HAWK-800 Sysex Patch Dump format
2010-12-04 by zoinky420
--- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote: > > Meanwhile, I'll get the other group members here to chime in with their own > templates. > How does one make a template?
Re: [korgpolyex] Re: HAWK-800 Sysex Patch Dump format
2010-12-04 by Michael Hawkins
Well, some of my fellow HAWK fans have created templates for the various sequencer, arranger and controller software packages that are out there. So I was referring to those. ________________________________
Show quoted textHide quoted text
From: zoinky420 <zoinky420@...> To: korgpolyex@yahoogroups.com Sent: Sat, December 4, 2010 3:23:57 AM Subject: [korgpolyex] Re: HAWK-800 Sysex Patch Dump format --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote: > > Meanwhile, I'll get the other group members here to chime in with their own > templates. > How does one make a template?
Re: HAWK-800 Sysex Patch Dump format
2010-12-04 by k9k9dog
if you upload a link to the new sysex data format and midi implementation chart, i could knock up a vst editor in synthedit. i just need to suss out how to send out sysex variables, but it shouldn't be too hard. (i'd like to know a bit more about midi cc's implemented, too. also, Mike, could you please email me about the order i want to place with you :) ) --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote:
Show quoted textHide quoted text
> > Well, some of my fellow HAWK fans have created templates for the various > sequencer, arranger and controller software packages that are out there. So I > was referring to those. > > > > > > ________________________________ > From: zoinky420 <zoinky420@...> > To: korgpolyex@yahoogroups.com > Sent: Sat, December 4, 2010 3:23:57 AM > Subject: [korgpolyex] Re: HAWK-800 Sysex Patch Dump format > > > > > --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> wrote: > > > > Meanwhile, I'll get the other group members here to chime in with their own > > templates. > > > > How does one make a template? >
Re: HAWK-800 Sysex Patch Dump format
2010-12-04 by k9k9dog
ugh, sorry, hadn't read previous post..nice long list :) i wrote a load of cubase mixermaps years ago, so it's familiar territory. just need the data format; if you send the hawk800 a data transfer request message, it will send back exactly what it uses, say, into a list editor in record mode. eg: one line: F0,manuf,device,(unit?), etc. ..F7 one thing i NEVER sussed out how to do - and i tried - was the NRPN+data entry thing. ???send simultaneously? couldn't work out how to do it. sysex works ok though. would be waaaay cool if all these could be mapped to MIDI CCs. --- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@...> wrote:
Show quoted textHide quoted text
> > if you upload a link to the new sysex data format and > midi implementation chart, i could knock up a vst editor > in synthedit. i just need to suss out how to send out > sysex variables, but it shouldn't be too hard. > (i'd like to know a bit more about midi cc's implemented, > too. also, Mike, could you please email me about the order > i want to place with you :) ) > > --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> wrote: > > > > Well, some of my fellow HAWK fans have created templates for the various > > sequencer, arranger and controller software packages that are out there. So I > > was referring to those. > > > > > > > > > > > > ________________________________ > > From: zoinky420 <zoinky420@> > > To: korgpolyex@yahoogroups.com > > Sent: Sat, December 4, 2010 3:23:57 AM > > Subject: [korgpolyex] Re: HAWK-800 Sysex Patch Dump format > > > > > > > > > > --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> wrote: > > > > > > Meanwhile, I'll get the other group members here to chime in with their own > > > templates. > > > > > > > How does one make a template? > > >
Re: HAWK-800 Sysex Patch Dump format
2010-12-07 by tim.tashpulatov
According to MIDI implementation, seems like it is possible to change one parameter at a time using CC84 and CC85. So I dug out my old proto board with Atmel MCU, some old touchpad and digital pot, and started thinking this over. And while looking for ways to attach pots to my board, I have found this: http://the-all.org/tx81z/twopot/index.html It's a simple project, sort of hardware patch editor with an LCD, a couple of knobs and MIDI output to control TX81Z. I guess something similar could be done for controlling HAWK-800, too. Having all the parameter names shown in human readable format on the LCD would be nice. --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote:
Show quoted textHide quoted text
> > Well, here is the raw format of the data. See the MIDI implementation for the > precise format of the sysex message.
Re: HAWK-800 Sysex Patch Dump format
2010-12-07 by k9k9dog
*if i may say* (...) seems really xxxx heavyweight, lol! for an issue that could be resolved more simply using sysex. i used to get some quite complex sysex edits going on without affecting timing, with multiple params moving, etc. am dl'ing this to examine offline, but think best to make equivalent of a cubase 'mixer map', accessing any parameter wanted via an GUI-based editor. ca make as synthedit(windows) VST instrument, and if anyone wants to port that to a Mac etc thing, can upload the project file. HOWEVER! if someone can accurately describe how to perform NRPN edit via MIDI, that could be another method (never got it to work here ) ie: an object(fader/knob) sends out a(ny) parameter value variable in realtime. --- In korgpolyex@yahoogroups.com, "tim.tashpulatov" <tim.tashpulatov@...> wrote:
Show quoted textHide quoted text
> > According to MIDI implementation, seems like it is possible to change one parameter at a time using CC84 and CC85. So I dug out my old proto board with Atmel MCU, some old touchpad and digital pot, and started thinking this over. > > And while looking for ways to attach pots to my board, I have found this: > > http://the-all.org/tx81z/twopot/index.html > > It's a simple project, sort of hardware patch editor with an LCD, a couple of knobs and MIDI output to control TX81Z. I guess something similar could be done for controlling HAWK-800, too. Having all the parameter names shown in human readable format on the LCD would be nice. > > > --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> wrote: > > > > Well, here is the raw format of the data. See the MIDI implementation for the > > precise format of the sysex message. >
Re: HAWK-800 Sysex Patch Dump format
2010-12-08 by k9k9dog
hi tim: i read that article, and see what it does, but would find editing tx/dx like that really frustrating (although you'd have to have a go with it before judging) i used to have a fun editor on the atari, and may even have had a cubase mixer map for it. for the poly/ex, seems like a nice GUI based editor would be most useful (if using a pc/mac) --- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@...> wrote:
Show quoted textHide quoted text
> > *if i may say* (...) seems really xxxx heavyweight, lol! > for an issue that could be resolved more simply using sysex. > i used to get some quite complex sysex edits going on without > affecting timing, with multiple params moving, etc. > > am dl'ing this to examine offline, but think best to make > equivalent of a cubase 'mixer map', accessing any parameter > wanted via an GUI-based editor. ca make as synthedit(windows) > VST instrument, and if anyone wants to port that to a Mac etc > thing, can upload the project file. > > HOWEVER! if someone can accurately describe how to perform > NRPN edit via MIDI, that could be another method (never got it > to work here ) > > ie: an object(fader/knob) sends out a(ny) parameter value variable > in realtime. > > --- In korgpolyex@yahoogroups.com, "tim.tashpulatov" <tim.tashpulatov@> wrote: > > > > According to MIDI implementation, seems like it is possible to change one parameter at a time using CC84 and CC85. So I dug out my old proto board with Atmel MCU, some old touchpad and digital pot, and started thinking this over. > > > > And while looking for ways to attach pots to my board, I have found this: > > > > http://the-all.org/tx81z/twopot/index.html > > > > It's a simple project, sort of hardware patch editor with an LCD, a couple of knobs and MIDI output to control TX81Z. I guess something similar could be done for controlling HAWK-800, too. Having all the parameter names shown in human readable format on the LCD would be nice. > > > > > > --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> wrote: > > > > > > Well, here is the raw format of the data. See the MIDI implementation for the > > > precise format of the sysex message. > > >
Re: HAWK-800 Sysex Patch Dump format
2010-12-09 by tim.tashpulatov
I agree, I would too prefer some on-screen controls with knobs and buttons running on PC. My setup is under Linux, and so far I haven't found any tools there suitable for hacking custom synth layout. You know, like those old true analog synth used to have on their front panels. (In fact, I havent even figured out how to just hack one single knob capable of sending certain CC.) It's that I've got enough spare parts in my junk box, and the itch to solder together another something after I've assembled my HAWK-800 :) --- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@...> wrote:
Show quoted textHide quoted text
> > hi tim: i read that article, and see what it does, > but would find editing tx/dx like that really frustrating > (although you'd have to have a go with it before judging) > i used to have a fun editor on the atari, and may even > have had a cubase mixer map for it. > for the poly/ex, seems like a nice GUI based editor > would be most useful (if using a pc/mac) > > --- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@> wrote: > > > > *if i may say* (...) seems really xxxx heavyweight, lol! > > for an issue that could be resolved more simply using sysex. > > i used to get some quite complex sysex edits going on without > > affecting timing, with multiple params moving, etc. > > > > am dl'ing this to examine offline, but think best to make > > equivalent of a cubase 'mixer map', accessing any parameter > > wanted via an GUI-based editor. ca make as synthedit(windows) > > VST instrument, and if anyone wants to port that to a Mac etc > > thing, can upload the project file. > > > > HOWEVER! if someone can accurately describe how to perform > > NRPN edit via MIDI, that could be another method (never got it > > to work here ) > > > > ie: an object(fader/knob) sends out a(ny) parameter value variable > > in realtime. > > > > --- In korgpolyex@yahoogroups.com, "tim.tashpulatov" <tim.tashpulatov@> wrote: > > > > > > According to MIDI implementation, seems like it is possible to change one parameter at a time using CC84 and CC85. So I dug out my old proto board with Atmel MCU, some old touchpad and digital pot, and started thinking this over. > > > > > > And while looking for ways to attach pots to my board, I have found this: > > > > > > http://the-all.org/tx81z/twopot/index.html > > > > > > It's a simple project, sort of hardware patch editor with an LCD, a couple of knobs and MIDI output to control TX81Z. I guess something similar could be done for controlling HAWK-800, too. Having all the parameter names shown in human readable format on the LCD would be nice. > > > > > > > > > --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> wrote: > > > > > > > > Well, here is the raw format of the data. See the MIDI implementation for the > > > > precise format of the sysex message. > > > > > >
Re: [korgpolyex] Re: HAWK-800 Sysex Patch Dump format
2010-12-09 by Michael Hawkins
you all need to seriously consider JsynthLib. I have the basic patch librarian part of it working. I just haven't finished the editor. If anyone is really interested in helping out then I'll post my work so far. Mike. ________________________________ From: tim.tashpulatov <tim.tashpulatov@gmail.com> To: korgpolyex@yahoogroups.com Sent: Thu, December 9, 2010 5:21:39 AM Subject: [korgpolyex] Re: HAWK-800 Sysex Patch Dump format I agree, I would too prefer some on-screen controls with knobs and buttons running on PC. My setup is under Linux, and so far I haven't found any tools there suitable for hacking custom synth layout. You know, like those old true analog synth used to have on their front panels. (In fact, I havent even figured out how to just hack one single knob capable of sending certain CC.) It's that I've got enough spare parts in my junk box, and the itch to solder together another something after I've assembled my HAWK-800 :) --- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@...> wrote:
Show quoted textHide quoted text
> > hi tim: i read that article, and see what it does, > but would find editing tx/dx like that really frustrating > (although you'd have to have a go with it before judging) > i used to have a fun editor on the atari, and may even > have had a cubase mixer map for it. > for the poly/ex, seems like a nice GUI based editor > would be most useful (if using a pc/mac) > > --- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@> wrote: > > > > *if i may say* (...) seems really xxxx heavyweight, lol! > > for an issue that could be resolved more simply using sysex. > > i used to get some quite complex sysex edits going on without > > affecting timing, with multiple params moving, etc. > > > > am dl'ing this to examine offline, but think best to make > > equivalent of a cubase 'mixer map', accessing any parameter > > wanted via an GUI-based editor. ca make as synthedit(windows) > > VST instrument, and if anyone wants to port that to a Mac etc > > thing, can upload the project file. > > > > HOWEVER! if someone can accurately describe how to perform > > NRPN edit via MIDI, that could be another method (never got it > > to work here ) > > > > ie: an object(fader/knob) sends out a(ny) parameter value variable > > in realtime. > > > > --- In korgpolyex@yahoogroups.com, "tim.tashpulatov" <tim.tashpulatov@> >wrote: > > > > > > According to MIDI implementation, seems like it is possible to change one >parameter at a time using CC84 and CC85. So I dug out my old proto board with >Atmel MCU, some old touchpad and digital pot, and started thinking this over. > > > > > > And while looking for ways to attach pots to my board, I have found this: > > > > > > http://the-all.org/tx81z/twopot/index.html > > > > > > It's a simple project, sort of hardware patch editor with an LCD, a couple >of knobs and MIDI output to control TX81Z. I guess something similar could be >done for controlling HAWK-800, too. Having all the parameter names shown in >human readable format on the LCD would be nice. > > > > > > > > > --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> wrote: > > > > > > > > Well, here is the raw format of the data. See the MIDI implementation for >the > > > > > precise format of the sysex message. > > > > > >
Re: [korgpolyex] Re: HAWK-800 Sysex Patch Dump format
2010-12-09 by joe peak
Ya know.......You've given me an idea......Like those old roland synths where they have a breakout box full of knobs and such. One could make a midi box using the very hip Arduino, and make knobs controlling MIDI CCs. The box would connect via MIDI and could sit on the Poly's top panel where the parameter tables are....Giving real knobs for parameters. I was also thinking about hacking my Oxygen8 midi controller and taking out the eight knobs and slider then putting them into a custom made box to attach to the poly. Those knobs on the Oxygen are programmable and could be changed whenever needed.
Just an idea.........
J.
--- On Thu, 12/9/10, tim.tashpulatov <tim.tashpulatov@...> wrote:
From: tim.tashpulatov <tim.tashpulatov@...>
Subject: [korgpolyex] Re: HAWK-800 Sysex Patch Dump format
To: korgpolyex@yahoogroups.com
Date: Thursday, December 9, 2010, 2:21 AM
I agree, I would too prefer some on-screen controls with knobs and buttons running on PC. My setup is under Linux, and so far I haven't found any tools there suitable for hacking custom synth layout. You know, like those old true analog synth used to have on their front panels. (In fact, I havent even figured out how to just hack one single knob capable of sending certain CC.)
It's that I've got enough spare parts in my junk box, and the itch to solder together another something after I've assembled my HAWK-800 :)
--- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@...> wrote:Show quoted textHide quoted text
> > hi tim: i read that article, and see what it does, > but would find editing tx/dx like that really frustrating > (although you'd have to have a go with it before judging) > i used to have a fun editor on the atari, and may even > have had a cubase mixer map for it. > for the poly/ex, seems like a nice GUI based editor > would be most useful (if using a pc/mac) > > --- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@> wrote: > > > > *if i may say* (...) seems really xxxx heavyweight, lol! > > for an issue that could be resolved more simply using sysex. > > i used to get some quite complex sysex edits going on without > > affecting timing, with multiple params moving, etc. > > > > am dl'ing this to examine offline, but think best to make > > equivalent of a cubase 'mixer map', accessing any parameter > > wanted via an GUI-based editor. ca make as synthedit(windows) > > VST instrument, and if anyone wants to port that to a Mac etc > > thing, can upload the project file. > > > > HOWEVER! if someone can accurately describe how to perform > > NRPN edit via MIDI, that could be another method (never got it > > to work here ) > > > > ie: an object(fader/knob) sends out a(ny) parameter value variable > > in realtime. > > > > --- In korgpolyex@yahoogroups.com, "tim.tashpulatov" <tim.tashpulatov@> wrote: > > > > > > According to MIDI implementation, seems like it is possible to change one parameter at a time using CC84 and CC85. So I dug out my old proto board with Atmel MCU, some old touchpad and digital pot, and started thinking this over. > > > > > > And while looking for ways to attach pots to my board, I have found this: > > > > > > http://the-all.org/tx81z/twopot/index.html > > > > > > It's a simple project, sort of hardware patch editor with an LCD, a couple of knobs and MIDI output to control TX81Z. I guess something similar could be done for controlling HAWK-800, too. Having all the parameter names shown in human readable format on the LCD would be nice. > > > > > > > > > --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> wrote: > > > > > > > > Well, here is the raw format of the data. See the MIDI implementation for the > > > > precise format of the sysex message. > > > > > >
Re: HAWK-800 Sysex Patch Dump format
2010-12-10 by k9k9dog
hey guys, well thanks tim, for showing us the tx thing, new to me. the thing i found about the ex800, is that you'd tend not to fiddle with patches while you worked, as not very immediate, like a juno, say. so a controller panel would be very fiiiine :) i'm still looking at that midid implementation chart, and a bit confused by midi cc's 22-30, and their purpose ????? please enlighten me if you know... also trying to work out what the sysex messahe format:order is exactly, as several types of message are listed(more time). however, if any of you have your machine there, you can find out the correct one (or any other black box) by performing a 'handshake': open your cubase? list editor, and insert a data transfer request message in the top line. then arm cubase to record - with midi in/out reciprocally from pc midi to device midi, and hit play; then stop play very quickly (best not to have a short loop running...) you will have captured a return message that gives you all the bytes in the correct order. up to you then to work out which is the parameter variable (which will feature as 'xx' when you create your (mixer map) object. if you have a midi implemenation chart with al parameter numbers, which we do, transpose them all into hex, and make an object for each one. this is the 'soft' version, and i'm going to try to suss out how to do this with synthedit. then maybe someone can code it up as a universam platform vsti... ???? i read about arduino, but over my head as yet...it might need to be a separate device addressing the sysex via assigned midi cc's, with a midi cc> sysex interface going on....? --- In korgpolyex@yahoogroups.com, joe peak <lovgh2000@...> wrote:
Show quoted textHide quoted text
> > Ya know.......You've given me an idea......Like those old roland synths where they have a breakout box full of knobs and such. One could make a midi box using the very hip Arduino, and make knobs controlling MIDI CCs. The box would connect via MIDI and could sit on the Poly's top panel where the parameter tables are....Giving real knobs for parameters. I was also thinking about hacking my Oxygen8 midi controller and taking out the eight knobs and slider then putting them into a custom made box to attach to the poly. Those knobs on the Oxygen are programmable and could be changed whenever needed. > >   Just an idea......... > >                 J. > >  > > --- On Thu, 12/9/10, tim.tashpulatov <tim.tashpulatov@...> wrote: > > From: tim.tashpulatov <tim.tashpulatov@...> > Subject: [korgpolyex] Re: HAWK-800 Sysex Patch Dump format > To: korgpolyex@yahoogroups.com > Date: Thursday, December 9, 2010, 2:21 AM > > > > > > > >  > > > > > > > > > > I agree, I would too prefer some on-screen controls with knobs and buttons running on PC. My setup is under Linux, and so far I haven't found any tools there suitable for hacking custom synth layout. You know, like those old true analog synth used to have on their front panels. (In fact, I havent even figured out how to just hack one single knob capable of sending certain CC.) > > > > It's that I've got enough spare parts in my junk box, and the itch to solder together another something after I've assembled my HAWK-800 :) > > > > --- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@> wrote: > > > > > > hi tim: i read that article, and see what it does, > > > but would find editing tx/dx like that really frustrating > > > (although you'd have to have a go with it before judging) > > > i used to have a fun editor on the atari, and may even > > > have had a cubase mixer map for it. > > > for the poly/ex, seems like a nice GUI based editor > > > would be most useful (if using a pc/mac) > > > > > > --- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@> wrote: > > > > > > > > *if i may say* (...) seems really xxxx heavyweight, lol! > > > > for an issue that could be resolved more simply using sysex. > > > > i used to get some quite complex sysex edits going on without > > > > affecting timing, with multiple params moving, etc. > > > > > > > > am dl'ing this to examine offline, but think best to make > > > > equivalent of a cubase 'mixer map', accessing any parameter > > > > wanted via an GUI-based editor. ca make as synthedit(windows) > > > > VST instrument, and if anyone wants to port that to a Mac etc > > > > thing, can upload the project file. > > > > > > > > HOWEVER! if someone can accurately describe how to perform > > > > NRPN edit via MIDI, that could be another method (never got it > > > > to work here ) > > > > > > > > ie: an object(fader/knob) sends out a(ny) parameter value variable > > > > in realtime. > > > > > > > > --- In korgpolyex@yahoogroups.com, "tim.tashpulatov" <tim.tashpulatov@> wrote: > > > > > > > > > > According to MIDI implementation, seems like it is possible to change one parameter at a time using CC84 and CC85. So I dug out my old proto board with Atmel MCU, some old touchpad and digital pot, and started thinking this over. > > > > > > > > > > And while looking for ways to attach pots to my board, I have found this: > > > > > > > > > > http://the-all.org/tx81z/twopot/index.html > > > > > > > > > > It's a simple project, sort of hardware patch editor with an LCD, a couple of knobs and MIDI output to control TX81Z. I guess something similar could be done for controlling HAWK-800, too. Having all the parameter names shown in human readable format on the LCD would be nice. > > > > > > > > > > > > > > > --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> wrote: > > > > > > > > > > > > Well, here is the raw format of the data. See the MIDI implementation for the > > > > > > precise format of the sysex message. > > > > > > > > > > > > >
Re: [korgpolyex] Re: HAWK-800 Sysex Patch Dump format
2010-12-10 by Michael Hawkins
From page 35 of the Owners Manual... MIDI CC “Hardware Controller Friendly” Method The third method is a non standard method for changing HAWK-800 parameters where a hardware MIDI controller is being used to change parameters. This method makes it easier to set up a MIDI hardware controller that has sliders and push buttons that can be assigned to parameter banks. This method uses MIDI CC's 22 through to 30. CC 22 is used to select parameter groups. There are 16 parameter groups starting at P1 11 through to P1 88 and then P2 11 through to P2 88. Once a parameter group is selected then CC's 23 through to 30 correspond to the parameter within the selected parameter group. To use this method, the MIDI CC messages would be sent in this order and format: 1) Send MIDI CC 22 with the data value set to select the desired parameter group where 00-63 corresponds to groups P1 1x to 8x and 64-127 corresponds to groups P2 1x to 8x. When you send this CC to the HAWK-800, the display will briefly switch to show the selected parameter group. 2) Send any MIDI CC from 23 to 30 where each CC corresponds to the parameters within the selected parameter group. This means that with the parameter group selected (in step 1 above) you can use MIDI CC's 23 to 30 to set the parameters of any of the 8 parameters within each parameter group. So for example, use MIDI CC 22 to select the desired parameter group (say DCO1 group) then use MIDI CC's 23 to 30 to change any of the parameters in that group (which would be DCO octave, DCO waveform, harmonics, level and DCO mode). The nice thing about this method is that a musician will generally edit HAWK-800 sounds by working inside of each parameter group. So it is very convenient to be able to set up a hardware controller to select a parameter group and then edit any one of the eight possible parameters in that group. Then the musician would select another parameter group and edit the parameters within that group and so on. And a little additional color... So imagine that you have a MIDI hardware controller with one knob assigned to controller 22 and then you have eight sliders assigned to 23 through to 30. Now let's say we want to edit EG1. In that case, you would use the knob to set the parameter group to P1 5_. Then you would edit attack, decay etc using the other eight sliders. Each one of those sliders is assigned to the eight parameters inside of the parameter group. So then to edit EG2 you would use the knob to select P1 6_ and then again, use the eight sliders to set all parameters in EG2 parameter group. I thought this was a nice way to edit parameters quickly using my Remote25SL. I provided this group with the parameter data layout and the MIDI implementation along with the data format that was posted here should explain it. Now, what is your specific question regarding sysex? Mike ________________________________ From: k9k9dog <domgoold@...> To: korgpolyex@yahoogroups.com Sent: Fri, December 10, 2010 6:54:37 AM Subject: [korgpolyex] Re: HAWK-800 Sysex Patch Dump format hey guys, well thanks tim, for showing us the tx thing, new to me. the thing i found about the ex800, is that you'd tend not to fiddle with patches while you worked, as not very immediate, like a juno, say. so a controller panel would be very fiiiine :) i'm still looking at that midid implementation chart, and a bit confused by midi cc's 22-30, and their purpose ????? please enlighten me if you know... also trying to work out what the sysex messahe format:order is exactly, as several types of message are listed(more time). however, if any of you have your machine there, you can find out the correct one (or any other black box) by performing a 'handshake': open your cubase? list editor, and insert a data transfer request message in the top line. then arm cubase to record - with midi in/out reciprocally from pc midi to device midi, and hit play; then stop play very quickly (best not to have a short loop running...) you will have captured a return message that gives you all the bytes in the correct order. up to you then to work out which is the parameter variable (which will feature as 'xx' when you create your (mixer map) object. if you have a midi implemenation chart with al parameter numbers, which we do, transpose them all into hex, and make an object for each one. this is the 'soft' version, and i'm going to try to suss out how to do this with synthedit. then maybe someone can code it up as a universam platform vsti... ???? i read about arduino, but over my head as yet...it might need to be a separate device addressing the sysex via assigned midi cc's, with a midi cc> sysex interface going on....? --- In korgpolyex@yahoogroups.com, joe peak <lovgh2000@...> wrote: > > Ya know.......You've given me an idea......Like those old roland synths where >they have a breakout box full of knobs and such. One could make a midi box >using the very hip Arduino, and make knobs controlling MIDI CCs. The box would >connect via MIDI and could sit on the Poly's top panel where the parameter >tables are....Giving real knobs for parameters. I was also thinking about >hacking my Oxygen8 midi controller and taking out the eight knobs and slider >then putting them into a custom made box to attach to the poly. Those knobs on >the Oxygen are programmable and could be changed whenever needed. > >   Just an idea......... > >                 J. > >  > > --- On Thu, 12/9/10, tim.tashpulatov <tim.tashpulatov@...> wrote: > > From: tim.tashpulatov <tim.tashpulatov@...> > Subject: [korgpolyex] Re: HAWK-800 Sysex Patch Dump format > To: korgpolyex@yahoogroups.com > Date: Thursday, December 9, 2010, 2:21 AM > > > > > > > >  > > > > > > > > > > I agree, I would too prefer some on-screen controls with knobs and >buttons running on PC. My setup is under Linux, and so far I haven't found any >tools there suitable for hacking custom synth layout. You know, like those old >true analog synth used to have on their front panels. (In fact, I havent even >figured out how to just hack one single knob capable of sending certain CC.) > > > > It's that I've got enough spare parts in my junk box, and the itch to solder >together another something after I've assembled my HAWK-800 :) > > > > --- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@> wrote: > > > > > > hi tim: i read that article, and see what it does, > > > but would find editing tx/dx like that really frustrating > > > (although you'd have to have a go with it before judging) > > > i used to have a fun editor on the atari, and may even > > > have had a cubase mixer map for it. > > > for the poly/ex, seems like a nice GUI based editor > > > would be most useful (if using a pc/mac) > > > > > > --- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@> wrote: > > > > > > > > *if i may say* (...) seems really xxxx heavyweight, lol! > > > > for an issue that could be resolved more simply using sysex. > > > > i used to get some quite complex sysex edits going on without > > > > affecting timing, with multiple params moving, etc. > > > > > > > > am dl'ing this to examine offline, but think best to make > > > > equivalent of a cubase 'mixer map', accessing any parameter > > > > wanted via an GUI-based editor. ca make as synthedit(windows) > > > > VST instrument, and if anyone wants to port that to a Mac etc > > > > thing, can upload the project file. > > > > > > > > HOWEVER! if someone can accurately describe how to perform > > > > NRPN edit via MIDI, that could be another method (never got it > > > > to work here ) > > > > > > > > ie: an object(fader/knob) sends out a(ny) parameter value variable > > > > in realtime. > > > > > > > > --- In korgpolyex@yahoogroups.com, "tim.tashpulatov" <tim.tashpulatov@> >wrote: > > > > > > > > > > According to MIDI implementation, seems like it is possible to change one >parameter at a time using CC84 and CC85. So I dug out my old proto board with >Atmel MCU, some old touchpad and digital pot, and started thinking this over. > > > > > > > > > > And while looking for ways to attach pots to my board, I have found this:
Show quoted textHide quoted text
> > > > > > > > > > http://the-all.org/tx81z/twopot/index.html > > > > > > > > > > It's a simple project, sort of hardware patch editor with an LCD, a >couple of knobs and MIDI output to control TX81Z. I guess something similar >could be done for controlling HAWK-800, too. Having all the parameter names >shown in human readable format on the LCD would be nice. > > > > > > > > > > > > > > > --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> >wrote: > > > > > > > > > > > > Well, here is the raw format of the data. See the MIDI implementation >for the > > > > > > > precise format of the sysex message. > > > > > > > > > > > > >
Re: [korgpolyex] Re: HAWK-800 Sysex Patch Dump format
2010-12-10 by joe peak
"Now, what is your specific question regarding sysex?"
Yes I was wondering that too.........I thought it all seemed to be some hot air floating around to get a software editor or hardware editor going......
I also had a sneaky suspicion that its all there already in Mike's excellent midi implementation. Which it is. Just buy a controller that can send Midi CCs and there you go.
I don't mean to be rude. I'm just confused as to what this thread is about.
J.
--- On Fri, 12/10/10, Michael Hawkins <korgpolyex800@yahoo.com> wrote:
From: Michael Hawkins <korgpolyex800@...>
Subject: Re: [korgpolyex] Re: HAWK-800 Sysex Patch Dump format
To: korgpolyex@yahoogroups.com
Date: Friday,
December 10, 2010, 8:23 AM
From page 35 of the Owners Manual...
MIDI CC “Hardware Controller Friendly” Method
The third method is a non standard method for changing HAWK-800 parameters where a hardware MIDI controller is
being used to change parameters. This method makes it easier to set up a MIDI hardware controller that has sliders and
push buttons that can be assigned to parameter banks. This method uses MIDI CC's 22 through to 30. CC 22 is used to
select parameter groups. There are 16 parameter groups starting at P1 11 through to P1 88 and then P2 11 through to P2
88. Once a parameter group is selected then CC's 23 through to 30 correspond to the parameter within
the selected
parameter group. To use this method, the MIDI CC messages would be sent in this order and format:
1) Send MIDI CC 22 with the data value set to select the desired
parameter group where 00-63 corresponds to groups P1 1x to 8x and 64-127 corresponds to groups P2 1x to 8x. When you
send this CC to the HAWK-800, the display will briefly switch to show the selected parameter group.
2) Send any MIDI CC from 23 to 30 where each CC corresponds to the parameters within the selected parameter group.
This means that with the parameter group selected (in step 1 above) you can use MIDI CC's 23 to 30 to set the parameters
of any of the 8 parameters within each parameter group.
So for example, use MIDI CC 22 to select the desired parameter group (say DCO1 group) then use MIDI CC's 23 to 30 to
change any of the parameters in that group (which would be DCO octave, DCO waveform, harmonics, level and DCO
mode).
The nice thing
about this method is that a musician will generally edit HAWK-800 sounds by working inside of each
parameter group. So it is very convenient to be able to set up a hardware controller to select a parameter group and then
edit any one of the eight possible parameters in that group. Then the musician would select another parameter group and
edit the parameters within that group and so on.
And a little additional color...
So imagine that you have a MIDI hardware controller with one knob assigned to controller 22 and then you have eight sliders assigned to 23 through to 30.
Now let's say we want to edit EG1. In that case, you would use the knob to set the parameter group to P1 5_. Then you would edit attack, decay etc using the other eight sliders. Each one of those sliders is assigned to the eight parameters inside of the parameter group.
So then to edit EG2 you would use the knob to select P1 6_ and then again, use the
eight sliders to set all parameters in EG2 parameter group.
I thought this was a nice way to edit parameters quickly using my Remote25SL.
I provided this group with the parameter data layout and the MIDI implementation along with the data format that was posted here should explain it. Now, what is your specific question regarding sysex?
Mike
From: k9k9dog <domgoold@...>
To: korgpolyex@yahoogroups.com
Sent: Fri, December 10, 2010 6:54:37 AM
Subject: [korgpolyex] Re: HAWK-800 Sysex Patch Dump
format
hey guys,
well thanks tim, for showing us the tx thing, new to me.
the thing i found about the ex800, is that you'd tend not to fiddle with patches while you worked, as not very immediate, like a juno,
say. so a controller panel would be very fiiiine :)
i'm still looking at that midid implementation chart, and a bit confused by midi cc's 22-30, and their purpose ????? please
enlighten me if you know...
also trying to work out what the sysex messahe format:order is
exactly, as several types of message are listed(more time).
however, if any of you have your machine there, you can find out the
correct one (or any other black box) by performing a 'handshake':
open your cubase? list editor, and insert a data transfer request
message in the top line.
then arm cubase to record - with midi in/out reciprocally from
pc midi to device midi, and hit play; then stop play very
quickly (best not to have a short loop running...)
you will have captured a return message that gives you all the bytes
in the correct order. up to you then to work out which is the parameter variable (which will feature as 'xx' when you create your
(mixer map) object.
if you have a midi implemenation chart with al parameter numbers,
which we do, transpose them all into hex, and make an object for
each one.
this is the 'soft' version, and i'm going to try to suss out how
to do this with synthedit. then maybe someone can code it up as
a universam platform vsti... ????
i read about arduino, but over my head as yet...it might need to be a separate device addressing the sysex via assigned midi cc's, with
a midi cc> sysex interface going on....?
--- In korgpolyex@yahoogroups.com, joe peak <lovgh2000@...> wrote:Show quoted textHide quoted text
> > Ya know.......You've given me an idea......Like those old roland synths where they have a breakout box full of knobs and such. One could make a midi box using the very hip Arduino, and make knobs controlling MIDI CCs. The box would connect via MIDI and could sit on the Poly's top panel where the parameter tables are....Giving real knobs for parameters. I was also thinking about hacking my Oxygen8 midi controller and taking out the eight knobs and slider then putting them into a custom made box to attach to the poly. Those knobs on the Oxygen are programmable and could be changed whenever needed. > >   Just an idea......... > >                 J. > >  > > --- On Thu, 12/9/10, tim.tashpulatov <tim.tashpulatov@...> wrote: > > From: tim.tashpulatov <tim.tashpulatov@...> > Subject: [korgpolyex] Re: HAWK-800 Sysex Patch Dump format > To: korgpolyex@yahoogroups.com > Date: Thursday, December 9, 2010, 2:21 AM > > > > > > > >  > > > > > > > > > > I agree, I would too prefer some on-screen controls with knobs and buttons running on PC. My setup is under Linux, and so far I haven't found any tools there suitable for hacking custom synth layout. You know, like those old true analog synth used to have on their front panels. (In fact, I havent even figured out how to just hack one single knob capable of sending certain CC.) > > > > It's that I've got enough spare parts in my junk box, and the itch to solder together another something after I've assembled my HAWK-800 :) > > > > --- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@> wrote: > > > > > > hi tim: i read that article, and see what it does, > > > but would find editing tx/dx like that really frustrating > > > (although you'd have to have a go with it before judging) > > > i used to have a fun editor on the atari, and may even > > > have had a cubase mixer map for it. > > > for the poly/ex, seems like a nice GUI based editor > > > would be most useful (if using a pc/mac) > > > > > > --- In korgpolyex@yahoogroups.com, "k9k9dog" <domgoold@> wrote: > > > > > > > > *if i may say* (...) seems really xxxx heavyweight, lol! > > > > for an issue that could be resolved more simply using sysex. > > > > i used to get some quite complex sysex edits going on without > > > > affecting timing, with multiple params moving, etc. > > > > > > > > am dl'ing this to examine offline, but think best to make > > > > equivalent of a cubase 'mixer map', accessing any parameter > > > > wanted via an GUI-based editor. ca make as synthedit(windows) > > > > VST instrument, and if anyone wants to port that to a Mac etc > > > > thing, can upload the project file. > > > > > > > > HOWEVER! if someone can accurately describe how to perform > > > > NRPN edit via MIDI, that could be another method (never got it > > > > to work here ) > > > > > > > > ie: an object(fader/knob) sends out a(ny) parameter value variable > > > > in realtime. > > > > > > > > --- In korgpolyex@yahoogroups.com, "tim.tashpulatov" <tim.tashpulatov@> wrote: > > > > > > > > > > According to MIDI implementation, seems like it is possible to change one parameter at a time using CC84 and CC85. So I dug out my old proto board with Atmel MCU, some old touchpad and digital pot, and started thinking this over. > > > > > > > > > > And while looking for ways to attach pots to my board, I have found this: > > > > > > > > > > http://the-all.org/tx81z/twopot/index.html > > > > > > > > > > It's a simple project, sort of hardware patch editor with an LCD, a couple of knobs and MIDI output to control TX81Z. I guess something similar could be done for controlling HAWK-800, too. Having all the parameter names shown in human readable format on the LCD would be nice. > > > > > > > > > > > > > > > --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> wrote: > > > > > > > > > > > > Well, here is the raw format of the data. See the MIDI implementation for the > > > > > > precise format of the sysex message. > > > > > > > > > > > > >
Re: HAWK-800 Sysex Patch Dump format
2011-01-09 by microbugix
--- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote: > > you all need to seriously consider JsynthLib. If you're on Windows, ok. JSynthlib on Mac does not work flawlessly due to buggy sysex routines in JSynthlib engine. I will prefer SoundDiver instead, since this was my favourite choice for all synths to edit. For nice programming with knobs you could use fader boxes like Behringer BCR2000 which is capable of handling sysex messages if one is willing to dive into its macro language. Greets Dietmar
Re: HAWK-800 Sysex Patch Dump format
2012-10-14 by korgpolyex800
From a while ago... I also should add that I am going to change P2-13 and P2-14 to combine them into P2-14. So you should write your controllers in such a way that lends them to easy modification. --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote:
Show quoted textHide quoted text
> > Well, here is the raw format of the data. See the MIDI implementation for the > precise format of the sysex message. > > In order, from patch byte 0 through to patch byte 127 (which takes two bytes > each in the patch sysex dump itself). > > The left hand is the maximum value for the parameter. If you exceed the value > then when the patch is selected the parameter that has the invalid value will be > set to half of the maximum for that parameter. > > Let me know if you have any questions at all. > > 2 , 11 DCO1 Octave > 1 , 12 DCO1 Waveform > 15 , 13 DCO1 harmonics > 12 , 14 DCO1 harmonic modulator waveform > 3 , 15 DCO1 harmonic modulator source > 15 , 16 DCO1 harmonic modulator depth > 31 , 17 DCO1 Level > 1 , 18 DCO mode single or double > 2 , 21 DCO2 Octave > 1 , 22 DCO2 Waveform > 15 , 23 DCO2 harmonics > 12 , 24 DCO2 harmonic modulator waveform > 3 , 25 DCO2 harmonic modulator source > 15 , 26 DCO2 harmonic modulator depth > 31 , 27 DCO2 Level > 0 , 28 Not used > 12 , 31 Interval > 3 , 32 Detune > 15 , 33 Noise > 99 , 34 Delay Time > 15 , 35 Delay Feedback > 31 , 36 Delay Modulation Frequency > 31 , 37 Delay Modulation Intensity > 15 , 38 Delay Effect Level > 99 , 41 VCF cut off > 2 , 42 Keyboard Track > 1 , 43 Polarity > 15 , 44 EG3 VCF cutoff influence > 1 , 45 EG3 Trigger > 12 , 46 EQ treble > 12 , 47 EQ bass > 1 , 48 Chorus > 31 , 51 EG1 Attack > 31 , 52 EG1 Decay > 31 , 53 EG1 Break Point > 31 , 54 EG1 Slope > 31 , 55 EG1 Sustain > 31 , 56 EG1 Release > 0 , 57 Not used > 0 , 58 Not used > 31 , 61 EG2 Attack > 31 , 62 EG2 Decay > 31 , 63 EG2 Break Point > 31 , 64 EG2 Slope > 31 , 65 EG2 Sustain > 31 , 66 EG2 Release > 0 , 67 Not used > 0 , 68 Not used > 31 , 71 EG3 Attack > 31 , 72 EG3 Decay > 31 , 73 EG3 Break Point > 31 , 74 EG3 Slope > 31 , 75 EG3 Sustain > 31 , 76 EG3 Release > 0 , 77 Not used > 0 , 78 Not used > 4 , 81 Velocity operator 1 intensity > 1 , 82 Velocity operator 1 invert > 11 , 83 Velocity operator 1 target > 4 , 84 Velocity operator 2 intensity > 1 , 85 Velocity operator 2 invert > 11 , 86 Velocity operator 2 target > 6 , 87 VCF velocity sensitive intensity > 5 , 88 VCF velocity sensitive response shape > > 15 , 11 LFO1 frequency > 15 , 12 LFO1 delay > 1 , 13 LFO1 free running > 1 , 14 LFO1 delay type > 62 , 15 LFO1 square wave PWM ratio > 12 , 16 LFO3 waveform select > 15 , 17 LFO3 modulation depth of SLFO1 > 0 , 18 Not used > 15 , 21 LFO2 frequency > 15 , 22 LFO2 delay > 1 , 23 LFO2 free running > 1 , 24 LFO2 delay type > 62 , 25 LFO2 square wave PWM ratio > 12 , 26 LFO3 waveform select > 15 , 27 LFO3 modulation depth of SLFO2 > 63 , 28 LFO2 sync driven 0=original oscillator, 1-63 sequencer clock > driven > 12 , 31 DCO MG 1st modulator waveform > 3 , 32 DCO MG 1st modulator source > 15 , 33 DCO MG 1st modulator depth > 0 , 34 Not used > 1 , 35 DCO MG EG invert > 15 , 36 DCO MG EG depth > 0 , 37 unused > 2 , 38 DCO MG mode > 12 , 41 VCF MG 1st modulator waveform > 3 , 42 VCF MG 1st modulator source > 15 , 43 VCF MG 1st modulator depth > 12 , 44 VCF MG 2nd modulator waveform > 3 , 45 VCF MG 2nd modulator source > 15 , 46 VCF MG 2nd modulator depth > 0 , 47 unused > 1 , 48 12/24db filter cutoff select > 99 , 51 Resonance set point > 12 , 52 Resonance MG waveform > 3 , 53 Resonance MG source > 15 , 54 Resonance MG depth > 0 , 55 Not used > 15 , 56 Resonance EG depth > 1 , 57 Resonance EG invert > 1 , 58 Resonance mode > 99 , 61 FM-800 set point > 12 , 62 FM-800 MG waveform > 3 , 63 FM-800 MG source > 15 , 64 FM-800 MG depth > 0 , Not used > 15 , 66 FM-800 EG depth > 1 , 67 FM-800 EG invert > 2 , 68 Noise mode > 15 , 71 SLFO3 frequency > 62 , 72 SLFO3 square wave PWM ratio > 1 , 73 SLFO3 free running > 98 , 74 sequencer clock random sample and hold increment > 15 , 75 SLFO4 frequency > 62 , 76 SLFO4 square wave PWM ratio > 1 , 77 SLFO4 free running > 31 , 78 sustain decay and release EG offset > 2 , 81 DCO1 tremolo off, LFO1/2 select > 15 , 82 DCO1 tremolo depth > 2 , 83 DCO2 tremolo off, LFO1/2 select > 15 , 84 DCO2 tremolo depth > 63 , 85 Bend depth > 63 , 86 Portamento slide rate > 0 , 87 unused > 3 , 88 Operating Poly Mode > > > All parameter values start at zero. For example, waveform is displayed as 1 or > 2 but is stored as 0 or 1. This applies to all parameters that start at one. > They are in fact stored as one less than the display shows. > > Please also keep in mind that I plan to rewrite the sysex patch dumps so that > they use a single MIDI byte instead of two per value. However, when I do that, > I will use a new sysex message ID number so that the existing patch dump sysex > commands still work. > > Ask as many questions as you wish. > > Mike > > > > ________________________________ > From: tim.tashpulatov <tim.tashpulatov@...> > To: korgpolyex@yahoogroups.com > Sent: Tue, November 30, 2010 2:25:07 AM > Subject: [korgpolyex] HAWK-800 Sysex Patch Dump format > > > Mike, > > Could you please shed some light on Hawk-800's patch dump format? I am thinking > of some external way to tweak patch parameters and to send changes back via > sysex. > > Regards > Tim >
Re: HAWK-800 Sysex Patch Dump format
2012-10-14 by bimmerfan222
Thanks for the reply Mike. I guess I'm just not getting it.. I dont see where in the code I can pluck out parameter values. Like where is: 11 Dco1 Octave 23 DCO1 Harmonics 88 Operating Poly Mode in this dump here- SYSX: F0 42 21 06 00 00 01 00 00 00 00 00 00 00 00 00 04 01 SYSX: 0F 00 00 00 01 00 00 00 00 00 00 00 00 00 07 01 0F 00 SYSX: 00 00 00 00 02 00 00 04 0B 00 0A 00 0A 01 00 00 00 05 SYSX: 05 00 00 00 01 00 00 00 00 00 0C 00 0C 00 01 00 00 01 SYSX: 0B 01 0F 01 0F 01 0F 00 03 00 00 00 00 00 00 01 0F 01 SYSX: 0F 01 0F 01 0F 00 03 00 00 00 00 01 03 00 05 01 0F 00 SYSX: 00 01 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SYSX: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SYSX: 00 00 08 00 00 00 09 00 00 00 00 00 00 00 00 00 00 00 SYSX: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SYSX: 00 00 00 00 02 00 06 00 00 00 00 00 00 00 00 00 00 00 SYSX: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SYSX: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 00 00 00 SYSX: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SYSX: 00 00 00 00 --- In korgpolyex@yahoogroups.com, "korgpolyex800" <korgpolyex800@...> wrote:
Show quoted textHide quoted text
> > From a while ago... > > I also should add that I am going to change P2-13 and P2-14 to combine them into P2-14. So you should write your controllers in such a way that lends them to easy modification. > > --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> wrote: > > > > Well, here is the raw format of the data. See the MIDI implementation for the > > precise format of the sysex message. > > > > In order, from patch byte 0 through to patch byte 127 (which takes two bytes > > each in the patch sysex dump itself). > > > > The left hand is the maximum value for the parameter. If you exceed the value > > then when the patch is selected the parameter that has the invalid value will be > > set to half of the maximum for that parameter. > > > > Let me know if you have any questions at all. > > > > 2 , 11 DCO1 Octave > > 1 , 12 DCO1 Waveform > > 15 , 13 DCO1 harmonics > > 12 , 14 DCO1 harmonic modulator waveform > > 3 , 15 DCO1 harmonic modulator source > > 15 , 16 DCO1 harmonic modulator depth > > 31 , 17 DCO1 Level > > 1 , 18 DCO mode single or double > > 2 , 21 DCO2 Octave > > 1 , 22 DCO2 Waveform > > 15 , 23 DCO2 harmonics > > 12 , 24 DCO2 harmonic modulator waveform > > 3 , 25 DCO2 harmonic modulator source > > 15 , 26 DCO2 harmonic modulator depth > > 31 , 27 DCO2 Level > > 0 , 28 Not used > > 12 , 31 Interval > > 3 , 32 Detune > > 15 , 33 Noise > > 99 , 34 Delay Time > > 15 , 35 Delay Feedback > > 31 , 36 Delay Modulation Frequency > > 31 , 37 Delay Modulation Intensity > > 15 , 38 Delay Effect Level > > 99 , 41 VCF cut off > > 2 , 42 Keyboard Track > > 1 , 43 Polarity > > 15 , 44 EG3 VCF cutoff influence > > 1 , 45 EG3 Trigger > > 12 , 46 EQ treble > > 12 , 47 EQ bass > > 1 , 48 Chorus > > 31 , 51 EG1 Attack > > 31 , 52 EG1 Decay > > 31 , 53 EG1 Break Point > > 31 , 54 EG1 Slope > > 31 , 55 EG1 Sustain > > 31 , 56 EG1 Release > > 0 , 57 Not used > > 0 , 58 Not used > > 31 , 61 EG2 Attack > > 31 , 62 EG2 Decay > > 31 , 63 EG2 Break Point > > 31 , 64 EG2 Slope > > 31 , 65 EG2 Sustain > > 31 , 66 EG2 Release > > 0 , 67 Not used > > 0 , 68 Not used > > 31 , 71 EG3 Attack > > 31 , 72 EG3 Decay > > 31 , 73 EG3 Break Point > > 31 , 74 EG3 Slope > > 31 , 75 EG3 Sustain > > 31 , 76 EG3 Release > > 0 , 77 Not used > > 0 , 78 Not used > > 4 , 81 Velocity operator 1 intensity > > 1 , 82 Velocity operator 1 invert > > 11 , 83 Velocity operator 1 target > > 4 , 84 Velocity operator 2 intensity > > 1 , 85 Velocity operator 2 invert > > 11 , 86 Velocity operator 2 target > > 6 , 87 VCF velocity sensitive intensity > > 5 , 88 VCF velocity sensitive response shape > > > > 15 , 11 LFO1 frequency > > 15 , 12 LFO1 delay > > 1 , 13 LFO1 free running > > 1 , 14 LFO1 delay type > > 62 , 15 LFO1 square wave PWM ratio > > 12 , 16 LFO3 waveform select > > 15 , 17 LFO3 modulation depth of SLFO1 > > 0 , 18 Not used > > 15 , 21 LFO2 frequency > > 15 , 22 LFO2 delay > > 1 , 23 LFO2 free running > > 1 , 24 LFO2 delay type > > 62 , 25 LFO2 square wave PWM ratio > > 12 , 26 LFO3 waveform select > > 15 , 27 LFO3 modulation depth of SLFO2 > > 63 , 28 LFO2 sync driven 0=original oscillator, 1-63 sequencer clock > > driven > > 12 , 31 DCO MG 1st modulator waveform > > 3 , 32 DCO MG 1st modulator source > > 15 , 33 DCO MG 1st modulator depth > > 0 , 34 Not used > > 1 , 35 DCO MG EG invert > > 15 , 36 DCO MG EG depth > > 0 , 37 unused > > 2 , 38 DCO MG mode > > 12 , 41 VCF MG 1st modulator waveform > > 3 , 42 VCF MG 1st modulator source > > 15 , 43 VCF MG 1st modulator depth > > 12 , 44 VCF MG 2nd modulator waveform > > 3 , 45 VCF MG 2nd modulator source > > 15 , 46 VCF MG 2nd modulator depth > > 0 , 47 unused > > 1 , 48 12/24db filter cutoff select > > 99 , 51 Resonance set point > > 12 , 52 Resonance MG waveform > > 3 , 53 Resonance MG source > > 15 , 54 Resonance MG depth > > 0 , 55 Not used > > 15 , 56 Resonance EG depth > > 1 , 57 Resonance EG invert > > 1 , 58 Resonance mode > > 99 , 61 FM-800 set point > > 12 , 62 FM-800 MG waveform > > 3 , 63 FM-800 MG source > > 15 , 64 FM-800 MG depth > > 0 , Not used > > 15 , 66 FM-800 EG depth > > 1 , 67 FM-800 EG invert > > 2 , 68 Noise mode > > 15 , 71 SLFO3 frequency > > 62 , 72 SLFO3 square wave PWM ratio > > 1 , 73 SLFO3 free running > > 98 , 74 sequencer clock random sample and hold increment > > 15 , 75 SLFO4 frequency > > 62 , 76 SLFO4 square wave PWM ratio > > 1 , 77 SLFO4 free running > > 31 , 78 sustain decay and release EG offset > > 2 , 81 DCO1 tremolo off, LFO1/2 select > > 15 , 82 DCO1 tremolo depth > > 2 , 83 DCO2 tremolo off, LFO1/2 select > > 15 , 84 DCO2 tremolo depth > > 63 , 85 Bend depth > > 63 , 86 Portamento slide rate > > 0 , 87 unused > > 3 , 88 Operating Poly Mode > > > > > > All parameter values start at zero. For example, waveform is displayed as 1 or > > 2 but is stored as 0 or 1. This applies to all parameters that start at one. > > They are in fact stored as one less than the display shows. > > > > Please also keep in mind that I plan to rewrite the sysex patch dumps so that > > they use a single MIDI byte instead of two per value. However, when I do that, > > I will use a new sysex message ID number so that the existing patch dump sysex > > commands still work. > > > > Ask as many questions as you wish. > > > > Mike > > > > > > > > ________________________________ > > From: tim.tashpulatov <tim.tashpulatov@> > > To: korgpolyex@yahoogroups.com > > Sent: Tue, November 30, 2010 2:25:07 AM > > Subject: [korgpolyex] HAWK-800 Sysex Patch Dump format > > > > > > Mike, > > > > Could you please shed some light on Hawk-800's patch dump format? I am thinking > > of some external way to tweak patch parameters and to send changes back via > > sysex. > > > > Regards > > Tim > > >