I recently upgraded to D6 and moved all of my config files to a new Macbook Pro. Most of the custom files I’ve created in D5 and on the old laptop work except for a few.
In this screenshot the VST instrument name has 2 exclamation points before and after the name, and that instrument isn’t working.
The endpoint config file is in fact present in the correct location on disk. What might be causing this and how may I fix it? Thanks!
The problem is that I guess the Opus plug-in itself (is that EW Play? I’m not familiar with all third-party libraries) is either not installed on your new system, or it’s not being recognised by Dorico itself.
It’s East-West’s Opus VST and it’s installed. Other playback templates which instantiate endpoints with Opus work OK. Not sure why this particular one is failing.
It’s only a handful of them that are doing this so maybe I’ll see if I can copy/edit the XML files and see if that works.
It could be, I guess, that this particular endpoint configuration refers to a different version of the plug-in with a different internal ID?
If Opus works in other projects but not that one, my guess would be that that project might be set to use the VST2 version of Opus instead of the VST3 version. The VST2 version would have to be explicitly whitelisted in order to load. I don’t usually whitelist it because I don’t want to accidentally add the VST2 version to a project (which I might do if I have it whitelisted and then I would see both versions showing up).
(EW Opus is the replacement for EW Play, it came out a few years ago and most everything has moved to it. I’m not sure why they gave it a new product name, it is basically EW Play 2.0)
I only use VST3 plugins. And this is EW Opus, not EW Play.
I’m afraid our options for troubleshooting this are limited, since I don’t have any of these plug-ins. Even if you were to send your endpoint configurations to me, I wouldn’t be able to tell you why the plug-in isn’t loading in that case. You could zip up the playback template and attach it here if you wish, and I can have a look at the files in case anything jumps out at me.
Here’s the playback template in question.
I’m confused why you don’t have access to plugins that are commonly used in Dorico. Having a cooperative, non-competitive/NDA agreement with other companies is common.
DGP - EWQLSO Strings.zip (1.1 KB)
There are only so many hours in the day and so many things I can personally manage, Debra! Working with third-party sound libraries etc. is something that I leave to my very capable colleagues.
I need to see the endpoint configurations, I think, which don’t seem to have been included in the file you uploaded, sorry. I think if you export the playback template and change its filename from .dorico_pt to .zip you should be able to upload it here, though possibly it’ll be too big because of the VST plug-in data blobs.
I misunderstood your previous message, I thought you wanted just the playback template alone. Here’s the exported template, zipped, and it does contain the endpoint configs. It’s only ~1.5 MB file size.
DGP - EWQLSO Strings.dorico_pt.zip (1.4 MB)
Everything looks OK in there. I guess for some reason the plug-in state file (the binary blob that contains the state of the plug-in and its loaded patches etc.) isn’t loaded correctly. Hopefully it won’t be a lot of work to reconstruct that particular endpoint configuration.
Thank you for looking into this for me. I too suspect there might be something in the binary blob contained in the endpoint configuration. But I don’t have time to parse it and figure it out right now. It’s much quicker just to go through all of my playback templates and reconstruct the ones that are problematic, I have a number of projects that I must finish by the end of the year, time is fleeting.
Again, thank you for taking the time to examine this issue. Take care.
