ilovefuzz.com

I've got a few ideas of bad things to do to incoming audio signals, which means that I'm looking for some sort of programmable effect pedal (ideally in C++, though other languages would be ok as long as they're not too obtuse) that has enough available memory to store loads of data while the thing is running.

Something with at least 2 in and outs (freely assignable from the code) and enough real-time controls/CV inputs.

The Owl seemed almost perfect but it only has 192kb of RAM, which is the equivalent of about 2 seconds of 16bits/44khz mono audio, i.e. not a lot.

Is there anything else available ?
Kickstarters, commercial stuff, etc. ?

While I can probably code what I want without any problems, I'm really not an electronics guy so making my own circuit would be far out of my comfort zone.

Rasberry Pi maybe with an AD shield (or whatever they call them in that world),
maybe that Arduino thing by Snazzy (I think you can store stuff on an ipod and update it)
Midibox interface would probably work well for something similar (cept you gotta burn eproms at least used to and building)... http://www.ucapps.de

The best solution might be to just get a little computer (rasberry pi) or something and just use that with an interface. Or code something for an android based device (just easier to free from the dumb store restrictions of apple from what I remember).

Honestly don't really know.

Well, I have a Raspberry Pi that I never put into use (was going to use it to run old videogame emulators). If you want it I can give it to you for a good price. It's just collecting dust as of now. PM me.

I remember when the Owl was still a kickstarter thing, I mentioned to them that 192kb wasn't all that much for anything but short-ish delay, when we're talking about delays and loopers in general, and asked about the possibility of adding cheap serial RAM to their design. If you can design what they designed, adding a bit of external RAM is a piece of cake.

Can't remember if they replied or not.

Turns out that I'm bad at reading specs . Which mention 1MB of SRAM too.

I sent a mail to the Owl people, who answered super fast and it turns out that the 192 Kb is for the code basically, and the 1MB is for audio buffers/other data. It's 5.6 seconds of stereo 16bits/48KHz, I think. So a bit more than 10 seconds mono, which suits me fine.

More would be great (RAM is cheap these days) but 10 seconds of audio buffer starts being reasonable. So I might start looking for one of these things .

And the Raspberry Pi can very likely do much more but the appeal for me would be something already fully integrated with knobs, audio in/outs, etc. I don't have the skills/free time to make a viable effect from a Raspberry Pi, I think. But if I only have to do code, no problems .

if you can downsample / bit reduce the audio on the OWL and enjoy some lofi-ness to your sound, u could get a lot more time out of that 1mb of SRAM.