Notifications
Clear all

Razor Chill Pluginguru library - Not working in Unify

9 Posts
3 Users
1 Reactions
117 Views
(@sean8877)
Eminent Member
Joined: 3 years ago
Posts: 19
Topic starter  

Hello,

I purchased Razor Chill which comes with the Razor patches as well as a ".guru" file for Unify. I was able to load the patches into Razor without issue. I added the "Reaktor 6.dll" via the "Known Plugins" page as I have done when adding any new plugin to Unify. Then I loaded the "PlugInGuru RZ Razor Chill.guru" file via the Settings page as per usual for a new ".guru" file.

The Razor Chill patches show up in Unify but when I try to load any of them it says:

"Can't load patch: plugin is missing or wrong format"

The Unify help page only says that you need to load the VST2 version of the plugin, which I have done since I chose the Reaktor 6 ".dll" file. I have the latest version of Reaktor and the patches play fine from within Reaktor. The Read Me file that comes with Razor Chill does not cover the Unify install so I have no idea why I am getting the above error when trying to load a patch.

Does anyone know why I'm getting the "plugin is missing or wrong format" error when I have the VST2 version of Reaktor picked in Unify and I followed the standard process that usually works fine when loading a new plugin into Unify?

Thank you for any help.


   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4487
 

@sean8877

I just reproduced this issue on my Windows PC. Something is wrong with the .unify patch files. They are trying to load the "Reaktor 6 FX" VST, when they should be loading the regular "Reaktor 6" VST. That's why you're getting those error messages. I'll alert John and Taylor to look into this.


UPDATE: When I add the "Reaktor 6 FX" VST to Unify's known plug-ins list, the patches will load, but not play. When I open Reaktor's GUI, I get an error message saying it can't find the Razor-Unify.ens file, and specifies a path (on my machine, E:\Native Instruments\Razor) where it's looking. Here's how I solved this:

  1. In Reaktor's GUI, in the Player tab, double-click the Razor.rkplr item to load the basic Razor ensemble.
  2. From the main menu at the top left (triangle icon beside "REAKTOR"), choose "Save As..." and save as Razor-Unify.ens in the folder where Reaktor said it was trying to load the ensemble.
  3. In Unify, hit INIT to unload Reaktor.

At this point, provided you got the file name and location exactly right, the unify patches should load.


I don't really understand why this is necessary or exactly why it works, but it may provide you with a work-around until John can provide an updated version of these patches.


   
ReplyQuote
(@toddskee)
New Member
Joined: 4 weeks ago
Posts: 2
 

I picked up the all the Razor libraries as well and was having the same problem. Pointing at different VSTs,  I got as far as no sound in Unify and the infamous "ensemble not found" - Razor-Unify.ens. I've spent a good part of the evening trying to track it down reading the forums and install videos and everything is up to date. I'm glad to hear there is an actual problem found that it's scoping Reaktor 6 FX by error. Crossing my fingers that will clear up the file missing file error message that's breaking the Unify patch. Lord knows I've tried every possible install location for the patches. Lol.  Thanks for looking into this, and we appreciate what you guys do. 🦊 - Happy Birthday John! 🎂


   
ReplyQuote
(@sean8877)
Eminent Member
Joined: 3 years ago
Posts: 19
Topic starter  

Posted by: @getdunne

@sean8877

I just reproduced this issue on my Windows PC. Something is wrong with the .unify patch files. They are trying to load the "Reaktor 6 FX" VST, when they should be loading the regular "Reaktor 6" VST. That's why you're getting those error messages. I'll alert John and Taylor to look into this.


UPDATE: When I add the "Reaktor 6 FX" VST to Unify's known plug-ins list, the patches will load, but not play. When I open Reaktor's GUI, I get an error message saying it can't find the Razor-Unify.ens file, and specifies a path (on my machine, E:\Native Instruments\Razor) where it's looking. Here's how I solved this:

  1. In Reaktor's GUI, in the Player tab, double-click the Razor.rkplr item to load the basic Razor ensemble.
  2. From the main menu at the top left (triangle icon beside "REAKTOR"), choose "Save As..." and save as Razor-Unify.ens in the folder where Reaktor said it was trying to load the ensemble.
  3. In Unify, hit INIT to unload Reaktor.

At this point, provided you got the file name and location exactly right, the unify patches should load.


I don't really understand why this is necessary or exactly why it works, but it may provide you with a work-around until John can provide an updated version of these patches.

Thanks for looking into that, I'll test out the workaround tomorrow.

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4487
 

@toddskee

As far as I can tell, there are two separate problems, both of which I have been able to work around:

  1. The patches require the "FX" version of the Reaktor VST. As long as this is available, they will load OK. Apparently, there is no real difference between the instrument and FX versions; the FX version will work as an instrument, so this isn't really important.
  2. The patches require a Razor-Unify.ens ensemble file, which is just a copy of the standard Razor ensemble, saved wherever the Reaktor (FX) plug-in chooses to look for it. I think this is a peculiarity of Reaktor, which, like Kontakt, needs this "ensemble" file to set it up to function as Razor. The instructions I gave above allow you to create this for yourself, and it only needs to be done once.

So if you follow the instructions I gave above, you should be able to use these patches as-is, without waiting for an updated version of the library.

There is also a third issue, which is that the wrong PDF was included in the download. It's supposed to be instructions for setting up Reaktor/Razor, but instead it's about Omnisphere 2.


   
ReplyQuote
(@toddskee)
New Member
Joined: 4 weeks ago
Posts: 2
 

@getdunne Hello Shane, I'm just confirming your instructions above worked great for the work-around here. If I could send you all some coffee and donuts, I would. Thanks to you, and the team for the A+ response and support.


   
getdunne reacted
ReplyQuote
(@sean8877)
Eminent Member
Joined: 3 years ago
Posts: 19
Topic starter  

Hi - Just checking if there's a plan to have an updated .guru file available for download with a fix, or is it something that is a difficult fix so we should use the workaround for the near future? Thanks.

This post was modified 3 weeks ago by sean8877

   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4487
 

@sean8877

I've asked John to answer this. I don't maintain the .guru files; I just help him with technical aspects sometimes.


   
ReplyQuote
(@sean8877)
Eminent Member
Joined: 3 years ago
Posts: 19
Topic starter  

Posted by: @getdunne

@sean8877

I've asked John to answer this. I don't maintain the .guru files; I just help him with technical aspects sometimes.

Sounds good, thanks.

 


   
ReplyQuote
Share: