Need testers for my x86 to x64 vst adapter

[umd]

umd,

I will try this tonight and get back to you. Kontakt 3 works great in Cubase (x86) and it works fine in every host I've tried.

Don't sweat it too much because they're supposed to release a 64-bit version of it sometime in the near future. I was just trying to get a head start.

That's ok, it may be something that can fix issues with other plugs. The problem is that there's no demo of Cubase available.

Hi! I want to try this out with Cubase x86/32bit on Vista x64 so I've installed the Jbridge-setup and the "vc2008 redistributables", both 64- and 32-version. Copyed the "plugin_name.32.dll"-file to my Cubase/VST-folder and re-named it after the VST I want to use. All things I was supposed to do. Then opening Cubase and my VST (East west SO Gold PLAY) but it opened as usual, not through the Jbridge/auxhost. What could be wrong? Any ideas? Would be awsome to get this to work.

/Joseph

I am wondering if Cubase ignores duplicated plugins, if it's the case, I can only think of a workaround for it (which will be a bit more messy to use).

[SimSam]

umd,

I tried the new .40b beta the results are the same -- crash.

This version does allow the plugin to load and show up within Cubase but within seconds the program goes white and stops responding. Or it goes white as soon as I click on any part of the Cubase interface.

When I close Cubase, Kontakt stays open. And I can actually load instruments into it. Odd.

This behaves the same with Kontakt 2 Player as well.

Brian

[umd]

Ok, thanks for the info.

Another thing, Cubase has its own 32 to 64 bridging, right? Is it active by default?

[SimSam]

Yes, umd, it is active by default. So I tried something...

I killed the VSTbridge after I started Cubase and then tried to load a 32-bit VST using your wrapper.

Kontakt still loaded but this time I got several errors that said VSTBridge had lost connection to the plugins and I should reload an older version of the project.

I also noticed that even though I killed the VSTBridge process it restarted when I loaded one of the VSTs using your bridge. It had always been my suspicion that your wrapper and Cubase's built-in one were conflicting.

[umd]

Let's try something in the next release...

I'm going to add another dll that can be in a different folder than the plugin, but reads its path from a text file or something.

Then you point Cubase to it, but not to the folder where the 32bit plugin is.

I'll put something up in a while.

[SimSam]

Okay, I'll look for it but I may not be able to test it until tomorrow morning or tomorrow night depending on when you post it.

[johncarter]

I'll also do some tests wednesday. So far I only bridged 32bit plugins to 32 bit host . But not 32 bits to 64 bits host.

Thanks for that great thing umd.

[jbone1313]

Why the thirty minute time limit on version .40?

[umd]

Okay, I'll look for it but I may not be able to test it until tomorrow morning or tomorrow night depending on when you post it.

I'll also do some tests wednesday. So far I only bridged 32bit plugins to 32 bit host . But not 32 bits to 64 bits host.

Thanks for that great thing umd.

np, thanks.

Why the thirty minute time limit on version .40?

It always had it. This was planned to be a commercial release from the beginning, however, nothing expensive, just a few bucks and with a special introductory price.

[jbone1313]

Cool; you definitely deserve to get paid once its nice n' stable.

[mvaillo]

Dear umd,

This is great, asbolutely outstanding!
I'm so glad. It works fine for me, but I'm not yet using any 32 to 64 or viceversa plugin conversion at this time.

Here's my setup:

WinXP64 Pro (Intel Core i7, 2.66Gz, 6Gb RAM).
Sibelius 5 + Console 1.6.2 (beta) as a host through Midi Yoke.
In it I use only 32bit plugins as Kontakt3 (about 3 or 4 instances) and some EWQLSO VST's like Gold XP, Brass, Wws and Perc. (not the new PLAY instruments).

A few crashes in the beginning (no VSTs crashed, it was Console, however sometimes happens...), now seems fine. Ideal for saving the RAM limit for 32bit process. The limit now is the system and RAM instaled.

If console goes x64 someday (as I exepct K3 and other VST's) I'll try your tool properly. For now, it works great for me! A real quantum leap

Thank you!

marc

[umd]

I don't know if it will be nice ( I suck at designing gui's, look at my midi plugins gui ), but I would sure like it to be stable.

Thanks for the info, mvaillo.

New version out, some significant improvements in the way of using. You can now bridge x86 or x64 plugins without worries ( please note that you still need to use the plugin_name.xx.dll that matches your host's architecture though ), it will detect the plugin's architecture automatically and load the correspondent auxhost.

Cubase x64 users, please try the following:

- update your plugin_name.xx.dll's (other users don't need to do it).
- Instead of placing plugin_name.64.dll next to your 32bit plugin, put it in another folder, then create a *.txt file next to it with the same name, and put inside it the path of the 32bit plugin, quoted.
- Point cubase to this folder (and exclude the folder where your 32bit plugin is).

i.e.:

ThisPlugin.64.dll
create
ThisPlugin.64.txt
put inside it something like this:
"c:\Program Files\VstPlugins\ThisPlugin.dll"
(*don't* forget the quotes)

Thanks.

[SimSam]

I will try this tonight (if I don't get home too late.)

[SimSam]

umd,

Okay I tried version .44 in Cubase 64. This time when I try to scan the folder to add the dll I am met with this error.

File not found or unsupported IMAGE_FILE_MACHINE_x

After that Cubase doesn't even list your plugin.

(And I followed the directions exactly.)

Brian

[jbone1313]

I love the always on top action!

One more thing: If you move the plugin to another monitor, would it be at all possible to have it remain on that monitor when its opened again?

In REAPER, plugins normally work like that.

-Thanks