Archive of the former Yahoo!Groups mailing list: Korg Poly800/EX800 Users

previous by date index next by date
  topic list next in topic

Subject: Re: Patch Dump problems still...

From: Michael Hawkins <korgpolyex800@...>
Date: 2012-11-07

Hi Blaine,

I tested the sysex dump request and on my setup and I don't get the extra message. Except...

I was able to recreate your issue by routing the input (from HAWK) of MIDI-OX back to the output (to HAWK). This has the effect of looping the MIDI data received from HAWK back to the HAWK. So what is happening is you send a request, the HAWK responds with the patch dump and then MIDI-OX receives it and replays it back to the HAWK. The HAWK receives the patch and treats it just as it should by writing it to patch memory and then outputs the acknowledgment "I received the patch AOK".

So I think your setup is probably looping the output from HAWK back into the HAWK.

CCing the Yahoo group so that this helpful hint is searchable for all.

Mike

From: Blaine Perkins <bperkins211@...>
To: Michael Hawkins <korgpolyex800@...>
Sent: Monday, November 5, 2012 12:28 PM
Subject: Re: Patch Dump problems still...

Hope all is well over there for you post Sandy.


I managed to write a script to filter out the extra midi message and now the GUI is setting the virtual knobs, switches, comboboxes, etc. correctly for me automatically when I change the patch via the GUI.

Anyway, I thought it was still important for you to know that code was in there at the end... probably a easy fix to edit out if you dont intend for it to be there.

-Blaine

On Sun, Nov 4, 2012 at 9:00 AM, Michael Hawkins <korgpolyex800@...> wrote:
I just got Internet back after going through Sandy storm. Give me a day or two to look into this.

Mike


From: Blaine Perkins <bperkins211@...>
To: Michael Hawkins <KorgPolyEx800@...>
Sent: Friday, November 2, 2012 5:45 PM
Subject: Patch Dump problems still...

Hello Mike,

I've been building this GUI controller and noticed an odd behavior.

When I send a patch dump request like this-

f0 42 21 07 02 f7    (req's patch 13)

I get this in my OX monitor-

 SYSX: F0 42 21 06 02 00 02 00 00 00 07 00 00 00 00 00 03 01
 SYSX: 0F 00 01 00 02 00 01 00 01 00 01 00 00 00 03 01 0F 00
 SYSX: 00 00 03 00 02 00 00 00 00 00 00 00 00 00 00 00 00 02
 SYSX: 09 00 00 00 00 00 00 00 01 00 00 00 00 00 01 00 05 01
 SYSX: 01 01 0F 00 00 01 0F 00 00 00 00 00 00 01 08 01 0F 01
 SYSX: 0A 01 0F 01 0F 01 02 00 00 00 00 00 00 00 00 01 0D 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 00 00 00 00 01 00 00 00 01 00 00 00 00 00
 SYSX: 04 00 08 00 00 00 05 00 06 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 03 00 00 00 03 00 02 00 00 00 00 03
 SYSX: 0A 00 03 00 00 00 0A 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 0A 00 00 00
 SYSX: 01 00 00 00 04 00 00 00 01 00 00 00 00 00 00 00 00 00
 SYSX: 00 03 0F 00
 0020CF7C   1  --     F7  Buffer:     6 Bytes   SysEx End            
 SYSX: 00 00 00 00 02 F7
 0020D238   1  --     F0  Buffer:     7 Bytes   System Exclusive     
 SYSX: F0 42 21 7E 06 02 F7


See that last line?  The F0 42 21 7E 06 02 F7 ?   That is code that is sent back also at the end of the dump.
According to the Implem. Chart, that code is suppose to be sent when you transmit a patch dump, not request one, right??

Anyway, I'm having problems with a script in the GUI controller when I do a Program Change.  IE, I change the patch from the GUI using a combobox/list.. it creates the f0 42 21 07 xx f7 code (inserts the correct hex value for patch selected in the GUI at xx), transmits it, gets the raw data and does a set of commands inside the script to fetch the two bytes for a parameter's value, translates the two bytes into a 0-127 value, then sets the value of the "knob" on the gui.

I've got it to work.. sorta.  Problem is that I see the knob change to the dump's value given (and it's the correct value after a formulation).  But it then immediatly snaps back down to zero again.
I'm thinking that the confirmation msg sent back is causing this to happen.

Now if I set that knob in the GUI to have a minimum value of "1", then the value gets a hard set minimum of "1" and it stays at the dump valu.. IE, it wont snap back to 0 again, it will set to whatever patch dump# value you chose.  But of course this is useless if you need to have a value of 0 and it wont let me dial in a 0 if I do that... the lowest I can go is "1".

Your thoughts??

-Blaine