8.7 updloaded (see top post for link)
Contains sound queue bugfixes and some fixes for the selecting time values in the menu.
8.7 updloaded (see top post for link)
Contains sound queue bugfixes and some fixes for the selecting time values in the menu.
Today I tested the named color menu.
Found and fixed several bugs.
Tested style option menu setting (small integers), found more bugs, which are now fixed.
New zip coming tomorrow.
Very close to having everything in the base OS tested.
(Prop makers have had a year to test their stuff, so hopefully it’s all good by now…)
Post-flash “Voice Pack Not Found” still plays garbled and sounds like it says “Muresev Not Found”. Obviously leaving the SD Card in stops it but it still needs to be resolved so it plays properly. Maybe there’s a way to slow down or edit the playback?
Those talkies are not easy to make or understand. I personally prefer the very old “military talkie voice”
It was discussed here:
I replaced some of mine: (they were recorded from my phone while played from my saber)
sd_card_not_found with “No”+“S”+“D”
font_directory_not_found with “No”+“F”+“O”+“N”+“T”
error_in_font_directory with “F”+“O”+“N”+“T”+“error”
And now that I am thinking about it, I could do:
Obviously, the errors.wav files should go in “common” (or font) folder but not necessarily part of a voice pack. And if no common folder or no errors.wav files in all fonts, then talkies will still be spoken.
But if you have no SD-Card inserted, sd_card_not_found should be spoken first ?
There’s wav file playback for errors for when they can be played.
But voice_pack_not_found shouldn’t be heard if no SD-Card is present, instead sd-card_not_found should be heard and that’s it. No ? At least that’s what I understood from @A_Rogue_Child:
@A_Rogue_Child, can you confirm you heard “Voice Pack Not Found” instead of “SD-Card Not Found” ?
@ olivierflying747-8 It’s definitely trying to say “Voicepack Not Found” and I just grabbed a newer recording and posted it in the book of faces OpenSource group so it can be listened to.
OS7 without the SD Card installed at the end of a flash will play
“Font Directory Not Found Font Directory Not Found SD Card Not Found”.
OS8 without the SD Card installed will play
“Font Directory Not Found Font Directory Not Found (*Voice Pack Not Found?) SD Card Not Found”.
*Maybe adding in more vowels or syllables for intonation would solve this? I know with voice generator stuff that’s a quick fix trick. Use it to slightly lengthen a specific part of the words or vocalizations. It’s not a life-ending thing and not the first time a talkie hasn’t sounded clean so if it gets tossed to the back-burner it’s fine. **Yes for this as well as another purpose the SD Card is out.
I replaced the “voicepack” sound with one that is hopefully better.
Is it understandable now?
v8.8 zip uploaded
Several menu fixes + new “voice pack” sound
“Voice Pack” reads slower so it’s understandable now, could use a little more tweaking. Added a third video clip in the book of faces.
FETT263_MANUAL_BLADE_ARRAY - tested and all works.
Will aim to do manual BladeID tomorrow.
Tested today:
You only have one update left… ![]()
ProffieOS uses a single decimal type of semantic versioning where 8.10 is > not = to 8.1.
ie: ProffieOS 7.15 which is the current official release.
@MattDoug27 Jinx.
…
I saw it too late ![]()
Ohhhohhhh, if we end up with the final official release as 8.88 it could be “applause” as well as “expanding fortune” in Kanji - Japanese. HadTo
I tried FETT263_MANUAL_BLADE_ID, but I can’t seem to get it working. I suspect there’s some detail I’m missing.
If I just use the define:
#define FETT263_MANUAL_BLADE_ID
I get the followingcompile error:
/Users/chrisandlindsey/Desktop/ProffieOS/props/saber_fett263_buttons.h:2292:5: error: 'PlayArraySound' was not declared in this scope; did you mean 'PlaySound'?
2292 | PlayArraySound();
| ^~~~~~~~~~~~~~
| PlaySound
exit status 1
Error compiling for board Proffieboard V2.
If I add
#define FETT263_MANUAL_BLADE_ARRAY
as well as the bladeid define, it compiles, but I can’t seem to trigger the scan. The prop says the button press should be:
case EVENTID(BUTTON_POWER, EVENT_FOURTH_CLICK_LONG, MODE_OFF):
which I believe means four clicks, hold for a second on the last click, and when I let go it should scan. But all that happens is the blade keeps igniting and retracting on the way through.
As I say, I suspect there’s some vital detail that I’m missing which when added will make it all work.
I don’t see any instance of
I’m seeing fourth held LONG
NEW! Manual Blade Array* = Quadruple (Four) Click + Hold PWR
or the 2-button combo