I don’t understand.
Isn’t that what idle.wav is supposed to do?
Wasn’t expecting it to start playing when plugging cable in, comes through all horrible and distorted sounds like it’s chewing up your speaker(even tho is isn’t) still makes you think that’s not right, but if thats what it suppose to do then fair enough
FWIW, that’s why I developed the “Toggle Idle / Off Sound Effect” Special Ability - it’s technically already in OS7.15 via my Early Access Library. It allows the user to toggle the idle sound on or off as needed instead of it just always running (it uses a different mechanism and sound than the OS8 version) - ProffieOS7 Style Library Phase 4 (Early Access) - Q & A - #60 by Fett263
1 Like
Using Proffie OS Beta8.4 and the Fett263 prop.
When adding
#define FETT263_SS_BUTTON_CLICKER
On Boot (after boot.wav plays):
Pressing Power:
I can hear both press.wav and release.wav and the saber turns on. Once on it remains on, even if I press power and hear press.wav and release.wav. Oddly, I believe that after many listens that release.wav is playing twice so that it sounds like a double click. No retraction or ability to turn off with the button, although twist off works fine.
Pressing Aux:
Very clear playback of press.wav and release.wav, but no function with short or long press (advancing through presets, etc). When ignited, getting playback of release.wav only and no press.wav. Button does not function regarding controls.
Everything functions normally when using the serial monitor commands.
When I remove this define and upload the config with 8.4, it functions normally (better than ever, really).
Happy to help test any updates or changes until it’s running 
, if and when you have time.
Thanks, I’ll take a look next week when I’m back from holiday.
1 Like
Great. Enjoy your travels!
You do know that you can apply battery power while the board is plugged in, right?
idle.wav plays when the saber is … idle. Plugging into power, the board boots and is idling because the blade is off.
I’ll make a PR to handle the preon stopping idle.
As far as fade in goes, @proffezorn could volume_overlay.h use something like
void StartAndFade() {
volume_.set(0);
volume_.set_target(kDefaultVolume);
}
?
Yes, if we want to fade things in, that is probably the way to go.
I’m thinking that we might want a bgnidle.wav…
That would be easier. The “work” is on the end user then to make a fade-in in the audio file.
Can’t think of another use for StartAndFade at the moment, but could be handy at some point I suppose.
Yea I’m aware of this now, I suppose mounting the sd to stop it ain’t that big of a deal, thing is when disconnect my board via the system try it reconnects pretty much strait away so when remove the wire it feels like I’m gonnabreak something cos it’s still playing sound, it’s not broke anything yet so…… might not be a problem,
This would be a good idea, it would be easy to work with, my work around for what I was using it for was too add a fade in of the idle sound to the end of the boot, font and pstoff sounds, it did the job but it’s a lot messing about
This doesn’t sound right. What do you mean?
Are you using #define MOUNT_SD_SETTING?
Is there a clamp on fade time? Based on sample rate?
I can’t seem to make any difference setting it to something like set_fade_time(3.0).
It still sounds like 1/3 of a second, which would make sense if it’s capped at .37 seconds.
Yh I’ve got that defined, it’s not the sd that reconnects it’s the board itself, when I click on the board to disconnect it in the system tray it disconnects then within a second
It reconnects and play boot and idle, it’s like the board never stays disconnected if that makes sense,
You don’t need to disconnect the board like that. Just pull the plug. You only need to gracefully eject the SD card when it’s mounted to the computer.
Just cutting power to the board is the same as pulling the battery out while it’s running. It’s fine.
Haha ok that’s good I don’t have to worry about it then 