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: Hawk 800 GUI- Latest version

From: bperkins211@...
Date: 2018-02-24

If you want the .bpanelz file you can either-

Open the Standalone and click: File > Export > Export Compressed Binary + Resources
  Then save it to whatever name you wish, then reopen it in Ctrlr.
  But that standalone is an editor already.. you can even open other panels in it.


If you want, you can just download the file here:

https://drive.google.com/open?id=1cH7wmcvgxEgDxmQAYZp-7b7lE41pAL7q

That file could let Mac users goto Ctrlr.org, download the Mac OS version of Ctrlr, then use that bpanelz file to open up the GUI.



Yea, the GUI can be a bit "busy" and colorful.  It was one of my first GUI's I tried to make several years ago and I didnt bother to change it.
All the colors were intended to help indicate where certain controls were and how they related to other areas.
Feel free to change it as you wish, the editor is built into the Standalone.
The hardest parts were doing all the LUA scripting to get the controls to autoset each time the patch changed.
Most likely I wont be working on it anymore.  I just simply dont have the time anymore with work and re educating my self for a future in the robotics industry.

AFAIK, all the controls work in the GUI.  My problem was when using it in a DAW as a VST that "Automated Control" didnt want to work correctly everytime.  When it worked it was cool!  But many times it would not work and cause glitches in the GUI.. like setting all the knobs to zero.



The HAWK's midi message limitations I encountered was when I would be playing an appergiator/several notes at once and changing 3+ controls all at the same time.
Otherwise if a simple sequence is playing and just two controls are tweaked, it should be fine.
I did notice that if you try to send it a sysex msg too quickly, it will stumble too.. in fact the GUI has some built in midi msg delays for the ADBSSR copy feature because the GUI was sending all the msgs together too quickly for the HAWK to respond.
It would change Attack, but then Decay, etc would all get ignored.  So I did some simple For/If loops to make the GUI sit and count a moment before sending the next msg.


If I were to do another HAWK mod to a Poly 800, I would dremel that socket out as carefully and as much as I could to get the individual pins exposed.  Then just desolder and remove each pin separately.