Not new to 2.0.26, but still pending; whenever VST live is running, it’s not possible to rename any folder or file with Windows file explorer. No matter what drive is concerned and permissions. As soon as VST live is closed and explorer re-opened, everything works. Now that’s a serious bug that affects the whole system. Exemple, if I create a new Cubase project while VST live is running, I can’t choose a name for the new project folder! Windows 11 latest version. File rename work when 1- right click, properties and edit in the name field.
Not true, tested on 3 systems. We’d certainly have realized.
But you may run some plugin which causes this…?
In any case, what exactly do you do when this occurs? Also maybe try to “Help/Clean all user Data”, remove the default Layer and try again.
We do not support running another DAW or similar audio software, including Cubase, at the same time VST Live runs. It may or may not work, and some functionality is expected to be limited at the least.
It bugs without any other application running. Not only Cubase.
“Not True” ??!!
Please don’t tell me it’s not true!
I lost a WHOLE day trying to isolate the service or background app that could have locked the file system, doing safe boot multiple times, without hardware support and so on. It appears that when VST Live is not running, everything works.
I cleaned user datas many times, uninstalled VST live, revert to previous versions, losing all patches etc… name it!
I didn’t want to spend another minute to dive any deeper in the issue because no matter what, I still can’t use MOTU Midi express 128 with VST Live v 2.0.26.157
Since I paid for it, I just lost another 2 hours this morning to “beta test” VST Live to find that the file renaming problem occurs only when the “Scan Plug-Ins On Start” is ticked (ON). C:/Program Files/Steinberg/VSTPlugins.
In the end, if I want to use VST2 plugs, I have to tick auto-scan, close the app. Open the app. Un-tick auto-scan. Close the app. re-open the app and then windows file renaming works even with VST live running. Once it’s done, no other scan is necessairy upon a new plug-in is added to the folder.
“Total commander” file browser is not affected by this behaviour, meaning I can rename files in all instances.
“Not true” means “Not true here” means we tested it on 3 systems and cannot reproduce. So it means “Not true except for your case”, which we still suspect to be caused by some plugin, probably a VST2 plugin.
It “works here” just as much as the Motu 128 “works” as reported by other users. We are also trying to get hold of one for the testing studio.
We want to help but need recipes to reproduce issues. With complex setups such as yours, it is necessary to narrow it and reduce the number of components involved.