- #JBRIDGE COMPATIBLE WITH STUDIO ONE 3 INSTALL#
- #JBRIDGE COMPATIBLE WITH STUDIO ONE 3 64 BIT#
- #JBRIDGE COMPATIBLE WITH STUDIO ONE 3 32 BIT#
#JBRIDGE COMPATIBLE WITH STUDIO ONE 3 32 BIT#
Anyway, the bridged 32 bit works just fine now in all my DAWs.
#JBRIDGE COMPATIBLE WITH STUDIO ONE 3 64 BIT#
When I attempted the 64 bit version, I looked under all the options Studio One offers … Flat Folder Vendor Files and no Alchemy.īelieve me I would have accepted the 64 bit version if I could. In the vendor list, it is in a folder called Camel Audio. I created a 64 bit jbridged version it did turn up in Studio One 4 as "VST Alchemy.64" in the instrument listing.
#JBRIDGE COMPATIBLE WITH STUDIO ONE 3 INSTALL#
I tried the 32 bit-only install just to see if there was a problem with the 64 bit and the 32 bit did not show up. I tried several times with full uninstall and reinstall and always had the same problem. In Sonar, you can actually identify vsts that failed the scan, the 64 bit Alchemy was listed there. When I did after installing the 64 bit, Studio One did say Alchemy dll failed. Studio 4 (the latest) when you boot it scans the vsts and looks for new ones. Sonar and Reaper did not report a problem, but did not put the vst in the available lists. I just did not reinstall on my new computer until recently and had this problem. It was on one of my older music computers so probably about then although since I did get the last download before Camel dropped support, I do know it worked fine on the older computer.
![jbridge compatible with studio one 3 jbridge compatible with studio one 3](https://rekkerd.org/img/201212/presonus_studioone.jpg)
I'm not sure how long ago I originally installed Alchemy. For the first failed install, I selected the 64 bit. The install software offered the option to install both 64 bit and 32 bit. That is the version I reinstalled v155.0. I'm not sure how Unify managed to accept the vst when my DAWs did not, but hey Unify is miraculous!!! With Alchemy loaded, I was then allowed to point to the Sound Files and scan the presets.įurthermore strangely, now my DAWs have Alchemy in their vst lists. However, it still allowed me to load Alchemy. Whoa … Unify seemed to like it although it said it needed to find the Sound Files as part of the processing, but it did not respond to the response to the query properly. I did this and even though JBridger had not trouble with it, the vst still failed to appear in my DAWs.īeing a hard headed problem solver, I decided to try the 32-bit Bridged vst drop into Unify. Hmmm I said, well there is also a 32-bit version in the install and I could use JBridger. Uninstall and several reinstalls did not solve this problem.
![jbridge compatible with studio one 3 jbridge compatible with studio one 3](https://2.bp.blogspot.com/-YAgDubTTNeU/XnuCMRTl_4I/AAAAAAAAWcs/5EvYJpC6YQsvMuGME7hp0G_5PHbvT4ZiQCLcBGAsYHQ/s1600/Jbridge%2BFull%2Bversion.png)
I tried dropping the dll in Unify, but it said it did not like it. Studio One reported a problem trying to initialize it and did not show Alchemy in its list of instruments. I installed the 64-bit version and although it seemed to install properly, Sonar and Reaper did not offer the vst in the vst lists.
![jbridge compatible with studio one 3 jbridge compatible with studio one 3](https://cdn.verasia.eu/9102-big_default_2x/jbridge-for-beginners-vol1-includes-2-cd.jpg)
Also, there is no support for Windows now.īut I had the installs and I figured, it should work. However, as some might know, Camel Audio sold Alchemy and the newer versions only run on a Mac. I found it and decided to install it on my newest music computer. I had a copy of Camel Audio's Alchemy which I never installed on my newer computers. Unify actually helped me tonight along with the JBridger app I just purchased a few days ago to allow me to use 32-bit vsts.