g.andreini

You have to know the correspondence between each note and led. Example: your firmware lights on the led n. 1 when it receives a C3-127-MIDI CH.1 your firmware lights off the led n. 1 when it receives a C3-0-MIDI CH.1 Then you set the PLAY-DECK A in traktor preferences as OUTPUT on note C3 Channel 1. If you don't know the notes try to connect a keyboard to the midi in hope it helps cheers

That's probably the easiest thing: traktor send midi notes for each control, you just have to set up it in the preferences/midi, selecting OUTPUT Then the controller has to be waiting for incoming midi signals (MIDI IN) and light the leds on/off depending on it. Ciao

i'm going on... but i changed direction and didn't go on width the PIC18F452 microcontroller

Hey Primate i made an interesting discover! I installed Midi Monitor on my Mac to check what traktor sends via MIDI-OUT when you press buttons around then... i discovered that in the preferences/midi mapping you can set the controls to send midi out (interaction mode: output) in this way you can choose which note or midi control use to send the midi feedback to the controller. Works fine! at this point the work has to be done after the midi-in port of the controller and switch leads on/off depending on midi messages!!!! hope it helps ciao

Really interesting to me! Keep us updated! g

i forgot to attach the diagram here it is

Thanks Stryd! i changed the direction of the MIDIBox Link as you suggested and updated the diagram i made the diagram with adobe illustrator, i work as web and graphic designer so it's quite easy :) For what concern the soft.... Here's what i found on the manual: Then looking at my current setup on traktor (setup for teh DX2 faderfox) i see note controls (like "Note C0 (ch 16)", Note E9 (ch 16)"...) and CC controls So i see you can have CC controls from 000 to 127, Notes from C0 to B8, Pitch Bend control for midi chanels from 1 to 16. Is it good? It should be good, isn't it? Anotherr very interesting thing i found on the manual is this: Does this means tha traktor can control wich led to light on/off depending on what's happening inside the software? If i press the loop button and a loop starts traktor tells the controller to light the loop led??? And then if i press again on the loop button, traktor removes the loop and "tells" the controller to ligh off the llop led?? Is there a way to have midi feedback? That would be excellent But i don't have an idea of how this can be made. Anyway i'll soon order the parts i need to start 3 cores + DINs and AINs to build the master section + 1 deck Any suggestion is welcome g

Hi dudes! i'm working on a project of a traktor controller. It's some weeks i follow the forum and read around the site and the wiki. OK, i feel i'm not the first thinking about that. But let's go on. The controller is made to control the 4 decks of the software. One of the most important thing is the ability of having al the controls on view, no needs to swicth anything to move from deck A to C or things like that, What you see under your eyes is what you can control in the software. Controls needed: Total ca 133 buttons ca 10 encoders ca 8 pots But that's not really the point My idea is to project something that is a little modular. I told my friends about my project and show them some ideas about the interface. All of them had different opinions on the controls they need. They want to use it in different ways so... different needs. The idea is to have an object divided in three parts: 1. Master section and Effects: Master tempo control, browsing controls, views controls, some free buttons 2. Decks A & B controls 3. Decks C & D controls Each of the these part has a MIDIBox 64 as brain. These 3 brains are connected by MIDIBox Link. Then connecting more or less buttons or pots or faders shouln't be a problem. The MIDIBox has enogh space for controls. I attach an image showing a diagram. I'd like to have some feedbacks about the project if it's possible. A great idea would be to do a kind of shared project with someone else trying to build a traktor controller and share experiments, solutions to probelms, tricks. Anyway there are still many dark aspects i'll try to make clear in the next days/weeks redainga round and asking (don't hate me). I'm about to buy the Cores, the Ains the Dins and the led in a couple of day.. so you you see something wrong in my diagram let me know... you couls save me from buying wrong components. Thanks :) My plan is to start building the controller with the three cores but just with one deck. Then when ione decks will be working i'll complete the other three. cheers g

Ok i've thinking a bit about my project I will post it in Design Concept, i think it's beter to go on there.

ok, thanks stryd_one i can assure that is a couple of weeks i'm reading around the site, the wiki and the forum but.. still i feel i know probably 0.1% about midibox... and don't like it really :( i'll go on reading for what concern the project... just let me say i've been djing many years, starting of course with vinyl the i moved on final scratch 2 (stanton) and moved to NI traktor scratch as it came out now i still dj with traktor scratch with two vinyls some months ago i decided to leave the vinyls and technics and move just to controller i've been playing (just in the studio, not in gigs) with two faderfox DX2 or a faderfox DX2 and a triggerfinger and so i came with a clear idea of what i really need to control traktor's 4 decks (not 100% satisfied with faderfox - still djing live with scratch + vinyls) i mean i feel what i would need, maybe this wouldn't fit another dj requirements. the interface should have push buttons of different sizes (big medium small) depending on how often do you use them and the kind of use: big are more performance buttons and smallers are editing buttons (allow to edit the grid, store loops and cue points etc etc) that's a brief introduction on the project on a more ergomonic and concept side unfortunately the new vestax controller (400) is not satisfying as it hasn't the controls for all the 4 decks, but requires you to swicth from A to C and B to D Anyway, first i want to acquire some basic knowledge that allows me to buy some stuff and start practicing and see how far i can go (hopefully.. very far ) The lucky thing is i have a couple of friend helping me, one is expert with electronics, soldering and the other is good on C programming se let's see what's coming out cheers g

Ok, thanks I'll try to go deeper in the wiki to see if i can make this more clear to me. I'm afraid a miss some base knowledge, but will try anyway. The project i'm thinking of is a traktor controller for 4 decks. It should have about 133 buttons 8 pots (for fx) some encoders. No faders as i'll be using 4 audio separate output and do the mixing on the mixer. The MIDIBox 64 should control the Master part (Master tempo, browser, view selection, Effects) with buttons (less than 64) encoders and pots. The MIDIO 128 should control the four decks, using mostly buttons and some encoders (that if i'm not wrong are connected do the DIN). So, as u see, the idea is to have the two main modules one controlling the master part and the other controlling the 4 decks. I need to have the MIDIO 128 to have the possibility to control more buttons. I didn't consider using 3 MIDIBox64, but that would be a solution, but honestly don't know what's better. This is the starting point for me, also because this is important for understainding which parts i need, and ordering them. Also i have other questions but will keep them for later. As i have understood how the main cores have to work i'll start working at a prototype (just for one deck + master section) and try to fix all probelms and doubts. I attach an image of the schema of the project. Ciao and thanks for welcoming :) g

Hi everybody! I can't really understand at which level is the difference between these two modules. I'm planning to work on a project and i'll need both these connected and working togheter, cause i'll need the 64 buttons of the Midibox 64 + the 128 buttons of the MIDIO128. I can't understand where the difference is: in the hardware? in the bootloader? the MIOS? simply depending on what you connect? I've been reading the site and the wiki but can't find an answer to this basic question. And more... for connecting the two modules.. what's the best way? MIDIBok Link? (http://www.ucapps.de/midibox_link.html) Thanks in advance for you help :) ciao