Need testers for my x86 to x64 vst adapter
-
- KVRian
- Topic Starter
- 1159 posts since 26 Feb, 2006 from Fartland
Hi.
Is it the normal version or the 16 or 8 out version of K4?
Can you send me a test project that I can open with K4 player?
Is it the normal version or the 16 or 8 out version of K4?
Can you send me a test project that I can open with K4 player?
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(...)"
- KVRAF
- 5817 posts since 8 May, 2008 from ssssskipping ......... I left you there
Hey!, I bring a brand new opcode to the party. "Dispatcher opcode 19 failed".
It only happens in Kontakt 3.5 (XP32, Cubase 4), and only when I load some very big instruments (around 1GB) that come with loads and loads of scripting (this seems to be the key, as other equally big instruments don't trigger this).
Truth is that, after clicking "accept", everything finish loading normally and the instument and Kontakt seem to work fine, so it's just the warning that I'm experiencing.
It only happens in Kontakt 3.5 (XP32, Cubase 4), and only when I load some very big instruments (around 1GB) that come with loads and loads of scripting (this seems to be the key, as other equally big instruments don't trigger this).
Truth is that, after clicking "accept", everything finish loading normally and the instument and Kontakt seem to work fine, so it's just the warning that I'm experiencing.
-
- KVRian
- Topic Starter
- 1159 posts since 26 Feb, 2006 from Fartland
Hello.
Is it with Cubase5?
If yes, please email me with your user details and I'll send you a test version, I've been working on that issue.
Is it with Cubase5?
If yes, please email me with your user details and I'll send you a test version, I've been working on that issue.
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(...)"
- KVRAF
- 5817 posts since 8 May, 2008 from ssssskipping ......... I left you there
No, Cubase 4.
-
- KVRian
- Topic Starter
- 1159 posts since 26 Feb, 2006 from Fartland
Ok, it could work as well, I've had this reported before but with Cubase5. Drop me a line, I have something for you to try.
Thanks
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(...)"
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"
- KVRAF
- 5817 posts since 8 May, 2008 from ssssskipping ......... I left you there
OK!.
- KVRAF
- 5817 posts since 8 May, 2008 from ssssskipping ......... I left you there
I run Jbridge in a 32 bit enviroment to overcome the host's 2GB of ram limit. The problem that I had (it has been adressed by the version that umd sent me) affected only very complex Kontakt's instruments.Pinnsvein wrote:Isn't Kontakt 4 64bit already? I run it in Cubase 5 on Windows 7 without any problem...standalone wrote:OK!.
- KVRAF
- 5817 posts since 8 May, 2008 from ssssskipping ......... I left you there
Move the plugins to another location out of the host's view and point Jbridge to put the "fake" bridged versions in their place.Pinnsvein wrote:How do I point my host (Cubase in my case) to the JBridge folder? Is this done under preferences or do I use the scan function
-
- KVRer
- 17 posts since 15 Mar, 2010
I must be doing something wrong here...
I moved the original .dll files in the vst folder to another location and then I ran Jbridge again, directing the program to put the bridged versions into this folder. They did not show up there but on another location I created before instead. I tried to move them manually but Cubase did not recognize them. Do I need to rescan something?
I moved the original .dll files in the vst folder to another location and then I ran Jbridge again, directing the program to put the bridged versions into this folder. They did not show up there but on another location I created before instead. I tried to move them manually but Cubase did not recognize them. Do I need to rescan something?
-
- KVRian
- Topic Starter
- 1159 posts since 26 Feb, 2006 from Fartland
Hi.
Please make sure that Cubase is not also scanning the folder where the original .dll files are. Check the plugin scan paths to be sure.
Regarding the instruments recognized as fx's, try renaming the created .64.dll/64.txt files to .dll/.txt and re-scan them.
Please make sure that Cubase is not also scanning the folder where the original .dll files are. Check the plugin scan paths to be sure.
Regarding the instruments recognized as fx's, try renaming the created .64.dll/64.txt files to .dll/.txt and re-scan them.
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(...)"
