Craig Anderton
Well-known member
I think this is correct, but back up your FX Chains before attempting the change.
I found out the following solution because I had issues with FX Chains not saving where expected, new FX Chains not showing up in the Browser but showing up in the same Explorer folder as other presets in the Browser, and a variety of other annoying issues that seemed to relate to Studio One vs. FSP. Maybe I'm the only one who's experienced these kinds of issues. But if not, and you use a lot of FX Chains, hopefully the following will ensure that your S1 FX Chains and newer FSP FX Chains will show up correctly in custom Browser folders.
If you have your FX chains in a User Data folder like D:\Studio One\Presets\PreSonus\FX Chains\v3.0 FX Chains, you need to move them to a folder in D:\Studio One\Presets\Fender\FX Chains\v3.0 FX Chains. I tried simply renaming the PreSonus folder in Presets to Fender, but that didn't solve all the problems I had. It seemed the files needed to be moved to the Fender-named folder.
I found out the following solution because I had issues with FX Chains not saving where expected, new FX Chains not showing up in the Browser but showing up in the same Explorer folder as other presets in the Browser, and a variety of other annoying issues that seemed to relate to Studio One vs. FSP. Maybe I'm the only one who's experienced these kinds of issues. But if not, and you use a lot of FX Chains, hopefully the following will ensure that your S1 FX Chains and newer FSP FX Chains will show up correctly in custom Browser folders.
If you have your FX chains in a User Data folder like D:\Studio One\Presets\PreSonus\FX Chains\v3.0 FX Chains, you need to move them to a folder in D:\Studio One\Presets\Fender\FX Chains\v3.0 FX Chains. I tried simply renaming the PreSonus folder in Presets to Fender, but that didn't solve all the problems I had. It seemed the files needed to be moved to the Fender-named folder.