September 16, 2011

Beepcat: A Modest Proposal...

by Chris Randall
 



I've spoken to some of you in person about this idea, and received generally good feedback, but we're getting to the point in this project where we need to start committing real resources, and I wanted to open it up to the wider community for discussion and to gauge interest before taking it to the next step.

The Elevator Pitch?: Beepcat is an open hardware and software shield for the Beagleboard Linux-based SBC. The board has a 128 x 64 graphic LCD, eight pushbutton/knob encoders, and eight buttons, and has stereo balanced audio I/O with a high-quality A/D/A convertor and MIDI I/O.

Some background information: after (and indeed during, to a certain extent) our ill-fated and somewhat expensive foray in to the Euro-Rack world, we were looking in to projects that didn't involve a fairly expensive infrastructure. After much consideration and discussion, we've hit upon this idea of a totally open and somewhat freeform platform called Beepcat.

The Beepcat could be purchased fully assembled, tested, loaded with software, in a nice case and ready to go. Or you could just buy the shield and an SD card containing the disk image from us and make your own case, or use our provided schematics and information from the Wiki and provided source code files to make your own or whatever. It would just plug right in to any existing Beagleboard; we have examined the idea of making a custom Beagleboard that doesn't have all their video and shitty audio and what-not (the Beepcat shield has its own audio codec, as the one on the Beagleboard is simply not suitable for pro audio) and this is something that we believe can occur.

The Beepcat software would consist of a custom Linux kernel that kicks a Beepcat Bootloader (BeepBoot) that allows you to choose one of the available programs on boot. The disk image we would provide as a stand-alone Beepcat environment would have programs that we made in-house (and which would necessarily not be open-source, for obvious reasons), along with a stereo effect framework with code and a monosynth with fully commented code to be used as starting points.

The shield itself would have, as I said, MIDI I/O and a much higher quality stereo balanced audio I/O rig, and the LCD display and controls, all of which are controlled by an ATmega; this wouldn't be written in Wiring, so you couldn't code for it just like for an Arduino, but it wouldn't be that dissimilar.

Coding for the Beepcat would not be that difficult. (With the caveat that "not that difficult" is a loaded statement when it comes to DSP.) With a full Beagleboard backplane, you can code directly in C++ or C on the Beagleboard itself, using the Geany IDE. That's how I wrote that synth above, right on the device. With the full monty provided, you could use the hardware plane for any number of things; it would make the Beagleboard in to a whole multi-media powerhouse.

So, in a nutshell, what Audio Damage would provide:

1. Two different packages to purchase (Full assembled tested ready to take on stage Beepcat, Shield + SD card only)

2. Beepcat Linux kernel and starter software as a downloadable image. This wouldn't include any of the AD-coded synths, but would enable you to use other people's Beepcat programs.

3. Full Wiki for coding for Beepcat, a repository for non-commercial programs, a method for selling commercial programs (e.g. if DMG Audio wanted to make and sell a high-quality compressor or EQ for Beepcat, we could handle the transaction.) The repository would also contain the Gerbers for the shield, a BOM, and firmware for the ATmega, should you want to just make your own from scratch.

Anyhow, that's the general idea. Eric and/or Adam will jump in and correct me if I make any technical mistakes, and can address any deep technical questions and comments. We are totally open to any and all ideas at this juncture. We're just getting to the prototype stage, and now's the time to open the floor for comments and to see what kind of interest there is in this concept. We've seen some rather spectacular failures of this idea (the Chameleon being the most notable example) but that was before the whole DIY / Maker scene really got traction, and I feel it's a different time. MeeBlip opened the door, and I think that we'd all benefit from something like this.

Comments? Criticisms?
 
 
 

110 comments:

Page 10 of 11
 
 

 
Sep.20.2011 @ 5:26 PM
Chris Randall
@moktor: No idea at this point. I will say that Eric is within spitting distance of a prototype. After that, we'll have a BOM and a general schematic, and can start thinking about production.

-CR
 
 

 
Sep.21.2011 @ 2:48 AM
atlastop
Woah! This looks like an awesome idea.... in fact, it now seems to be so obvious a concept, that I'm wondering why this hasn't been done successfully before.

The real kicker for me is AD plugins running on it. Then the DIY aspect would be worth it.

Of course if Valhalla DSP and DMGaudio also port code. Then this is Ye God's guitar pedal!

Actually... will it have Hi-Z imputs for guitar/bass?
 
 

 
Sep.21.2011 @ 11:29 AM
jip
Any plans for direct digital in and out?
 
 

 
Sep.21.2011 @ 12:25 PM
Chris Randall
@jip: No, that would be the same as using plug-ins. No fun there, added expense on the build, and not something most people would use in this context.

@moljen: We'll look in to adding a switch to knock the inputs to hi-Z, but right now I'll say "unlikely." There are, of course, about 10,000 solutions out there for bringing a guitar signal to line level and back, so it's not an insurmountable problem by any means, assuming (and it's a safe assumption) we _don't_ include this feature.

-CR
 
 

 
Sep.21.2011 @ 1:18 PM
jip
@CR: digital i/o's are just something that have been on my feature list lately. I have a pile of dig i/o's that could be utilized and I didn't see any particular mention of an analogue aspect that would be of particular sonic benefit aside from a software handler.
However I really appreciate "the same as using plug ins" aspect but why go through extra conversions if unnecessary? And I am certain to be corrected if wrong but is not this essentially an self contained vehicle for what amounts to a plug in?
Sounds like a real interesting product none the less and will be watching as it rolls out.
 
 

 
Sep.21.2011 @ 1:50 PM
Chris Randall
@jip: Not really. It's a self-contained vehicle in the same way a SuperNova or MachineDrum is. Not quite as sophisticated, of course, but this is primarily for performance use, either in the studio or on the stage. Having it set up as a plug-in, well, it runs at 48/24, which isn't a terribly common format. Imagine loading a track you're working on at 44.1, then plugging your new Beepcat in to your system, and watching in dismay as your DAW makes a feeble (and some would say quixotic) attempt to change the sample rate of the project.

Now imagine if that project has some hundred audio loops in it.

You'll see my point. This is not designed for that context. There are tools that work for that sort of thing (notably the MUSE Receptor).

-CR
 
 

 
Sep.21.2011 @ 1:54 PM
dingo
As someone who was trying to compile fluidsynth for the Chumby One because it looked cool plugged into the KORG nano line and used a nord micro modular as a volume pedal; I'm in.

Any thoughts on the power supply? Something easy replace minutes before stage time from a big box store in middle america or can just be plugged into mains in europe I hope.
 
 

 
Sep.21.2011 @ 5:25 PM
boobs
srsly.. drum synth + waveshaper/folder/multiplier/filter

srsly.. synth engine that tracks incoming audio synced to tempo with note quantization so beat in 16th notes can be tracked in whole (1/8,1/4, triplets etc) notes (with slew).. etc.. threshold setting/gate etc.. add waveshaper/folder/multiplier to that and you could feed this standalone box anything and have it track and viola. instant melodies/drones/beat accompanist for the tweaker.

can has instant fun box?
 
 

 
Sep.22.2011 @ 1:40 AM
mitchell
No one's with Boobs yet? You people are letting me down.
 
 

 
Sep.22.2011 @ 6:07 AM
renderful
I'm with boobs.
 
 

 
Page 10 of 11
 
 

Comment:

 

Sorry, commenting is closed for this blog entry.