Closed ShawkMusic closed 2 years ago
Also, sometimes instead of saying the above, it just stays scanning and Reaper says this:
it stays there for like a minute and then Reaper just gives up and stops scanning
Seems like it might be a Wine problem or a LinVst installation problem.
The first thing to try is to install LinVst again (to /usr/bin) and then reconvert all of the vst folders.
I did that and it still doesn't work. Although now instead of stalling for a minute it just instantly doesn't work (and shows up on Reaper's "plug-ins that failed to scan", like it did before)
Does it work any better if you cd to the wine vst plugin folder before running the program? Also try running it after you cd to /usr/bin It could be a known wine bug
Does it work any better if you cd to the wine vst plugin folder before running the program? Also try running it after you cd to /usr/bin It could be a known wine bug
cding into ~/.wine and then running it made it better, it was able to scan and I can load the VSTs now, but now every time I open up Reaper it's like a coin toss over weather it's just gonna work smoothly or if it's gonna get stuck on loading the VST plugins and never open the project, which I seem to only be able to solve by rebooting my computer
A few things.
When things suddenly go wrong it's usually because of something has changed, so the first thing to suspect is something in the wineprefix has gone wrong, maybe a config file or a corrupted file or whatever.
Sometimes some new app install might actually interfere with older app installs because of dll's etc.
The first thing to do would be to reinstall the vst and update Wine to 6.2x (I think it's up to 6.23 at the moment, the Wine versions around 6.14 had a bug from what I remember that affected loading.
Then if that doesn't work, there is also the option of deleting the wineprefix ~/.wine and reinstalling everything from the beginning.
The first thing to do would be to reinstall the vst
What do you mean by "reinstall the vst"? Does that mean re-convert it, or re download it, or something else?
and update Wine to 6.2x (I think it's up to 6.23 at the moment, the Wine versions around 6.14 had a bug from what I remember that affected loading.
I'm on Manjaro which is rolling release so I'm on Wine 7.0rc2-1. Is that okay?
Then if that doesn't work, there is also the option of deleting the wineprefix ~/.wine and reinstalling everything from the beginning.
I've tried renaming my ~/.wine folder to ~/.wine_b so I can go back to it in case I need to and ran Wine so that it created a new ./wine folder, and it's still not working.
The first thing to do would be to reinstall the vst
What do you mean by "reinstall the vst"? Does that mean re-convert it, or re download it, or something else?
and update Wine to 6.2x (I think it's up to 6.23 at the moment, the Wine versions around 6.14 had a bug from what I remember that affected loading.
I'm on Manjaro which is rolling release so I'm on Wine 7.0rc2-1. Is that okay?
Then if that doesn't work, there is also the option of deleting the wineprefix ~/.wine and reinstalling everything from the beginning.
I've tried renaming my ~/.wine folder to ~/.wine_b so I can go back to it in case I need to and ran Wine so that it created a new ./wine folder, and it's still not working.
The wine version is ok, I'm running wine-7.0-rc5 (Staging) on EndeavourOS (Endeavour and Manjaro are both arch based).
I say reinstall the vst (or vst's) because of possible file corruption.
Like, if you reinstall Kontakt or CSR Reverb and then it loads ok but the other vst's still have problems then that would mean the problem had something to do with corrupted files in the wineprefix ~/.wine
The corrupted files might be in the wineprefix and/or the linvst files including all of the linvst converted vst .so files and the lin-vst-server files in /usr/bin.
Usually when something was working and then doesn't, corrupted files might be involved somehow.
I have a similar problem to yours, when someone upgraded their Ubuntu system and LinVst/Wine stopped working as it did.
Usually I'd suspect corrupted files when something was working and then suddenly doesn't, and the easiest way to deal with it is to reinstall the components ie LinVst and the vst related files in the wineprefix where the vst installation files will be.
The first thing to do would be to reinstall the vst
What do you mean by "reinstall the vst"? Does that mean re-convert it, or re download it, or something else?
and update Wine to 6.2x (I think it's up to 6.23 at the moment, the Wine versions around 6.14 had a bug from what I remember that affected loading.
I'm on Manjaro which is rolling release so I'm on Wine 7.0rc2-1. Is that okay?
Then if that doesn't work, there is also the option of deleting the wineprefix ~/.wine and reinstalling everything from the beginning.
I've tried renaming my ~/.wine folder to ~/.wine_b so I can go back to it in case I need to and ran Wine so that it created a new ./wine folder, and it's still not working.
If plugins were working then suddenly don't, try testing if it's the wineprefix that is causing the problems
Basically to test a plugin using a temporary new wineprefix, open a Terminal and then set it up to use the new wineprefix (only valid for the Terminal that was opened and setup, not other Terminals).
To test if it's the wineprefix that's causing the problem (possible file corruption, installation problems etc),
open a Terminal
cd into your home directory
then enter into the Terminal
mkdir .my-new-prefix
export WINEPREFIX=/home/yourusername/.my-new-prefix (this sets the wineprefix to use for this Terminal only, system files need to be setup to make it permanent)
winecfg
and that will create a new wineprefix named .my-new-prefix
and then in the same Terminal window install a simple vst "wine delay.exe" or whatever vst
Reinstall LinVst so that possible LinVst file corruption in not an issue, download LinVst from the releases page and copy all of the lin-vst-server files to /usr/bin
sudo cp /home/yourusername/Downloads//LinVst-4.7/lin-vst* /usr/bin
start linvstconvert and select the linvst.so file from the downloaded LinVst 4.7 folder
find the vst dll in the /home/yourusername/.my-new-prefix folder and hit the start button.
Start your daw up (from the same terminal window) and set the search path to the vst folder(s) in /home/yourusername/.my-new-prefix
restart the daw
See if the daw loads and scans the vst ok.
If the plugin runs ok in this new wineprefix (/home/yourusername/.my-new-prefix) and the same plugin doesn't run ok in the old wineprefix ~/.wine (default wineprefix) then there is a high probablity that the ~/.wine (default wineprefix) is causing some problems.
To test the same plugin using the default wineprefix (~/.wine), delete the temporary wineprefix rm -R .my-new-prefix and then exit the Terminal used for testing and then install the plugin into the default wineprefix and set it up using linvstconvert.
Thanks for all your help I wiped my Manjaro install and switched to Arch for a couple of different reasons, and now this seems to be working for me.
(This issue is a copy of the issue I made at https://github.com/Goli4thus/linvstmanager/issues/25, where I was told I should post here instead. I've also tried downgrading wine from 6.16 to 6,15 and it still doesn't work)
I keep getting this error when trying to load VSTs on Reaper. It was working before, I don't know what changed.
"The program lin-vst-servertrack32.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience"
This is what "Show details" says: