Skip to main content

Bluetooth MIDInator

I got inspired by a Youtube video on making a cool MIDI controller by Switch & Lever https://www.youtube.com/watch?v=JZ5yPdoPooU
He uses scrapped/recycled parts for the controls screwed into a beautifully crafted casing. Sadly, I'm not as talented as a craftsman as the Youtuber and could not conjure up the energy to start looting up phone dials and joysticks, yet I took on the project by building up my version.

I decided to make a Bluetooth MIDInator.  

The Arduino board I use is a Bluno board with integrated Bluetooth https://www.dfrobot.com/product-1175.html
The controller layout is a much simpler version than the original MIDInator with 16 potentiometers and four encoders.

First, I forked the repo and took a look at the code. It was understandable and readable, thus a good starting point for the project. I use a breadboard and a potentiometer to try out the MIDI communication through the serial port to a DAW with Hairless MIDI and loopMIDI, and it works pretty much out of the box.

Now came the trickiest part of the project, which was to make the wooden casing. It's made out of plywood and some wood scraps I found at my parent's farm. I drilled the holes for the potentiometers and encoders and glued up everything else but the lid.

The lid


I used copper tape on the lid as a bus for 5V and ground connector. I soldered and attached the parts close to the way as in the original MIDInator.

All wired up


Setting up the Bluetooth connection was a pain. I thought I could use a generic Bluetooth connection, but it turned out Bluno uses some proprietary protocol, and I needed to order a separate Bluetooth dongle. In hindsight, it would have been smarter to use a regular Arduino with a separate Bluetooth shield to enable the use of a universal BT dongle.

Once I received the dongle and got the connection working, all that was left to do is to modify the code to support the 16 pots and 4 step encoders. I pretty much copy-pasted stuff from the existing implementation to find out if I had any wiring problems (which I did). The coding part here was the easiest, and after a few tweaks, it was working.







Comments

Popular posts from this blog

Bird is causing high CPU on my macOS

There is no lack of people complaining about MacOS Tahoe, mostly about rounded corners and inconsistent design decisions. I have not paid that much attentention to that, but there is one mac bug i have paid attention to. It hasn't been a visual or ux but rather few system processes pegging the CPU. trustd , alongside with ecosystemd and ecosystemanalyticsd all reported high CPU usage. I can't exactly recall when this started, it might have predated my Tahoe upgrade but anyway, the trio of processes all had high CPU usage. Sure, it may have been the virtual efficiency cores and whether it affeced battery life or slowed down other processes i don't know to be hon...

I'm not a passionate developer

A family friend of mine is an airlane pilot. A dream job for most, right? As a child, I certainly thought so. Now that I can have grown-up talks with him, I have discovered a more accurate description of his profession. He says that the truth about the job is that it is boring. To me, that is not that surprising. Airplanes are cool and all, but when you are in the middle of the Atlantic sitting next to the colleague you have been talking to past five years, how stimulating can that be? When he says the job is boring, it is not a bad kind of boring. It is a very specific boring. The "boring" you would want as a passenger. Uneventful.  Yet, he loves his job. According to him, an experienced pilot is most pleased when each and every tiny thing in the flight plan - goes according to plan. Passengers in the cabin of an expert pilot sit in the comfort of not even noticing who is flying. As someone employed in a field where being boring is not exactly in high demand, this sounds pro...

How my work has changed in the past few years

When I started at my current job 3ish years ago, we had nothing but a few PowerPoint slides and a Figma prototype. I recall talking with one of the founders, whom I had worked with some 10 years ago, and pointing out that the very next step after PowerPoint and Figma was still the same as it had always been: translating those slides and mockups into CRUDs, forms, and other basic building blocks. Sure, all the new fancy tools and frameworks (we had jQuery then) help, but I still had to tinker with very basic primitives like tables and forms. I could not just say, "here is a table, here is a form." Well, yes, technically I could, but I still needed to write a lot of code to make a working form or table. This was around the time of GPT-3, Copilot beta, and very early Cursor. I did attempt to use them, but they could only perform very basic tasks and were pretty much useless for frontend work. We, being one of the first-wave "ChatGPT wrapper" startups has naturally pus...