This is Mackie Control Universal Pro.
It comes with motorized fader, LCD, and is connected via MIDI.
I was thinking to make this because MCU protocol is used everywhere, ranging from their own MCU, icon QCon Pro or even virtual ones such as TouchDAW
Anyone can guide me where to start? and is Arduino a compatible board for this kind of stuff?
EDIT : If this succeeded, I will post every journey I got here on GitHub!
Maybe... But, I'd recommend starting with something a lot simpler...
The basic MIDI functions don't require much processing power and you can expand the number of digital & analog inputs with multiplexing.
For example, the ATmega chip only has one multiplexed analog-to-digital converter so there are multiple analog inputs. By using external digital or analog multiplexer chips you can have an almost unlimited number of inputs.
However, the displays on the Mackie unit make me think there is some more processing power in there.
And, it's probably impossible to build anything that looks that good.
DVDdoug:
Maybe... But, I'd recommend starting with something a lot simpler...The basic MIDI functions don't require much processing power and you can expand the number of digital & analog inputs with multiplexing.
For example, the ATmega chip only has one multiplexed analog-to-digital converter so there are multiple analog inputs. By using external digital or analog multiplexer chips you can have an almost unlimited number of inputs.
However, the displays on the Mackie unit make me think there is some more processing power in there.
And, it's probably impossible to build anything that looks that good.
I almost sure that MCU talks with DAW with 100% MIDI.
I've seen another icon product that also emulates MCU, but without LCD.
I'm not worried about the build quality. Hehehehe
Yes you can do all that with an Arduino, it looks like you will need to squeeze in a lot of code and memory is needed for the LCD so I would go for a Mega.
How much about MIDI do you know?
Grumpy_Mike:
Yes you can do all that with an Arduino, it looks like you will need to squeeze in a lot of code and memory is needed for the LCD so I would go for a Mega.
How much about MIDI do you know?
Not that much, I only played with MIDI CC and MIDI notes. I myself used MIDI almost everyday on stage and at studio with Ableton Live, and have done some complex MIDI routing.
I know that this thing should have SysEx or something that makes the MIDI code unique, but I haven't debugged them.
I still have about one year to complete this project, so I'm not in rush. To be honest, I'm planning to use this project for my thesis, and we just started learning arduino related stuff this semester 
In that case I would recommend this book Arduino Music and Audio Projects | SpringerLink
Ok so I wrote it so I might be biased but it gives you a firm introduction into what MIDI is and how to use it along with lots of projects both small and very big.
You only need SysEx messages to communicate your controller specific things, I can't see you needing any in this project.
The big cost is in the buttons and knobs. Motorized faders are ~$20-$50 each.
If I were you I'd start by figuring out how to build a fader module. It'd be a great ATTiny project involving the mechanics/enclosure, analog read of the pot, a motor driver, and I2C addressability so you could eventually build up a bank of faders that would be controlled be a separate, "master" Arduino.
Grumpy_Mike:
In that case I would recommend this book Arduino Music and Audio Projects | SpringerLink
Ok so I wrote it so I might be biased but it gives you a firm introduction into what MIDI is and how to use it along with lots of projects both small and very big.You only need SysEx messages to communicate your controller specific things, I can't see you needing any in this project.
So you wrote that book? hahahaha nice. I'll put that in to my shopping list.
And yes, I'm also not quite sure if MCU uses any SysEx.
Chagrin:
The big cost is in the buttons and knobs. Motorized faders are ~$20-$50 each.If I were you I'd start by figuring out how to build a fader module. It'd be a great ATTiny project involving the mechanics/enclosure, analog read of the pot, a motor driver, and I2C addressability so you could eventually build up a bank of faders that would be controlled be a separate, "master" Arduino.
Yes, just realized that price 
Is there any DIY solution?
Just realized that your idea is great! I mean, I could make one uno that talks with the fader only, then control the rest with mega, then make the uno and mega talks with MIDI. sounds cool 
Just realized that your idea is great!
Well as the writer of that book I would not go along with that, it sounds more trouble than it is worth.
Yes, just realized that price
They tend to be more expensive that getting them on eBay.
Grumpy_Mike:
Well as the writer of that book I would not go along with that, it sounds more trouble than it is worth.
They tend to be more expensive that getting them on eBay.
I think MIDI is freedom. We can make something trigger totally different thing and nobody would complain.
Also, why I think this is a great idea, I can make (almost) modular thing and know where to debug if things gone wrong. Or am I wrong?
Care to elaborate?
I'm still thinking about that motorized fader. Do the cost actually worth it? Or is there any cheaper solution?
It does not make sense to have the fader more expensive than the arduino itself
Often the Arduino or processor is a lot cheaper than the box you put it in, that is the way of things these days. You can make chips in vast numbers in a small time with few people. Mechanical things can take time and you don't sell them in the same large numbers.
Sure you can do what you want but this forum is about advice. Over they years I have seen many many beginners think that a smart solution is to have multiple processors. This is only because their limited knowledge of how to do things makes that solution look appealing but it often causes more problems than it solves.
Grumpy_Mike:
Often the Arduino or processor is a lot cheaper than the box you put it in, that is the way of things these days. You can make chips in vast numbers in a small time with few people. Mechanical things can take time and you don't sell them in the same large numbers.Sure you can do what you want but this forum is about advice. Over they years I have seen many many beginners think that a smart solution is to have multiple processors. This is only because their limited knowledge of how to do things makes that solution look appealing but it often causes more problems than it solves.
I'll keep that in mind, thanks.
But then, my lecturer requires me to implement network support!
One thing that comes in my mind is rtpMIDI.
But is that even possible?
But then, my lecturer requires me to implement network support!
So this is the first mention of a lecturer, therefore I assume that is is some sort of assignment.
One thing that comes in my mind is rtpMIDI.
But is that even possible?
It might be but you will have to look into it. What is wrong with OSC?
Grumpy_Mike:
So this is the first mention of a lecturer, therefore I assume that is is some sort of assignment.
It might be but you will have to look into it. What is wrong with OSC?
no, this is for my thesis. I still have a year to complete it.
I have no experience with OSC.
My lecturer also told me to try consider using Raspberry Pi.
... well, okay. sure we can send MIDI output, networking is already there, and sure I can shove anything inside since that is basically a computer.
But then, how can I use 8 motorized fader (I think the pin would not be enough), and giving USB MIDI to computer without involving arduino as a MIDI to USB converter?
A Raspberry Pi can not produce the baud rate required by the MIDI standard without a great deal of bother so I would forget that.
Yes you need a proper driver for the motorised faders, no processor pin is going to be able to power that sort of motor directly. You need a H-bridge driver to move the fader in both directions and requires two output pins. Also you need another two for monitoring the end stop switches and finally an analogue input for reading the value. So that is six pins per fader. Look into port expanders, you will need them on this project.
Grumpy_Mike:
A Raspberry Pi can not produce the baud rate required by the MIDI standard without a great deal of bother so I would forget that.
I'll let my lecturer know that. Thanks!
Grumpy_Mike:
Yes you need a proper driver for the motorised faders, no processor pin is going to be able to power that sort of motor directly. You need a H-bridge driver to move the fader in both directions and requires two output pins. Also you need another two for monitoring the end stop switches and finally an analogue input for reading the value. So that is six pins per fader. Look into port expanders, you will need them on this project.
Again, once again, thank you. I learned many things from you.
I'll keep this thread updated with my progress.
Now I had to look for arduino simulator before doing this in real life ... :s
Now I had to look for arduino simulator before doing this in real life ...
The problem with an Arduino simulator is that it is not very good at simulating outside components. My advice would be do it for real.
Just in case your lecturer thinks I don't know what I am talking about you can tell him I also wrote / co-wrote these books:-
Grumpy_Mike:
The problem with an Arduino simulator is that it is not very good at simulating outside components. My advice would be do it for real.
Yes, I know simulation sucks. But I had to do it.
Also, we have no mega around, I still have to buy the motorized fader (I'm at Indonesia and should import them from somewhere?), these things are expensive and I'm not even sure if these things works ._.
So yeah ... I have no choice for now.
You know any good simulator that can talk to my DAW somehow?
(I heard Proteus 7 can do that, but I'm not feeling good when pirating software, since my Ableton Live is genuine lel)
As I never use simulators I know nothing about them, sorry.