What would you like on BT / CF V5

[erv]

checking the previous thread to extract important feature requests :

* Including a software volume control or setting (other than the vol POT itself)
* New architecture for v5... departing from the v2,3,4 a bit
* More boards available overall, more often (hopefully!).
* less parts, smaller board, easier to built (for me)
* Some different parts removed; another better one to replace them
* Overall cost NOT increased
* Increasing the current to 2000mA
* maximum backward capacilities
* enhanced sound quality + louder
* Allowing the flicker options to affect poweron and poweroff (power on flicker is already there). Options to enable or disable those fx
* probably a sound fx config file and a specific led config file, we'll see
* new audio engine (my problem) - more efficient
* wav support (works for a year when I initially planned V5 but... no time). Doesn't change anything from the reading of the sound files actually since WAV = 95% RAW
* more accent LEDs (multi purpose)
* option do get the accent LEDs go crazy during lockup => use an altleds.txt sequence just like on my chestbox controller or blaster core. If altleds.txt, lockup doesn't
affect accent led sequencing, hence no additionnal parameter is needed.
* improved safety for the board with optionnal settings depending if you target absolute newbie proof or extended performance
* more gesture recognition
* more sound slots. Maybe, like 4 power on sounds for instance.
* nova mute-on-da-go proposal to temporarly mute the saber instead of jumping in a muted sound font
* separate accelerometer with mini daughter board : NO
* separate SD card on mini daughter board : NO. (for both it's been proved you can fit CF in tiny spaces, you don't need that. Engineer a little bit your saber instead of asking CF to self adapt to any situation. It's already pretty "adaptable".
* enhanced clash flash WITH flickering and shimmering during clash / lockup with separate timings from the luxeon (ideal for creating even more chaotic fx and contre point)
* pre scan to find automatically how many files to use : probably not. I'm not convinced of that. Fixed sound fonts would be easier to handle for everyone.
* RGB *mixing*. NO. I'd need 3 current regulator that will NEVER FIT. You guys want rainbow sabers, cool. CF isn't just PWM dimming / chopping voltage to the led, it's a complete servoing system. The current RGB selection system will probably remain, maybe extended to 4 dices control so that the great ledengin leds could be used to their full potential. As for on board PE, no neither, there are probably like less than 1% of people wanting a color changing saber and I don't want to increase the size of the board for that. If you need the feature, you'll need to wire up external PEs somewhere in the hilt.
* 25V support : no. I tested many things and stepping down from high voltage to the core voltage of CF is an issue. It generate a lot of useless heat. I prefer to improve the current if can generate so that the 2 cell setup remains the best solution for everyone instead of wiring dices in serie. V5 will be compatible with at least 12 / 13V and won't feat a 3 cell setup anyway.
* more switch options. I got a request to add the ultrasound delayed power off to handle poor switches with a lot of bouncing. APOP handles that already and I'm not fully conviced but why not.
* ramp up fx timing : param to select if matching the power on sound duration, or custom duration. Extension of the "quick on" current param.
* same for the power off I suppose.
* a param to define if gesture recognition starts immediatly if ramp up time < poweron sound length
* separate gesture detection "rate & flow" from the visual fx. Right now, the clash rate is limited by the shimmer duration. It's convenient for user's BUT... to be accurate, shimmer clash is one thing, and clash gesture is something else. User might like a very speedy sequence of clashes even if the shimmer fx of each clash is interrupted. Another parameter like a the "swing" one that limits the swing rate (I'm sorry, my motion regognition algo is "too" fast ).
* multiple power on with saber orientation selection (3 sounds)
* multiple power off with saber movement/idle selection (2 sounds)
* Press & release aux = entering blaster mode. Further swings = more Blasters. Wait for the end of a blaster sound OR clash interrupt blaster mode

pretty good as a start, isn't it ? Many of those are in the burner for a year. But House Shot First

[Malaki Skywalker]

I think that covers just about everything *Mouth waters*

Only other thing I can think of is for Accent LED bar graphs getting the option to go crazy during a lock up sequence to represent the Saber is taking some serious stick

Cheers Erv'

[H@rrY89]

I've Discussed this idea with Malaki and It is a Feature that I would absolutley love to see in the next CF Version.

I was talking to my dad one day about how the lightsabers in star wars always seem to have different ignitions. We threw a few theories at each other and we came up with this:

The Theory we have is that when a Lightsaber is held at different angles it affects the ignition sound of the saber.

The way we came up with the theory is from Episode III. Anakin uses his saber throughout the move and the ignition sounds are relitivley the same. Then he goes to Jedi Temple to kill off the remining Jedi and his saber has a Sith like Ignition. Now most people would claim it's to add to the tension of the scene which it does very well, but what if it were the lightsaber itself that causes the sound.

So My Idea is called Angular Ignition.

When the saber is in idle mode the accel is still on, instead of one "saberoff" setting you have maybe 2 or 3 instead that corrorspond with some angles. How many angles is up to Erv of course but lets say he uses three angles:

90 Degree

180 Degree

-90 Degree

Here is how the ignition works:

90 Degree = saberon1

180 Degree = saberon2

-90 Degree = saberon3

Anything in between you can still have a basic ignition e.g. saberon.

Anywho, thats just my idea. Hope you Like it Erv. It would be an honor to see this feature on CF v5

[Novastar]

...The Theory we have is that when a Lightsaber is held at different angles it affects the ignition sound of the saber. So My Idea is called "Angular Ignition".

...90 Degree = saberon1, 180 Degree = saberon2, -90 Degree = saberon3

Anything in between you can still have a basic ignition e.g. saberon.

Anywho, thats just my idea. Hope you Like it Erv. It would be an honor to see this feature on CF v5

BRILLIANT IDEA, HARRY!!! THAT ONE IS ONE IN A MILLION!!! That would really make great use of the "random" sounds being more oriented to the motion detection... good job!

[erv]

seconded. I love it. The angular measurement is already used for pitch shifting and that's a great selection technique for an ignition sound. I'll add it to the list of features. Plus it's easy to make.
thanks for that brillant contribution. Let me reformulate it by inverting the angular mapping to the file # and let me call dibs on that reverse angular power on selection or RAPOS. You'll get a free cardboard CF for your idea

more seriously. I love it (bis, adlib).

As for the motor pad, it will require a power xtender and a resistor, or I'll need to provide a specific motor. That's not as generic as expected. But at least the control pad could be here. The motor.txt isn't a bad idea per say. However, you need to consider :
- vibrating motors have a slow startup, and for a reaction to a clash, you'll never really feel their vibration, most of the sensation being visual and the physical smack of the blade.
- I do like the possibility to define how the motor should pulse
- however (again) so far a pulsing vibration is possible with wiring the motor as a mirror of the luxeon

I'm not sending the idea to the trash, I'm trying to see how current setup could be adapted and I don't want to add too much pads or dedicated things.

stereo / sound mixing. I already designed something but it adds more parts and doesn't increase the ease of use. It then adds even more complexity to the dynamic mixing level of the sound fonts. Add a fader on the hum over fx, people will ask for faders on individual fx, I see it coming. We end with audio enginneer skills to make sound fonts, plus it depends so much on the speaker and setup.

I'm honnestly still very happy of the premixed sound font, the way I initially implemented it back in 2005. That's with some true audio experience and background that I found how to properly play the files with the illusion the module is polyphonic. Some people still think that it's difficult to make a soundfont because it's about the RAW. Nope, it's about general understanding of digital audio, spectrum and DSP. And having some hear of course.
I've heard other things like "I'm working on that font with protools". LOL, same idea as saying you using a CNC so you'll end with a brillant result. Unfortunatly no. I could have an Ibanez JS sig edition, I'll still be playing satriani's music like a *smelly brown material*. And give JS an aria pro II and he'll make you cry.
Using big words like CNC, CAD program, 3D, RPM (rapid prototyping machines), or ProTools will not create your skills from nothing. Novastar is using movie smucker and goldwave, just like I do. I use SoundForge too cause it can do batch processing & conversion, it's just about "faster", not "better".

saber building hobby requires, as I've said many times, a lot of cummulated layers of skills. You feel lost about wiring a CF, make soundfonts, choose the right optics and blades, luxeon binning ? that's normal.

[DJMoonbass]

I've heard other things like "I'm working on that font with protools". LOL, same idea as saying you using a CNC so you'll end with a brillant result. Unfortunatly no. I could have an Ibanez JS sig edition, I'll still be playing satriani's music like a *smelly brown material*. And give JS an aria pro II and he'll make you cry.
Using big words like CNC, CAD program, 3D, RPM (rapid prototyping machines), or ProTools will not create your skills from nothing. Novastar is using movie smucker and goldwave, just like I do. I use SoundForge too cause it can do batch processing & conversion, it's just about "faster", not "better".

saber building hobby requires, as I've said many times, a lot of cummulated layers of skills. You feel lost about wiring a CF, make soundfonts, choose the right optics and blades, luxeon binning ? that's normal.

oh i can do it, did i say it would be easy? NO i did not. but i work in the midi lab and recording studio at my college all the time, pretty much everyday. protools is one of multiple programs i like to work with, protools is my personal favorite because it is user friendly. will i fail the first time? absolutley... will i give up? no i wont. why? because i know i can make it. i dont deny that i have a ton of things to learn about audio. yes i have a TON. my knowledge is noob compared to nova. But i have people that can help me with the proper settings to make it work. you dont need to doubt my skill when you dont even know what skills i do and dont have. and to put it in text i will probably never be as good as nova but all the same i do look up to him as an inspirational person in the audio world, im not mad or anything i just want to make things clear. and i never said it was a font. just an activation sound. fonts are, im sure, more complicated.

that was long

as for the CF v5. im not making any suggestions because i know nothing of the CF but i have to say that h@rrys idea was brilliant. way to go. and erv this board is going to be awesome. once again you amaze me.

[Onli-Won Kanomi]

Sounds great...especially if "smaller board" means narrower rather than shorter...12-13V YAY!...and best of all: "More boards available overall, more often (hopefully!)"

[erv]

Only other thing I can think of is for Accent LED bar graphs getting the option to go crazy during a lock up sequence to represent the Saber is taking some serious stick

solution added in the first post. Use of an altleds.txt file like on blaster core or chestbox core.

I've edited the first post to add some contribution.

[Novastar]

Additionally (not to be overkill, but)...

with the "blaster" sounds, we all have MANY choices these sounds could be for. That is... they are not limited to "blaster only" sounds.

Pressing the aux button could trigger "lightning"... or "choking"... or anything you dream up! Just depends on the imagination. Remember CF is *FULL* of possibilities.

Additionally, I've taken the "liberty"(?) of making some of the blaster sounds on the CDs... umm... how do I say this--more robust. That is--sometimes triggering a blaster sound will trigger "more than one" sound...

Such as the "Episode IV" (both versions, both CDs) sound of Luke on the Millenium Falcon blocking three shots from that little round floating sphere thing.

In this way, you can have a sequence of effects chained together, and mimic the goofy motions you want (of blocking, or whatever).

The moral is: each "blaster" sound:

* Can be any length
* Can be any sound
* Is open to your imagination

Much like the force and force2 sounds. They are not limited to being "all about" a particular sound. They can be ANYTHING. Anything you like.

[erv]

indeed,

anatim for instance dupplicate the force sounds to all blasters too so that he can trigger force with the aux button. Sound slots can be affected to anything, it's just *your* context.