I switched from win7 32 to win7 64 bit.
As expected, Mulab runs fine,
but the 64bit versions of vst-plugins are disabled immediatly after adding in vst-plugin-manager, 32bit version is ok (e.g. Kontakt-player).
Is this because mulab is written for 32 bit only ?
only 32bit vst plugins ?
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Yes, MU.LAB currently still is 32 bit only.
I wonder: Are there any VST plugins that only exist in a 64 bit version?
I wonder: Are there any VST plugins that only exist in a 64 bit version?
-
- KVRist
- Topic Starter
- 152 posts since 15 May, 2009 from Germany
Ok,
I thought it would depend on the os-version, but seems it depends on the host-version.
For kontakt4 and ewql also 32 bit versions available, no problem.
I thought it would depend on the os-version, but seems it depends on the host-version.
For kontakt4 and ewql also 32 bit versions available, no problem.
Everything should be made as simple as possible, but not simpler!
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
It depends on the type of address space the VST DLL is loaded into. A 32-bit host can - with support - use 64-bit VSTs and vice-versa. Just it needs bridging between the two types of address space. A 64bit OS runs a 32bit app in a 32bit address space. The 32bit app can load 32bit DLLs into that address space no problem. But it can't "naturally" get to 64bit. I don't know a lot about bridging but I imagine there's some overhead in passing data between the address spaces whereas it's usually in shared memory.Eggu wrote:I thought it would depend on the os-version, but seems it depends on the host-version.