Kontakt x64

[stephenjw]

Trying Bidule with Kontakt x64 (hoping to be able to use more memory). (x32 works fine.)

Kontakt x64 dll in plugin folder. Bidule "can't load Kontakt etc" makes some excuse "invalid byte at line 1". Bidule x64 uninstalled, reinstalled, still the same.

Any tips anyone?

[seb@plogue]

Is that at scanning time, when you attempt to add an instance or when you load a .bidule containing Kontakt instances that work in 32bit?

[stephenjw]

Hi Seb

It's
a. when I try to run Bidule x64, newly installed. Doesn't find it at startup, or when I scan for plugins.
or
b. Error report if I double-click on the Kontakt4 dll (definitely x64 version).

(x86 is installed and working - can you have both versions installed?)

best wishes

(Windows 7, lots of RAM)

[stephenjw]

Since then on several occasions Bidule x86 has also failed to find Kontakt - same symptoms. Rebooting the PC solved it (until the next time?!)

[seb@plogue]

There is no problem with having both x86 and x64 versions of Bidule installed.

I haven't received any bug reports about something similar. Which version of Kontakt ?

Could you double-check that the .dll you have in the VST folders Bidule uses are the correct version?
(IIRC, there is a VST subfolder in your Kontakt install folder where the plugins are always copied/updated,
I don't recall if the update process for Kontakt will check for/see all the copied .dll files in other folders/drives)

[stephenjw]

Kontakt version is 4.2.4 (x64)
in folder C:\Program Files\Plogue\Bidule\VSTPlugins (I moved it there manually)

When it first didn't work, I uninstalled Ploguex64. There was still a Plogue folder in Program Files so I tried to delete it. Foolish move! thanks to the bizarre convoluted hidden structure of the Windows 7 filing system, it started to delete 1.5Gb of files, including a whole lot of Kontakt stuff. Fortunately I managed to stop it before it did massive damage. I don't know if this was relevant - the problem was there before.

It's not vitally important to have x64 but any suggestions would be very welcome.

[seb@plogue]

Does the Kontakt x64 standalone works fine?
Do you have any other x64 host, does Kontakt x64 loads fine in there?
I'm wondering if there is not something in the Kontakt db/startup file that could cause that error.

[stephenjw]

Standalone Kontakt4 works fine.

I am now regularly getting Bidule x86 also not recognising Kontakt4, though this problem seems to have been solved by un-installing Bidule x64.

I have reinstalled Bidule x64 a few times, and also Kontakt - no improvement with x64.

Since Kontakt standalone x64 works fine, I can program stuff there and survive without Bidule x64!

Thanks for your input. Best wishes

[seb@plogue]

I can't see what could be causing the error, the message is coming from Kontakt as far as I can tell. That is why I was wondering about standalone and other hosts. The only thing that could possibly cause this would be the Use Regional Options preference being enabled, but I don't recall this causing issue on Windows before.

[stephenjw]

It's the VST plugins path. For some reason Bidule was looking in Program Files (x86)\Plogue\Bidule for plugins. Correcting this has solved the problem.

(I might just mention that it's a complete fluke that I could see this: the display only lets me see a tiny part of the current path - fortunately it was the important bit!)

Thanks for excellent support as always

[stephenjw]

Actually it hasn't sorted the problem, and I am running into severe problems having with both versions in one PC.

If I change the VST plugin folder for one version, it changes it in the other version too.

I did get x64 to work with Kontakt4 and even saved a layout. However I cannot now get X64 to recognise K4 even when I have directed it to the correct plugin folder. (I have double checked all the dll files etc). I'm not keen to experiment in case I get the same problem with Bidulex86.

There must be some resource that is shared by the 2 versions. As things are, I would not recommend having both versions in the same computer at the same time.

(Strange things have been happening to the windows since this started, too: the main Bidule screen will not come to the front when it is in focus - it can be moved about behind the subsidiary bidule windows - and when it is minimised the subsidiary bidule windows disappear too. Adjusting "floating frames" makes no difference. Hard to see how this can be connected)

[seb@plogue]

If I change the VST plugin folder for one version, it changes it in the other version too.

Are you running an old version of Bidule? You should be able to have different VST folders for 32 and 64bit, the 64bit version will use the vst path of the 32bit version if there is none set for the 64bit one.

Adjusting "floating frames" makes no difference.

floating frames will only be enabled the next time a window is created, "closing" a window hides it, double-clicking on a bidule will show it again without recreating it from scratch (I'm simply stating this in case it explains "makes no difference".

[stephenjw]

I am using v9724 for both x32 and x64.

What happens is completely reproducible.
1. I close Bidule x32 with Kontakt (working perfectly)
2. I open Bidule x64 - wont recognise Kontakt. Its VST folder is set to the x32 folder.
3. I change this to the x64 folder, where 3 64-bit Kontakt4 dlls are stored. Still won't recognise Kontakt (this is a new problem - it did work before).
4. I close Bidule x64
5. I re-open Bidule x32, now its VST folder is set to the x64 folder.
6. I correct the VST folder and now x32 + Kontakt works fine (so far!).
7. Go to (1.)

I don't vitally need x64 but I wonder if other Bidule users are successfully running both versions on the same computer?

The window phenomenon is no more than an irritation. (The main Bidule window functions perfectly well, but is hidden behind all the subsidiary bidule windows even when it's in focus, and minimising it minimises all the subsidiary windows too.) I only mention it because it also is a new phenomenon which seemed to start around the same time as the x64 business.

(I disabled Regional Options, whatever that is, and it's not that.)

Don't spend hours on it if you think it's some weirdness in my PC. It's not that important.