OT: Korg padKontrol not working with Scope

siriusbliss · Post by **siriusbliss** » Sun May 07, 2006 1:57 pm

I just bought a Korg padKontrol for triggering dfhSuperior drum samples inside Samplitude Pro.

With my basic Yamaha keyboard I can trigger dfh just fine using the normal MIDI source/dest modules, but with the PK I can't get MIDI in to work at all. If I unplug the USB (bus power as well as optional MIDI) and use a 9V DC power supply I get NO MIDI activity at all.

Plus, with the DC power supply, the LED screen just blinks and I get just basic MIDI note messages, but no triggering. Using USB power I get full functionality of all the PK's features.

Could there be a conflict between the PK's USB MIDI and Scopes standard MIDI I/O?

Greg

H-Rave · Post by **H-Rave** » Mon May 08, 2006 3:41 am

Do you have to switch between usb and midi modes on your controller ?

[ This Message was edited by: H-Rave on 2006-05-08 04:41 ]

siriusbliss · Post by **siriusbliss** » Mon May 08, 2006 7:18 am

I don't have to, but I've tried either mode - a simple switch changes from DC to USB power.

When on USB bus/phantom power, the unit behaves correctly, but I get no MIDI data to/from the unit. WIth DC power the LED screen blinks, and I DO get some MIDI data, but the rest of the unit doesn't behave properly at all.

I am also unable to send/receive scenes.

I presume that the PK will work correctly on my older basic Soundblaster machine, so I'm going to try it.

I'm still just trying to figure out if this is an issue with Pulsar conflcting with USB MIDI apps., or maybe my Asus P4C800 motherboard is gagging on multiple IRC's on the USB ports, or whatever.

I know that in the past there was a conflict with USB and Pulsar, but I have external harddrives and Samplitude USB dongle/key on my machine now with no problems at all.

Greg

Post by **garyb** » Mon May 08, 2006 8:27 am

you can use both usb and midi ports. usb will provide power and patch/remote control of the unit. midi will communicate with scope.

if you use just usb, you will need another app(midi ox or a sequencer) to loop the midi through the seq midi source module in scope. there is no module for usb midi sources. you will need to receive the midi data in the second app and transmit it to scope. drivers communicate between hardware and software, not between two pieces of hardware.

siriusbliss · Post by **siriusbliss** » Mon May 08, 2006 8:17 pm

I already understand all this, but I have had no luck with running the USB power while using MIDI into Pulsar source to sequencer dest.

I've tried various configurations with no luck yet.

Next I will try it on another system.

Greg

Post by **garyb** » Mon May 08, 2006 10:02 pm

it sounds broken....

i use an akai mpd16 powered by usb w/midi connected to scope with no problems. i've used a few keyboards that way as well.

[ This Message was edited by: garyb on 2006-05-08 23:03 ]

siriusbliss · Post by **siriusbliss** » Fri May 12, 2006 7:20 pm

It works on my laptop via USB only. Still have to try it on another system.

valis · Post by **valis** » Fri May 12, 2006 11:47 pm

From what I can see in the manual, it has a note on page 12:

If you’re using a USB connection, the data from the
computer is transmitted from the padKONTROL’s MIDI OUT
connector. MIDI messages generated by operating the
padKONTROL’s trigger pads and X-Y pad will not be
transmitted from the MIDI OUT connector. (p.28)

In other words, when you have it connected via usb the midi out port functions as a midi out for your software (in the computer), NOT for the padkontrol. The controls only send data via usb.

If this is intended for studio use, it probably makes more sense to just route it through your sequencer to the Creamware midi drivers and use usb for midi into your sequencer. While there are a few milliseconds of jitter introduced by routing through software, if you're recording the midi data anyway it won't make any appreciable difference.

[ This Message was edited by: valis on 2006-05-13 00:50 ]

siriusbliss · Post by **siriusbliss** » Sat May 13, 2006 2:15 pm

yes, thanks, I read this in the manual, but with DC power I get MIDI activity into Scope, but not Samplitude, and the padKontrol doesn't behave properly (no rolls/flams/scense, etc.). With USB power/MIDI, the padKontrol behaves properly, but I get no MIDI activity in Scope.

I need to see MIDI data into Scope getting to Samplitude so that I can trigger dfhSuperior drums. Right now it's an either-or situation, and neither one works.

It's working fine on two other systems using USB only (with inherent latency), but not with DC power and MIDI I/O. If I have USB AND MIDI connected I get nothing at all.

This is the only USB unit I've used with Scope. ALL my equipment runs normal MIDI with no problems.

Korg seems to have hidden tech support via their website buried somewhere where you only get FAQ's and redundant support emails that get no replies.

So, my backup plan for upcoming sessions is to trigger dfhS on an older machine and use the MIDI tracks in Samplitude later on.

Either that or I'm just an idiot.

Greg