JBridge is a bit wrapper which enables you to run 64 bit VSTs in a 32 bit host, 32 bit VSTs in a 64 bit host, and 32 bit VSTs in a 32 bit host, breaking the 4GB RAM barrier. Each VST is run as another process outside the host in Windows so uses it's own RAM. Since each VST runs in its own process, if a VST crashes it doesn't take the rest of your project with it.Why would you want to use it in Mixcraft?
1. There is a VST you want to use which only exists in 64 bits
2. You are running out of RAM with the 4 GB Mixcraft allows as a 32 bit host.
3. You use a lot of badly-written freebie VSTs that crash & burn your project.
4. (Future Application) After Mixcraft goes 64 bit, you will still be able to use your 32 bit VSTs in it.Installing jBridge:
Installation directions are on this page:http://jstuff.wordpress.com/jbridge/jbridge-troubleshooting/782-2/
Follow them religiously, setting the listed programs and Mixcraft to be 'run as administrator' and turning off UAC.Using jBridge:
1. Again read & follow the instructions.
2. Keep your VSTs to be wrapped in a separate folder from the rest of your VSTs, copying
them from their original locations.
3. If you have another version of the VST running in Mixcraft, rename the VST you are about to wrap. My first experiment was with Kontakt 5. I can run Kontakt 5 as a 32 bit VST in Mixcraft. It is also installed as a 64 bit VST elsewhere, so when I copied the 64 bit dll to the 'to be wrapped' folder I changed the name to Kontakt 5 64 so there wouldn't be conflicts in the Mixcraft file system between the 32 and 64 bit versions. EDIT: It now seems to be necessary to remove the 32 bit version of the VST so Mixcraft can't see it as even a different name still produces a conflict. See EDIT 1 below.
4. It is best to set the .32 and .64 extensions to be off when asked by jBridge. Mixcraft didn't seem to recognize the wrapped VST with that extension AND when I removed it manually Mixcraft went into a cascade, dancing with 100's of instances of auxhost until I shut the computer down.
5. Make sure Mixcraft can see the folder where you had the wrapped VSTs installed.
So now the wrapped version of Kontakt is up & running in Mixcraft. I so far have loaded 6 tracks and all is running fine. Kontakt takes a little longer to load this way but that is the only difference performance wise I have noticed so far.
In Task Master, Mixcraft and it's 6 Kontakt tracks (listed in TM as Auxhost) use memory like this so far:
I'll gradually keep adding tracks until something happens
If you are interested in using jBridge and pretty much understand what I have posted in this thread, you can get jBridge here: http://jstuff.wordpress.com/jbridge/
It is in Euros, but works out to <> CAN$20.EDIT 1:
OK I've added some more tracks and moved in & out of Mixcraft and rebooted a couple of times. Very occasionally the instrument disappears from one of the tracks with accompanying error messages about Mixcraft not being able to find the instrument and a dialog to sent data to j. So far the fix has been to isolate the old 32 bit Kontakt VST so Mixcraft can't see it. Then no problems AND Mixcraft automatically replaces Kontakt 5 with Kontakt 5 64 VSTs in existing projects.
At 20 tracks of Kontakt, Task Manager reads 7.18GB of RAM used for both Windows and Mixcraft/Kontakt. Occasionally there still is a loading problem for the wrapped VST but restarting Mixcraft has solved it so far. Only once I had to restart the computer to recover the instrument. I want to get to at least 10GB of RAM use for a proper test.
At 45 tracks of Kontakt I reached 10.2 GB usage with Mixcraft still using its 48229K, all the rest being used by bridged VSTs. For those interested, the 3930K peaked at 20%. At times there is still a failure to load instruments, but after mucking around with it, it seems always to happen after lots of edits & saves in Mixcraft and is almost always cured by restarting Mixcraft or, failing that, restarting the computer. IMO this is a minor issue since there is an easy work-around. This behavior has also been echoed several times in the EWQL forums, but IMO is a jBridge issue, not an issue with the DAWs or VST engines.EDIT 2:
The test project is over 50 tracks now. Since enabling "use existing auxhost" the RAM usage has dropped but with a few other wrinkles. I've added some unwrapped VSTs inside Mixcraft and a couple multi-channel instances of Kontakt, All running well, EXCEPT when I try to change an instrument in the single instances of wrapped Kontakt, I am unable and Mixcraft crashes. What I found works is to load a different VST then reload Kontakt and the new instrument and all is fine.To sum up:
It works but not perfectly and definitely not for beginners. I intend to keep using it though as the issues are minor.Idiosyncrasies:
1.[Edited] Tracks containing wrapped versions of Kontakt may appear to lose one or more instruments upon reload. DON'T PANIC. THEY ARE STILL THERE. If this happens:I exchanged emails with J on this and he suggested enabling "use existing auxhost" in the jBridge banner below the Kontakt GUI, pressing the 'settings' button.
This is done on a per plugin basis. It creates one big auxhost rather than a small one for each instance of Kontakt. There has not been one load failure since I enabled this.
If this doesn't work:
a. Immediately quit the project as soon as loading is finished. DO NOT EDIT OR SAVE ANYTHING.
b. Restart Mixcraft. If problem is not fixed......
c. Restart Computer.2. Duplicate track command doesn't work consistently when trying to duplicate tracks using (wrapped) Kontakt.
3. To change instruments in a single instance of wrapped Kontakt you must first replace Kontakt with any other VST then reload Kontakt with the new instrument. This behavior does not occur in a multi-channel instrument, only single instances of Kontakt.
My next acquisition is EWQL CCC. I intend to use wrapped 64 bit Play and will run the same test & post results on this thread.