sysrqer wrote:ubuntuuser wrote:
Maybe some sort of 64/32 bit mixup.
It seems like a 64 bit wine program (lin-vst-server) is being run with a 32 bit wine prefix
Then you seemed to change to 32 bits so the 32 bit linvstconverttree would need the 32 bit libgtk-x11-2.0.so.0
sudo apt install libgtk2.0-0:i386
btw there is also a gtk3 version of linvstconvert/tree
Usually on a 64 bit system, I would use a 64 bit wine prefix.
Unfortunately, this seems to be problematic:
Code: Select all
sudo apt install libgtk2.0-0:i386
[sudo] password for alex:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) libpangoft2-1.0-0 [ i386 ] < none -> 1.38.1-1 > ( libs )
Broken libpangoft2-1.0-0:i386 Depends on libharfbuzz0b [ i386 ] < none -> 1.0.1-1ubuntu0.1 > ( libs ) (>= 0.9.30)
Considering libharfbuzz0b:i386 0 as a solution to libpangoft2-1.0-0:i386 1
Holding Back libpangoft2-1.0-0:i386 rather than change libharfbuzz0b:i386
Investigating (0) libpangocairo-1.0-0 [ i386 ] < none -> 1.38.1-1 > ( libs )
Broken libpangocairo-1.0-0:i386 Depends on libpangoft2-1.0-0 [ i386 ] < none -> 1.38.1-1 > ( libs ) (>= 1.28.1)
Considering libpangoft2-1.0-0:i386 1 as a solution to libpangocairo-1.0-0:i386 0
Holding Back libpangocairo-1.0-0:i386 rather than change libpangoft2-1.0-0:i386
Investigating (1) libgtk2.0-0 [ i386 ] < none -> 2.24.30-1ubuntu1.16.04.2 > ( libs )
Broken libgtk2.0-0:i386 Depends on libpangocairo-1.0-0 [ i386 ] < none -> 1.38.1-1 > ( libs ) (>= 1.28.3)
Considering libpangocairo-1.0-0:i386 0 as a solution to libgtk2.0-0:i386 9999
Reinst Failed because of libharfbuzz0b:i386
Reinst Failed because of libpangoft2-1.0-0:i386
Broken libgtk2.0-0:i386 Depends on libpangoft2-1.0-0 [ i386 ] < none -> 1.38.1-1 > ( libs ) (>= 1.28.3)
Considering libpangoft2-1.0-0:i386 1 as a solution to libgtk2.0-0:i386 9999
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies.
libgtk2.0-0:i386 : Depends: libpangocairo-1.0-0:i386 (>= 1.28.3) but it is not going to be installed
Depends: libpangoft2-1.0-0:i386 (>= 1.28.3) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Is there a way to convert a prefix to 64 bit?
I don't understand why this whole situation is a problem for reaper, I can use linvst with 32 bit prefix inside 64 bit renoise and ardour. Strangely, airwave plugins work in reaper, just not linvst.
On a 64 bit system usually the wine prefix would be 64 bit and then the 64 bit LinVst can run 64 bit and 32 bit vst's using the 64 bit wine prefix, but for the 64 bit LinVst to run 32 bit vst's multilib needs to be installed.
The 64 bit LinVst (that can handle 32 bit vst's) needs to be made using the 6432 makefile (the LinVst binary releases are made from the 6432 makefile).
With a 32 bit wine prefix on a 64 bit system, I'm not so sure about because I've never done that before, I suppose it would work with 32 bit wine apps but there might be some incompatibilities, I'm not sure.
The 32 bit only LinVst version is really for 32 bit systems like the old core duo systems etc that are 32 bit processors.
I'm not sure about what Airwave does as far as wine prefixes go, maybe install a hard coded link to the wine prefix using the utility it comes with, I'm not sure.
A 64 bit wine prefix is created by default on a 64 bit system when starting winecfg and it's called .wine or /home/user/.wine.
Someone can have different (or more than one) wine prefixes and have vst's within them and then when those vst's are loaded (using LinVst) then that wineprefix will be used (and all of it's dll overrides and settings etc).
Just say Delay.dll is installed in a 64 bit wine prefix called .wine2 in the VSTPlugins directory, so the path to the vst would be /home/user/.wine2/VSTPlugins/Delay.dll and then using linvstconvert it adds a Delay.so file in that directory ( /home/user/.wine2/VSTPlugins).
The daw's vst search path then needs /home/user/.wine2/VSTPlugins added to it and then when Delay.so is loaded in the daw the Delay.dll vst will be using the .wine2 prefix (and all of it's dll overrides and settings which can be different to another wineprefix say .wine or .wine3 or whatever).
Each wineprefix can have it's own windows environment (dll overrides etc).
Someone could use and setup a wineprefix for a game and also use another wineprefix for Office and also use another wineprefix for vst's or whatever (wine game players are pretty good at setting up wineprefixes).
With LinVst, a symbolic link outside of the wineprefix say in /home/user/vst can point to /home/user/.wine2/VSTPlugins or to /home/user/.wine2/VSTPlugins/Delay.so and the the daw can load the vst from /home/user/vst
So to make a long story short usually the default 64 bit .wine prefix gets used on a 64 bit system and LinVst would be the 6432 version that also needs multilib installed for 32 bit vst's.