Os6.6 false clashes and stab sound and effects

BK_Saber · August 23, 2022, 4:37pm

ok, ill give that a whirl when i get home tonight

BK_Saber · August 23, 2022, 4:55pm

Are you referring to the clash strength being tied to specific wav files? I do recall that was one of the first OS6 enhancements where depending on how hard you hit the blade, if you hit it softly it would trigger to play only clash1-3.wav, and harder hits would sequentially play clash8-10.wav or something of that sorts.

You may be on to a good hunch here.,…

Nick_Mcglown · August 23, 2022, 5:12pm

Yes that’s what I’m thinking maybe if there’s a way we can change it in the profiles back to the old OS

Fett263 · August 23, 2022, 5:17pm

Both profezzorn and I have tried to determine cause and fix for a while (including AUDIO_CLASH_SUPPRESSION_LEVEL, which seemed to fix the issue for a lot of users)
Other than those tests we haven’t really had any conclusive help on the matter if I’m being honest. Like I’ve said a bunch of times, I have OS6 running a dozen sabers and none of them exhibited any change in clash sensitivity, if anything I maybe had to increase CLASH_THRESHOLD_G by maybe 0.5 on a few of them. So am I unable to fix something that I can’t replicate. We’ve gone down this hole multiple times and either users magically have it fixed or they disappear or they aren’t actually helping determine cause and fix.
I have no problem trying to fix whatever is wrong but from my point of view it’s something specific to the sabers that are experiencing it so the owners of said sabers need to help and not disappear.
I understand some people want to also help but the suggestions of what to test I see them making aren’t really helping to determine the cause IMHO. Nothing personal but if you start with what you think the cause is you’ve already cut off potential leads to the truth.
If someone really wants to help narrow it down, please start a new thread, post your current config and an explanation of what you’re experiencing and we’ll give you some things to try out to start looking for the actual cause, but you’ll need to actually stick around and provide feedback as we try stuff or nothing’s really going to change.

Fett263 · August 23, 2022, 5:19pm

All of that occurs AFTER the clash is detected but just remove FETT263_CLASH_STRENGTH_SOUND define and test.

Fett263 · August 23, 2022, 5:33pm

NoSloppy:

Talking about the whole prop file.
Changing

#ifdef CONFIG_PROP
#include "../props/saber_fett263_buttons.h"
#endif

to

#ifdef CONFIG_PROP
#include "../props/saber_sa22c_buttons.h"
#endif

@BK_Saber
I’d just remove or comment out the whole #ifdef CONFIG_PROP section in your OS6 config, sa22c’s prop is from OS5 but it shares portions of the Battle Mode code from my prop. If we want to start at ground zero to determine what may be causing just use default button control and test leaving EVERYTHING else the exact same in your config.

If that doesn’t produce false clashes then add my prop back but comment out ALL defines that start with FETT263_ and test, then report back and we’ll start looking deeper.

BK_Saber · August 23, 2022, 6:01pm

Roger Roger. Will do tonight and report back

VenomThePooh · August 24, 2022, 12:02am

New thread started here: OS 6.7 Delayed Clashes and Effects with Fett263 Prop File

BK_Saber · August 24, 2022, 12:50am

ok, did a quick test with no fett or sa22c prop files. Heres the upper portion of my config:

#ifdef CONFIG_TOP
#include "proffieboard_v2_config.h"
#define NUM_BLADES 1
#define NUM_BUTTONS 2
#define VOLUME 2700
const unsigned int maxLedsPerStrip = 144;
#define CLASH_THRESHOLD_G 3.5
#define ENABLE_AUDIO
#define ENABLE_MOTION
#define ENABLE_WS2811
#define ENABLE_SD
#define IDLE_OFF_TIME 60*5*1000
#define MOTION_TIMEOUT 60 * 15 * 1000
#define DISABLE_DIAGNOSTIC_COMMANDS
#define ENABLE_SPINS
#define NO_REPEAT_RANDOM
#define FILTER_CUTOFF_FREQUENCY 50
#define FILTER_ORDER 8
//#define AUDIO_CLASH_SUPPRESSION_LEVEL 16
#endif

//#ifdef CONFIG_PROP
//#include "../props/saber_sa22c_buttons.h"
//#endif

#ifdef CONFIG_PRESETS
Preset presets[] = {

Still getting false clashes when the saber ignites, blaster blocks, double-clashes , accent swings, etc. Oddly enough, with the clash threshold set to 3.5, it reacted like the good old days where it would trigger a hit/clash like back in the OS5 days, very responsive. But sadly the double/false clashes were every where.

Going to test with fetts prop file next

BK_Saber · August 24, 2022, 1:02am

Tested the same settings as above, just un-commented the CONFIG_PROP section and added Fetts buttons.

Oddly enough, im now experiencing exactly as the poster (Venom) above is as well, where it will let you do a single clash, but not consecutively multiple clashes in a row. Its like you have the let the saber breath in between clashes in order to trigger them properly. Trying to do multiple clashes consecutively in a row, yields in the saber just ignoring you and you get no clashes at all…until you wait like 2 seconds, and then try again…but only allows you to do 1 clash and then waiting 2 seconds in between in order to get the next clash.

However the flash clashes were still apparent and there.

Moving on to sa22c’s prop for testing…

Fett263 · August 24, 2022, 1:05am

OK, so false clashes with or without my prop, correct?

BK_Saber · August 24, 2022, 1:06am

so far, with no prop file and with yours (fett), false clashes were there. So I dont think this issue has to do with prop file buttons files. Its gotta be in the main code somewhere

Fett263 · August 24, 2022, 1:06am

Yes, this is known. prop base adds a 400ms delay on Clash Event, we’ll have a fix for testing when profezzorn is back from vacation. See here:

Fett263 · August 24, 2022, 1:09am

Thanks, was pretty sure it wasn’t prop related but good to have confirmation on a saber experiencing.

OK, let’s cut your VOLUME in half to 1350 and test with my prop leaving everything else as is.

BK_Saber · August 24, 2022, 1:14am

cut the volume to 1350 and left in your prop file…no change. Still triggering false clashes on ignites, blaster blocks, etc

Its funny cause the sabers so quiet now, but the very first ignite of the test triggered a false clash, lol

Fett263 · August 24, 2022, 1:19am

Hmmm that’s very odd, leave volume at 1350 and comment this out and upload we may need.

\\#define DISABLE_DIAGNOSTIC_COMMANDS

Then hook up to Serial Monitor and keep battery power on and turn on saber, see if it does false clashes still, if so post the Serial Monitor output.

BK_Saber · August 24, 2022, 1:26am

Not sure what you mean by this. You mean turn on serial monitor with the battery inserted in the hilt?

Fett263 · August 24, 2022, 1:27am

yes this way the saber is fully powered an not running on USB power

BK_Saber · August 24, 2022, 1:29am

heres the monitor…false clashes galore. The only thing i did was ignite the saber, did a couple blaster bloacks, turned saber off. Ignite the saber…did a few blaster blocks…etc. All clashes recorded in the monitor were a result of false clashing

EVENT: Power-Pressed#1 millis=175727
EVENT: Power-Pressed millis=175727
EVENT: Power-Released#1 millis=175908
EVENT: Power-Released millis=175909
EVENT: Power-Shortclick#1 millis=175909
EVENT: Power-Shortclick millis=175909
Ignition.
unit = 0 vol = 0.50, Playing elite/preon/preon01.wav
channels: 1 rate: 44100 bits: 16
Playing elite/out/out01.wav
channels: 1 rate: 44100 bits: 16
unit = 1 vol = 0.00, Playing elite/hum/hum01.wav
channels: 1 rate: 44100 bits: 16
humstart: 800
unit = 2 vol = 0.00, Playing elite/swingl/swingl01.wav
channels: 1 rate: 44100 bits: 16
unit = 3 vol = 0.00, Playing elite/swingh/swingh01.wav
channels: 1 rate: 44100 bits: 16
EVENT: Clash ON millis=176540
unit = 4 vol = 0.50, Playing elite/clsh/clsh05.wav
channels: 1 rate: 44100 bits: 16
Battery voltage: 3.40
EVENT: Aux-Pressed#1 ON millis=185449
EVENT: Aux-Pressed ON millis=185449
EVENT: Aux-Released#1 ON millis=185527
EVENT: Aux-Released ON millis=185527
EVENT: Aux-Shortclick#1 ON millis=185528
EVENT: Aux-Shortclick ON millis=185528
unit = 0 vol = 0.50, Playing elite/blst/blst02.wav
channels: 1 rate: 44100 bits: 16
EVENT: Clash ON millis=185904
unit = 4 vol = 0.50, Playing elite/clsh/clsh08.wav
channels: 1 rate: 44100 bits: 16
EVENT: Aux-Pressed#1 ON millis=187547
EVENT: Aux-Pressed ON millis=187547
EVENT: Aux-Released#1 ON millis=187629
EVENT: Aux-Released ON millis=187629
EVENT: Aux-Shortclick#1 ON millis=187629
EVENT: Aux-Shortclick ON millis=187630
unit = 0 vol = 0.50, Playing elite/blst/blst08.wav
channels: 1 rate: 44100 bits: 16
EVENT: Clash ON millis=187902
unit = 4 vol = 0.50, Playing elite/clsh/clsh01.wav
channels: 1 rate: 44100 bits: 16
EVENT: Aux-Pressed#1 ON millis=189564
EVENT: Aux-Pressed ON millis=189564
EVENT: Aux-Released#1 ON millis=189649
EVENT: Aux-Released ON millis=189649
EVENT: Aux-Shortclick#1 ON millis=189649
EVENT: Aux-Shortclick ON millis=189649
unit = 0 vol = 0.50, Playing elite/blst/blst04.wav
channels: 1 rate: 44100 bits: 16
EVENT: Clash ON millis=190054
unit = 4 vol = 0.50, Playing elite/clsh/clsh09.wav
channels: 1 rate: 44100 bits: 16
EVENT: Aux-Pressed#1 ON millis=191214
EVENT: Aux-Pressed ON millis=191214
EVENT: Aux-Released#1 ON millis=191276
EVENT: Aux-Released ON millis=191278
EVENT: Aux-Shortclick#1 ON millis=191278
EVENT: Aux-Shortclick ON millis=191278
unit = 0 vol = 0.50, Playing elite/blst/blst03.wav
channels: 1 rate: 44100 bits: 16
EVENT: Clash ON millis=191405
unit = 4 vol = 0.50, Playing elite/clsh/clsh02.wav
channels: 1 rate: 44100 bits: 16
Playing elite/swingl/swingl01.wav
channels: 1 rate: 44100 bits: 16
Playing elite/swingh/swingh01.wav
channels: 1 rate: 44100 bits: 16
EVENT: Aux-Pressed#1 ON millis=193562
EVENT: Aux-Pressed ON millis=193562
EVENT: Aux-Released#1 ON millis=193653
EVENT: Aux-Released ON millis=193653
EVENT: Aux-Shortclick#1 ON millis=193653
EVENT: Aux-Shortclick ON millis=193654
unit = 0 vol = 0.50, Playing elite/blst/blst01.wav
channels: 1 rate: 44100 bits: 16
EVENT: Clash ON millis=193828
unit = 4 vol = 0.50, Playing elite/clsh/clsh10.wav
channels: 1 rate: 44100 bits: 16
EVENT: Power-Pressed#1 ON millis=196321
EVENT: Power-Pressed ON millis=196321
EVENT: Power-Released#1 ON millis=196400
EVENT: Power-Released ON millis=196400
EVENT: Power-Shortclick#1 ON millis=196400
unit = 0 vol = 0.50, Playing elite/in/in02.wav
channels: 1 rate: 44100 bits: 16
No sounds found: pstoff
Amplifier off.
EVENT: Power-Pressed#1 millis=198622
EVENT: Power-Pressed millis=198622
EVENT: Power-Released#1 millis=198702
EVENT: Power-Released millis=198703
EVENT: Power-Shortclick#1 millis=198703
EVENT: Power-Shortclick millis=198703
Ignition.
unit = 0 vol = 0.50, Playing elite/preon/preon01.wav
channels: 1 rate: 44100 bits: 16
Playing elite/out/out01.wav
channels: 1 rate: 44100 bits: 16
unit = 1 vol = 0.00, Playing elite/hum/hum01.wav
channels: 1 rate: 44100 bits: 16
humstart: 800
unit = 2 vol = 0.00, Playing elite/swingl/swingl03.wav
channels: 1 rate: 44100 bits: 16
unit = 3 vol = 0.00, Playing elite/swingh/swingh03.wav
channels: 1 rate: 44100 bits: 16
EVENT: Clash ON millis=199163
unit = 4 vol = 0.50, Playing elite/clsh/clsh06.wav
channels: 1 rate: 44100 bits: 16
Battery voltage: 3.34
EVENT: Aux-Pressed#1 ON millis=202992
EVENT: Aux-Pressed ON millis=202992
EVENT: Aux-Released#1 ON millis=203059
EVENT: Aux-Released ON millis=203059
EVENT: Aux-Shortclick#1 ON millis=203059
EVENT: Aux-Shortclick ON millis=203059
unit = 0 vol = 0.50, Playing elite/blst/blst08.wav
channels: 1 rate: 44100 bits: 16
EVENT: Clash ON millis=203317
unit = 4 vol = 0.50, Playing elite/clsh/clsh02.wav
channels: 1 rate: 44100 bits: 16
EVENT: Aux-Pressed#1 ON millis=204786
EVENT: Aux-Pressed ON millis=204786
EVENT: Aux-Released#1 ON millis=204844
EVENT: Aux-Released ON millis=204844
EVENT: Aux-Shortclick#1 ON millis=204844
EVENT: Aux-Shortclick ON millis=204846
unit = 0 vol = 0.50, Playing elite/blst/blst03.wav
channels: 1 rate: 44100 bits: 16
EVENT: Clash ON millis=205209
unit = 4 vol = 0.50, Playing elite/clsh/clsh08.wav
channels: 1 rate: 44100 bits: 16
EVENT: Aux-Pressed#1 ON millis=206504
EVENT: Aux-Pressed ON millis=206504
EVENT: Aux-Released#1 ON millis=206527
EVENT: Aux-Released ON millis=206527
EVENT: Aux-Shortclick#1 ON millis=206527
EVENT: Aux-Shortclick ON millis=206527
unit = 0 vol = 0.50, Playing elite/blst/blst05.wav
channels: 1 rate: 44100 bits: 16
EVENT: Clash ON millis=206597
unit = 4 vol = 0.50, Playing elite/clsh/clsh10.wav
channels: 1 rate: 44100 bits: 16
EVENT: Power-Pressed#1 ON millis=208917
EVENT: Power-Pressed ON millis=208917
EVENT: Power-Released#1 ON millis=208948
EVENT: Power-Released ON millis=208948
EVENT: Power-Shortclick#1 ON millis=208948
unit = 0 vol = 0.50, Playing elite/in/in01.wav
channels: 1 rate: 44100 bits: 16
EVENT: Clash millis=209355
No sounds found: pstoff
Amplifier off.

Fett263 · August 24, 2022, 1:30am

OK, let’s rule out your SD, run ‘sdtest’ in Serial Monitor and post results.