Notifications
Clear all

Trouble with OB-Xd on new instances


bbarker3
(@bbarker3)
New Member
Joined: 1 month ago
Posts: 3
Topic starter  

Question: when I start with an initialized patch in Unify 1.8 and select the OB-Xd plugin, I get the following message on-screen - not sure what is wrong - all the other native plugins work fine. When I select other patches with the OB-Xd plugin already set up, it opens and works fine. Seems to be problematic with selection for any new instance. Any help appreciated.No photo description available.


Quote
getdunne
(@getdunne)
Member Admin
Joined: 3 years ago
Posts: 3502
 

@bbarker3

The most likely thing is that you have registered an additional (newer) copy of the OB-Xd plug-in into Unify's Known Plug-Ins list, so Unify is trying to open that one, but it's not correctly configured. Click the plug-in icon to see the list, and look to see if there are two or more entries for the plug-in. The one that is bundled with (and installed automatically with) Unify is called Obxd. It's a VST, and its version number is 1.5.0.0, and the manufacturer name will show as "Datsounds"; later versions are typically called OB-Xd, will often be VST3, and show manufacturer name "DiscoDSP".

The simplest thing to do is to locate any additional entries in the Known Plug-Ins list, right-click each one and choose "Remove plug-in from list". Then you can load new instances in the usual way, by selecting the plug-in from the "Unify Standard" sub-menu.

If you want to use the newer version of OB-Xd alongside the bundled one (there is little advantage in doing so, to my knowledge), you need to configure it. The plug-in looks for a folder called "discoDSP"; the v1.5 version bundles with Unify looks for this in the Public Documents folder, but newer versions look in your personal Documents folder. Your screenshot suggests that you're trying to run a newer version, but it isn't finding a folder ~/Documents/discoDSP. You could try running the OB-Xd installer again to create it. Another possible issue is that you might have copied an older version of the discoDSP folder to your ~/Documents folder, perhaps one that contains the older Skins sub-folder instead of the Themes folder used in later versions.


ReplyQuote
bbarker3
(@bbarker3)
New Member
Joined: 1 month ago
Posts: 3
Topic starter  

@getdunne thanks much, I see that I did at one time load an independent version of Discodsp so I'll delete that and make sure there's nothing non-Unify-native in the plugin list.  Will report back.


getdunne liked
ReplyQuote
bbarker3
(@bbarker3)
New Member
Joined: 1 month ago
Posts: 3
Topic starter  

@getdunne thanks - that fixed it - all good here!


ReplyQuote
Share: