Notifications
Clear all

Airwave Patch Problem

4 Posts
3 Users
0 Reactions
1,427 Views
(@larry-ludwick)
Trusted Member
Joined: 4 years ago
Posts: 78
Topic starter  

Attempted to load "BPM ARP - Altered Spaces" error result attached.

 
Also: BPM - PolyBox Attacker, BPM SPLIT - Bodelire, BPM SPLIT - Brandenburg 1989 Xpanded, BPM SPLIT - Cadenzah
 
All other patches loaded without problem.
 
This topic was modified 4 years ago by Larry Ludwick

   
Quote
(@thsve)
MR
Joined: 4 years ago
Posts: 343
 

Make sure that you have the VST version of UNIFY in your "Known Plugins" list. VST3 is not working as plugin in within UNIFY. 

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
ReplyQuote
pluginguru
(@pluginguruforums)
Honorable Member Admin
Joined: 5 years ago
Posts: 321
 
Posted by: @larry-ludwick

Attempted to load "BPM ARP - Altered Spaces" error result attached.

 
Also: BPM - PolyBox Attacker, BPM SPLIT - Bodelire, BPM SPLIT - Brandenburg 1989 Xpanded, BPM SPLIT - Cadenzah
 
All other patches loaded without problem.
 

As Thsve said, you need to use the VST version of Unify - it is possible you have not scanned your VST plugins? If you prefer using VST3 (which kills patch compatiblity by the way) then you can drag the VST version of Unify into the Known PlugIns list so that the VST version of Unify is added but not the rest of your VST plug-ins, if you wish to use mainly VST3. Be aware any libraries (like the Serum library) we make for a specific plug-in will require the VST version to be accessible by Unify because we save all patches with the VST version of the plug-ins so that the patches are cross-platform compatible.

Life is Sound / Sound is Divine
www.pluginguru.com


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

@pluginguruforums

 

Ugh the Vst2 vs Vst3 gotcha. Strangely enough, I have only been running the Vst3 version of Unify and I've had no problems with the 545 Vsts I've reviewed.

Another strange thing is ... I made a false assumption and that was that Unify itself would be a default in the list of vsts available to Unify layers. Nope, not so. Now I see why only the Unify layers were reporting problems. I dropped the Vst3 version of Unify into my Vst list. This did not work.

 

I therefore had to install the Vst2 version of Unify and then drop that version into my Vst list for Unify … Voila, the problem patches now work.

I'm still running the Vst3 version, but as far as Unify is concerned any time an instance of Unify is dropped into a layer, it only finds and attempts to load the Vst2 version and all is working fine.

 

PROBLEM SOLVED.

 

However, I realize that using the Vst3 version, although it might work for all the patches I have created, it could be a problem for eventually sharing patches in the future. I will probably switch to running the Vst2 Unify exclusively.

This post was modified 4 years ago by Larry Ludwick

   
ReplyQuote
Share: