All gesture ignitions have a delay for repeat events to prevent ignition-retraction-ignition in quick succession which would occasionally create odd behavior on the saber but those have been there since OS5. Expected use is turn saber on do some stuff turn saber off, turning it on then off then on in really quick succession isn’t really how you’d use the saber. After turning off there is a 2 second delay before the gesture can ignite again. But those delays have been there since the previous OS in my prop.
1 Like
You can remove the delay in your version, it is there to prevent odd behavior when you try to reignite before the off functions are allowed to complete using gestures. There were also instances of users doing too many gestures in quick succession so there are delays on repeat gestures to prevent, bt none of this has changed since OS5.
1 Like
@MegtoothSith @astromech or others.
I have put together a test version with the Gesture “Spamming” delays removed but we’ll need it beat up pretty good before considering. This removes the 2 second delay on gesture events that were there to prevent users from “spamming” gestures or from doing the movement accidentally in quick succession (particularly twists).
Unfortunately, with the holiday this week my time and access to my saber and computer for testing is going to be very limited so I’d like to get several testers to beat it up. This is applicable to the following, so we need to make sure that if you “spam” these events we don’t get issues or odd behavior, like the saber not turning off or sounds getting stuck or preon/ignition/retraction not working as expected:
- Twist On / Off
- Thrust On
- Stab On
- Multi-Phase (needs define enabled)
- Gesture Sleep
This is only a test version so you’ll have to pull from my fork, I don’t want to submit to main until it’s thoroughly proven out.
1 Like
Fernando, you didnt need to do that. If spamming prevention delay was put there because of issues, it might need to stay there. Now that I know there is a delay, I can account for it. But Ill test what you wrote. Ill also go grab the fixed female menu voice files from nosloppy. You have already busted behind on this prop file. I dont want to mess it up.
It’s worth testing, if we can remove then I will, if not then I just won’t submit the change. During OS5 testing users were getting odd behavior when spamming so the delays were added but with the changes profezzorn made to the OS they may not be needed anymore. Only testing will prove/disprove.
2 Likes
Ok. I will test and spam it. That is what I get for not being involved enough in OS5 testing. Was out of the loop. Glad Im testing in OS6. There is so much to learn. The saber has so much it can do now, its a bit intimidating. I haven’t even touched choreography yet. Everything is simple, and intuitive, but there is a lot thats new here. Color Change and Save State were game changers for installers. Edit Mode is a game changer for users, and definitely puts Proffieboard apart from anything else I have seen. PS, I haven’t generated any hum glitches yet, but if I do, I’ll create a new thread.
2 Likes
aaah, this might be why I’m seeing the same thing, I’m doing everything in quick succession.
I’ll wait for the next update of the proffieOS-master on github. I’ll post a new thread for it if I can reproduce it. thanks @profezzorn
Tried to test OLED bullet count on my DL-44 proffie blaster. Two problems arose before I could. Using a blaster_v3 config file that I’ve used successfully previously - 1. My trigger and mode buttons became reversed. 2. The OLED display became corrupted. Serial monitor says “wrong size image” and then lists the size of the file 64x6400.
Using the latest download of v6. 0
Using the same config file with 5.9 gives a different result?
Can I see the file?
I was doing some testing with your font, and I found a fixed a problem where the saber won’t turn on properly if you switch to the next font while preon is playing. (The saber gets stuck in a not-quite-on mode, which can be fixed by turning it off, then on again.)
I’m not sure about the hum-staying-on problem though, but maybe you can try the latest github master and see if it fixes any of the problems you’re experiencing?
1 Like
I’ll give that a go.
I was testing the fix you did and was able to reproduce the issue.
the font name is bank03. I was able to reproduce the issue. to turn off the saber I pressed the off button and then changed the preset.
20:47:44.786 -> Welcome to ProffieOS, type 'help' for more info.
20:47:44.877 -> Booster off.
20:48:00.166 -> Battery voltage: 2.84
20:48:20.142 -> Battery voltage: 2.84
20:48:22.001 -> unit = 0 vol = 0.00, Playing Ixam_Letsi/hum01.wav
20:48:22.001 -> channels: 1 rate: 44100 bits: 16
20:48:22.001 -> unit = 1 vol = 0.50, Playing Ixam_Letsi/out/out03.wav
20:48:22.001 -> channels: 1 rate: 44100 bits: 16
20:48:22.001 -> humstart: 1800
20:48:22.001 -> unit = 4 vol = 0.00, Playing Ixam_Letsi/swingl/swingl07.wav
20:48:22.001 -> channels: 1 rate: 44100 bits: 16
20:48:22.001 -> unit = 3 vol = 0.00, Playing Ixam_Letsi/swingh/swingh07.wav
20:48:22.001 -> channels: 1 rate: 44100 bits: 16
20:48:25.487 -> Playing Ixam_Letsi/in/in01.wav
20:48:25.487 -> channels: 1 rate: 44100 bits: 16
20:48:25.520 -> Style RAM = 1032
20:48:25.720 -> Playing Bank03/font01.wav
20:48:25.720 -> channels: 1 rate: 44100 bits: 16
20:48:25.720 -> Audio underflows: 14
20:48:25.720 -> unit = 1 vol = 0.00, Playing Bank03/hum01.wav
20:48:25.753 -> channels: 1 rate: 44100 bits: 16
20:48:25.753 -> unit = 2 vol = 0.50, Playing Bank03/out/out02.wav
20:48:25.753 -> channels: 1 rate: 44100 bits: 16
20:48:25.753 -> humstart: 1800
20:48:25.753 -> unit = 3 vol = 0.00, Playing Bank03/swingl/swingl03.wav
20:48:25.753 -> channels: 1 rate: 44100 bits: 16
20:48:25.753 -> unit = 4 vol = 0.00, Playing Bank03/swingh/swingh03.wav
20:48:25.753 -> channels: 1 rate: 44100 bits: 16
20:48:27.613 -> Playing Bank03/swingh/swingh03.wav
20:48:27.613 -> channels: 1 rate: 44100 bits: 16
20:48:28.244 -> Playing Bank03/swingl/swingl03.wav
20:48:28.244 -> channels: 1 rate: 44100 bits: 16
20:48:36.377 -> Playing Bank03/swingh/swingh03.wav
20:48:36.377 -> channels: 1 rate: 44100 bits: 16
20:48:37.372 -> Playing Bank03/swingl/swingl03.wav
20:48:37.372 -> channels: 1 rate: 44100 bits: 16
20:48:39.232 -> Playing Bank03/hum01.wav
20:48:39.232 -> channels: 1 rate: 44100 bits: 16
20:48:40.162 -> Battery voltage: 2.78
20:48:44.978 -> Playing Bank03/in01.wav
20:48:44.978 -> channels: 1 rate: 44100 bits: 16
20:48:46.007 -> EVENT: Stab millis=245889
20:48:46.007 -> Ignition.
20:48:46.007 -> unit = 1 vol = 0.00, Playing Bank03/hum01.wav
20:48:46.007 -> channels: 1 rate: 44100 bits: 16
20:48:46.007 -> unit = 2 vol = 0.50, Playing Bank03/out/out01.wav
20:48:46.007 -> channels: 1 rate: 44100 bits: 16
20:48:46.007 -> humstart: 1800
20:48:46.007 -> unit = 4 vol = 0.00, Playing Bank03/swingl/swingl04.wav
20:48:46.007 -> channels: 1 rate: 44100 bits: 16
20:48:46.007 -> unit = 3 vol = 0.00, Playing Bank03/swingh/swingh04.wav
20:48:46.007 -> channels: 1 rate: 44100 bits: 16
20:48:46.259 -> No sounds found: pstoff
20:48:46.505 -> Playing Bank03/swingh/swingh04.wav
20:48:46.505 -> channels: 1 rate: 44100 bits: 16
20:48:49.859 -> Playing Bank03/swingl/swingl04.wav
20:48:49.859 -> channels: 1 rate: 44100 bits: 16
20:48:52.251 -> Playing Bank03/in01.wav
20:48:52.251 -> channels: 1 rate: 44100 bits: 16
20:48:52.251 -> Style RAM = 1368
20:48:52.550 -> Playing Ixam_Letsi/font.wav
20:48:52.550 -> channels: 1 rate: 44100 bits: 16
20:48:52.550 -> Audio underflows: 14
20:48:52.550 -> unit = 1 vol = 0.00, Playing Ixam_Letsi/hum01.wav
20:48:52.550 -> channels: 1 rate: 44100 bits: 16
20:48:52.550 -> unit = 2 vol = 0.50, Playing Ixam_Letsi/out/out06.wav
20:48:52.550 -> channels: 1 rate: 44100 bits: 16
20:48:52.550 -> humstart: 1800
20:48:52.550 -> unit = 3 vol = 0.00, Playing Ixam_Letsi/swingl/swingl08.wav
20:48:52.550 -> channels: 1 rate: 44100 bits: 16
20:48:52.550 -> unit = 4 vol = 0.00, Playing Ixam_Letsi/swingh/swingh08.wav
20:48:52.583 -> channels: 1 rate: 44100 bits: 16
20:48:55.904 -> Playing Ixam_Letsi/in/in04.wav
20:48:55.904 -> channels: 1 rate: 44100 bits: 16
20:48:56.469 -> No sounds found: pstoff
20:48:56.535 -> Amplifier off.
20:48:57.498 -> Unmounting SD Card.
20:49:00.153 -> Battery voltage: 2.80
I’ve been testing these updates on a 1-button saber.
-
Track Player - This is working exactly as expected
-
Fix Scroll Preset Increment - Fixed
-
Added Swing Option - Fixed
-
Release wav_player - I’m not sure what this is
-
Prevent Hold Button or Long Click Button in Color Editing or Blade Length Editing - Fixed. For one-button, when in blade length editor, both a long click and/or hold “revert” the changes. In color list, a long click and/or short click “save” changes while a hold “reverts” changes. Is this expected? In the other menus, a long click and/or hold “revert/cancel”
-
Color Zoom for Color List - On-the-fly color change is working great for Edit-Mode styles (I don’t have any other style loaded currently). The color zoom worked in color list (both on-the-fly and in edit mode) and adjust color hue, but there is no audio “zoom in” sound for any of those.
-
All of the one-button controls are working as expected. The demo edit mode styles don’t have POWERSAVE, so I haven’t confirmed that 100% yet. Rehersal/Choreography mode work mostly as expected with a few exceptions.
Rehersal: cancel rehearsal mode is supposed to be Triple Click and Hold PWR, this just enters battle mode but doesn’t end rehearsal
Choreography: end choreography is Hold PWR–this does work, but it doesn’t play the end choreography audio. Also (this may be expected) the end choreography audio overlaps with the final clash or lockup. -
HOLD_BUTTON_LOCKUP - I haven’t tested this define
-
FETT263_DUAL_MODE_SOUND - Fixed
-
On-the-Fly Copy Preset - Works great
Thanks, appreciate it.
-
this would only show up in Serial Monitor, it’s more of a background fix to release the prompt wav_player so it’s available for other effects when not needed.
-
I believe for Color List you mean the “on-the-fly” version for ColorChange as opposed to the Color Editing version in Edit Mode. Yes, we have to Save the “on-the-fly” version, there is no Revert capability outside of Edit Mode because this method is different without menu.
-
I had to remove zoom sound for “on-the-fly” Color List because it overlapped with the color change sound files (ccchange, ccend) because they are not part of prompts.
7a. Yeah POWERSAVE isn’t really needed with the dimming capabilities in Edit Mode so it’s mostly for older styles.
7b. Fix submitted - control for Cancel Rehearsal updated
7c. Fix submitted - audio added for end choreography buttons
7d. Yes, when the sequence ends the end choreography sound plays (the actual intention on the begin and end choreography sounds is to be a quote or some audio cue for the user, the voice prompt is more of a “placeholder” but it plays right after the last event in the sequence to signify it’s ended, this can overlap depending on length of the sound for clash or lockup.
- this is a 2 button define to let prop work like sa22c’s hold button version, I believe @MegtoothSith will be testing as it was his request
-
I was talking about the edit mode color editing. Color list and color hue options
-
The zoom sound also does not play in edit mode
Ah, dammit ColorZoom is getting in the way of Revert, I’ll have to look at how to fix but it’ll probably have to be next week as I’m heading out of town for the holiday and won’t have my saber or computer with me.
Just going on the record, I do not use or like 1 button and it’s been an absolute PITA. I hope all 1 button users understand how much additional work getting all of this stuff added to 1 button has been for me and it’s something I will NEVER use. I’ll get it fixed but things are just so much simpler with 2 button…
3 Likes
Let me be the first to say, thank you so much for all of the hard work you’ve put in especially for one-button. Your efforts aren’t lost on me. I understand how much work goes into editing a prop file. So, even though you won’t benefit directly from the one-button features, it means a lot to me to have them available. Hopefully someday I’ll be able to get my hands on a two-button or learn how to solder so that I can add one. Until then, these one-button controls are awesome! Thanks again for all the hard work you pour into this community.
2 Likes
It is of course appreciated. I prefer two button, but my converted MR Anakin is one button, and I had to disable the AUX slide switch on my Graflex because it kept ghost activating. One button is definitely useful for people.
2 Likes
But the LGTers will adore you
3 Likes