@profezzorn So what can we do with dumpwavplayer ?
Looks like we’re getting the position at the time it’s entered…
FYI if you didn’t see, serial monitor does the report, but also gives a “Whut?? dumpwavplayer”
It’s a developer command, for figuring out when something is wrong with a wav player. Although, it turns out, that wasn’t the problem…
SOLVED. It’s saying “Loop”.
I’m seeing when the saber is off and long hold on PWR to get the track to play it saying “LUKE” as it begins to play the tracks. It’s doing this with all my font sets now EXCEPT TRON. It does do a blip sound w Tron but doesn’t say “LUKE”. Weird because it was fine last night. Finally if the blade is lit it doesn’t happen. *I don’t have anything Luke. Even with changing to tracks/none.wav it still says it.
Copy of config: ProffieOS 6.1 Config - Pastebin.com
Here’s the serial.
Welcome to ProffieOS, type ‘help’ for more info.
Battery voltage: 3.80
EVENT: Power-Pressed#1 millis=122711
EVENT: Power-Pressed millis=122711
EVENT: Power-Held#1 millis=123013
EVENT: Power-Held millis=123013
EVENT: Power-HeldMedium#1 millis=123512
EVENT: Power-HeldMedium millis=123512
EVENT: Power-Released#1 millis=124029
EVENT: Power-Released millis=124029
EVENT: Power-Longclick#1 millis=124029
EVENT: Power-Longclick millis=124029
SD card is busy, flags= scsi medium
SD card is busy, flags= scsi medium
File SD card is busy, flags= scsi medium not found.
Playing mselect.wav, SD card is busy, flags= scsi medium
SD card is busy, flags= scsi medium
(not found)
EVENT: Power-Pressed#1 millis=131921
EVENT: Power-Pressed millis=131921
EVENT: Power-Held#1 millis=132222
EVENT: Power-Held millis=132222
EVENT: Power-HeldMedium#1 millis=132727
EVENT: Power-HeldMedium millis=132727
EVENT: Power-Released#1 millis=132947
EVENT: Power-Released millis=132947
Playing mup.wav, SD card is busy, flags= scsi medium
SD card is busy, flags= scsi medium
(not found)
Battery voltage: 3.80
I see it playing mselect.wav and mup.wav, perhaps together they sound like “luke” ?
Figured it out. Had to put it into a recording and play with it using Siri.
“Loop” so NVM, all good it just threw me for a (say it) loop. Updated my post above w SOLVED.
Also, your tests show that the SD was mounted to the computer and not available for the board to use.
There’s currently an open issue where if you have SAVE_STATE active (or any save I suppose) , it might freeze the board when trying to write to the SD if it’s unavailable.
Not life threatening, just a heads up in case you experience it.
I didn’t have save state active, actually I just put that back. I’ll remember to next time, I was as I keep saying very short on free time. I’ll eject the SD next time I test, thanks.
You really should read all of the new controls at the top of the prop before testing, it will save you a lot of headaches. You’re activating track player without setting up /tracks in the font. If there is only one track the Track Player says “Loop” and loops your default track.
Tracks were setup. I read the documentation. I even just reread it this morning. It sounded like it was saying “Luke”. I wasn’t expecting to openly hear it say “Loop” like it did. No worries though. I get why you’d suggest that.
I will suggest consider changing that to say “Loop Track”. I’m not the only one who thought it said “Luke”.
I meant your confusion over why it was happening only on some fonts and not while saber was ON, the controls describe everything including why it would “Loop” if you only had one track because you were doing the control with the saber parallel 
Same with the confusion over the Volume menu, all “NEW!” or “NEW Control!” changes in my prop are noted in the top sections, it will help if you keep it handy when you run into something you’re unable to figure out so you don’t have to spend hours thinking something is working when it is.
NEW! Track Player* = Long Click PWR parallel
*requires tracks in either font/tracks/ or common/tracks/
*if no tracks in font or common will "Loop" default track
Turn Right (Stepped) = Next Track
Turn Left (Stepped) = Previous Track
Click PWR = Play Current Track Once
Click AUX = Random (will play current track and then randomly select next tracks)
Hold PWR + Turn Right = Rotate (will play current track and then next sequential tracks)
Hold PWR + Turn Left = Loop Current Track
Long Click PWR = Stop Track Player
This should be fixed, you’ll need the github version not v6.1 (this will be included in v6.2 when next version releases).
From ‘master’ choose “Code” > “Download ZIP”
Volume Menu is fixed in this version! There may be an answer to this that I missed in the documentation, but before updating to this version, I copied all of the .ini and .tmp files from the SD card root directory. After uploading, I pasted in the files, but none of my edits are loading on the saber. I tried copying with and without the .tmp files. I can see that the presets.ini has all of my edits stored, but they aren’t loading. Is there a way to restore edits after uploading a config?
2 Likes
You’d need
#define KEEP_SAVEFILES_WHEN_PROGRAMMING
Just a note on this though, if you change anything in your config (new or change styles in a preset, change order of presets, add or remove a preset) or other changes affecting values stored in the .ini files you may have odd behavior or be unable to see changes from .ini so using this define is more if you upload the same config but update a version or something, if you make larger changes to the config and have this define you’ll want to delete the .ini files manually from your SD and start “clean”. When OS6 releases and I get time to write up editing by hand approach there will be more detail.
1 Like
Thanks! That define did the trick
Can I please ask about the Master via GitHub vs the 6.1 BETA.
6.1 BETA is fixes bundled together at any one time put into a version right?
Master is a live version thats somewhere between 6.1 and the next release 6.2 (that hasn’t dropped yet).
So Master is always the most upto date, BUT the BETA (currently 6.1) is always the version people will move to test against so it can be referenced?
Additionally I have questions regarding the new fett263 track menu layout.
As I understand it, I need to lay the font out like this:
{ “fontname;common”, “fontname/tracks/track.wav”,
So do I need to name a primary music track in the tracks folder and then it will just play through all in there?
Also do I have to name all the tracks within that folder, track1, track2, track3 and so on?
I think ive got the gist of most of this … but the tracks bit has me a bit confused and im in the middle of building a mammoth config file right now …
“fontname/tracks/track.wav” is still your default track so if you just “Play Track” this is the track that will play (refer to the controls at top of prop file).
“Track Player” uses all tracks found in “fontname/tracks/” (or “common/tracks” -or both) and starts at the first track it finds, then you use the controls to choose a track and/or playback method as described in controls at top of prop. If you have tracks you want on all presets add them into common/tracks, if you have tracks you want for a preset only add them to fontname/tracks then go into Track Player and you can select from all tracks found for your active preset.
As noted in the controls if you only have one track or are missing fontname/tracks/ and common/tracks/ folders on your SD then your default track just loops when you try activate Track Player (and as noted above it says “Loop”).
The controls for Play Track and Track Player are separate in the prop just read the controls listed at the top of prop to use either.
@profezzorn can probably elaborate more, but pretty much.
The master contains the current round of additions and/or fixes to be tested, typically based on things discovered since the last version. So if we need something tested we’ll note it’s in master so it can be tested to make sure it actually fixed the issue and/or works correctly. Sometimes, it takes a few tests to get the fixes sorted so not everything in master is finalized. Once enough fixes, etc. are actually finalized they’ll become part of the next version as the next benchmark.
So, yes, the master would be the latest version BUT it doesn’t mean it’s fully tested so there may be more changes coming so if you’re using I’d recommend keeping an eye for additional updates. For testing I’d say using the latest ‘master’ at a given point in time is probably better it just may still be going through updates to resolve something.
Okay gotcha.
So do I need to name my primary track for each font still and point to that track (it wont auto find it on a regular play via the font - not in track mode).
And additionally for track mode to work, do I need to label them track1, track2, tracks etc, or are wild names ok too?
Also, the master will soon start to diverge from the 6.x branch.
New features and stuff will be happening on the master, while the 6.x branch will only have bugfixes. However, right now master and 6.x are nearly identical, except for a few new fixes that are only on the master branch right now.
2 Likes