Play/Pause Toggle no worky!
I have a midi assignment for Play/Pause that is triggered by my NanoPad. It only seems to work if I set it to Hold or Direct. When set to Toggle, it does nothing. Has anyone else experienced this?
This T3 or TPro?
Traktor Pro 1.1.1.001
Can you use MIDI-Ox or something to see what kind of message the pad is sending? That could have something to do with it. I’m not in front of my machine, unfortunately, so I can’t troubleshoot it, but if no one gets to this by this evening I’ll give it a look 
Yeah, can you tell me the kind of messages that the NanoPad is sending?
Midi Ox says it’s a C#3 on channel 9. That’s also what the Kontrol Editor says. Here’s the output in Midi Ox:
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
0002C1F2 1 – 98 31 3A 9 C# 3 On
0002C47C 1 – 88 31 40 9 C# 3 Off
In Traktor Pro, here’s the settings for my Midi Mapping:
Play/Pause
Note C#3 (ch9)
Assignment: Deck A
Interaction Mode: Toggle
Type of Controller: Button
Modifier Conditions: None
Nothing happens when I press the button and Traktor receives the signal. However, if I change the Interaction Mode to Hold. The track will play while I’m holding the button.
Any idea?
I am not sure why you aren’t using direct, as I believe this has worked for me (I am not at home so I can’t check my settings atm).
mepetersen, cause Direct will have only one command, and it will be “On” so he could never stop it from playing.
I know I had this problem, B33… I’m just trying to remember what caused it, and how I fixed it. I’m taking tomorrow off from work so I’ll take some time and bash my head against Traktor to figure this out.
It is strange tho. It’s worked for me before… and even the other day, it worked again for a while.
Don’t know if this issue is related, but it seems that after playing say 5-10 tracks, my Deck B stops responding to Play or Cue midi commands and I have to resort to using the mouse. But sometimes, it will start working again if I load a new track to Deck B.
that is weird… is it giving you this problem with any other USB devices?
Yeah… my VCI-100 on my Deck B also seems to lose control of the touch platter part. Like I can’t use the scratch mode to move the track back and forth. This all happens at the same time. Deck A never seems to have this problem.
The play/pause issue on the nanopad is the same for both decks though.
More observations…
I have Play/Pause also set up on my computer keyboard. Bomes translates the key press into midi and sends it to Traktor. This still works even when the Nanopad’s play pad/button is not. So I went into Traktor and duplicated the midi mappings that make this work and then assigned the duplicated mappings to my play pad/button on the nanopad… still no worky.
Seems like the problem must be with the midi signal being sent.
I reassigned my Pad 5 (Deck A play) to trigger a cue point instead. Looks like I have a defective pad. It doesn’t respond like any of the other pads. It triggers the cue point inconsistently and seems to get stuck so that the playback on the cue continues to play longer than it should.
There’s still a problem somewhere because the same reassignment with pad 12 (Deck B play) shows that pad 12 responds as all the other pads do, very consistent and quick. However, when assigned as a play button, it does not toggle playback.
It could be the unit. Might be sending bad messages to the software.
So, more observations:
I also have a Korg NanoKontrol. I’ve set up a button to toggle “Effect Unit 1 On”. Just like my Play/Pause on my NanoPad, this button used to work fine. Now just like the Play/Pause on the NanoPad only using “Hold” or “Direct” does anything.
At the same time, I have the exact same mappings set up for “Effect Unit 1 On” and “Play/Pause” in Bomes. Both of these work fine. Wtf?
I’ve now gone through all the midi mappings that I have set up as “Toggle”. None of them seem to work when I assign them to buttons on the Korg NanoPad/NanoKontrol. I’m going to experiment with the settings in the Korg Kontrol Editor to see if I can get it working.
Post a midi ox midi log before the midi goes into Bomes and also your bomes midi log and ill have a look at it.
Okay, will do in a sec…
I figured one more thing out… there’s no hardware problem with my NanoPad. Pad 6 was responding slowly because its “Pad Behavior” was set to “Toggle” rather than “Momentary”.
Midi Ox Log…
I pressed button 1 on my Korg NanoKontrol. Toggle in Traktor doesn’t do anything. Same settings in Traktor as I listed above.
Here’s the outgoing Message from Bomes:
OUT: MIDI 99 60 01
I think it might have to do with the message type, then.
Try the out message being 99 60 00
Momentary messages send different commands than toggles, which Traktor then interprets differently. That’s something I can check with my Remote when I get home tonight. What
Okay, I’m going to experiement with different settings in the Korg Kontrol Editor.
To clarify, the message, OUT: 99 60 01, is from Bomes and that message is working in conjunction with Toggle.
…It’s the momentary CC messages that don’t seem to work with toggle at this point. (I also tried to use notes, but that didn’t make a difference.)