Feature Update

OK, so just a quick update on the current controller/interface and implemented features. Basically the system has 4 'pages', page one is for note entry, page two is for note tweaking, page three is a mixer, and page four is for changing the live playing pattern for any track from one place. Here is what we have done so far -

BTW, I'm using Google Docs for this kind of stuff, to-do lists etc.

See it, hear it

Right, well I've delayed long enough, and I am always guilty with these projects of not actually sharing what things sound like. So, here is a quick lo-res video of the thing in action at this point in time.

...and a pic of the lot to muse over and try to guess what's going on in the UI...

Filters and keypads

Right, well the "FX" chain of the Acid line is going to pass through distortion and a filter. Finding small/cheap things to cram into a box at some point is difficult and a little expensive. However, in terms of keeping everything as components to break out for future projects, and for other use, I finally had an excuse to buy a Monotron.

I want the MS-20 filter for this project, and it has audio in to do that, but having just had a noodle around with this it's a cool piece of kit in it's own right. Plus it's small, light, and battery powered. Need to test it properly but here it is fresh out the box.

In terms of controls, firmly set in the idea of a numeric keypad now, but I had some headaches with the first one (a little bit self induced) but anyway I've gone in for a slightly odd pad found on Amazon that has no numlock but instead has a tab button. I can easily map all of these in Python using curses and it's leading me down a minimal design for data entry and UI navigation.

I've made a sheet in Google docs to start to map out the functions, here's the template, waiting for the post to turn up and to actually try the pad, hope it works with Linux.

On the case...

Ok, so while I want to get everything contained in one box at the end, I'd like to keep the main parts as self contained components, within reason; so I picked up a wonderful extension to the Pibow case on eBay which gives extra protection to the LCD and seals the Pi and LCD together nicely.

I also ordered a case for the MakeyMakey, long overdue as I was always very careful handling the board directly, but now I can use it and not worry too much about damage.

This clear case also leaves all the various points exposed. Ironically I may not be using the MakeyMakey in this project (it has many other uses so it isn't a waste), I'm starting to favor a USB numeric keypad to get around the whole pain and size of housing cables and switches everywhere, as fun as that's been, it's getting in the way now.

It's alive!

Well, first prototype is complete. Below is the rather larger than planned controller, the Pi with LCD running the software, and a speaker, all connected up and running together for the first time.

Close up of the software, plenty of refinement to be done, but the basic UI does it's job, shown here the top row is the current track and you can see a bunch of notes in there. The line underneath is a summary of track, buffer, octave and a few other things, really just a debug output for now but you get the idea.

Ah the delivery box turned controller in all it's hacked-together glory. Well, this taught me roughly what controls I need, how they might hang together, that push-to-make works fine with makeymakey and a bunch of other things about crimping and cables. I'm not sure I'm going to progress with these chunky buttons for the next revision.

Switches and wires

Well, some bits arrived in the post - wires and switches. This is basically everything I need, I think, to take human input and map that via MakeyMakey to functions in Acid-Py on the, erm, Pi.

I quickly hooked at some of the 'push to make' switches to MakeyMakey, using the clips. Once I have a prototype I need to worry about soldering but for now I need to be able to connect/move things about freely.

So with the basics proved, I've updated the software on-board MakeyMakey to map every available input (18 in total, afaik) to the keys I've laid out in a spreadsheet which shows what they are going to do in the software that will be running on the Raspberry Pi.

I tested each input quickly on the PC, so far so good. I didn't test every switch though, yet! The process of having the PC correctly recognize the MakeyMakey, get the Arduino software working, then patch/upload updated software was a little interesting; something for a dedicated post sometime.

Anyway, hope you enjoy the pics!

Building a mini sequencer/groovebox

Long time no post. So, I got a Raspberry Pi --- the first thing I did? Get some emulators running to play some old games, cool! But, next thing, of course I need to make it play some beats. So, "project with no name" was conceived, the goal - to build a basic sequencer with the Pi.

I decided to use Python, never used it before so a chance to learn, and I needed to know if it could keep in time, before going lower level. Turns out the PyGame timer is accurate enough for me, so far, and I got it playing a 4/4 kick drum easily enough.

Then I figured I would like to run with a custom display, no screen to cart about, so I got hold of a 16x2 LCD with basic controls, from the helpful guys at Proto-PIC. In not alot of time at all I had a basic drum machine, using the built in controls on the LCD board to navigate and insert/delete kick notes along a 16 step timeline.

Being a fan of the TB-303 and 909 acid combo and having some great sample packs of individual hits, I decided the project would be based around those samples. The 16x2 LCD drove the decision to have 16 steps, and I've decided on 4 tracks, 1 = kicks, 2 = snare/clap, 3 = hats/cymbals, 4 = acid.

But, the clicky cursors on the LCD board while neat, and possibly useful for a future project, made entering notes a bit of a chore and so I expanded the project to include a custom panel using my makeymakey. This can have up to 18 inputs, so my restrictions (which help me creatively, to actually get stuff done) are set.

"Insert project name here"

• 4 track, 16 step, acid/303/909 sample sequencer.
• Software written in Python running on Raspbian.
• 16x2 LCD display.
• 18 key inputs (12 will be each note of an octave, leaving 6 to play with for functions)

I have a couple of other ways to extend that with FX but for now I need a prototype before getting too carried away. Ordered about 20 switches and 40 cables online, on their way here now. Meanwhile, back to the software...