jonetsu wrote: ubuntuuser wrote:
Can this also be helpful for other VSTs ? How is winecfg being run, any parameters ?
Just winecfg from the terminal.
It's mainly helpful for slower hard disks because Wine can take a while to load it's libraries etc off the disk which can throw a plugins startup routine off.
I tried it, and it will bring a dialog box with several options, and 'Windows 7' selected. At that point, do you select any options or is 'OK' simply clicked ? Are there any options in there that can benefit linvst ?
just choose ok.
The main point of it is that winecfg loads a lot of things off the disk and then any accesses to Wine after that will be speeded up.
The first time a Wine app is run after a boot, Wine needs to load a lot of libraries and that can take time with slower hard disks and can interfere with some vst timing startups when used with LinVst or whatever and I've had Kontakt and other vst crash because of it on some of my older testing systems with slow hard disks.
So just use winecfg to preload the Wine libraries but it's only needed on slow hard disk systems.
The Libraries tab in winecfg is where dll overrides are entered.
If a vst needs a dll override (the vst crashes because of an unimplemented Wine dll function (start the daw from the Terminal and look at the output for any Wine unimplemented function dll errors and take note of that dll)) then get the real windows dll and put it in the winprefixes system32 (64 bit) or syswow64 (32 bit) folders and then enter the dll's name in the winecfg Libraries tab and choose native then builtin.
Some daws don't display Wine info when they are started from a terminal but Reaper does, so even if someone doesn't use Reaper it can still be used to obtain Wine error info.
Also, winecfg builds a wineprefix ~/.wine if one doesn't exist.
The wineprefix is basically the windows system that contains the windows and system32 and syswow64 folders and dll's etc.
Sometimes the wineprefix might go a bit weird if something was corrupted or if an install resulted in weird things happening, so what I tend to do is to delete the wineprefix (sudo rm -R ~/.wine) and then run winecfg to build a new wineprefix, but doing this means that things need to be installed again ie vst installs etc