#NotationSoftware

Dorico 6: Worth the Wait

Dorico 5 to Dorico 6 has been the longest gap between major version releases in the program’s life thus far.1 Among other things, many free updates during the lifecycle of 5 (many of which were to help users coming from Finale) kept things busy. But in spite of all the smaller updates throughout the lifecycle of 5, Dorico 6 delivers in the scope you would expect, perhaps being the biggest upgrade since Dorico 2.

As ever, Scoring Notes is going to have the best and most detailed review, I’m just offering opinions as a band director. The “Making Notes” blog at Steinberg also has interesting information.

Dorico 6 is a big update. It’s awesome. It’s exciting. It’s worth the upgrade price. If you go through Steinberg’s upgrade flow, you’ll have it up and running before you could finish reading this article. I have little idea of how Steinberg is going to market the update, though, and in my opinion, the most impressive “headlining” features for most people are not half as big or impactful as so many other features in it. The update is jam-packed with small improvements in addition to new systems.

Engrave Mode’s Big Day

The team has made a massive improvement to Engrave Mode in the form of rulers and guides. It’s been awhile since I’ve done particularly complicated layout work for a student resource, but keeping things aligned always proved to be one of the principal challenges. In the past, I’d have to do a lot of setting of positions in the properties panel manually, but guides will allow much more of that work to be done graphically. I am hoping for this feature to be followed up by some kind of snapping, but I’m happy today for guides as they exist.

I assumed I’d feel like rulers are just a feature ‘along for the ride,’ but going back through some recent projects with the rulers on, I might actually make some tweaks to how I approach a few things in the future being able to see more clearly where I hit the page margin vs the music frame margin.

Proofreading

When I saw the notes on Proofreading mode, I thought it was a feature aimed at people less experienced with notation software. The sort of people who don’t listen to podcasts about it and make it a part of their personality. Then I started handling projects in Dorico 6.

Proofreading mode is amazing.

It’s the sort of feature that, now having gotten used to it, shocks me that it hasn’t been a standard feature in all notation packages since 2002. Sibelius and Finale have historically had plugins that can do some of these things, but this is an amazing implementation that works very well. When I work with student composers and arrangers, this will be a big part of trying to push them off of MuseScore into Dorico. It’s also saved me a reprint of an editing project or two.

Jump Around

Introduced in Dorico 4, the Jump Bar has been a productivity boon for awhile. Being able to quickly set an accidental as parenthesized or enable an l.v. tie without taking my hands off the keyboard to do so in the properties pane makes using Dorico better.

Dorico 6 has made it even more powerful, but in a way that helps newer users especially; it now surfaces options.

With all the Finale users coming to Dorico, it’s been a nice reminder of how the “Dorico Way” takes some getting used to. A lot of the “opinionated” things Dorico does aren’t hard to change, but odds are, you want to change them across the whole project (e.g. cautionary accidentals, beaming rules, splitting the bar…) rather than every time they occur, unless you intentionally want an exception somewhere. By putting options in the Jump Bar, users will ideally be guided back into these options when using the jump bar to change things.

All the Small Things

There’s a lot of “smaller” features too that were added (though I question whether the effort behind any of them would qualify as small), and it’s really easy to miss them with the size of the version history.

A big one is the ability to import and export user settings. I’ve personally tweaked so many defaults for myself over time that I’ve forgotten half of them, I was working with some new Dorico users recently and while the Library Manager is a great way to change a lot of things for an individual project, I’m going to wind up sharing my defaults with a lot of people (including here soon) to help others out.

Paragraph Styles got a lot of love and refinement, including moving a lot of things out of Engrave Options into Paragraph Styles (such as distance from the staff settings). One particular new Paragraph Style setting is “case” so you don’t have to put the project title in all caps any more (and thus be yelling at yourself in your file names) in Project Info if you want it in all-caps in your actual layouts.

The Popover itself got some new superpowers that I also have to fawn over. For lyrics (and now also chord symbols) it’s a bit more obvious and helpful when navigating between different ‘lines’ (verses in lyrics and sets of chord symbols). Further, for the kinds of Popovers that can be applied to only one player (like a time signature or key signature) this is vastly more discoverable with a little dude next to the text input field, rather than having to remember that it’s the ⌥ key.

Headline News

While Proofreading is one of the “headlining” features, it’s worth mentioning the others.

Cutaways are impressive for those that need them. I have something saved from IMSLP myself to play with the feature when I have time. In education, I don’t know how much they come up, but this goes firmly in the category of things in Dorico where, if you need it, it’s thoughtfully delivered. Reading the Version History on this particular feature reminds you very acutely that the team at Steinberg aren’t just people making a program, but true music nerds at heart. It was probably the best mini musicology lesson I’ve had yet in 2025.

Chord symbols received a lot of love in this update. If there was something you couldn’t do with them before, chances are you can now. I personally wasn’t running into limitations before, but in the jazz arranging or editing world, I imagine some were.

For Cycle Playback and Fill View I don’t really have much to share; it seems to me the latter is made much more useful by having a big monitor.

Another Playback Feature

When Dorico 5 came out, there were people upset that it was too focused on playback features. In fairness, it was a bit lighter in other areas.

Well, those same people will be deeply disappointed to know that playback features are still improving in Dorico, though this time in ways I’m much more materially excited about: Steinberg now includes a marching percussion sample library, which is a solid improvement. In fairness, they face stiff competition from MuseScore in this regard, with really impressive drumline materials on that side of the fence.

Where do we go now?

Some time ago, I laid out every “complaint” I wanted to see improved in Dorico. The screenshot of a checklist I made in Marked is stretching really funny on iOS. Maybe one of these days I’ll do some more serious work on this site.

On the engrave mode front, as mentioned above, we have guides now. There’s also flow heading overrides in this version, which are really the improvement I wanted at the time for flow headings.

Even though I’ve gotten a really good feel for a lot of option changes’ effect (and they describe things very well), I’d still love a way to preview the option changes I’m making on the project I’m working on. The only real way to do this is when I’m working with a second monitor right now, moving the options over to that monitor and watching when I hit “Apply.” I find that a bit awkward, and I often lack my second monitor, so I still desire a different solution here.

Percussion notation has gotten a lot better, but my standards for it have gotten more aggressive too in honesty. 4.3 solved my biggest complaint by making common roll conventions much more straightforward to input (i.e. with the addition of rel as a popover suffix when inputting them).

Percussion notation in Dorico works differently to most other instruments to allow for the needed flexibility, but the behaviors around it are a bit different as a result. Bringing that into the “promised land” remains a hope for me, as does (somehow) making it more intuitive for new users, because I’ve been trying to guide some people on what they’re doing with percussion and seeing their confusion.

One new gripe I have, perhaps because I thought I could solve this with the addition of some other features, is changing the preferred order of instrument transpositions. I want my Euphonium to default to non-transposing, darnit. Maybe I have just missed how to do this if it was added at some point in the 5.x lifecycle and need to dive deeper.

With the jump bar, I think I can live at peace with the fundamental disagreements I have with the Dorico team about a philosophy of keyboard shortcuts. My beliefs haven’t changed, and maybe time has just worn down my commitment to them, but if I were going to remake an awkward checklist graphic, I’d strike it out at this point.

Wishcasting

With all these impressive new features, it’s still nice to think about what I’d like to do in the future with Dorico and what “major” features I’d like to see beyond things I merely believe it can continue to do better than it already does.

The big one is support for Roman Numeral analysis. On the heels of figured bass, some speculated it would follow shortly, but it hasn’t. What do I want it to do that isn’t already served by the MusAnalysis font? I’m not actually sure, but I’m still convinced I want it.

I’ve begun thinking about another feature I desire that is…a bit hard to describe honestly. I think “transpositional text tokens” roughly describes the idea. I’d like to have tokens that I can place alongside other text (whether that’s in a flow heading or a text frame for a work sheet) where I could place something like {@ConcertF@} and in a flute part it labels it “Concert F,” but in an Alto Saxophone part it labels it as “D (Concert F),” with a few different configurations of this (e.g. omitting the word ‘concert’ in C parts, taking out the concert pitch reference in transposed parts) settable in options. This would really open new doors in the kinds of resources I could efficiently prepare for students.

It’s kind of rude of me to even start to flesh out that token idea in a blog post rather than submitting it as a suggestion on the forums, but this is the first time I’ve thought to put this nebulous idea into words and I’m busy.

I think it’s noteworthy that, of all my wishes and desires, I can’t envision the interface for them or how they might be achieved otherwise. While I’m no software designer, I can usually imagine how I’d like to use a feature in a pretty reasonable way. But if I can’t even see in my head how it might work in an abstract way, then it strikes me as fruit pretty high up the tree to be asking for from the Dorico team.

Dorico 6 is going to make my daily work better, faster, and easier. And that’s before 6.0.10 or 6.1 or anything more to come in the Dorico 6 lifecycle. The team should be proud of their release, and anyone who really appreciates this program should be excited to see all these great additions.2

  1. 3.5 was a “major” version apart from the rest of the 3 series. Dorico 4, the first post-COVID release, came 602 days after 3.5. Dorico 6 comes 707 days after Dorico 5. ↩
  2. Aside from not wanting the other footnote to feel lonely, I wanted to apologize for the corniness of the headings throughout. I rushed to have this ready for release day, but life got in the way. ↩

#apps #dorico #notationSoftware

Thomas Alexander Kolbethomas@mastodon.gruenelin.de
2024-08-27

It’s the second-busiest time of the year, but there’s very little news that gets bigger than this.

In 2012, I had to do my first serious arranging project. I had found Bill Holcombe’s arrangement of Liszt’s Liebestraum #3 for tuba quintet in a jazz style. A short presentation on Animal Collective’s Cuckoo Cuckoo the previous year had led me there, and I recruited some friends to play it for Iowa’s State Solo & Small Ensemble Festival before our Winter Break. Being somewhat ignorant, though, I assumed that a tuba quintet was for five tubas, not a mixture of tubas and euphoniums – so with Bill Holcombe’s permission, I set out to arrange it down a fifth to sit in our range, rather than find a second or third euphophonist.

I had no budget, so at the time, Finale Notepad was my only option. Dorico did not exist yet, MuseScore wasn’t on my radar1, and I don’t believe there was a free option for Sibelius, so unless I was willing to pony up more money than any high schooler would tend to, Finale NotePad was my only choice.

I thought I could do the whole project – five parts of 181 measures – all by clicking my notes in. I realized before I was part of the way through that I needed to learn the shortcuts to have any hope of ever finishing the project. I had lots of frustrations, some inherent to Finale, some inherent to the NotePad version2. When I later went to college, I would eventually buy the full version of Finale. I still remember sitting in my freshman dorm as my best friend worked on jazz transcription and I did something else in Finale, and us both cursing it to the moon for one frustrating behavior or another.

When I was an undergrad, I felt like everyone used Finale except the composition students. When I took Arranging For Band, we were guided through the Sibelius tutorial, but allowed to arrange in whatever software we liked (I liked some things about Sibelius on our lab iMacs, but I couldn’t abide by its terrible shortcuts on a laptop…) and I jumped right back over to Finale. I saw a lot of arrangements of peers, and was eventually motivated to clean up some of my engraving in Finale (or to just learn the software well enough to not leave an empty bar at the end of every project – something Finale made it all too easy to do for the novice user).

As I had more and more projects where it was necessary for me to edit parts of arrange things, I got fast at Finale. If there were races for digital music copyists, I thought I could hang with any professional working with notation software. Among other things, seeing our conducting TAs working in Finale on their Macbook Pros made me envy the portability and battery life (compared to the Windows laptops I was used to) for working specifically in notation software that eventually brought me to the Mac.

Over my college career, I kept pushing my skills and understanding of Finale, but after Dorico came out, I was impressed with what I was reading, and tried it. There were a few things about it that didn’t stick for me in version 1, but when I came back to Finale, I felt dirty drawing smart shapes and going into obscure tools to make everyday changes. I realized that there were so many ‘easy’ things that were hard in Finale, and Dorico’s release was actually the reason I switched from Finale to Sibelius, funnily enough. I learned Sibelius as well (and better) than I ever knew Finale, and never really looked back, eventually moving to Dorico.

Finale announced today that it’s done.

There are lots of nerd ‘holy wars.’ Mac vs. PC, vim vs. emacs, and amongst music computer nerds, Sibelius vs. Finale was one of the hottest. For over a decade, they were really the only two options for anyone truly serious about their notation software.

Once upon a time, though, Austria was afraid of the Ottoman Empire.

Finale, by its architecture, appears to have had bigger issues with “technical debt” than Sibelius ever did. To get real nerdy with it for a second, it wasn’t using a cross-platform framework like Qt to help it manage how it interacted with the operating system. There were ways in which this was actually a benefit, but it was harder to maintin. The headlining feature of Finale 25 (in 2016) was 64-bit support, which took considerable resources for little apparent benefit for users.

As Finale’s progress slowed and competition from Dorico made the professional space a three-way race, the free MuseScore made great strides in refinement and became the ‘default’ for a new generation of people using their first scoring software.

I have very mixed feelings about all of this. If I sound like I’m gloating in any of this, I don’t mean to. Had I never bought Finale, I likely would have a completely different relationship with all technology in my life. But I also can’t open Finale without reliving lots and lots of frustration that is years in the past. While I got much better results by learning the program more, design is how it works. The problems people ran into and created for themselves in Finale are a byproduct of how well the software set them up to do a complicated job that most people don’t know the rules of. But it’s been a very long time since I’ve seen issues arising from amateur results in Finale; Musescore is producing those efforts today.

So I’m a bit misty-eyed in all of this I guess. I have a good number of .musx files I never converted to MusicXML because I always thought I could buy Finale when I finally wanted to get around to it. While I have my complaints and gripes with it, it’s weird to think that we live in a world without Finale now.

As always, Scoring Notes kills it with the coverage. I can’t wait to read Philip’s history section.

  1. At the time, MuseScore had not even reached version 2 yet, which is the first time I ever remember seeing people use it. There a few FOSS notation software packages out there, but MuseScore 3 was the first time one of them was a serious ‘competitor’ with commercial software IMO. ↩
  2. One limitation of NotePad I discovered about a third of the way through the project: You couldn’t change key signatures within a project. This piece had five. I had to ask a teacher to help me paste five different files together to make it one continuous document. ↩

https://mrehler.com/2024/08/26/end-of-finale/

#3 #dorico #notationSoftware #sibelius

Dan Carkner🎻carkner@klezmor.im
2024-08-26

Oh😯I never used #Finale, I was on #Musescore and then #Dorico for the last few years. I guess they are winding it down and offering a Dorico discount to try and make it up to their users. I like Dorico, but I'm not sure I'd be thrilled about that.
finalemusic.com/blog/end-of-fi

#EngravingSoftware #MusicSoftware #MusicNotation #NotationSoftware

Fellow musicians! Do you use #musescore4 ?

Does anybody of you know an easy way to double the length of the notes of a whole section/ several bars at once (i.e. two bars of sixteenth notes are transformed into four bars of eighth notes)?

Edit:
I found it out. It“s surprisingly easy as there is a „paste double duration“ option integrated in the Edit menu or ctrl+shift+w.
Great programme!

#musescore #music #notation #notationsoftware #fedihelp

Dorico 5.1 is out, and it’s a fantastic update!

But wait, I never did get around to posting about Dorico 5 when it came out in…May?

Well, to my credit, I did write about it. I was relatively satisfied with it, but there were a lot of people on the official Facebook group and the official Dorico forums who were upset by the perceived focus on playback features.

And then Daniel Spreadbury made this post1. While it’s been a minute since it was originally written, I find it just as necessary now to highlight as I did then. It’s a long read, but I highly encourage reading it in its fullness. It’s a masterclass in public relations, in transparency, and in humility – something that I find to be depressingly absent from so much modern discourse, especially online.

So if you want my initial thoughts on Dorico 5.0, I threw them up as a Github Gist2. It’s a mostly finished post.

So onto Dorico 5.1: Long story short, it delivers on the whole point of “there are great point releases coming.”

To me, the most exciting features are the ‘instrument families editor’ and the ‘score order editor.’ I haven’t had enough time to figure out if the former will allow me to make the default transposition for a euphonium to be concert pitch, but I’m hopeful once I get some time to treat it as the most important thing in my life. The latter proves to a be a good workflow improvement to anyone who wants something outside of the existing score orders on a recurring basis (the program can already handle ‘no score order’ in a single project, but if you wanted to reuse that order or add additional players on existing instruments, I could see how this improves things). The update also brings a proper jazz band score order, so to my mind that only leaves brass bands and small ensembles (like woodwind quintets) that the program doesn’t already offer out of the box. I remain grateful for the existing band score order that ships with Dorico, in the hopes that it will save people from making ill-informed decisions.

There’s a lot of other features, too! The crashing of the audio engine has long been one of the most frustrating crash states the program can hit (though it’s been rare for me) as it’s previously been unclear to many users how to get the program to start again after this occurs. Knowing to force quit the VSTAudioEngine process is no longer necessary, though, as the program can solve this itself now.

Playback improvements continue with Iconica Sketch and playback for fermatas. For the latter, it really feels like a finally. I understand that development requires prioritization, but it’s really felt like a limitation for awhile. That said, the immense and granular control continues to reinforce the idea that the “Dorico way” isn’t simply doing the thing, but doing the thing with as much customization and flexibility as one could ever desire. Their ethos continues to seem to be that “we won’t put a feature out until it’s going to be everything we feel it needs to be,” even when those features sometimes feel overdue with how mature Dorico has gotten.

The last feature work explaining anything about is the support for a subset of Markdown in project info. Entering text like “The Musical – *Chairs*” can now render “The Musical – Chairs” in the output. The subset of Markdown here is just *Italic*, **Bold**, and ***Both***. _Underscores_ substitute in for asterisks on all three formats for those who prefer them. Given the place this occupies, I don’t think any other parts of the Markdown spec really make sense, though when making worksheets that feature a lot of content in a text frame… maybe this lays the groundwork for further improvements.

Other quick notes/highlights are:

  • Edit history
  • Stats panel
  • New text export features
  • Improvements with cautionary key signatures
  • Rhythmic slashes in cues
  • Hidden input in popovers!
  • Printing individual flows as separate files

These are all nice features, some of which satisfy long-standing entries on my personal wishlist and some I didn’t realize I really wanted. I’m greedy, so I’m already hoping for 5.2 goodies.

For more coverage on this, Scoring Notes has a good breakdown, and the official Dorico blog has a lot of video explanations.

  1. This is on Facebook, but it should be publicly available, even if you don’t have an account. ↩
  2. I actually prefer Pastebin to Github Gists in general, but for Markdown formatting, Github is hard to beat. ↩

https://mrehler.com/2023/12/24/dorico-5-1/

#dorico #notationSoftware

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst