Notifications
Clear all

BBCSO Unify that I cannot get working properly

10 Posts
3 Users
0 Reactions
220 Views
(@spinner)
Active Member
Joined: 1 year ago
Posts: 5
Topic starter  

Hi,

 

I have BBCSO Unify that I cannot get working properly. I did a clean install and added PlugInGuru ProStation.guru. The reason I did this was Discovery and Core keep showing even though they are not installed on my computer and I didn’t add those files to Unify. 

This is perplexing as well as over complicated for an app that costs a reasonable amount of money, in my opinion. I keep avoiding using this app because I’m always hurting my foot by kicking my computer trying to get it to work properly. Should I run the terminal script? Please advise. 

 

Mac M1 Monterey 12.4

Unify 1.9.1


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

@spinner

Sorry to hear that you're struggling with this. We'll get you sorted out.

The first question is: have you added the BBCSO VST (not VST3 or AU) plug-in to Unify's Known Plug-Ins list? If not, this would definitely be the reason why the patches don't open for you.

I just tested on my own M1 Mac Mini, and found I had to re-install the libraries and enter my license key. This may not mean anything, though, because I use this Mac for development, and so it's often in a strange state. Also, I installed the DiscoverStation library first, then the CoreStation version. I will re-do the test now, trying with CoreStation only.


   
ReplyQuote
(@spinner)
Active Member
Joined: 1 year ago
Posts: 5
Topic starter  

Hi yes I am following all instructions. Ive been through it a lot of times trying to get it working. The BBCSO presets are there and they load, but the core and discovery plugins load and not the pro even though there is a PS in the top right corner, as well as no core or discovery icons. Because core and discovery are not installed on my computer the presets don't work.


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

@spinner

I will ask John to advise you further. I don't own the Pro version of BBC Symphony Orchestra.

Reinstalling Unify will not remove libraries. If you are seeing the DiscoverStation and CoreStation libraries, and you don't want them, you'll need to remove those library folders manually, then rebuild the patch databases. Right-click any patch from either library and choose "Reveal in Finder". Navigate up two steps, to Unify's Libraries folder, select and remove the four DiscoverStation and CoreStation folders, then click the "lightning bolt" icon at the top right corner of the Unify GUI.

Having said this, I personally would advise you to keep at least the DiscoverStation folders, because those patches load much more quickly, and can be useful to audition patches. When you find the one(s) you want, switch to ProStation and load the corresponding patches there instead.


   
ReplyQuote
(@spinner)
Active Member
Joined: 1 year ago
Posts: 5
Topic starter  

Posted by: @getdunne

remove the four DiscoverStation and CoreStation folders,

They don't exist.

I told you they are not installed on this computer. So on your advice I downloaded and installed Discovery. Added the guru file and now I have 2 abbey road one patches too (I don't own Abbey Road One). The patches seem to be loading correctly but some of the patches still don't make sound ie. BPM ELE-String Element, Woodwind Element, Brass Element and etc.


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

@spinner

Please clarify: Are you still seeing DiscoverStation and CoreStation patches listed in Unify's patch browser? If so, you may need to perform a full rebuild of the patch database by holding down Option when clicking the lightning bolt. (I advise against this unless you're sure you must, as this may cause you to lose your designated "favorites".)

The four Abbey Road One patches are bonus patches, signified by the "z" at the start of the name, and also in the patch comments. If you wish, you can remove them as follows:

  • Click on the patch to load it
  • Dismiss the load error-message pop-up
  • Right-click on the patch name and choose "DELETE this patch"
  • Click OK to confirm

Please note the "BPM ELE" patches only play within a limited range of notes. Please try higher and lower octaves.


   
ReplyQuote
(@spinner)
Active Member
Joined: 1 year ago
Posts: 5
Topic starter  

 

 

So edit, the BPM ELE patches work in DS but not PS. So I added Core and CS, BPM ELE seem to be working in all iterations.

I really only wanted the PS patches and you may need to note somewhere in the manual that this does not seem to be possible.

This post was modified 1 year ago 3 times by Spinner

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

Posted by: @spinner

How do you figure out which patches go with which library?

Use the library-selector pop-up at the top-right in Unify (by default it says "all libraries") to select only a single library at a time.

The patches in all 3 libraries should be the same. However I can't speak for ProStation, since neither I nor John actually own the Pro version of BBCSO. John told me that one of our users created the ProStation patch library for Unify.

...when I loaded it I got the DS VST GUI...

This sounds like an issue with the BBCSO VST, not Unify. I believe there is an option in their GUI to select which version is shown, but I'm pretty sure it should select the correct one, depending on whether you load Unify patches from the DiscoverStationCoreStation, or ProStation libraries.

If so why are they listed in the browser when I don't want them?

I gave instructions above for how to delete libraries you don't want. You won't see any change in Unify after simply deleting the library folders. You need to rebuild the patch database as well. (Unify will re-scan all library folders to find only the files which are actually there.)

Is it necessary to load stuff I don't want to get the stuff I do want to work properly?

No. It should be fine to have only the ProStation library. I have verified on my Mac that I can remove the DiscoverStation library completely, and CoreStation patches will still load. I would expect this should extend to ProStation as well, but I can't confirm as I don't own BBCSO Pro.

BPM ELE patches work in DS but not PS. So I added Core and CS, BPM ELE seem to be working in all iterations.

As I said before, one of our users created the ProStation patches. From what I can tell, they appear to have updated all patches to use only files under the PlugInGuru ProStation folder, but this can be difficult. It may be that some patches actually refer to other folders, because the original patches (which the user modified to create the Pro versions) were in those other folders.

I haven't saved any patches because I can never seem to get stuff working and I fixate on these problems.

I understand. This stuff can be confusing and frustrating when you're just trying to get started. It's complicated, because there are multiple plug-ins and multiple libraries involved, from two different companies, but rest assured that others have managed to get this working and are using it daily without problems. We will do our best to help you, but it's a step-by-step process.

 


   
ReplyQuote
(@spinner)
Active Member
Joined: 1 year ago
Posts: 5
Topic starter  

I’m okay now. I know how to make and save basic patches and stuff. Just haven’t done more than scratch the surface. I couldn’t have figured this out without your help. So big thank you. 


   
ReplyQuote
pluginguru
(@pluginguruforums)
Honorable Member Admin
Joined: 5 years ago
Posts: 322
 

Hi Spinner - I'm glad Shane was able to take the time to help you get this version of the BBCSO library working! Just a little background, the library was created first for the Discover version of the BBCSO library and then converted by me to the Core version because I purchased the Core version myself. I don't own the Pro version. About 45 days after the library came out, I was contacted by one of our customers that owns the Pro version and he informed me he was doing a 100% conversion of the library to the Pro edition. I give him guidance and suggestions but was never able to personally test anything he produced. That was around 2 years ago and numerous other Pro edition owners have let me know the library works for them so to this date I am comfortable stating we're compatible with the Pro version even though it has never gone thru our usual level of personal testing due neither Shane nor myself owning the Pro version.

 

All that just to say that I am very glad it is still working and that if there are places where it is not working, please let us know so we can try to evaluate why it is not working and figure out if there is anything we can do to help get it working better for you.

 

I hope you find the value of the library worth the trouble it took to get it working!

 

Kindest regards,

John Lehmkuhl

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


   
ReplyQuote
Share: