You don’t need to unless you have audio glitches and want to optimize how many reads it takes to open a file.
Currently I have my fonts organized into subdirectories, but style code points just to the soundfont folder, and I’m getting the “font directory not found” jingle.
This is what I currently have
{ "Anomaly", "",
Do I then need to point the preset at that subdirectory in the style code i.e. if I have 3 directories in the root with fonts in them: 1grey, 2grey, and 3grey, and the “Anomaly” soundfont folder is the grey1 directory should the first line of the preset my look like the following?
{ "1grey/Anomaly", "",
Nevermind Profezzorn
For anyone else looking at this, you need to provide the complete filepath as directed in the proffie documentation:
You may also want ;common in there, like:
{ "1grey/Anomaly;common", "",
It is, yes, thank you. I forgot about that when I posted here, but not when I updated the config.
One more thing though, on the soundfont configuration documentation:
it describes the filepath using “backslashes” instead of “slashes”:
“The first entry in the presets[] array specifies the full path to the font directory. For example, you can have your fonts sorted as sith\1\sith1 , or fonts\jedi\named\obiwan , etc.”
I’m not sure if that is intentional, but it definitely confused me as a newbie. Would the “backslash” have worked? I didn’t use it because the text editing software I’m using immediately highlighted it in red.
They would not. \ inside of a string literal (just text inside of " quotes) marks a special, usually invisible, control character (Technically it’s used for lots of other special values you want to put into a string too… but anyways…). E.g. \n for “newline”.
You can put a backslash into a string with \\, two backslashes (known as an “escape” sequence or escaped character. This only puts a single backslash in, in terms of characters, but you need two because of the aforementioned special usual purpose of \… it’s a little complicated if you’re unfamiliar)
If you’re curious you can read about ASCII encoding and escape literals but it’s a little into the weeds.
The TL;DR is no, that wouldn’t work.
Profezzorn would have to answer if the filesystem recognizes “\” the same as “/” (in which case \\ would work), but even if it does it would be my strong advice/opinion to only use /. There’s not really any reason to use a backslash, and as you can see using it means interacting with more complex things, just to represent a path in an unusual way Windows 
Yes it does.
1 Like
Thanks! That was an excellent explanation.
1 Like