ProffieOS v7.x feature requests

Would be neat if we can add in some sort of new font-config parameter to delay the blaster Block LED illumination by a configurable amount of time (milliseconds). So the blaster-block sound file plays when you hit your aux button…but the actual deflection illumination on the neopixel blade is delayed by xxx amount of time. I know CFX has this currently…and i find it to be a neat realistic feature.

Why make it timed? Seems antiquated - I have Interactive Blast already that will react to what you’re actually doing with your saber :wink:

With this new interactive, will the sound fonts need to be created so the blaster sound is its own wav file, and the deflection sound is its own wav file?

Edit: never mind, just re-read that it will be 2 separate sounds. This feature will be SWEET

Yes, the blaster firing is blast.wav (borrowed from blaster prop), deflection is current sound.

Isn’t that already how it works?

You can.
Just create a few super-styles using fett263s library, then use edit mode, the workbench or a text editor to create variations with different parameters. If you arrange your fonts carefully on the sd card, you can have thousands of fonts. (File read time becomes an issue if you don’t arrange the fonts carefully.)

1 Like

One suggestion is a saber reset for edit mode. Reset everything back to base level.

2 Likes

Honestly, just resetting all bladestyle to default (or maybe have it as a edit section root menu option).

1 Like

that’s already there, revert or the changing of the global.ini should do that. and I’m sure the Proffie Workbench has it as well.

You would just delete presets.ini, curstate.ini and/or global.ini from your SD to remove all respective edits.

1 Like

thats what I do now. its a touch annoying. but I am also getting better with using edit mode.

Then just re-upload the config, either removing the .ini files or uploading the config both revert the saber to it’s original state, not sure allocating more memory to “reinvent the wheel” is all that worthwhile.

That said, you can “Reset Colors” on a per preset basis in Color Editing menu and you can Delete Preset in the menu, those are the most common “revert” type uses. For everything else; fonts, tracks, controls, styles, etc. just using the menu to select what you originally had also works. The library also includes the original selections, etc in the copyright section so that you can always refer back, this is why it is recommended to keep this section intact in your config and keep a copy of your config available.

But for just a global “factory reset” removing the .ini files or uploading a new config is quickest and doesn’t use up valuable memory on the board.

Adding it to the workbench wouldn’t use up almost any space on the board.
For the most part it would just issue some “rm” commands and then reboot the board.
The only tricky part is to figure out which files to delete. With save directories there could be multiple sets of them.

1 Like

But isn’t the point of edit mode to maximise user control from the saber itself? Having some sort of fallback to defaults within the menu seems like sensible UX…?

You can already “revert” while in any specific editing mode or you can “re-edit” any changes you already saved back to what they were before or your can “delete” any preset you added, so it’s all already there to do, redo and undo any edits you’ve made.
We also have a “reset colors” to revert all colors in a preset back to the original upload. All of these cover the most common edits and undos users already had.
The question at hand was a single “factory reset”. I don’t know many devices that bundle editing and full factory reset together, usually a factory reset is separate and different from straight editing. In addition, I don’t believe many users need to do a “factory reset” often enough to warrant the additional memory we’d have to take up to do it.
Someone else is welcome to add it (the beauty of open source), but it’s already possible through existing menu items and/or SD/config uploads and if profezzorn adds to Workbench.

1 Like

Not sure if this is possible with the hardware and or software at the moment but a blade style that can react to a .wav file on the sd card (like a music track) to be used like a music visualiser (just as a meme :smile: )

Already possible, try something like:

InOutHelperX<Gradient<Red,Orange,Yellow,Green>, SmoothSoundLevel>

“Audio Level Bar Graph” and “VU Meter” are also available in the library under Crystal Chamber, Accent LED or Build a Sequence as custom ON or OFF styles.

I’m not sure if this is discussed but I did notice that 6.7 doesn’t allow you to edit the secondary colour so my Feature Request is an additional menu if there’s a secondary colour to be able to edit it.

ALT_COLOR_ARG is editable in the menu already, if the style uses it. OS7 will include 2 additional ALT_COLOR2_ARG and ALT_COLOR3_ARG.

2 Likes

disable all edit mode features in idle. Copy preset works in idle, and it shouldnt. I really hate global color change, the cc in edit mode is better, because you can specify which blade.

I think building some standard bladestyles with shortcut code could be good for beginners.

Really dont care for any new features, my proffies already do what I want them to do.