Notifications
Clear all

How Unify came to my rescue.

5 Posts
3 Users
3 Reactions
2,120 Views
(@larry-ludwick)
Trusted Member
Joined: 4 years ago
Posts: 78
Topic starter  

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.

 

I had a copy of Camel Audio's Alchemy which I never installed on my newer computers. I found it and decided to install it on my newest music computer. However, as some might know, Camel Audio sold Alchemy and the newer versions only run on a Mac. Also, there is no support for Windows now.

But I had the installs and I figured, it should work. 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. Studio One reported a problem trying to initialize it and did not show Alchemy in its list of instruments. I tried dropping the dll in Unify, but it said it did not like it.

Uninstall and several reinstalls did not solve this problem.

Hmmm I said, well there is also a 32-bit version in the install and I could use JBridger. I did this and even though JBridger had not trouble with it, the  vst still failed to appear in my DAWs.

Being a hard headed problem solver, I decided to try the 32-bit Bridged vst drop into Unify. 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. However, it still allowed me to load Alchemy. With Alchemy loaded, I was then allowed to point to the Sound Files and scan the presets.

Furthermore strangely, now my DAWs have Alchemy in their vst lists.

 

I'm not sure how Unify managed to accept the vst when my DAWs did not, but hey Unify is miraculous!!!

 

 


   
DOMINIQUE reacted
Quote
(@leszek-1953)
Member
Joined: 5 years ago
Posts: 442
 

@Larry Ludwick

 

You're right. Unify is great.

 

Les..


   
DOMINIQUE reacted
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4437
 

I'm not quite sure what happened, but I'm happy it worked out for you!

I should note, however, that you do not have to use jBridger for Unify, because it has built-in support for jBridge. jBridge is the basic 32/64 bridging software; jBridger is a program included with it, which creates separate 64-bit "wrapper" plug-ins for 32-bit plug-ins. Unify doesn't need the wrappers, though your other DAWs might.


   
ReplyQuote
(@larry-ludwick)
Trusted Member
Joined: 4 years ago
Posts: 78
Topic starter  

@getdunne

Since I jump through 3 DAWs constantly, I did need to use JBridger. Reaper does not need it, but Sonar and Studio One did not recognize any of my 32 bit plugins. I have very few, but when I tried HG Fortune plugins, I found I needed it.

Very weird that Unify helped me out. The only thing certain was one) the 64 bit version of Alchemy would not work in any of my DAWs or in Unify. The 32 bit did not work directly in my DAWs even when I created at 64 bit wrapper. However, Unify was the only launcher that showed me the message about pointing to the Sound Sources. Weird but wonderful.

In fact, I went to Sonar which allows you to scan vsts in its own way. There was an option to scan vsts that failed to process through their scanner. It indicated Alchemy was one that had failed. But then who knows about this older vst, 2015 was when Camel Audio screwed its users by selling out its software to a company that would no longer support Windows.

 

 


   
mj_prod reacted
ReplyQuote
(@larry-ludwick)
Trusted Member
Joined: 4 years ago
Posts: 78
Topic starter  
Posted by: @transmit

Hello @Larry Ludwick

 

I can only tell you....

 

  1. the last old Alchemy version 1.55.03386 (legit) is clearly a 64 bit plugin !!! (not 32 bit)
  2. i use it since 2013 with success in Studio One 4 (previously Studio One 2 and 3
  3. Maybe it is just not shown in your Studio One because there is an option to show or hide the plugins

Please see above right to the wrench symbol (Screenshot), there you can make loaded plugins visible, if you switch the white dot on or off

 

If you pay attention, it should work,

 

 The Alchemy.dll can be scanned in Unify without problems

That is the version I reinstalled v155.0 . The install software offered the option to install both 64 bit and 32 bit. For the first failed install, I selected the 64 bit.

I'm not sure how long ago I originally installed Alchemy. 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. I just did not reinstall on my new computer until recently and had this problem.

Sonar and Reaper did not report a problem, but did not put the vst in the available lists. Studio 4 (the latest) when you boot it scans the vsts and looks for new ones. When I did after installing the 64 bit, Studio One did say Alchemy dll failed.

In Sonar, you can actually identify vsts that failed the scan, the 64 bit Alchemy was listed there.

I tried several times with full uninstall and reinstall and always had the same problem.

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 created a 64 bit jbridged version it did turn up in Studio One 4 as "VST Alchemy.64" in the instrument listing. In the vendor list, it is in a folder called [jBridge]Camel Audio. When I attempted the 64 bit version, I looked under all the options Studio One offers … Flat Folder Vendor Files and no Alchemy.

Believe me I would have accepted the 64 bit version if I could. Anyway, the bridged 32 bit works just fine now in all my DAWs. The only thing that might have happened when I installed the 32 bit version is I did not look for jBridge in the naming convention and therefore the Unify load of the 32 bit might not have done what did the trick because all DAWs might have recognized the 32 bit version already.


   
ReplyQuote
Share: