I am about to start making my Mackie Clone, (to use with Cubase SX), but are a little confused :-/ about the connection between the modules and the core.
My Mackie clone will have 8 motorfader, 9 encoder, 8 ledrings (of 11+1 LED), 73 LED, 89 button, 3 switch input and 2 2x40 LCD display. (And maybe a bankstick to change settings)
(I will bring a picture soon ;D)
Here is a picture of how I think the modules need to be connected.
The problem is that on the webpage for the core, it say the the MF module need to be connected to J10, but in the pdf for the MF modules it say J7.
Also I think I read somewhere, that the LEDrings are connected to the same chain of Dout module as the single LED, and the encoder is in the same chain of Din modules used for button input.
As I am only going to use 8 LEDrings can I just use a Doutx3 and not the Doutx4 in the pdf.
Hope to clear this up before I start making my box.
Thanks and see you all.
Kent
PS. I have not looked that hard on the MIOS files for the LC yet, but I will do that in the near futura, I know some of my answer may be in there.
Also I think I read somewhere, that the LEDrings are connected to the same chain of Dout module as the single LED, and the encoder is in the same chain of Din modules used for button input.
That´s right, just put the DINs and DOUTs for the Encoders/LED-rings somewhere in the chain and configure them in mios_tables.inc (encoders/LEDs rings) and lc_io_table.inc (normal buttons/LEDs).
You can also use the open in/outs on the encoder/LED-ring boards for some more buttons/LEDs. It´s a good idea to have some spare pins for extensions like layer-switching, display modes, LED meters and future features
Just a note: the touch sensors require an additional DIN shift register which can be connected at the end of the last DINX4
To the box layout: I would add at least one dedicated button for MIDIbox LC specific functions. Currently following functions are supported (see lc_io_table.inc):
#define ID_MBLC_DISPLAY_PAGE0 0x80 ; switch to page 0
#define ID_MBLC_DISPLAY_PAGE1 0x81 ; switch to page 1
#define ID_MBLC_DISPLAY_PAGE2 0x82 ; switch to page 2
#define ID_MBLC_DISPLAY_PAGE3 0x83 ; switch to page 3
#define ID_MBLC_DISPLAY_NEXT 0x84 ; switch to next page
#define ID_MBLC_SWITCH_LAYER0 0x90 ; switch to layer 0 (like radiobutton)
#define ID_MBLC_SWITCH_LAYER1 0x91 ; switch to layer 1 (like radiobutton)
#define ID_MBLC_TOGGLE_LAYER 0x92 ; like a "caps lock" key
#define ID_MBLC_HOLD_LAYER 0x93 ; like a common "shift" key
#define ID_MBLC_SWITCH_LEDMETER0 0x98 ; ledrings are working as normal
#define ID_MBLC_SWITCH_LEDMETER1 0x99 ; ledrings are working as meters
#define ID_MBLC_TOGGLE_LEDMETER 0x9a ; like a "caps lock" key
#define ID_MBLC_HOLD_LEDMETER 0x9b ; like a common "shift" key
just pick your favourite behaviour. I think at least a shift button with “hold” function should be used, this enables you to switch the LEDs and all other buttons (in later versions also the encoders and motorfaders) to an alternative layer.
how is the second LCD connected? is the second LCD connected in paralell to the first one, except for the data bus? where is the data bus? is it 4bit or 8bit? how do you know the pinout for J10 in relation to the second LCD?
any replies appreciated…Steve  ;)
btw, Thorsten is about to clock 900 posts! amazing!!
The inputs of the second LCD have to be connected 1:1 with the control lines of the first LCD. Just only the E (enable) input requires a seperate interconnection to the core module: J10:RC (pin RC.4 of the PIC)
Thorsten, I have made 4 dedicated button on my controller, one for shifting layer (name 2. FUNC) and 3 for other things to come (named EX.1 Ex.2 and EX.3).
I do not have dedicated button for “REC En.” (Record enable) but will use 2. layer for that on the “Select” button.
A little thing I fund out, is that in Cubase SX (that my controller are going to be used with) you can enable more than 1 controller, so you can have the Mackie controller enable and a Generic Remote Device.
This and the use off 2. layer gives you access to more custom functions and thing you may not access by using only the mackie controler.
I know that if the faders have touchsens it have to be connected to the DIN module (to send the mackie touch message), but the fader I am going to use have not :-[
Btw. does MIOS keep track off the status for led,so that when I switch to 2. layer and switch back to 1. layer again the led will have the right status?
To Steven_C and other, hope the picture help with making yours midibox. 8)
See you all
Kent
Ones again, Thanks Thorsten for making this great project, a ½ year ago I was going to make the code myself but then I found your site, and there it was 8) 8) 8)
Btw. does MIOS keep track off the status for led,so that when I switch to 2. layer and switch back to 1. layer again the led will have the right status?
yes, the application registers all incoming LED status messages so that they are also saved during the alternative layer is active
The block diagrams above are great - but how do I connect multiple cores together for having more than just 8 MFs with touch capability? It seems to cover everything else I need.
Also, what code do I put in the cores? Do I install the basic MIOS bootstrap and then download the standard build for all of the cores or do the MF only cores need some other code installed since they are not funcitoning for anything else?
I’m getting closer to understanding all that is needed to build a LC or mackie clone, but now I need some help with the software side of things so I know how to get it working with Sonar 2.2 once I build it! Any links out there on that subject? I’ve searched, but haven’t found anything detailed enough yet.
perhaps you have not been to http://www.ucapps.de/ this is where all the onfo on mios and mbhp are stored.
down on the left hand side on the menu there is a link called midibox link under the title concepts. here is the link http://www.ucapps.de/midibox_link.html
mb link uses the same connection as the ltc and the gameport. basicly you are connecting the pics uarts with one another. dont forget it connects like midi in –> midi out NOT midi in–> midi in
Thanks! I did find under the Core page under the connector listing table. I found after more careful reading that J11 is the port used to connect multipled cores together.
Please correct me if I’m wrong, but I understand that on the “slave” core modules, the optocouplers should not be installed to avoid midi corruption. That way the “slave” cores only get their midi data from the “master” core and nothing else. Is that correct?
Is my understanding also correct that the “master” core power supply can feed the other cores or should I wire them all to the power supply independently?
Thanks again for putting up with the dumb questions!
just for laughs do a search on “dumb Questions” there are some interesting views on this one 8)
optocouplers are not needed except for the midi in and the midi out ( i am not 100% certain on this)
if you have a large power supply you will only need one
so you dont need the voltage regulator on slave boards.
as i under stand you want another core so you can have more than 8 mf’s. motor faders need lots of power if i am correct so i think you will have to do a little research on this one.
the MBLC project emulates the original mackie control And the new mackie control that can control Sonar, Protools, DP, etc is different, as far as I know. So I don’t think the MBLC is compatible with Sonar, etc.
I remember someone had already tried Sonar with some success. I’ve tried to search for that thread but can’t find it. I know it works - but can’t remember who it was!
I plan to build the beginnings of an LC unit - probably just the shuttle and zoom buttons for now. I’ll add the other stuff later. When I get it built, I’ll let you know how it goes.
)
