I'm not new to the midibox project, i've already done a midibox64 (Video), then after this one i've tought in the last two years to do a complete dedicated traktor controller but a lot of other tasks kept out me from the realization while i ever did schemes and layout prototypes in the meantime without building it.
By the way, going ahead with my idea!
In these last days was announced a new controller for NI Traktor, the 4midiloop. It is really cool, well builded, top components etc, it was conceived with in mind the total control of four decks, four fx, and all the deck loop, cue, etc controls without too many shift functions or layers. I really like this concept and is very near, if not the same of mine not developed in these years.
Seems that the quality build cost something, in fact the price is set to 1300€, personally too much for a controller, obviously they've invested on it and someone that is afraid to build himself controllers perhaps is tempted to buy it. Not me, a "brave" DIY player!
So, if you've read the 4midiloop specs you can see that the components are:
Rubber knobs for best tactile feeling
166 Push buttons
USB bus powering Power supply via USB- Bus / consumption less than 300mA
USB interface class compliant / no driver necessary
1- I'll start with the usb bus powering, from what i know with midiboxHUI projects can't be used the new core32, i had to stick with the core8, then if core32 can be used i didn't saw a documentation for the core32 linking. Can you confirm me the use of core8?
2-For the 47 pots + 5 faders is quite simple, a core with 2 AIN Modules.
3-The 9 encoders + the 166 push buttons requires a total of 184 digital inputs, considering the first core were the 2 AIN are connected i've 64 digital inputs available with 2 DIN modules, so another core, linked to the first one, is necessary for the remaining 120 digital inputs. If i don't get wrong, i can use a core with midibox64 (for pots, faders and first 64 buttons/encoders) and a 2nd linked core with midio128 for the remaining 120 buttons/encoders. A confirm of this chain is really the focus for this project.
4-The Led's are consequential to the digital inputs, so no problem about Led's if all the digital inputs for buttons&encoders can be obtained with before explained 2 linked cores system.
5-(I'll update this point about knobs, case and panels after the project idea phase have success!)
Resuming, here are the components:
2 Pic based Cores (which one PIC for my needs?) or 2 STMcore32 (if possible to use them with midiboxHUI projects and if they're linkable linke the Pic based one)
2 AIN modules
6 DIN modules (2 on the first midibox64 core, 4 on the second midio128 core)
6 DOUT modules (2 on the first midibox64 core, 4 on the second midio128 core)
The last thing, but perhaps the more cool, is the idea to put all in a single pcb board to ensure a better fit for the case, this require a lot of effort in the pcb design but i'm not afraid of this, i did pcb design in my school so i've a bit of experience, but as ever, advices on this are really appreciated. I know that if i use all the separated modules i can dubug it easily than a "monster pcb", but you know, that's the cost to pay for a custom choice.
I don't use schematic and pcb software since some years, i'm trying Eagle and after some test i've found that isn't difficult to use it.
The things that i miss that might be useful are the schematics, in the ucapps website i find, for every project, the .brd pcb files but not the .sch schematics files. These files can speed up the single big pcb board design process.
Well, after this long intro i wait your thought and advices before starting this project that i'll use for my university design thesys.
Thank you all for the support and sorry for my school learned english!
(Later i'll add a flowchart of the system to be more clear if the description isn't)
Edited by Rics, 19 September 2010 - 10:34.