Quote:
Originally Posted by osxmidi
Are you taking about rebuilding a wineprefix?
On my old laptop the hard disk is so sloooooooooow that by the time Wine loads it's libraries the vst has timed out after Reaper tries to load it twice.
I think it affects systems with slower hard disks and memory because of the time it takes for Wine to initially load it's libraries on a new boot and then after that it's ok until the next boot.
Running winecfg seems to load Wine libraries or whatever, and then the vst loading in Reaper doesn't time out but vst loading will time out without first running winecfg or something that loads Wine.
I have to prime the Wine pump, so to speak.
More modern systems would not get the Wine loading time problem.
When I use my more modern quad core I don't have to do it.
|
Not that I know of. Never noticed a slowdown the first time I run wine. What I mean is that whenever you have updated the wine binary (new version or change to/from wine-staging), there will be a delay while starting wine for the first time in a specific index. Sometimes it even prompts you to update wine-gecko or mono in the wine prefix.
__________________
Reaper for Linux Documentation (WIP). Software: Archlinux/KDE, Fabfilter FX, Komplete 8, Nebula, Schwa/Stillwell, T-racks Max/Amplitube/SVX, etc. Gear: i7-2600k/4700HQ/16GB, RME Multiface/Babyface, Behringer X32, Genelec 8040, etc. :)
Last edited by Jack Winter; 08-15-2017 at 07:16 AM.
|