Notifications
Clear all

ReFX Nexus 2 and Steinberg Plugins

14 Posts
5 Users
1 Likes
1,430 Views
(@batterydead)
Active Member
Joined: 4 years ago
Posts: 16
Topic starter  

Hi there,

I have some issues with ReFX Nexus 2 and some Steinberg Plugins (on Mac OS Mojave)

Nexus 2 works fine in Unify when I create a new Layer set, but when saved and reopened there is no sound from Nexus 2 when playing it over Midi. When using the Nexus built in Keyboard with the mouse I can hear the correct sound. 

*Edit: Problem with Nexus 2 only occurs in VST3 Version of the Plugin.. I'll change my Plugin Subset to use VST or AU instead.. This one problem is solved for me 😉

 

Steinberg Padshop and Retrologue work only once in Unify. When I select an other Patch and come back to Retrologue/Padshop I get an error message saying "The host application did not reload the plugin properly. Please restart the host."
When I close Unify (Standalone) and reopen it my Patches load and are playable.

Would be great to hear if these issues will be adressed in the future.

Best regards,
Christian


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

Hi Christian,

There were some problems with MIDI and VST3 plug-ins in Unify v1.0.12, and earlier, which should be fixed in the just-released v1.1.3. Have you tried this?

I have added all of your comments to my file of user feedback about plug-in compatibility issues, and will look into them.

 


   
ReplyQuote
(@paull)
Member
Joined: 4 years ago
Posts: 26
 

@batterydead

I haven't been able to re-produce that behavior on my PC (Win 10). I have Cubase Pro 10.5. I tried both VST2 and VST3.

I created a patch using both padshop and retrologue and saved it in my user library.

Then I created another patch with both instruments and saved it to my library.

I was able to switch back to the first patch without a problem.

Then I tried loading a Unify factory patch, then going back to a saved padshop/retrologue  patch. It loaded OK.

Are either of these scenarios like what you're experiencing?


   
ReplyQuote
ChrisG UK
(@chrisg-uk)
Member
Joined: 4 years ago
Posts: 127
 
Posted by: @batterydead

Hi there,

I have some issues with ReFX Nexus 2 and some Steinberg Plugins (on Mac OS Mojave)

Nexus 2 works fine in Unify when I create a new Layer set, but when saved and reopened there is no sound from Nexus 2 when playing it over Midi. When using the Nexus built in Keyboard with the mouse I can hear the correct sound. 

*Edit: Problem with Nexus 2 only occurs in VST3 Version of the Plugin.. I'll change my Plugin Subset to use VST or AU instead.. This one problem is solved for me 😉

 

Steinberg Padshop and Retrologue work only once in Unify. When I select an other Patch and come back to Retrologue/Padshop I get an error message saying "The host application did not reload the plugin properly. Please restart the host."
When I close Unify (Standalone) and reopen it my Patches load and are playable.

Would be great to hear if these issues will be adressed in the future.

Best regards,
Christian

I can agree it happens with these Steinberg plugins. I’m using mac catalina latest and it does it within Cubase latest version as a vst and also as a separate Unify. It does this with HALion SE too. 

regards,

Chris

Chris G
Hardware: ROLI Seaboard, ROLI Lightpad, LinnStrument, Native Instruments S61, CC121
Software: Cubase 12 pro, Native Instruments, Equator 2, Cypher2, Strobe2
OS: MacBook Pro 2019, Big Sur 11.7, iPad Pro


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

@chrisg-uk, @batterydead

Please clarify: Is this happening in Unify v1.1.3?

 


   
ReplyQuote
ChrisG UK
(@chrisg-uk)
Member
Joined: 4 years ago
Posts: 127
 

Hi Shane,

I am at Unify 1.1.3.  I have looked through my plugins.  I cannot get the AU version of Retrologue 2 to install and drag into Unify so this is VST3.

Steinberg does not install anything but a VST3 version of Halion Sonic SE3.

Padshop has an AU version which works no problems but not when using VST3.

Hope this helps.

Chris

Chris G
Hardware: ROLI Seaboard, ROLI Lightpad, LinnStrument, Native Instruments S61, CC121
Software: Cubase 12 pro, Native Instruments, Equator 2, Cypher2, Strobe2
OS: MacBook Pro 2019, Big Sur 11.7, iPad Pro


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

@chrisg-uk

Thank you for clarifying. I have only the AU version of Padshop on my Mac. I will look into the VST3's you mention, and try to find out what may be going wrong when patches are saved and re-loaded. This is likely to take some time, but at least I know what I'm looking for now.

 


   
ChrisG UK reacted
ReplyQuote
ChrisG UK
(@chrisg-uk)
Member
Joined: 4 years ago
Posts: 127
 

@getdunne

Hi Shane,

I played again this morning.  I searched for the '.component' for Retrologue and it was there but wasn't auto detecting when I searched for new AU's.  I dragged it into Unify and the AU version behaves.  I removed the VST3 version from known plugins and tried to recall my previously saved presets and layers and now they don't use the AU version and revert to red text upon loading.

Is there any way Unfiy can select the 'AU' version from presets when it can't find the 'VST3' version?  Or is that I must resave all of my presets layers again using the AU version?

So in all, Steinberg Halion Sonic SE3 is the only VST3 version issue I have as it doesn't allow you to choose any other plugin type.

Here is the error that appear when using the VST3 version when reloading a second patch for your reference.

Cheers,

Chris

Chris G
Hardware: ROLI Seaboard, ROLI Lightpad, LinnStrument, Native Instruments S61, CC121
Software: Cubase 12 pro, Native Instruments, Equator 2, Cypher2, Strobe2
OS: MacBook Pro 2019, Big Sur 11.7, iPad Pro


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

@chrisg-uk

There is not much point in Unify automatically using version Y of a plug-in when the expected version X is not found, because AU, VST, and VST3 do not save their data in the same way, and there is no automatic way to convert one to the other. (Believe me; I've tried.)

You would run into the same problem if you created a project in any DAW using, say, an AU plug-in, and then attempted to load it on another computer where only the VST version is available.

As to the other issues you reported (layers saved using VST3 plug-ins don't receive MIDI after reload, "host application did not reload the plugin properly" message), I will be looking into both these issues, but can't make any promises at this point.


   
ReplyQuote
ChrisG UK
(@chrisg-uk)
Member
Joined: 4 years ago
Posts: 127
 

@getdunne

Thanks for the info.  I guessed we couldn't convert them as I took a look at the XML file.  So I am having the pleasure of resaving my presets 😩 Only 50+ more to go lol

Chris

Chris G
Hardware: ROLI Seaboard, ROLI Lightpad, LinnStrument, Native Instruments S61, CC121
Software: Cubase 12 pro, Native Instruments, Equator 2, Cypher2, Strobe2
OS: MacBook Pro 2019, Big Sur 11.7, iPad Pro


   
ReplyQuote
ChrisG UK
(@chrisg-uk)
Member
Joined: 4 years ago
Posts: 127
 

@getdunne

So not one to give in, I decided to remove my VST3 versions of Halion Sonic SE and reinstall the AU version into Unify 1.1.3.  What I noticed in Unify is that if I dragged the AU component file it reads as if it was a VST3!!!!

So I removed the vst3 file from Unify and left the AU version.  This made it work!! My previous instrument presets made with the original VST3 version are calling this 'AU-VST3' version of Halion Sonic and they load properly!!

I'm not asking to change it just thought it may be useful if anyone gets an issue with Halion Sonic SE3.

Cheers,

Chris

Chris G
Hardware: ROLI Seaboard, ROLI Lightpad, LinnStrument, Native Instruments S61, CC121
Software: Cubase 12 pro, Native Instruments, Equator 2, Cypher2, Strobe2
OS: MacBook Pro 2019, Big Sur 11.7, iPad Pro


   
ReplyQuote
(@batterydead)
Active Member
Joined: 4 years ago
Posts: 16
Topic starter  

Hi Shane,

I just tested the VST3 and the AU Version of Padshop in Unify 1.1.3 standalone on MacOS Mojave and I still get the same result  I can open up several Padshop instances into layers, and I also mixed up VST3 and AU in one patch for testing. But I can only reopen it when I close and re-open Unify standalone. This also happens when I try it in Cubase Pro 9.5.
I can open a Padshop, play around with it, save the Patch. When I switch between patches and come back to the Padshop patch (does not matter if there is only one Padshop or more layers) it says "The host application did not reload the plugin properly. Please restart the host."

Steinberg Retrologue: same thing..

 
Regards,
Christian


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

@batterydead

The plot thickens! Thank you for this new set of details. This may be enough for me to engage with Steinberg to try to get to the root of the issue.

Having said that, however, my past experience with Steinberg for developer support has been quite dreadful. Multiple meaningless email responses, and I ended up figuring out the problem (how to build Unify stand-alone for Mac to work trigger the connection to their awful synsopos.app) by myself.


   
ReplyQuote
Tod Slaughter
(@tod-slaughter)
Active Member
Joined: 4 years ago
Posts: 14
 

Steinberg sheesh! Always a good idea to keep older elicenser installers backed up and then try updating to see if it fixes your issues or makes them worse! At least you can roll back if necessary. 


   
ReplyQuote
Share: