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

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

Extracting object properties from an IFC file with IfcOpenShell

Besides the object geometry information, IFC files may contain properties for the IFC objects. The properties can be, for example, some predefined dimension information such as an object volume or a choice of material. Some of the properties are predefined in the IFC standards, but custom ones can be added. IFC files can be massive and resource-intensive to process, so in some cases, it helps to separate the object properties from the geometry data. IfcOpenShell  is a toolset for processing IFC files. It is written mostly in C++ but also provides a Python interface. To read an IFC file >>> ifc_file = ifcopenshell.open("model.ifc") Fetch all objects of type IfcSlab >>> slab = ifc_file.by_type("IfcSlab")[1] Get the list of properties >>> slab.IsDefinedBy (#145075=IfcRelDefinesByType('2_fok0__fAcBZmMlQcYwie',#1,$,$,(#27,#59),#145074), #145140=IfcRelDefinesByProperties('3U2LyORgXC2f_hWf6I16C1',#1,$,$,(#27,#59),#145141), #145142

Hubristic developer

Almost half of any Finnish generation goes through a shared experience: the conscript army. An integral part of that experience is learning military slang, a set way people in the army talk. The stories told with said jargon often spread outside of the barracks. It is not uncommon to hear strangers bonding together over beers reminiscing and feeling nostalgic about freezing cold nights spent in tents. There is a similar phenomenon detectable among us coders. To be part of the coder tribe, there is at least one type of story that one must master. That is - of course - ranting about legacy codebases. "Can you believe how much of a mess the previous coders left? Hear, hear!" There is no better way to onboard a new team member than to blame some previous B-team for all the murky parts of the system at hand. This can be seen as harmless, a subject for a good  meme . Rarely do we hold real grudges against "the legacy folk" and can be the best of friends in a social gather