September 5, 2016
After trying the BeatBuddy MIDI Volume Control for a while I found that the pedal was far too sensitive, so much so that sometimes just taking my foot off the pedal would change the volume from where I had set it. In the original software I could adjust the volume from 0 to 100% using the foot pedal but I really never needed to go much below 65 to 70% so most of the pedal travel was never used.
So I’ve changed it now so that the full range of motion on the foot pedal will now only affect a much smaller volume range (which is configurable). This makes the foot pedal much less sensitive and much easier to use at the expense of not being able to completely silence the BeatBuddy (although I can still configure the BBMVC to let me do that if I wanted but then I’m back to the sensitivity issue).
August 30, 2016
This is the little project that I have been working on. I call it the BeatBuddy MIDI Volume Control or BBMVC.
August 28, 2016
Turned out a message buffer area in some of the debugging code associated with handling the midi input was not large enough which was obviously causing a storage overlay! Quick change and it all works just fine now. I wouldn’t mind but that code won’t even be in the final ‘production’ version of the code so the problem would never occur.
August 28, 2016
Did a little test this morning and I am beginning to suspect a software problem. The enable/disable switch for the volume pedal only stops working after the unit receives midi commands from the other unit it is plugged into.
So all is not lost yet!
August 27, 2016
I have to declare my latest project a failure. It works fine on it’s own and hooked up to the computer but once I put it on the pedal board and hooked it up to all the other gear, it was just to flaky. The switch (which enables the volume pedal) would simply stop responding which means I cannot actually use the box to do anything.
Oh, what was this thing you ask? A volume control pedal for my Beat Buddy drum pedal that used midi to control the volume.
Like I say, on its own it is fine but I guess all the other signals and electrical noise going through it just cause it to die/stop responding in various ways.
I am still running the development code tough and I know that’s not going to be as fast as the live code because of all the debugging messages in it but even so, it should not be as flaky as it is. No way I can use it live for now.
Oh well, it was a fun little exercise and I learned a lot too.
August 26, 2016
Did a quick test this morning using just a gender changer coupler between the midi source and the new box and it works fine so it’s obviously the length of the midi cable that is causing the problem. I can only assume that the Arduino is not capable or driving the signal over a long midi cable. While I think everything will work for now I may have to look into some sort of signal driver circuitry for future Arduino based midi projects.
August 25, 2016
Well it works, just not when hooked up to the MIDI controller on the pedal board that it will eventually be hooked up to. Now this might be because I am using really long MIDI cables since my little gadget has to sit near my computer since I am using the USB to power it plus also to receive the debugging messages I have built into the code, while my pedal board is on the other side of the room.
So as a little test I hooked up my iRig midi interface to my iPad and used Midi Wrench to send it some midi commands and it worked just fine. I could see the debugging messages in the Arduino Serial Monitor. I even hooked up the output midi from my gadget back to the input midi on the iRig and could see the commands getting passed through the device and returned to the iPad where I could see them in Midi Wrench.
So, I am hoping it’s just a matter of using short cables. Since the new box will live right next to the existing box on the pedal board that should not be a problem. It could well be because the Arduino just cannot drive the output midi hard enough to go over a long cable. I could always beef up the output circuits in the other box but if it works with a short cable (pleas god make it work with a short cable!) I’ll leave that for a future revision (I.E. Never!).
Anyway, just for fun and to relieve the boredom, here’s a couple of pictures:
First up is the iRig test setup (sitting on top of my shredder):
And next, inside my magic box:
I always think it’s a shame that people (I.E ME!) put so much effort into building things like this and then have to go and hide it all inside some nondescript project box. For me, after getting the bloody thing working properly, what’s inside the box is the best part!
August 25, 2016
I added the missing resistor and also found that I had the wires from the midi in socket reversed (probably not good!). Also checked the continuity of all the other connections involved in the midi in but still no joy.
What is annoying is that this same circuit works just fine in my other project. The only difference is , is that I had to directly solder the opto coupler chip to the board this time due to the height limitations of the project box which I hate to do, much better to use a socket. Oh well, next step is to get the old silly scope out and start looking at signals!
If that does not help then I guess I need to redo the interface board and perhaps use a socket this time. I did figure out that I could put the socket and opto coupler on the underside of the board instead of the top. It’ll still work just fine, I’ll just have to think ‘backwards’ or upside down or maybe end both, when wiring it up!
August 24, 2016
My latest little electronics music project is ‘almost done’. Got most of the bugs worked out of the software (hopefully all of them LOL) but I did find the MIDI input is not working which sorta sucks as I need that! Anyway, did a little bit of digging on the ol’ t’internet and I think I just forgot a resistor on one of the lines to the opto coupler (oops) in my circuit diagram so hopefully an easy fix tomorrow.
August 22, 2016
In the middle of my current little electronics project, I came up with an idea for an other ‘quicky’ project so my efforts are taking a small detour as I put together this new idea. In the middle of that I came up with an idea for yet ANOTHER project but I suspect that will be more involved so it’s going to sit on the back burner until I get the first one (and this little detour) out of the way.
I need more time (or fewer ideas!).
August 9, 2016
You sit down to write some code and find that you did it a couple of weeks ago. That change log in my code finally came in useful!
July 31, 2016
While I was working on the MIDI input code I decided to add a couple of ‘status lights’ to the display to indicate MIDI activity on the two inputs. It was as much about just seeing how well it would work as being anything useful since I know the hardware works already.
Anyway, here’s what I have so far:
Notice the cool vertical captions on the screen as well. Extra effort just to do that. Does it make any difference? Probably not but it was a bit of fun just doing it and who knows, it might come in useful sometime.
July 28, 2016
Whoo Hoo! Did a quick test, just reading MIDI notes in on either input and echoing them to the MIDI out and it worked just fine.
Now the serious coding begins!
July 26, 2016
I would not want to minimize or make light of the threat that this group makes to the world but I have noticed a trend recently in the news that IS seems to claim responsibility for almost every ‘terror’ event in the world.
I am sure that pretty soon we will see a headline along the lines of “Five Year old stubs toe. IS claims responsibility”
July 24, 2016
This is the completed Arduino Due MIDI Shield:
It doesn’t look pretty but it is a prototype after all.
It sits between the Arduino MPU board and the LCD Interface board so I inserted it into the Arduino stack in the appropriate place:
Then hooked the power to see if it still worked….
So far it look OK as in everything that used to work (the LCD, the touch screen and SD card) still works so at least I have not broken anything. Of course I’ve not tested the actual MIDI shield yet but I figure that’s enough for one day.
July 21, 2016
After a LOT of research and trial and error I finally found an Arduino Due prototype shield by nkcelectronics that has the Ardiono pins broken out AND a good mix of pin spots and strips that I can use to build up a prototype MIDI interface board. It’s actually for an Arduino MEGA but the pin placement is the same for the important pins like power etc and all the rest are just i/o anyway so it works just fine with the Due.
One problem is that MIDI typically runs at 5v while the Arduino Due runs at 3.3v so unlike my earlier Arduino (UNO) MIDI projects that could just hook up directly to the Arduino Uno, this one requires voltage level shifting circuits as well.
This is my circuit for the MIDI in and out:
This is the prototype board with the sockets, connectors and the TXB0104 board (Adafruit) in place:
I added a small piece of Veroboard to the prototype board so that I could solder some of the components to it as the prototype board just has a lot of those through hole connections and strips make it so much easier to hook things up, even if I do have to solder to the top of board.
July 7, 2016
Take the guns off the cops until they’ve had far more training than they apparently get now!
June 15, 2016
Not much but it is progress….
I got a couple of buttons to appear on the screen and when you touch them it correctly registers the button that’s been touched and, for now anyway, just displays the button name on the screen.
The bolts on the right end of the LCD board are just to help support it at that end as it only has a connector on the left end so if bends badly in the connector when pressed without some sort of support.
I’m already at 12% of the available programming memory (around half a megabyte)!
Next step, add code to read the SD card. The Next/Prev buttons will let me scroll through the files on the SD card. Well, that’s the idea anyway.
June 14, 2016
The bad news is that the Arduino library code that I am using for my latest project takes up so much space for variables that there’s bugger all left for my own data when I use the Uno. The good news is that the LCD screen I got for the Due has a touch interface so I don’t need to build a button shield for it, I can just use virtual buttons on the LCD for now. Eventually I’ll need ‘real’ switches but that’s a long way off.