issues trying to import MIDI settings

When trying to import the DJTT 2.2.8 tsi that Ean Golden created, I am unable to select importing the MIDI settings. On the one I exported a while ago I am able to import the MIDI settings. However I have all sorts of issues with my mapping, the deck in focus is being switched between the different decks in rapid seemingly random progression. Anyways, not sure whats going on here. Will report a bug ticket when I have more details.

 

I had the same problem.
I deleted all the midi settings and reloaded the settings from my backup.
(the add button => then import)
After that everything went fine...

 

i managed to get the import issue solved by using the import in the controller mapping section and not the global section.

anyways, the entire mapping done by Ean for the VCI-100 is totally broken. Very few buttons behave as they did before, the LED's dont behave etc. i got quite scared that my VCI-100 was broken, so I went back to 1.1 for now .. everything is running fine again. not sure what the issue was, but i am guessing there were some serious issues with the MIDI import.

 

Some things I've run into:

when trying to map an LED light I choose new output and the "learn" function is grayed out. I can manually choose the channel and note, but can't "learn".

I think it would be an improvement if the controller manager tab remembered wether you were mapping the keyboard or midi last, because sometimes I close the window while mapping but I need to go back and edit the MIDI settings.

When duplicating a midi mapping the assigned note is deleted but i liked having it remain the same because often I want one button to do many things.

In my MIDI mappings, all the tempo faders were changed from relative to direct. Fortunately once I changed it to relative I could see that my percentages were retained. I wonder why?

I've found a way to get Ean's 1.3 firmware and traktor pro map LEDs to work but haven't ironed out my original custom alterations on it due to the dual function of some buttons and shared notes when applied to the new MIDI paradigm in traktor.


That's all for now - no actual bugs yet, just adapting and experiencing growing pains.

 

+1 to all of the above. also adding that i do not think its a good idea to not allow me to change an in to and out midi message and vice versa. as stated above the workflow is usually that you create one mapping and then duplicate to work out all the additional mappings for that behavior.