Programming question...

[Eco]

To all the programming savvy saber geeks out there, I have a question regarding a new soundboard design.

How difficult/practical would it be to develop a non-driver soundboard, that starts with the basic idle hum sound effect, then uses an accelerometer that increases the volume/pitch/tone/bass of the idle hum in a linear manner when you swing it?

EDIT::
I suppose I should also include that there is no *specific* sound effect for swings, just the variation of the basic idle hum. So the only sound effects on a given font would be: Ignition, idle/swing, clash, power down.

[Thaxos]

Hmm, interesting idea... Unfortunately I'm not electronic savvy enough to answer this one for you! Hopefully someone will though, I'll keep an eye on this.

[jtzako]

I've been thinking of making one myself but havent done all the research.

I dont think it would be that difficult really. In fact, there are some semi-premade ones out there that could play the sound (even several sounds) and you'd just have to program the accelerometer part and tell it what sound to play.

Unfortunately the pre-made ones I've found do not fit in a saber hilt so they couldnt be used for anything more than a basic template.

[Novastar]

How difficult/practical would it be to develop a non-driver soundboard, that starts with the basic idle hum sound effect, then uses an accelerometer that increases the volume/pitch/tone/bass of the idle hum in a linear manner when you swing it?

Unfortunately, it's not a very "linear" thing regarding:

* the way an accelerometer captures data
* the way you interpret that data and expect it to "translate" into what pitch shifts to apply to the base sound
* playing the sound BEFORE / AS / WITH the swing itself.

On that last point--what I'm saying is... you need a VERY FAST processor to playback sound "real time"... as in what would match the current motion you're making. Especially if you're planning on having a high "granularity" of how quickly the pitch can be changed... based on a minor, minor change or (obviously) a major change.

But fine, fine: ok, skip all that and say you detect motion... great. Now you need to interpret that data... select the sound to play... pitch shift the sound based on the data captured...

All the while, new motions are being detected and/or the motion is changing speed... direction... orientation.

SO... you have to (generally) COMPLETE a sense of motion BEFORE you play a sound with it. Think about this carefully. It's quite a catch-22. Well... without a pretty powerful chip in there. Which means expense goes up... and chip size might generally go up. Heat goes up too (in general). Complexity gets worse as well.

So if that all = "simple"... I say, great.

[Eco]

Hm... Sounds easy to me!

But seriously, what about using multiple accelerometers all set with a delay on collecting new data. You'd have to set a range of velocities that would still be counted as your baseline. Yes? No?

[jtzako]

You wouldnt want to use multiple.. just 1 accelerometer with 2 or 3 axis would be plenty. You would, of course, have to have some delay before sensing changes.

I suspect one could make a 'board' that works similar to the way the iphone lightsaber does. (that also uses an accelerometer) That one plays at least 3 different movement sounds (not counting clashes) based on how fast you move the phone. It detects a change in direction to start a new sound.

[Novastar]

You wouldnt want to use multiple.. just 1 accelerometer with 2 or 3 axis would be plenty. You would, of course, have to have some delay before sensing changes.

No. Not if you wanted to capture more data faster. I think Eco was suggesting multiple ACCs to get the same data from multiple sources. Still... this would be a bad idea:

* Faster processor would be a better answer
* More ACC = greater cost... and a lot more room used
* Granted... even a faster processor would be more $$$

So... this is just grasping for straws. Sorry.

I suspect one could make a 'board' that works similar to the way the iphone lightsaber does. (that also uses an accelerometer) That one plays at least 3 different movement sounds (not counting clashes) based on how fast you move the phone. It detects a change in direction to start a new sound.

The iPhone is pretty expensive, runs on an operating system, and also has a microprocessor that is at least (just guessing) 250x more powerful than the processor in CF. But I imagine it certainly could be done by someone. Always someone.

[jtzako]

Yeah, Iphone is expensive and has a faster processor, but the lightsaber app (the motion/sound portion) doesnt need much cpu. Based on some pre-made things I found I dont think this deal would be terribly hard to do with something like a Arduino. (assuming you know what parts you need and how to program it)