Need testers for my x86 to x64 vst adapter

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS
jBridge jBridgeM

Post

SimSam wrote: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
Hum, just re-tested it, it works fine, on xp64 and windows 7, I need to change that message to be more specific.
Did you added the quotes? It won't work without them.
jbone1313 wrote: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
It should be possible to do it... give me a few days, I'd like to check first if it's possible at all to place the gui inside the native gui's window. ;)
Free MIDI plugins and other stuff:
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"

Post

Sweet! I have faith in you, umd.

When can I pay to have the time limit removed? ;)

Post

I'm counting on putting this out in a couple of weeks. :D
Free MIDI plugins and other stuff:
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"

Post

Yes. The quotes are there. I created a folder called 'JBridge test'. In it I have these two files:

Kontakt 3.64.dll
Kontakt 3.txt

The body of the text inside the Kontakt 3.txt file is:

"C:\Program Files (x86)\Steinberg\VstPlugins\Kontakt 3\Kontakt 3.dll"

I pointed to this folder in the plugin manager in Cubase, updated and got the error. The spaces in the folder names come exactly from the explorer window.

Is all this correct?

Post

Don't see anything wrong there.

Is your kontakt 3.64.dll the latest bootstrap version?
To use the *.txt feature, you'll need to copy the new plugin_name.64.dll from the program's folder over again ( for versions below v0.44 ).
Free MIDI plugins and other stuff:
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"

Post

I'm sure it is. I deleted the other folder first before running the installer for .44. Then used that dll and built a new folder.

Tonight I'll install it on one of my XP64 satellite system and try running it under Nuendo 64. Maybe it's just a Cubase thing.

Post

That's indeed weird.

I did tried renaming my files to those exact names and it worked.

Let me know if you find anything.

Thanks.
Free MIDI plugins and other stuff:
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"

Post

Hmm so far I have the same problem as Sim Sam.

Tried many things, didnt forget the quotes in the .txt , checked the .txt path file, tried to copy the original .dll plugin file to c:\ to see if it wasnt a problem of space in the path. But didnt work.

What's weird is Cubase 64 bit seems to see the jbridge.64.dll as a "FX" vsts and not vst instruments.
When I try to put the original dll plugin file in the same folder as the pluginname.64.dll , Cubase still see the bridge dll as a FX VST and not VST instruments. And Cubase sees the original DLL as a 32 bit vst so when you launch it it uses the VSTbridge of Cubase and not the jbridge.

Post

the main problem is clearly the fact that Cubase studio 4 doesnt take into account duplicated plugins

Post

Do the same files work with Reaper?
Free MIDI plugins and other stuff:
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"

Post

Ok now it works , I think I know why /


For a weird reason , I named the plugin-name.64.dll , like :

01EWStrings XPVST.dll.64.dll

I added a ".dll" ( the first before 64 ) which wasnt supposed to be there.

Check that Sim Sam. that message "File not found or unsupported IMAGE_FILE_MACHINE_x " is a problem of wrong path file probably

Post

I did some tests .

Bridging 32 bits plugins to 64 bit host. Doing a test with a relatively fast strings staccato cue. 7 tracks , on each track strings short notes ( with Round Robin *8 , platinum strings ) , around 200 voices playing constantly.

My CPU : core 2 DUO E4200 , 4 gb of ram, XP64 , delta audiophile 24/96 as sound card.


CPU perf : average 49 percent.


I did the same test, same short cue, but with the regular 32 plugins and cubase 4 32 bits : CPU perf : average 40 percent
With 32 bit to 32 bit bridge : 40 percent
There's no difference between 32 bit to 32 bridge and using 32 plugins without the bridge , except with jbridge you can overcome the ram limit ;)

Really great program. I think it's close to become usable professionnally.
Could you just add an option so that we can de-activate the "always on top" ? :D

Post

umd (and John),

I checked the file name and path and it's correct. But after that error mine I noticed mine are showing up in the VST FX not the VSTi's as well. I don't have it misnamed either.

Anything else you did to get it working, John? Because obviously mine is behaving like yours was, too. And this btw in Cubase 64 on Vista64, and Nuendo 64 on XP64. Checked it in both and even had to change paths.

(Can't wait till 64-bit is the standard so I can quit typing '64' in everything.)

Brian

Post

johncarter, that's great news. :) Glad you got it going.
Yes, actually I need to change the current "always on top" implementation, it doesn't work right with some plugins that pop up messages on initialization.

SimSam, your bridged plugins should appear exactly as they would in a native host, as that information comes from the plugin itself only. Could you check if it happens in other host as well?
Free MIDI plugins and other stuff:
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"

Post

Simsam , could you make screenshots of your plugins directory, and also of your .txt textfile , just to check if the path are good. Sometimes we dont see something very evident!!

Post Reply

Return to “Instruments”