I’ve been working on a Traktor mapping for the Machine and it is almost finished. However, the more it grows (it now has 6MB+), the slower the configuration window and switching between the midi devices gets. I have now 8 or 9 different devices defined and it now takes like 20+ seconds for the Preferences window to come up or to switch between devices. I have set up different parts of the mapping in different devices all pointing to the machine (which seems to work).
Is this slowness normal behavior and is separating functionality in different device definitions a bad idea in any way? I couldn’t imagine putting all the mappings in one device definition. I think I’d go batty trying to map that way.
Any experienced help with mapping in Traktor would be greatly appreciated.
You would think that as more and more complicated controllers get on the market, this issue will get worse too. I’ll write a ticket to NI and see what they say about it.
Well, I got an answer from NI. It isn’t really what any of us want to hear. I’m not even going to post it, as it would be just a waste of your all’s time reading it. I’ve written them back to tell them what my “practically useless” TSI is all about, why I want it working smoothly and that it does make some sense, at least to me it does. I’ll keep you up to date, if and when I get more responses.
“I don’t see any use for these other than cramming up mappings for 9 different controllers”
That is because I have used the devices to keep logical order of the different functions of each button page and knob set for the Machine. I asked in my last mail, if that isn’t the right way to manage so many commands, what is? Everything in one device? I said, that would be practically impossible.
I’m just hoping they’ll see that the controller manager could use some rethinking for very large controller mappings and might take it up to improve it in the future. Crossing my fingers…
LOL! i am definately not going to send them the bunch of tsi’s i currently have in traktor then
[quote]
That is because I have used the devices to keep logical order of the different functions of each button page and knob set for the Machine. I asked in my last mail, if that isn’t the right way to manage so many commands, what is? Everything in one device? I said, that would be practically impossible.
I’m just hoping they’ll see that the controller manager could use some rethinking for very large controller mappings and might take it up to improve it in the future. Crossing my fingers…
scamo[/quote]
hell yes… i can only hope that one day very very soon they come to their sense and add the much needed improvements to the controller manager.
out of all the functional areas within traktor surely this has to be the easiest of all to improve??? no need to worry about real time performance etc, it’s just a fricking editor window. how hard can it be to improve that?
maybe that xtreme mapping app popping up has made them think more about it? if i was a mac user i would get it - but as not i’d like to think that app has helped to raise their awareness of the issues a bit more if people are willing to shell out extra cash to improve them…
Yes, I even get some audio dropouts because of it. Probably because of all the LED outs on my Livid Code. This should be fixed, although it doesn’t bother my DJing experience if I don’t open the preferences.
Nope, you probably wouldn’t. But it doesn’t excuse the fact that this issue still sucks for those who want to do more with their controllers and more and more people are getting into more “devices”.
Looks like I’ve (we’ve) got some attention (as I’ve been linking to this thread and one on NI’s Forum too). The support person is taking this issue to the “DJ Support Team” and I should be getting an answer in a couple of days as to any course of action. Crossing fingers.
cool, sounds good. one of the main things traktor has going for it verses other software is the mapping flexability so they really should solve this issue…
also ofc they should improve the actual controller editor tho that might encourage even more complicated mappings - so i think they should solve the other issue first
Yeah. In my last mail to them I also mentioned the fact the editor/ manager is unweildy, in that you can’t see all of the mapping fields. In other words, I’d actually like to see the controller editor in its own window and not all squished up in the preferences window.
)
