2020-01-01 (W) MIDIGlocken

To make things easier on my eyes, I formatted the incoming MIDI signals to make them readable. Instead of a string of integers rammed together without spaces, I:
  • added "0x" in front of each number
  • added a space after each
  • printed everything in HEX
  • added a newline after each command. 
During my formatting, I created an array to store each new message. The array made it easier to isolate the part of the command I was interested in. Since I will not control how hard the keys are pressed, the velocity portion of the message can be ignored, and I will want to ignore which channel data comes from. The remaining data was the note, and I decided to use the default whole-notes from my portable piano controller.
Working screen with good looking MIDI on the serial port

With the relevant data right where I wanted it and a stable connection, I added code to trigger relays from MIDI the same way it would be triggered from the switches. The function that controls the relays doesn't know the difference between a button press and a MIDI signal so they cannot conflict with each other.
(0:14) Playing MIDIGlocken Through 
MIDI Controller

The rest of the posts for this project have been arranged by date.
First time here?

Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6

Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com

This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.

All information in this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.

All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by  Brian McEvoy, cannot be used to claim property or assets.

Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.

This blog, including pictures and text, is copyright to Brian McEvoy.