Dorico Team - I’ve had about a week now to use it in the trenches and learn as much as I can of its features. I lost count of the times that I went, “No way, you’re freaking kidding me… this is unbelievably good.” Somebody there (or all of you) really gets the perspective of trying to make a living with it, and trying to shave time from anything and everything that isn’t actually part of the writing process. The Player organization and Print features alone… I seriously owe you as I think you solved most of my biggest problems in making deadlines. I think you’re serious in your goals for Dorico.
Which is good because I also lost count of the number of times that it crashed - a couple of times where no amount of restarting or rebooting would get the sound back and if it weren’t for a couple of things Ulf had told me… Which brings me to my suggestion: Pro Tools has an unofficial PT Prefs tool which will get you out of some scrapes by cleaning up various config issues that can go wrong. I don’t want to distract you though, and maybe the Dorico community needs to build it…but at the moment I think we could use something similar to clean up after a bad fall. Something to help us get it back to a fresh state in the VSTEngine3 directory lets say, without deleting things you don’t want to delete like a whitelist. Any thoughts?