Yes, it’s customized to work with traktor…what else would you want in a traktor controller? Is there some reason you want MB64(e) firmware (a generalised controller app), instead of an application specifically designed to do exactly what you want?
I think you may find it easier to add LCD functions to the traktorizer, than to add all of it’s features to MB64. That said, MTE has already pointed out: the LCD is not required, as his design already provides feedback to the user.
Rasteri’s scratch wheel is not supported with the MB64 firmware, but you can connect more than one scratch wheel to one core. Again that will require software modification. tj, I think you may need to do some more research before you take on a task like this. You’ll need to be familiar with either C or ASM programming, or to change your plan to a less complex solution.
In your case, as a short term solution in lieu of learning a new programming language, I would recommend that you build the traktorizer, as designed. MTE has made the controllers with the LCD, and then removed them, and decided that they were well suited to being made without LCD. I don’t know why he has made this decision, but I do know that he has put a great deal of work into building his traktor controllers, and has taken every consideration into account. I have been there for extensive periods of testing and experimentation and I can assure you that it would blow your mind!
What I’m trying to say is this: I think you need to spend some time learning, and until then, trust MTE’s design. He knows his stuff, big time
I just bought an m-audio 1by1 for about 40$, pulled the pcb out of the case and jumpered the wires underneath the pcb’s so i would’nt need a bulky cord and it works well too
