Korg Poly800/EX800 Users group photo

Yahoo Groups archive

Korg Poly800/EX800 Users

Archive for korgpolyex.

Index last updated: 2026-03-30 01:10 UTC

Thread

Atomahawk V2 Aggressive Resonance issue...

Atomahawk V2 Aggressive Resonance issue...

2017-03-25 by bperkins211@...

well I got the V2 Atomahawk installed last night... yay!

All seems to work ok.  The FM, Filter db selection, etc..
ALL THE CONTROLS respond to my GUI system.
Each control makes the HAWK's LED display show that parameter change.

But there's a problem..

When I choose "Aggressive Resonance", it wont latch in.

In other words, If I am currently playing a note and activate Aggr. Res, I will most definitely hear it howl/screech, etc.. all the signs of major feedback happening.
BUT, if I let go of the key and re-trigger the sounds/filter..  The Aggr. Res. will cease to function.
I check the parameter and it is most definitely still set to Aggr. Res.
It sounds like it is off.

So I go in and shut it off, hold a note down, hit it ON again and I again hear it howl AS LONG AS I HOLD THE NOTE DOWN..  but again, if I let go of the note/key and retrigger with a new note.. it stops working.


I can make a vid later on if it helps..  right now I'm in the midst of getting things finished up with the GUI.
I spent probably 4-5 hrs last night putting the Atomahawk in.   I was very careful, I triple and quadruple checked each step in the install as I went.  I am 100% certain all parts are where they should be and all wires as well.  I can and had planned on providing pics of the installed V2 board later on.

/Blaine


Re: [korgpolyex] Atomahawk V2 Aggressive Resonance issue...

2017-03-26 by Michael Hawkins

Wow! That's quite a bug you found, which I just confirmed.

I'll try to get that fixed asap.

/Mike


From: "bperkins211@... [korgpolyex]" <korgpolyex@yahoogroups.com>
To: korgpolyex@yahoogroups.com
Sent: Saturday, March 25, 2017 1:49 PM
Subject: [korgpolyex] Atomahawk V2 Aggressive Resonance issue...

 
well I got the V2 Atomahawk installed last night... yay!

All seems to work ok.  The FM, Filter db selection, etc..
ALL THE CONTROLS respond to my GUI system.
Each control makes the HAWK's LED display show that parameter change.

But there's a problem..

When I choose "Aggressive Resonance", it wont latch in.

In other words, If I am currently playing a note and activate Aggr. Res, I will most definitely hear it howl/screech, etc.. all the signs of major feedback happening.
BUT, if I let go of the key and re-trigger the sounds/filter..  The Aggr. Res. will cease to function.
I check the parameter and it is most definitely still set to Aggr. Res.
It sounds like it is off.

So I go in and shut it off, hold a note down, hit it ON again and I again hear it howl AS LONG AS I HOLD THE NOTE DOWN..  but again, if I let go of the note/key and retrigger with a new note.. it stops working.


I can make a vid later on if it helps..  right now I'm in the midst of getting things finished up with the GUI.
I spent probably 4-5 hrs last night putting the Atomahawk in.   I was very careful, I triple and quadruple checked each step in the install as I went.  I am 100% certain all parts are where they should be and all wires as well.  I can and had planned on providing pics of the installed V2 board later on.

/Blaine



HAWK software version 2.65i is now available...

2017-03-27 by Michael Hawkins

There was a bug in version 2.65h that broke extreme resonance (Moog Slayer).

So I fixed that and it is now available.


/Mike

From: "bperkins211@... [korgpolyex]" <korgpolyex@yahoogroups.com>
To: korgpolyex@yahoogroups.com
Sent: Saturday, March 25, 2017 3:55 PM
Subject: [korgpolyex] Re: Atomahawk V2 Aggressive Resonance issue...

 
Forgot to add..
Running v2.65h


Re: HAWK software version 2.65i is now available...

2017-03-28 by bperkins211@...

That was fast!
Confirmed working as intended.. Thanks!

Now for a quick question...
The CC#123 Notes Off control.
How does that work?

I tried sending CC#123 value 0, 1 and 127 with no response.
It wouldn't shut off a playing note.
But if I use the global interface, it will shut off.

What's the trick to using the CC#123?

Thanks again,
/Blaine

Re: [korgpolyex] Re: HAWK software version 2.65i is now available...

2017-03-28 by Michael Hawkins

The MIDI implementation chart has a typo in it.

It should be "Yes" for transmit but it should be "No" for receive.

123 All Notes Off Yes No
124 Omni Mode Off No Yes
125 Omni Mode On  No Yes

If you really want MIDI CC #123 all notes off receive, I can add it.

/Mike


From: "bperkins211@... [korgpolyex]" <korgpolyex@yahoogroups.com>
To: korgpolyex@yahoogroups.com
Sent: Monday, March 27, 2017 10:09 PM
Subject: [korgpolyex] Re: HAWK software version 2.65i is now available...

 
That was fast!
Confirmed working as intended.. Thanks!

Now for a quick question...
The CC#123 Notes Off control.
How does that work?

I tried sending CC#123 value 0, 1 and 127 with no response.
It wouldn't shut off a playing note.
But if I use the global interface, it will shut off.

What's the trick to using the CC#123?

Thanks again,
/Blaine


Re: [korgpolyex] Re: HAWK software version 2.65i is now available...

2017-03-28 by bperkins211@...

ahh.. that's why it don't work! 

Heck yea, if you can add it, it would be a nice feature to add to the GUI.
I already made a Panic/Notes Off button.. just needs to work.


Also, I wonder if there's a way to make a Write Patch method/sysex or NRPN control.
A way to make a button on the GUI that allows you to hit "Save Patch" and it will save the currently edited patch to the current Patch Number.
It would save the trouble to reach over, hit Write, then try to carefully press in the two numbers to save the patch to.
Once in a great while the buttons will double hit and instead of say, "74" it will save to "77".. or instead of "48" it saves to "44".. due to an error either from button bounce, crappo switches, operator error, etc.

Just a thought..

/Blaine

Re: [korgpolyex] Re: HAWK software version 2.65i is now available...

2017-03-28 by Michael Hawkins

OK, I'll add the All Notes Off CC reception.

I like your patch write idea alot! Actually, I love it. I will definitely add that too.

I would have sysex message 0x10 (16).

F0 42 21 10 0x 0y F7

where:
x is the source patch (0-63 would be patches 11-88 and 64 would be running patch) and
y is the destination patch (0-63 would be patches 11-88 and 64 would be running patch).

A confirmation message would be sent back F0 42 21 7E 10 01 F7 on success.
A confirmation message would be sent back F0 42 21 7E 10 00 F7 on write protect enabled.

I've added that as a feature request to the sourceforge pages so I don't forget about it.

/Mike


From: "bperkins211@... [korgpolyex]" <korgpolyex@yahoogroups.com>
To: korgpolyex@yahoogroups.com
Sent: Tuesday, March 28, 2017 1:11 PM
Subject: Re: [korgpolyex] Re: HAWK software version 2.65i is now available...

 
ahh.. that's why it don't work! 

Heck yea, if you can add it, it would be a nice feature to add to the GUI.
I already made a Panic/Notes Off button.. just needs to work.


Also, I wonder if there's a way to make a Write Patch method/sysex or NRPN control.
A way to make a button on the GUI that allows you to hit "Save Patch" and it will save the currently edited patch to the current Patch Number.
It would save the trouble to reach over, hit Write, then try to carefully press in the two numbers to save the patch to.
Once in a great while the buttons will double hit and instead of say, "74" it will save to "77".. or instead of "48" it saves to "44".. due to an error either from button bounce, crappo switches, operator error, etc.

Just a thought..

/Blaine