Hi josephsowa, I had a look again at your diagnostic file that you uploaded earlier, and I noticed that you did not even have Play on your whitelist.
Please do and if it still does not appear, please attach a new diagnostic report.
I’m embarrassed and I have to admit that I completely mixed up Aria Player and East West Play. My apologies.
There was so much traffic on this forum and we were working so hard on helping on so many issues in parallel that this happened.
But since I have an environment now, where I can reproduce the issue, I will download tomorrow Play from East West and see how that behaves with me.
So please a little patience again, I will get back as soon as possible.
No problem - thanks for looking into this!
I’ve added it to my whitelist for Dorico 3 and attached the diagnostics. Hope this helps.
Thanks again, Ulf!
(Here’s the attachment)
Dorico Diagnostics.zip (566 KB)
So now I installed East West Play 6 (latest version) on my Mac and it turns out is the same situation as with UVIWorkstation.
Play has a code signature, but the scanner bails out because it finds that the signature is not valid.
Same as UVI, Play is also copy protected by Pace, so it is most likely the same issue, they need a Pace update.
I will get in contact with East West and explain the situation.
By the way, Play comes in both, VST2 and VST3 format, but also both have the same issue, so either won’t work with Dorico 3 at the moment.aa
@josephsowa: Actually, if you have the VST3 version of Play installed, then you don’t need to whitelist it, it will get picked up automatically.
But as mentioned before, because of that code signature it gets blacklisted at the moment in Dorico 3. So please wait for a Play update.
Update, this is what East West replied: “We are working on it.”
Thanks Ulf!
Must be a MAC thing; no problem on PC
Thanks, Ulf!
Actually, as it turns out, we found that in this case not Play is the problem but PACE.
PACE is an SDK for copy protection used by lots of plug-in vendors.
There is a problem in that SDK that crashes our vstscanner.
We found that we can work around this problem, but for a proper fix PACE has to do it in the SDK.
We will bring out a new vstscanner with that workaround in the next Dorico 3 maintenance update.
The update is not scheduled, yet, we are still gathering bugs and issues, but it will not be too far away.
So please be a little more patient.
Btw., in case of UVI, they definitely also need to do some work on their end.
Thanks for the update!
(I’ve been using Vienna Ensemble Pro as a workaround, so I’m good for the time being.)
Many thanks for the update. I don’t own Vienna Ensemble Pro so I suppose I will keep using Sibelius until this is solved.
Could it be that the problem is present even if the iLok is a virtual one?
Yes, the problem affects the Play plug-in itself, and isn’t directly related to the iLok itself.