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

Hi!

I've been working on this for a few days, and by now it seems stable enough for public testing.

It's a little app to run 32bit vst plugins in 64bit hosts, usage instructions are included inside the program's folder.

I am interested in your feedback, what works ( if it works :hihi: ), what doesn't, where does it crash, how it crashes, etc.

Download:
http://jstuff.wordpress.com/jbridge

Changelog and other stuff available here:
http://jstuff.wordpress.com/

How to use:

After running the installer, use the jBridger utility ( Check the Start menu, in the program's folder ) and follow the instructions to prepare the plugins for being bridged.

Once again, credits for all the folks who have been helping me, specially Brad Robinson from TopTen Software who has been helping me a lot. :P

Thanks!
Last edited by umd on Mon Jan 18, 2010 5:42 pm, edited 39 times in total.
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

Good luck with this:-) I am not using a 64 bit os mostly because of vst problems.

Post

Thanks. Tagging for later, will check it out when I get home.
Regards, Mike
Image

Post

umd,

To answer your question from the other thread...there's not a demo of Cubase. One of the big gripes everyone has against Steinberg.

Anyhow, I'll look into it some more when I get home tonight.


Brian

Post

Not sure why this hasnt been jumped on yet - it could be bloody fantastic!!


Earliest I can play around with it is next week, will do so though. Cubase current VST bridge sucks so my fingers are crossed. :)





You might want to post this on some of the orchestral based forums, Soundsonline etc.... where most of the 64bit users are.

Post

Too bad there isn't a demo of cubase... :(

I've uploaded a new version that changes the way it processes internal midi data, hoping to fix the existing midi issues with vst arpegiattors. I bumped it to v0.1, let me know if there's any performance difference, i've left 0.05 there.

This can also be used for running x64 plugins in x86 hosts, or even for bridging x86 plugins with x86 hosts, to overcome the memory limit of a single 32bit process (not sure if in win64 each 32bit process can use around 3gb or if its 3gb for all the 32bit processes), I don't know if there's any interest for these variants, but if yes, let me know... it's just a matter of compiling. :hihi:
Last edited by umd on Wed Mar 11, 2009 4:31 am, edited 1 time in total.
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

So far, so good! I was very happy to have it work with Mach5 and Kontakt on a 2nd computer with FxTeleport. I haven't noticed any yet, but there any latency issues we shold be aware of?
K

Post

Cool!

Hum, afaik, there shouldn't be any extra latency, as it reads/writes the audio buffers like a native x86 plugin. But you guys tell me.

Only the cpu usage should be higher.
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

For me, the next step would be an installer where you specify the 32bit VST folder, and the installer searches for plugins. You would then select from the list the plugins you want to port to the 64 bit ap. The installer would ask for the 64 bit VST folder, and...voila...the installer copies the 32 bit VST's, adds and renames separate instances of your applets, and makes folders if needed.

I'd buy it!

Post

I do plan to save the user from having to copy and rename files around, but I want to test and finish the bridging engine first.

So for now it'll have to be like this. :oops:

For now, what you can do for faster updating is creating a *.bat file with these lines (replace with your plugin's name / proper path):

copy <plugin_name.64.exe origin> <plugin_name.64.exe destination>
copy <plugin_name.64.dll origin> <plugin_name.64.dll destination>
del "ThisPlugin.64.dll"
del "ThisPlugin.64.exe"
rename plugin_name.64.exe "ThisPlugin.64.exe"
rename plugin_name.64.dll "ThisPlugin.64.dll"

I am currently doing something like this.
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

Tried it with Reaper x64 ver. 2.56 and FXpansion DR 008 ver. 1.21, it didn't work. Reaper froze for a good 3 minutes, then got a message: "could not load the plugin".

I'm on Vista Ultimate x64 sp1.
No, that wasn't me.

Post

Tested with Tascams GVI.

Host: Reaper64.

Did not work. Got the messages:

could not contact the aux host

could not load plugin

freezes...

Too bad... I was excited to be able to access more ram with GVI than in a 32bit host.

Post

Ok, I'll check dr 008 later, the link is down currently. :P

samplemania, check if you renamed the files correctly. That's weird, it should at least find the auxhost exe.
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

Wow this is awesome news :D
I am going to install Windows 7 64bit and Orion so i can test it for you :D

Post

umd wrote:Ok, I'll check dr 008 later, the link is down currently. :P

samplemania, check if you renamed the files correctly. That's weird, it should at least find the auxhost exe.
I did.

GVI.64.dll
GVI.64

I did also test samplelord (demo).

Results are the same.

Maybe you should download ReaperX64 for testing.

http://reaper.fm/files/2.x/reaper256_x64-install.exe

Post Reply

Return to “Instruments”