Nice. I now have all of these on my saber, I made a “.voices” folder and threw them all in there, and assigned them to my presets like this:
{ "001_BLUE;.voices/Cal_Kestis;common", "tracks/", ...
{ "002_GREEN;.voices/Qui-Gon;common", "tracks/", ...
{ "003_PURPLE;.voices/Mace;common", "tracks/", ...
{ "004_RED;.voices/Dooku_CW;common", "tracks/", ...
Works like a charm 
Interesting that it’s happy with a dot In the directory name, specifically starting with the dot. Typically that’s reserved for hidden files in my experience.
I had to look up the font reading code in proffieOS, it skips folders that start with a . and it skips “common” when looking for Font folders. So, I named it .voices to make sure it didn’t try to read the voices folder as a font.
Well now you’ve piqued my interest. I’m not understanding why you have it in your font search path. Typically, you’d pre-empt a font to override sounds. So if you have a common folder and you want to override it, you would put your voices common folder first, I’m not really sure what’s going on with what you’re doing, but a detailed explanation would be pretty cool.
He’s talking about “list_fonts”.
Using a name that starts with . hides the directory from “list_fonts”.
Sub-directories and directories without hum files would also work.
Yeah, I don’t know of a way to select a voice pack for a font from the saber, like in EDIT_MODE. AFAIK if I want to make per-font voice packs for EDIT MODE, i.e. character voices, adding the specific voice folder in front of common folder in the font’s folder list is the only way (other then dumping the voice pack into the individual font’s folder, but that’s messy and makes a lot of duplicate files)
So, basically, instead of replacing the voice pack in common folder, i have multiple common folders i can choose from per font.
Edit Mode expects one ‘common’ folder and automatically appends “;common” to all presets. If you want to have voices specific to a font you need to put the voice prompt files into the font folder, this will then use those voices with that font in place of the common folder (font search path).
Edit Mode will always go to “font;common” on any preset when you use it’s Edit Font feature, if you have other folders or font search paths beyond this they will be overwritten so it is not recommended that you try to make up more “common” folders or add more search paths if you intend to use Edit Mode.
Edit Mode only allows you to edit the “font”, it will always use “common” with that as it’s hardcoded in to ensure a Voice Pack is always present so that users don’t accidentally disable the prompts while using the menu.
This is explained and covered in the Edit Mode documentation. Fett263 ProffieOS6 Edit Mode
As profezzorn notes, a “font”, in terms of use for Edit Mode, must contain hum.wav, otherwise it is not seen by the Edit Font menu as an option.
Yes, the fonts use the common folder, and the “.voices” folder has folders full of all the optional voice packs. So, when I want to use a voice other then the default one in common folder, I just put that specific voice folder in front of common in the folder load order, and those voice files are used by the menu instead. If a voice pack is missing any files, it still falls back to read the “common” folder. (and non voices like beeps only exist here, too)
I just find it cool that I can use shared voice packs on multiple fonts (I set all my green fonts to use Qui-Gon voice pack, he’s my favorite)
I’ve got to say, your experimentation with ProffieOS stuffage is neat to me 
I try.
I like finding new things that nobody’s tried/made before.
Sure, I can go to the Style Library and copy existing code. But I like then to study that code, tear it apart, and find out how far I can stretch/bend it to do something new/different. Then I also like making something entirely new from scratch that doesn’t exist yet.
Absolutely! I think that’s really what ProffieOS (open source in general) is all about, it’s just really cool to me to see more people interested in that.
This is the way.
So this then gives further options in switching the voice pack on the fly using the existing resources, correct? You don’t need to copy over a main font pack and then dump the sounds into that and use that. The chance of cross-error is reduced and you’ve expanded the options.
“Most impressive.”
Yeah, the only down side is that you have to set the voice for a given preset in the saber’s config file, then upload. You can’t change it on the fly (yet).
You missed what I said, this way will be overwritten if you use Edit Font.
Edit Mode expects and requires
"Font;common"
If you put an extra font search path in like
"Font;voice;common"
as soon as you use Edit Font it will overwrite back to
"Font;common"
and you lose your alternate voice.
If you don’t want this to happen and you want different voices in presets you still need to put the sounds in the fonts themselves.
If you’re just uploading a config you can do whatever font search paths you want BUT as soon as you try to Edit in Edit Mode you will lose the voice if it’s not in the font or common.
Font search paths have been around a while and are fine when uploading, but if you want to edit fonts using Edit Mode you cannot use.
I tested and it seemed to work as expected, but you’re saying if I choose the “EDIT_FONT” it’ll revert back to common voices, hmm. I’ll have to test around with that.
The way I have my presets configured, I have one preset for every font on my SD card (currently 73), so I never really tried changing EDIT_FONT option.
I may end up having to dump the voices into the font folder, but that’ll mix em in. Can a font have a sub folder “common” and it’ll read it? Or do all the voices have to be in the font’s root directory?
Yes, nothing to test, it’s hardcoded in 
ProffieOS Workbench also follows the same set up “font;common”
No, the sounds need to be in root of font.
If you NEVER edit font it will work, BUT this ISN’T a viable approach for most users that set up Edit Mode as Edit Font is one of the main features used. Others have done what you’ve done and then can’t understand why the voice keeps reverting, so I have to remind everyone that the set up for Edit Mode can only be:
"font;common"
Any other search paths are not supported by Edit Mode. When all of the new voice packs came out multiple users were doing what you are and it started to spread that users could just add more voices via search paths, which then caused problems for users, so I already had to address this earlier in this same thread.
The correct and intended way to use multiple voices in Edit Mode is to set font specific voices in the font you want them associated with (within the root) and then have your default in the common folder as described in the Edit Mode documentation.
This allows you to have unique voices in each font and not lose them when you use Edit Font.
Ah. Ok. Yeah I have not yet messed with “Copy preset” feature, so I may end up doing just 1 actual coded preset, to save memory. In which case, I’ll have to copy/dump voices into root of font.
Q: What about the folders within common/voices, “clrlst” and “mnum”, do those files also have to be dumped into root of font, or just move those folders
Q: Are you planning to make a live action Ahsoka voice? I’d love that.
She’s so blaaahh