Loading fxp , folder never remembered

What do you know about my folder structure ??

All my vst’s are in

C/programfiles /vstplugs64/

and for vst 3

/programfiles/commonfiles/vst3

All my audio and projects are one C/gentleclockdivider Audio/etc…

So are my fxp

C/gentleclockidivder/Audio/fxpresets

This makes it incredibly easy to back -up my stuff every few months

When I want to load an fxp* from the folder above ( from the import preset tage here ) , It’s NOT normal that renoise always goes back the vst dir where the instrument is installed ( either in program files or commonfiles )
This never happened in previous versions , it always remembered the last location
Try it , load an fxp from there , to which dir.does renoise take you ??

Well at least a reply from Taktik would be on it’s place

Either way , it sucks monkey balls

It’s about loading presets ( which on my pc is C/GentleclockdividerAudio/fx and presets

Renoise automatically takes you the folder where the VST is installed , which in 99% of the cases is in programfiles/vsts/Name of plugin

or for vst3

programfiles/commonfiles/vst3

symlinks might help you all.

Linux 3.5.2, if I save a preset in a specific folder from a VST, when I click load, it takes me back to the default preset folder for that folder (~/.vst3/presets/developer/vst_name/)

Linux 3.3.2, if I save a preset in a specific folder from a VST, when I click load it takes me back to the previously used folder.

I guess some users prefer option A, some users prefer option B. Having this behaviour as an option (Remember last used folder for VSTs [True/False]) would be a compromise, assuming there was a decision made to change this behaviour based on user feedback or someone’s personal workflow/preference. I can understand how saving your presets for a specific VST in their specific folder would make sense, and similarly loading them from that folder would too, but if that’s not the default location, yeah, you’re gonna get frustrated having to navigate every single time.

2 Likes

In Renoise 3.5 the “default” preset folder from the plugin now always is used. It may indeed be more useful to use this as the default for each plugin and memorize the paths the last preset was loaded from or save to.

3 Likes

Can we have the option to set our own default directory ?

None of my presets are in program files , only the vst dll’s are , and this requires me to constantly re-navigate a few folders back .
It’s just a bad design choice

mh, isn’t there already an table entry per plugin for preset path? I don’t fully understand, but I agree with your suggestion.