Ableton Forum

Anyone who has a padKontrol and Live 5.2.2, can you please take just a moment (from drowning in the OT threads ) and test this now. It's a simple test and I'd really appreciate it.:

Try to play an F3 (midi note #53) on the padKontrol to any instrument plugin in Live 5.2.2. Does it play the note?

To select F3 on the padKontrol, press "setting" -> "note/CC" -> hit a pad and turn the data wheel until F3 is displayed.

I've been driving myself crazy with this!

are you sure F3 isn't assigned to anything remote control related?
i'm so busy with other things that i haven't touched Live for months now...

Really? That could be it? Every note works on the padKontrol except F3 in Live. But when I plug a midi cable from the padKontrol directly into a hardware synth, it plays the note. So it's definitely something within Live.

I thought that remote messages and note messages were totally different even though they use the same note names.

I have my Live set template mapped for my faderfox controllers. It's the template file settings that come with the faderfox.

So if a midi note is programmed as a midi remote, it will only control that object and not play the note?

icedsushi wrote:Really? That could be it? Every note works on the padKontrol except F3 in Live. But when I plug a midi cable from the padKontrol directly into a hardware synth, it plays the note. So it's definitely something within Live.

I thought that remote messages and note messages were totally different even though they use the same note names.

I have my Live set template mapped for my faderfox controllers. It's the template file settings that come with the faderfox.

So if a midi note is programmed as a midi remote, it will only control that object and not play the note?

Hi,

It is true that a same note on the same MIDI channel can only be used either to 'play' a synth, or as a remote control. So, you should use a different MIDI channel for your PadKontrol and the Faderfox, as to avoid any confusion.

Regards,
Amaury

Cool. Thanks! This certainly sheds some light on the situation. I'll give it a try tonight...

This had been bugging me for months. I was ready to throw the padKontrol out the window. And Korg tech support had no idea what the problem was.

That did it. Problem solved!