Surreal that this album is now #1 IN THE WORLD!
Last night I had the pleasure of attending a special seminar in Los Angeles given by Daniel Spreadbury demonstrating Steinberg’s new notation application, Dorico. As some readers may already be aware, Avid -- the parent company of Sibelius -- laid off its core team of developers several years ago, and this team was quickly snatched up by Steinberg and given the task of developing a fresh new notation program. The resulting product, Dorico, was released in the last quarter of 2016.
Last Night’s Presentation:
Mr. Spreadbury’s presentation last night was outstanding. Despite starting a bit late (LA traffic), a number of very impressive features were demonstrated. Intuitive setup, workflow, layout, intelligence, flexibility and efficiency make Dorico stand out as a very viable competitor to Finale and Sibelius. Dorico’s team has poured their talents into this new software, and their attention to detail, design and execution is invigorating.
Having had a chance to work with the program personally for several days prior to attending Mr. Spreadbury’s presentation, here are some features to report my impressions on:
Score setup is quite straight-forward and logical. Upon starting the program, the user is greeted with the “Steinberg Hub” menu, which, among other options, offers the user a choice of various orchestral, band, choral, musical theater, and chamber music templates. Regrettably missing are templates for big-band, small jazz ensembles, and most other pop / rock music ensembles. Upon selecting a template, a blank score containing a single quarter rest appears on the screen, ready to accept notation input.
Dorico features five discrete “modes” for different types of tasks: Setup, Write, Engrave, Play, and Print. You can quickly switch between the five modes with the ⌘(command)+1-5 keys.
Keyboard shortcuts (key commands)
As a user who absolutely detests reaching for the mouse or trackpad, I love that there is a key command for nearly every action within the program. Although the default commands are very logically laid out and share some similarities to other notation programs I am familiar with, every key command is customizable, and each action lacking a default key command by default can have one assigned to it. However, hovering the mouse cursor over buttons in the user interface does not always display the corresponding key command, which I find to be slightly annoying and hope that Dorico will address in a future update.
Inputting notes, dynamics, articulations, lyrics, and other musical elements into Dorico is quite easy to figure out, and once I better familiarize myself with the menus and keyboard shortcuts, I believe input can be done much faster and more efficiently using Dorico than with any of the competing notation programs. The layout looks quite beautiful immediately upon entering notes with virtually no alignment or collision issues. I also tested opening several scores that were exported from other programs using MusicXML and found the results to be quite impressive.
Sounds and Playback
One of the first things I noticed when inputting notes into Dorico was the superb sound quality. Dorico makes use of the HALion Sonic SE VST instruments, and their default settings are quite good. Perhaps the days of sending a disclaimer to clients to apologize for a cheesy sounding orchestral mockup may be finally over!
Another feature I love is the ability to fine-adjust the parts in piano roll view without affecting the printed notation - very useful for tweaking specific parts to make even more realistic sounding playback. Dorico also supports nearly every third-party VST3 instrument and plugin, and I was pleased to see that all of my third-party VST3 plugins were available and functional within Dorico without too much additional configuration needed.
No Chord Symbol Support Yet
According to Dorico, this feature will be included in a future update. Their reasoning behind omitting this feature seems to have been largely due to the time constraints of the release deadline. Since I work a lot in pop and jazz genres, this missing feature will unfortunately prevent me from being able to seriously use Dorico for the time being. However, I plan to begin training myself in how to use Dorico in anticipation this feature release.
Dorico is a very promising, well-designed program, and I wholeheartedly compliment Daniel Spreadbury and the Dorico development team for their hard work. As many Finale and Sibelius users will attest, the increasing need for workarounds and third party plugins to compensate for buggy or illogical behavior in those programs has long been a source of irritation to users. Dorico, while not quite perfect yet, has enormous potential and I believe that it may eventually be the notation program that many of us have long wished for. I look forward to the release of the next update of Dorico and may then seriously consider abandoning Sibelius and Finale altogether.
Sibelius plugin review: Tom Curran's Impose Sketch onto Template, version 2.01
When I heard about the initial release of this plugin last week, I was immediately excited to give it a try, as it brings several much-needed features to Sibelius. Since many notation projects involve importing material from one type of score into another, this plugin can be a huge time-saver and eliminate several tedious steps from the process.
The plugin functions to import the structure and various fundamental elements from one score to another. In addition, it transfers tempo markings, time signatures, key signatures, bar number changes, rehearsal markings, system symbols, system lines, and special barlines (double, final, repeat, etc.) from the source score into the template score. In a DAW environment, one might compare this plugin to the "Import Session Data" feature of Pro Tools.
But how is this better than simply using Sibelius’s built-in “System Passage” function to select and then copy/paste from the source score into the template? The default “System Passage” function, while useful, doesn’t offer options to selectively omit certain elements from the source score. As a result, this method usually creates a mess of unwanted material in the template score. Tom Curran’s very smart plugin, on the other hand, is extremely customizable and only does what you tell it to do, allowing you to better retain the look of the template score without having unwanted elements imposed upon it.
The usage of the plugin is very clearly documented in the Sibelius plugin site and even includes a YouTube video demonstration. Below are several screen captures from the video, showing the plugin being used to import the structure from a piano-vocal sketch into a larger orchestral template.
My only gripe with the plugin is its name, which falls a bit short in describing what the plugin actually does. I might have named it something along the lines of “Selective Score Element Import,” but nevertheless it is an excellent addition to the the Sibelius plugin collection and I am deeply grateful to its creator, Tom Curran, for putting in the time to build it. Bravo!
A significant part of my work involves transcribing music. Whether it's prepping a live show for an artist, making charts for a recording session, or transcribing an entire orchestral score, the basics of my transcription process remain essentially the same. The primary goal is to create error-free parts and scores that are clear and easy to read.
It goes without saying that in order to properly notate music, one has to have proficiency in music theory and music notation, and must be able to recognize rhythms, pitches and chords. Beyond that, an understanding of each instrument's respective ranges and capabilities is needed to correctly notate its parts.
1. TWO-WINDOW ENVIRONMENT
I do most transcriptions in a two-window environment: source audio on one side, score on the other. Often, I will tile the windows to accommodate whichever application requires the most space. On a Mac, I use BetterSnapTool to neatly place each window just where I want it and to maximize screen real estate. On a PC, the OS has similar functionality built in without the need of a third party add-on.
2. AVOID MEDIA PLAYERS - USE A DIGITAL AUDIO WORKSTATION (DAW) APP
I find it extremely helpful to put my source material in a multitrack audio program such as Pro Tools, Logic, Cubase (my DAW of choice for this is Cockos Reaper). This enables me to quickly tempo-map the source audio and establish the form, exact number of bars, location of beats, tempo changes, and meter changes. Having all of this information laid out visually in a grid makes it easy to create a transcription that has the correct number of bars. THIS DOES NOT NEED TO BE A COMPLEX, SAMPLE-ACCURATE TEMPO MAP. I will be publishing another article on advanced tempo-mapping techniques soon.
Learn to navigate within your DAW with keyboard shortcuts. It is a huge time-saver to be able to skip back one bar, forward two beats, or to advance to the next chorus -- all without having to touch the mouse. In many DAWs, you can even create your own custom keyboard shortcuts to further reduce the amount of wasted time and mental energy spent hunting through your source audio.
Q: DO I NEED TO MAKE A TEMPO MAP IF THE MUSIC IS REALLY SIMPLE?
A: It depends. If the music has a perfectly steady tempo, then you just need to determine the initial tempo, form, number of bars, and location of any time signature changes. Often, however, tempo-mapping out a simple-sounding song will reveal that it has a cleverly inconspicuous 2/4 bar or an unconventional form.
Q: IT'S TOO HARD TO CREATE A TEMPO MAP FOR THIS PARTICULAR PIECE BECAUSE THE TEMPO KEEPS CHANGING AND THERE ARE LOTS OF HOLDS. WHAT DO I DO?
A: Learn to do it. It's worth it. It is especially important when working with music that has numerous tempo changes to determine where the beats and subdivisions are. Without doing this, you have little hope of creating an accurate transcription that a performer would be able to play.
3. NOTATION SOFTWARE
Although I admire the beauty of hand-written music, its limitations with regard to revisions, scalability, and error-checking make it impractical for my purposes. Though I used Finale for many years and still maintain proficiency with it, I now prefer to work in Sibelius.
Just as with the audio sequencer, it is essential to master the keyboard shortcuts of the notation software. I use a number of custom keyboard shortcuts to further streamline my workflow.
Finale and Sibelius come with many useful ready-made templates that can make your score look clean and professional. I have also created a number of my own templates to help me avoid needing to rebuild scores for instruments and types of ensembles. I avoid the fonts and templates that mimic handwritten charts, not only because I find them ugly, but also because the text can be hard for players to read in poor lighting.
Making a good transcription is part listening, part deductive reasoning.
Transcribing music is more than just "hearing" what is in the recording. The focus must be on the more important information, while filtering out what is less relevant. The reality is that instruments are not always perfectly in tune; sometimes passages are not executed clearly; sometimes musicians play ahead of- or behind the beat; and sometimes the recording's mix makes it impossible to pick out what certain players are doing. In all of these cases, a good transcription is one that most accurately depicts the intent of the music and will then enable whoever will be playing the transcription to re-capture that intent.