There’s no harm in using the define on 1 button, it just doesn’t do anything so error is not needed.
I’ll update comment for the define when I get a chance.
1 Like
I don’t think there is any serial monitor output associated with this.
Only the output sound changes.
sounds like it’s not quite fixed yet then.
Is it just random, or is it particular fonts?
Or something else?
1 Like
I added the numbered audio files from edit mode to clsh, bgnlock, endlock, in, out, preon, pstoff, and swing. I still need to edit the config.ini files in my fonts to test the acceleration-based accent swings, but everything else is working as expected except for the Dual-Mode ignition/retraction. Pstoff isn’t playing odd/even files as it should. Everything else is working great
I’d just re-export it to be safe. The Project rate in the bottom left corner set to 41000Hz, and then in the export dialog window, have the File Type as WAV, and Encoding as Signed 16-bit PCM.
1 Like
I’ll have a look at this after I finish current round of updates.
1 Like
It’s when I put the battery back in. Which means it reverts to the first preset on my config. That soundfont was modded by me. So I will swap it out with one of the other fonts.
Maybe send me the font and see if I can reproduce it that way?
Afterimage fixed!
Per-effect volume test.
# Set the volume for each effect individually, in percent.
# 50 makes it half as loud. 200 makes it twice as loud.
# Maximum allowed value is currently 255. The default is 100.
# EFFECTNAME can be "clash", “preon”, “out”, “pstoff”, etc.
# ProffieOS.SFX.EFFECTNAME.volume=100
ProffieOS.SFX.blst.volume=75
ProffieOS.SFX.clsh.volume=25
ProffieOS.SFX.out.volume=250
Works as expected, cool! Video for demo:
All wavs recorded at identical volumes and normalized to 0db, then copied to SD card.
(note* out.wav was recorded as “200%”, but ended up bumping it up to 250 afterwards)
2 Likes
Just for fun @Afrojedi , have you tried a fresh new version of config.ini?
Maybe there’s an old Gforce-stab parameter or something that affects things?
Shot in the dark.
All the files look formatted correctly.
Also, any difference organizing your font sounds for performance ie: multiple sounds in sub-folders, but single sounds (like hum) back in the font root level?
1 Like
I kind of thought i did that, but I did notice that the other customised font I made is also having the same hum issue on after turning off.
Does it make a difference if you don’t have all those voice pack files in there? Just the font and then use a common folder for the spoken prompts?
1 Like
the issue went away when I tested it with bank04 and I just checked bank04 doesn’t have the voice pack in it. I was hoping to have all the english voice packs in the fonts so each one is slightly different but I might just use the common folder and be done with it.
testing now.
I don’t know why it would be different, unless it is… 
But you could still do variation with Font Search Paths and the common folder.
Folder structure like:
common/English/voiceA
common/English/voiceB
etc…
Then presets could be like
{ "font1;common/English/voiceA", "tracks/.........
{ "font2;common/English/voiceB", "tracks/..............
1 Like
I tried that and instead of having it nested in common/etc… i did
{ “font1;common”, "tracks/…
{ “font2;comun”, "tracks/…
didn’t work and I was informed by Fett263 I should put the files in the font2 folder rather then having a separate folder. but I’ll test this out as well to see if it works.
I don’t understand, what “didn’t work” about this?
the common folder took precedence and the comun was never used.