MIDI dropouts when Houtcues assigned to Mascine pads

When mapping hotcues to the 16 pads on maschine the response is very good untill I stop my decks (scratch control mode). Now if I want to play with my hotcues and play them just as long as I keep the pad pressed it works ok for 1 or 2 or 3 times and then the x-time keeps playing when I let go of the pad.

I have to say that when mapping hotcues to pads on the maschine you have to change the pads default notes to MIDI CCs in order to get the aforementioned effect.

Anybody has the same issue?

 

Yup, I've got exactly the same problem, desribed here:
http://www.native-instruments.com/forum/showthread.php?t=91341

I've also noticed that sometimes turning one knob in also affects another knob in traktor no matter how simple or complicated midi-mapping I've created.


Overall the new midi-mapping, glorious in it's "logical controller" solution, is not very stable at all. This must be an absolute top priority for NI since it's affecting ALL features, imho.

 

Yeah, I agree with you! Hope this will be fixed in the official update...

 

I've just re-done the mapping to my VCI-100 due to the many changes in controller types with beta 1.2 and now I've got MAJOR issues, but none that can be repeated on a regular basis (these bugs are not the same as the thread starters but I believe they belong to the same category of bugs). For more info regarding the same bug as described in the first post, check my link to my other thread a few posts up.


Basically I've mapped out the functions so that I control deck A&B in traktor per default. With a modifier toggle I can then control deck C&D instead. I've done this mapping at least 20 times from scratch so I'm 100% sure that everything is mapped correctly. Now to some of the issues:

When I press the "next cue" button on Deck B control, Deck D jumps to hotcue 3 and starts playing from it by keeping the CUE button pressed down (it's the same button on the VCI but it's regulated by different modifier states - yes I've checked and double checked, there is nothing wrong with the midi-mapping or how the modifiers are behaving). When i toggle deck C&D control and hit CUE on deck D, the playback stops as expected. The crowd would give me funny looks if it were to happen on a regular club as you might understand. I do the same thing again, and I get exactly the same results. When I try it for the third time nothing happens and traktor seems to be doing exactly what I want it to do. Good times.

Now I go into browser mode and look up a new song to play. When I hit "LOAD DECK A" (which is the same button as CUE - Deck B in "playback mode"), the song loads into Deck A and Deck B is cued - the music stops and a live audience would give me sarcastic applause and laugther. I repeat exactly the same steps three more times but I can't recreate the error.

There are a lot of other "strange" behavior here and there, but it's hard to remember them all.
Anyhow, this is NOT good... obviously both Machine, the VCI-100 and my custom controller has these issues which leads me to believe that it is NOT hardware related, but something within the new midi-mapping engine in traktor.

Please let our voices be heard, if this is not fixed I can't go live with traktor any longer, it's just to much to risk (even if the software itself is pretty rock solid, crashwise)

 

Did you put Modifier state 0 and 1 for this or just 1? I mean if you have one action without pressing the modifier (here you have to state that modifier value is 0), this action will be executed again when pressing the modifier unless you put in a previous action modifier value 0.

I have another problem... Traktor sometimes doesn't react to incoming MIDI at all. Works for a few times and then suddenly just stops converting the MIDI messages.

 

when M3 is 0, the VCI-100 controls deck A&B and when M3 is 1, the VCI-100 controls deck C&D

and the button for changing the M3 state is not any of those I pressed...