#Dorico tutorials code#

#Dorico tutorials code#

That’s not necessarily a weakness in every context, but Finale has amassed a pile of technical debt, an accumulation of decades of old code that makes it nearly impossible to improve core functionality. Although the bug fixes have continued at a respectable pace, Finale feels like a 30-year-old program. The first was the trajectory of MakeMusic, the company that owns Finale. Besides, novelty alone is never a good reason to do much of anything, especially something like changing one’s professional workflow.īut two concerns were growing in my mind. I had no expectation that I’d ever move away from Finale. And my experience confirmed that: I had amassed plug-ins and expression libraries and shortcuts and workarounds, and I was moderately pleased with everything. Use any program long enough, and you’ll become proficient enough to make it do what you need it to do. After all, people don’t know what they like they like what they know. Rather than rehash what others have written, I thought I’d share my experiences with it as an arranger and composer.įinale has a comforting familiarity for me, especially as my usage has increased over the past ten years. You can find out more about Dorico here, and here, and here, and peer behind the curtain here. Dorico has exceeded my expectations in every way, and it’s already changing the way I write and arrange. And today, when my trial expired after a thirty-day test drive, I immediately purchased a license. One month ago, after following its development from a distance for a year or so, I downloaded a free trial of Dorico.