Sound Editor cant recognize device

rkane136 · Post by **rkane136** » Mon Mar 02, 2009 8:12 pm

I am trying to Connect my microKORG synthisizer to my computer to edit the sounds on the KORG using the KORG soundEDITOR program supplied as freeware by the company. I am using the minisport UNO interface. The problem is that the program recognizes the minisport UNO as the midi in/out device. But it cannot recognize the microKORG.. a couple problems that might have to do with this that i ran into along the way are, when i put in the supplied minisport UNO cd, it would not install the software or drivers. i have Vista 32-bit. So i went to the m-audio website and downloaded the drivers for vista 32 bit, ( i dont know what sp-1 means) so i just got the regular one. still i get no recognition from the microkorg program. When i use the program MIDI-OX it sences some kind of signals when i touch the keys but other then that it really doesnt sync up. just hopeing you guys can help. OH i remembered to take the write protection off and i turned it to E-E

Daz · Post by **Daz** » Mon Mar 02, 2009 8:30 pm

Hi R.,

IIRC when this kind of problem has come up before it was because the microKorg wasn't using channel 1 as the global midi channel. What's yours set to ?

D.

rkane136 · Post by **rkane136** » Mon Mar 02, 2009 8:41 pm

Yeah i know i have the midi channel set to 1, but is it different for global, if so, can you specify how to change it to whatever i need it to change to

rkane136 · Post by **rkane136** » Tue Mar 03, 2009 12:03 am

im still getting a message that says check MIDI device settings. does that mean that it is a problem with the MIDIsport UNO or the microkorg.

rkane136 · Post by **rkane136** » Tue Mar 03, 2009 12:28 am

heres what i get on a midi input and output viewer. This is recorded when microkorg sound editor tries to sync up , or recognize the microkorg.

Midi input : TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
0001DA6C 1 -- C0 7C -- 1 --- PC: Telephone Ring
0001DA70 1 -- FE -- -- -- --- Active Sensing
00025695 1 -- C0 78 -- 1 --- PC: Guit Fret Noise
0002569A 1 -- FE -- -- -- --- Active Sensing
000358C1 1 -- C0 7C -- 1 --- PC: Telephone Ring
000358C6 1 -- FE -- -- -- --- Active Sensing
000393EC 1 -- C0 78 -- 1 --- PC: Guit Fret Noise
000393F1 1 -- FE -- -- -- --- Active Sensing

MIDI output;
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
00025695 1 1 C0 78 -- 1 --- PC: Guit Fret Noise
00025695 1 2 C0 78 -- 1 --- PC: Guit Fret Noise
000358C1 1 1 C0 7C -- 1 --- PC: Telephone Ring
000358C1 1 2 C0 7C -- 1 --- PC: Telephone Ring
000393EC 1 1 C0 78 -- 1 --- PC: Guit Fret Noise
000393EC 1 2 C0 78 -- 1 --- PC: Guit Fret Noise

Daz · Post by **Daz** » Tue Mar 03, 2009 3:40 pm

That looks odd to me, I would have expected to see a device inquiry followed by a suitable reply from the MK identifying itself.

Daz.