Since the settings file is not explained in the manual (which seems to be a bit outdated, version 2.5) and it might be of interest to others as well, I'll ask here...
I was trying to enter the path of my own preset folder, but somehow it doesn't seem to work. The path contains spaces and --- . Is that the reason?
Also, what do those remember options 0, 1, 2 (and maybe more?) mean? If there were only 0 and 1, it would obviously be off and on respectively.
Finally, do I have to enter 0 as the key value for disabling individual key mappings?
Would be cool by the way, if there were indeed a Save option for saving presets. Currently it says Save in the settings file, but it is really Save as, which opens the dialog box instead of simply updating an existing patch as would be the case with Save.
Settings file
-
fluffy_little_something fluffy_little_something https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=281847
- Banned
- 12880 posts since 5 Jun, 2012
-
fluffy_little_something fluffy_little_something https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=281847
- Banned
- Topic Starter
- 12880 posts since 5 Jun, 2012
PS: After restarting my DAW the path works 
-
- KVRian
- 1330 posts since 25 Sep, 2006
The remember option can have the following values:
0 – don’t remember, but always use the SoundBankFolder in the settings.xml file as your Custom folder.
1 – use the SoundBankFolder as default at startup, then remember the folder changes whenever you load a bank from another folder. Remember changes as long as Sylenth1 is running.
2 – always remember the last picked folder, even after Sylenth1 is closed.
0 – don’t remember, but always use the SoundBankFolder in the settings.xml file as your Custom folder.
1 – use the SoundBankFolder as default at startup, then remember the folder changes whenever you load a bank from another folder. Remember changes as long as Sylenth1 is running.
2 – always remember the last picked folder, even after Sylenth1 is closed.
-
- KVRian
- 1330 posts since 25 Sep, 2006
No, just give the key an empty string if you don't want any key mapped:fluffy_little_something wrote:Finally, do I have to enter 0 as the key value for disabling individual key mappings?
<MAPPING commandId="10001" description="Switch to default skin" key=""/>
-
- KVRian
- 1330 posts since 25 Sep, 2006
VST plugins store their preset/bank data in the project file, so when you load the project later on it'll load all the correct presets.fluffy_little_something wrote:Would be cool by the way, if there were indeed a Save option for saving presets. Currently it says Save in the settings file, but it is really Save as, which opens the dialog box instead of simply updating an existing patch as would be the case with Save.
If we were to link each preset to a path and store that in the preset data, then all paths would be invalid when the project is loaded on someone else's computer, or even when you move the presets to another folder on your own computer.
There's no way to properly implement this without creating a path mess.
-
fluffy_little_something fluffy_little_something https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=281847
- Banned
- Topic Starter
- 12880 posts since 5 Jun, 2012
I don't know how it works inside, but It does work in Hybrid 3 by pressing Shift while clicking on the Save buttonLennard wrote:VST plugins store their preset/bank data in the project file, so when you load the project later on it'll load all the correct presets.fluffy_little_something wrote:Would be cool by the way, if there were indeed a Save option for saving presets. Currently it says Save in the settings file, but it is really Save as, which opens the dialog box instead of simply updating an existing patch as would be the case with Save.
If we were to link each preset to a path and store that in the preset data, then all paths would be invalid when the project is loaded on someone else's computer, or even when you move the presets to another folder on your own computer.
There's no way to properly implement this without creating a path mess.
I like it that way...I assume that the plugin kind of temporarily stores the path of the currently loaded patch and uses that path for merely updating the patch. And when I load another patch, the temp path is updated accordingly.
It also enables things like comparing original and changed version of the loaded patch.
-
fluffy_little_something fluffy_little_something https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=281847
- Banned
- Topic Starter
- 12880 posts since 5 Jun, 2012
Cool, it workedLennard wrote:No, just give the key an empty string if you don't want any key mapped:fluffy_little_something wrote:Finally, do I have to enter 0 as the key value for disabling individual key mappings?
<MAPPING commandId="10001" description="Switch to default skin" key=""/>
Now I only have Shift + L / S / I / R / O
(for loading, saving, initializing, renaming and resetting to original state, respectively) for patches and none for banks (which I never use anyway).
The key mappings have been properly updated in the Menu.
-
fluffy_little_something fluffy_little_something https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=281847
- Banned
- Topic Starter
- 12880 posts since 5 Jun, 2012
Maybe it would make sense to include a write-protected factory Settings file in the same folder so that one can reset the file in case one has messed it up.
Or maybe you could paste the content of the factory Settings file here in this thread as a reference so that people can copy and paste it back if needed.
Or maybe you could paste the content of the factory Settings file here in this thread as a reference so that people can copy and paste it back if needed.
-
- KVRian
- 1330 posts since 25 Sep, 2006
If you messed up the FactoryBank files, just re-install Sylenth1 to fix it!
-
fluffy_little_something fluffy_little_something https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=281847
- Banned
- Topic Starter
- 12880 posts since 5 Jun, 2012
Huh?! I was talking about the Settings file with all those mappings. Now that I have deleted and changed most mappings, I would not know the original values if for whatever reason I wanted them back months later...
No idea what FactoryBank files are...
No idea what FactoryBank files are...
-
- KVRian
- 1330 posts since 25 Sep, 2006
Ah sorry, I misread your question. Just open the Settings.xml file, delete all contents and save it. Then restart Sylenth1 to restore it to the factory defaults. (Or just delete it and re-install Sylenth1).
-
fluffy_little_something fluffy_little_something https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=281847
- Banned
- Topic Starter
- 12880 posts since 5 Jun, 2012
Ah, ok, good to know
-
fluffy_little_something fluffy_little_something https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=281847
- Banned
- Topic Starter
- 12880 posts since 5 Jun, 2012
I just tried renaming for the first time, and noticed that renaming my own patches in my own folder does not work, probably because of the missing patch path again, right?
So, does manually renaming my patches in Windows Explorer do the same or is the name also included within the fxp file itself when renaming within Sylenth1? I.e. it would be missing when renaming in Windows Explorer...
Because of that I actually did rename the first patch of some factory bank by accident, but it seems the change was not saved, anyway. Are the factory presets write-protected?
Speaking of presets, there are 4 banks x 128 patches, so, where are the remaining 800 or so?
With very few exceptions I don't like those factory patches, anyway, but I am curious where the rest are since it says on your site there are 1300+.
So, does manually renaming my patches in Windows Explorer do the same or is the name also included within the fxp file itself when renaming within Sylenth1? I.e. it would be missing when renaming in Windows Explorer...
Because of that I actually did rename the first patch of some factory bank by accident, but it seems the change was not saved, anyway. Are the factory presets write-protected?
Speaking of presets, there are 4 banks x 128 patches, so, where are the remaining 800 or so?
With very few exceptions I don't like those factory patches, anyway, but I am curious where the rest are since it says on your site there are 1300+.
-
- KVRian
- 1330 posts since 25 Sep, 2006
To rename a preset, click the edit button on the left side of the preset name in Sylenth1. The preset name is stored in the file. Changing the filename will have no effect on the preset name.
If you wish to load presets by filename instead, you can change the usefilename option in the Settings.xml file:
<PresetFolder remember="1" path="" usefilename="1"/>
Your other question is answered here:
http://www.lennardigital.com/support/soundbanks.php
If you wish to load presets by filename instead, you can change the usefilename option in the Settings.xml file:
<PresetFolder remember="1" path="" usefilename="1"/>
Your other question is answered here:
http://www.lennardigital.com/support/soundbanks.php
-
fluffy_little_something fluffy_little_something https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=281847
- Banned
- Topic Starter
- 12880 posts since 5 Jun, 2012
I had set usefilename to 1. So, using that option I have to name my patches twice, right? Once within Sylenth1 via the dot, and then the filename as such?
Renaming the preset via the dot does not seem to work, next time I load it, it has the old name again.
Why do my own patches from my own folders get loaded into the first slot of the factory bank?
I find it all a bit confusing
Renaming the preset via the dot does not seem to work, next time I load it, it has the old name again.
Why do my own patches from my own folders get loaded into the first slot of the factory bank?
I find it all a bit confusing