![]() ![]() Clearing the VST cache (couple times) didn’t do anything. It was a combination of modifying the blacklist XML file, running the audio engine again (I could see it finding NP at that point). So it’s not without precedent.ĭaniel has since stated they do test with NP, and I’m glad to hear that. That’s because they realise that breaking apps for people is not a good thing. I own a copy of NP, too.Īctually Microsoft for one spend an enormous amount of effort testing with popular applications when they made changes to Windows. It’s likely that patches or upgrades will happen, hopefully sooner than later. Dorico and Finale are its second and third priority. Especially as in this case, when NotePerformer’s prime directive (to borrow a metaphor) is to work with Sibelius. Since NotePerformer is not a Steinberg product, neither is it a native app to Mac or Win, I don’t understand why you should expect that.Įven if they did the testing you want(and we have no knowledge one way or the other), there’s no reason to expect Steinberg to delay a release because a non-essential 3rd party app has problems with the latest version. I’ve never had a problem updating Sibelius. I hope from now on, now that Steinberg knows how many people are using NotePerformer, that they put some more significant testing in for that. If that isn’t sufficient for you, please let us know and we will of course be happy to investigate further. I am sorry to hear that you are one of those users.Īt the moment it appears to be sufficient for most users to click the ‘Clear Audio Engine Cache’ button on the Play page of Preferences and then restart Dorico. ![]() But of course here on the forum you will see only those users who encountered problems. Thousands of users have updated to Dorico 3.5 already and no doubt a good number of them have NotePerformer, and everything is continuing to work correctly for them, just as it has done in all of our internal testing throughout development. ![]() This problem has occurred on a few occasions before – normally in connection with graphics card drivers – but that doesn’t appear to be what’s going on here. ![]() We do of course test with NotePerformer internally, and we did not uncover the problem that some users have experienced with NotePerformer being blacklisted during our testing. Adrien, I’m sorry you have encountered problems with NotePerformer in Dorico 3.5. ![]()
0 Comments
Leave a Reply. |