Who’s T? Is it the now MuseScore design head?
. I’ve been actually toying with MuseScore and already “fixed” a small bug in the icon for Ubuntu, and helped fixing a bug that made one note tremolos display wrong. So, I guess I contributed already to fixing two bugs (and I’m not a programmer!). MuseScore is happily in a position where, if you know what you’re doing and want to spend some time manually tweaking stuff (the way Finale was/is), you can certainly produce a professionally looking score. The thing is, I still remember my years with Finale before switching to Sibelius, and I remember the pain of the hours I had to spend moving stuff around with the mouse, and the imminent danger that one millimeter in the wrong direction could basically destroy the whole score. When I discovered Sibelius 7.5 at the end of 2013, I also compared it to Finale 2014. I was really impressed by seeing how much of what Finale just did wrong by default was automatically done right in Sibelius. The magnetic layout, and the ability to “reset” the layout made me save countless hours in the next years, since I didn’t have to drag so much stuff around with the mouse anymore. So using MuseScore brings me back memories of Finale… That’s something that I would like to avoid for the moment. The work being made for MuseScore 4 looks very promising anyways.
The typing stuff with Lilypond has its advantages, I would say. Typing proper stuff with the keyboard is certainly way faster than remembering shortcuts. Stuff that in other programs are “advanced” features, make no difference in Lilypond and are as easy to remember. Say the command \tempo vs. the command \snappizzicato. Both things are keywords that already exist in the vocabulary of a musician. Having to remember instead a combination of keyboard shortcuts and going to the right menus, clicking stuff in the right order, remember to do all that in the right mode, looking for a Bartok pizzicato in an 800 symbol palette until you find it, etc., is more difficult than what it looks like. I guess Dorico’s equivalent of Lilypond commands is the pop-over feature (but I suspect it’s also filled with shortcuts to some degree, I can’t use Dorico, so I don’t really know
).
The good thing about Lilypond’s algorithm is that it always works fairly well. If you don’t like Lilypond’s default look, you can just use a different font. The engine will still do a pretty good job. I don’t think it’s a matter of adding more code. I really have to do very little manual tweaks (the bright side being, that it “understands” it in a way that the same tweak makes sense in the part as well as in the score). On the other hand, I can usually tell when a score has been made in Finale or Sibelius as well, provided that the user didn’t change the font
.





