I suspect that cubase doesn't like duplicated plugs. Unfortunaly there's no demo of it for me to investigate that.
Need testers for my x86 to x64 vst adapter
-
- KVRian
- Topic Starter
- 1159 posts since 26 Feb, 2006 from Fartland
Try method 2 (check the readme pdf) and see if it's any different.
I suspect that cubase doesn't like duplicated plugs. Unfortunaly there's no demo of it for me to investigate that.
I suspect that cubase doesn't like duplicated plugs. Unfortunaly there's no demo of it for me to investigate that.
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(...)"
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"
-
- KVRist
- 103 posts since 24 Aug, 2005
Well, method #2 isn't going to work - you say not to "point the host to where the original vst is". Well, if you don't point the host to where the original vst is, then the host is still only going to see the .32.dll, no? The point here is to get the host to see both the .dll AND the .32.dll.
Cheers.
oh, btw - you wrote in the pdf:
"point the host to the folder where you putted these files..."
Heh - putted should be put.
Cheers.
oh, btw - you wrote in the pdf:
"point the host to the folder where you putted these files..."
Heh - putted should be put.
-
- KVRian
- Topic Starter
- 1159 posts since 26 Feb, 2006 from Fartland
No. The objective of method #2 is precisely to "hide" the original dll from the host. That's why you add a *.txt with its path instead.
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(...)"
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"
-
- KVRist
- 103 posts since 24 Aug, 2005
Right - but I don't want to hide the original .dll from the host. I want the host to see the original .dll - I want the host to see BOTH. Or am I not understanding something here?
-
- KVRian
- Topic Starter
- 1159 posts since 26 Feb, 2006 from Fartland
I was talking about the plugins that don't show at all, or just one of the dll's. I was interested in knowing what would happen with method #2.
Anyway, I don't know how Cubase handles duplicated plugins (or if it has any issue with that at all), so I certainly can't be of much help. I don't have any experience at all with Cubase.
The only information I have on it comes from the user's feedback, but I don't want to be bothering people all the time to test stuff for me.
Eventually all the information gathered will converge to some conclusion ( I hope ).
Anyway, I don't know how Cubase handles duplicated plugins (or if it has any issue with that at all), so I certainly can't be of much help. I don't have any experience at all with Cubase.
The only information I have on it comes from the user's feedback, but I don't want to be bothering people all the time to test stuff for me.
Eventually all the information gathered will converge to some conclusion ( I hope ).
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(...)"
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"
-
- KVRist
- 103 posts since 24 Aug, 2005
Ok, I just tried the txt file method - i can't get that to work.
Seeing as though you say NOT to point the host to the folder where the original VST is, I moved StylusRMX.dll out of C:\Program Files (x86)\Steinberg\Cubase 4\VSTPlugins (where Cubase is going to point to by default) and put it in C:\Temp.
In C:\VSTPlugs I put plugin_name.32.dll, and created a .txt file in the same folder and called it plugin_name.32.txt. The text in that text file reads as follows:
"C:\Temp\StylusRMX.dll"
I launched Cubase, and added C:\VSTPlugs as a VST folder. But Cubase does not see the RMX dll file.
Did I do something wrong?
Seeing as though you say NOT to point the host to the folder where the original VST is, I moved StylusRMX.dll out of C:\Program Files (x86)\Steinberg\Cubase 4\VSTPlugins (where Cubase is going to point to by default) and put it in C:\Temp.
In C:\VSTPlugs I put plugin_name.32.dll, and created a .txt file in the same folder and called it plugin_name.32.txt. The text in that text file reads as follows:
"C:\Temp\StylusRMX.dll"
I launched Cubase, and added C:\VSTPlugs as a VST folder. But Cubase does not see the RMX dll file.
Did I do something wrong?
Last edited by RiffWraith on Tue Mar 31, 2009 1:30 am, edited 1 time in total.
-
- KVRist
- 103 posts since 24 Aug, 2005
Well, it handles duplicate plugs of Trilogy, Kontakt2, Ivory, Hypersonic just fine.umd wrote:Anyway, I don't know how Cubase handles duplicated plugins (or if it has any issue with that at all)
-
- KVRian
- Topic Starter
- 1159 posts since 26 Feb, 2006 from Fartland
Don't see anything wrong... Thanks for testing.
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(...)"
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"
-
- KVRian
- Topic Starter
- 1159 posts since 26 Feb, 2006 from Fartland
v0.65 is out. 
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(...)"
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"
-
- KVRian
- Topic Starter
- 1159 posts since 26 Feb, 2006 from Fartland
Ok, but until v1.0, you can discard the previous version.
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(...)"
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"
-
- KVRer
- 9 posts since 26 Mar, 2009 from NYC
Hi I'm trying to use Jbridge in conjunction with Kontakt2 within Overture4 http://www.geniesoft.com, Overture scans the plugin but it it doesn't add it to the list of Vst plugin. Any suggestions. There is a demo available for download to test.
-
- KVRian
- Topic Starter
- 1159 posts since 26 Feb, 2006 from Fartland
Hi!
I've tried the demo here with Kontakt3, worked fine. Is it the only one that doesn't work there?
I've tried the demo here with Kontakt3, worked fine. Is it the only one that doesn't work there?
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(...)"
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"
-
- KVRer
- 9 posts since 26 Mar, 2009 from NYC
Kontakt2 is the only one that I have tried it with so far. When I get home I will try it with Kontakt3 and see if it will work. I just want to make sure that I'm setting everything up right. I'm using XP64, I installed the program it installed under the regular programs not the (X86) I copied the .32dll and installed in the vst folder that Overture points to and renamed it Kontakt2.32.dll. Initally when Overture scanned the Vst folder I got the message "JBridge Program not found" so I copied the JBridge folder from the "Regular Program" folder and put it in the (X86)folder and restarted Overture. This time it scanned the plugin with no problem but when I go to the VST pull down it does not show anything other then the originial Kontact2 plugins and if I open any of them they open normally without the JBridge. Did I install this right ? If not what did I do wrong?
-
- KVRian
- Topic Starter
- 1159 posts since 26 Feb, 2006 from Fartland
If you move the program's folder it won't work for sure, as the bridging dll's query the registry for the path you specified during installation ( by default it goes to you x64 program files folder, no problem with that ).
Ah, I just experienced your problem with kontakt 3 as well here. Not sure how Overture keeps track of the scanned plugins.
What I did to solve it was deleting the plugin_name.32.dll from the folder, open Overture again, let it scan the folder, closed it, added plugin_name.32.dll back again and renamed to Kontakt 3.32.dll and it works fine again.
If it doesn't work, try ( the messy ) method2.
Ah, I just experienced your problem with kontakt 3 as well here. Not sure how Overture keeps track of the scanned plugins.
What I did to solve it was deleting the plugin_name.32.dll from the folder, open Overture again, let it scan the folder, closed it, added plugin_name.32.dll back again and renamed to Kontakt 3.32.dll and it works fine again.
If it doesn't work, try ( the messy ) method2.
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(...)"
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"
