I think most people would just deal with having to hit the deck button 3 times rather than trying to remap everything or fiddle with the firmware.
Printable View
I think most people would just deal with having to hit the deck button 3 times rather than trying to remap everything or fiddle with the firmware.
Someone will come up with A-C / B-D tsi's sooner then later...
Maybe NI will improve the mapping part of Traktor :D haha no, i don't think so either
I think that's where the biggest problem is. It shouldn't be hard to batch in a controllerist's software.
And oilythread, i appreciate what you're trying to do. It's not easy stepping up and fight for a cause when getting flamed at. A space-highfive is on it's way to you :)
Quote:
Originally Posted by MrPopinjay
Quote:
Originally Posted by Stewe
Yeah definitely... But considering all of the other problems that are caused by this, it honestly just doesn't make sense for behringer to not just fix the problem.
Really Nemonic... You can totally just say "No we're not going to fix it, because it isn't worth it to us", and that's the end of it, (until they come out and people start bitching about how bad the system is)... But I've proven that it is, in fact, a flaw... So you're going to have to just admit that.
Thanks man :) I'm glad you see what I'm trying to do here.Quote:
Originally Posted by partylike1369
Ok, putting aside the fact that remapping is now going to take longer, what are the other problems?Quote:
Originally Posted by oilythread
Four main issues, all of which could be easily 100% solved by adding a firmware layer toggle.
1. Having to hit the deck button extra times (which has someone who currently uses even a correctly-working layer switch system... I can tell you will lead to preventable mistakes live.)
2. The LED readouts not working correctly (mostly only a big problem just because they won't work correctly for the vast majority of users)
3. Custom mapping either from scratch or by editing the factory TSI being vastly more complicated, as well as taking easily twice as long. In fact the amount of extra time it takes goes up exponentially based on how complex the mapping is.
4. The initial setup of the controller being very complicated and time consuming for the majority of users, including the ones who want to use the stock mapping.
How you can judge controller you haven't tested yet?Quote:
The LED readouts not working correctly
It's a bit late in the discussion to bring up that point. Nemonic has explained how it works...Quote:
Originally Posted by Stewe
I believe every deck page send massages in different MIDI channels and if so all LED output commands mapped in various pages should work properly.Quote:
Originally Posted by oilythread