Hi there,
I don’t know if this is a 2.2.16 specific issue: I owned VST Live for some time, but now starting to seriously getting to know it for my next project.
Not sure this is a bug or user error, but it is (for me atleast) certainly unexpected behaviour, and I can replicate it everytime. It has to do with how folders are managed in the mediabay. It seems such a basic thing I wonder if it is a ‘me’ (or my machine) problem. I’ve only tested it with ‘Sound’, but maybe this goes for the other assets as well.
I’m using Windows 11, and moved my local assets folder to C:\Users<username>\OneDrive\VSTLive. Maybe that is relevant.
Issues and steps to reproduce:
- Start with an empty presets folder
- Start new project
- Save a sound via the menu bar → Sound → Save Sound
- Save a second sound the same way, but now create a new subfolder when saving the new sound. After this is done, the subfolder appears in the mediabay, but the saved sound does not [issue 1]
- Close and restart VSTLive, start a new project again.
- The “Sound” browser in the media bay now sees the newly created subfolder as root [issue 2], and there is no way to browse back to the ‘presets’ root in the media bay. So, only the last saved sound shows up.
- The only way to get back to the root folder, is to load a sound via the menu → Sound > Load Sound, browse to the root level and load the first saved sound. This loads the first saved sound, but the media bay still shows only the contents of the subfolder
- Close and restart VSTLive again, start a new project
- The Mediabay now sees the folder of the last loaded sound as root [issue 3]. So, now the first saved sound, the folder and the sound in the folder show up and all is well…
- … until I save a new sound in the (now existing) folder, it starts over again: the mediabay again sees this subfolder as root.
This behaviour is also triggered when loading a sound from a subfolder via the menu instead of the Mediabay. The next time VSTLive starts it sees that folder as presets root. This also happens if the chooses subfolder is in a location outside of the assets folder.
Thanks in advance for looking into this.
edit: just noticed this after typing my post:
When VSTLive is ‘stuck’ in the wrong preset root:
- Close VSTLive, delete everything in the Presets folder
- Restart VSTLive → New project
- The just deleted folder structure is rebuild to the path where VSTLive was stuck.
This might be expected behaviour however, since VSTLive recreates what it thinks is the preset folder in my assets map.
