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