Finale alternative for orchestral scores

If you write full orchestral scores and you were using Finale, you are probably looking for the right tool to switch to, since it stopped being developed in August 2024.

Orchestral writing puts weight on things a smaller project never tests: transposing instruments written correctly, twenty or more staves you can reorder into score order, rehearsal marks that stay in sequence when you cut bars, long rests consolidated in the parts, and a clean part for every player. Your existing scores also have to come across, and that depends on what your old files will export rather than on which editor you prefer.

Here is what to check, and how Flat handles each of them.

Where your scores stand now that Finale is unsupported

Finale still opens on any machine where it is already authorized, and MakeMusic has said that downloading and authorizing registered products stays available for the foreseeable future. So there is no cliff edge. What there is instead is a slow narrowing: development ended, technical support has closed, and every operating system release from here is one the application was never tested against. Plenty of people will get another few years out of it.

An orchestral catalogue is a particular kind of exposure. These are not files you rebuild in an afternoon. A single score can represent months of work, and the parts that went with it were proofread over several rehearsals. If a piece gets programmed again in three years, you need to open it, fix the two things the players flagged, and print a fresh set. That is the reason to move deliberately rather than take the first recommendation from a forum. If you want the wider field first, we looked at the main Finale alternatives separately.

What to look for in a Finale alternative for orchestral scores

Orchestral scores have requirements that smaller formats never expose. These are the ones worth testing before you move a catalogue.

• Transposing instruments, both ways. You need to read the sounding harmony while you work and hand each player a part in their own key. Flat can show a score in concert pitch or in each instrument's written pitch, so clarinets and horns read what they expect without a separate file.
  
  💡 Display the score in concert pitch.
• A large instrument list you can reorder. Twenty or more staves have to sit in score order, and that order changes when you add a second harp or drop a doubling. Flat lets you add, remove and reorder parts in an existing score rather than starting again.
  
  💡 Add, remove or re-order score parts.
• Rehearsal marks that keep their sequence. Nothing wastes rehearsal time like marks that stopped matching after a cut. Flat has rehearsal letters and numbers and maintains the sequence as you add and remove them.
  
  💡 Add or remove rehearsal marks.
• Multimeasure rests in the parts. A third trombone should not be counting forty empty bars one at a time. Flat consolidates rests of more than three bars, which is exactly what instrumental parts need.
  
  💡 Add or remove multimeasure rests.
• Divisi on one staff. Two independent lines on a single string staff, with their own rhythms, is standard writing rather than an edge case. Flat supports more than one voice within a staff.
  
  💡 Working with voices.
• Control over where systems and pages break. Page turns decide whether a part is playable. Flat lets you place system and page breaks yourself instead of accepting whatever the automatic layout gives you.
  
  💡 Add or remove system breaks.
• Gradual tempo changes. An accelerando is not a text marking, it should affect what you hear when you check a transition. Flat treats accelerando and ritardando as tempo changes rather than decoration.
  
  💡 Accelerando and ritardando.
• Exporting the score and every part. One conductor's score, then thirty parts, is the actual deliverable. Flat exports the full score, one individual part or a set of parts, as PDF, MIDI or MusicXML, plus an MP3 or WAV of the playback.
  
  💡 Print and export your scores.

How easily your existing scores transfer

Moving a catalogue is quicker than most people expect. Export from Finale while you still have a working installation, since its own files open only in Finale and MusicXML is the way out. You do not have to go one at a time either: Finale batch exports to MusicXML, so the whole catalogue can leave in a single pass. There is a step-by-step guide for the Finale end of this, and Flat reads the resulting files directly. Notes, instrument assignments and most markings arrive intact, though on a large score it is worth checking transposing staves and page turns before you print parts.

Anything that will not export, or only ever existed on paper, comes in another way. Flat imports PDFs and turns them into editable scores, which covers older material that was never in any software. If you want the detail on how transposition itself works, we have a separate piece on transposing in Flat.

Why Flat works for orchestral scores

The score is not tied to one machine. Flat runs in a browser and as apps on iOS and Android, so the movement you were orchestrating at your desk is the same file you open on a laptop at a rehearsal, with nothing to export and no version to keep track of. For work that stretches over months, that alone removes a category of mistake.

The other difference is who else can be in it. Two people can work in the same score at once, so a copyist, an assistant or a conductor with questions can be inside the actual file rather than annotating a PDF you then have to transcribe. And when you want to see how someone else laid out a large ensemble, the public scores in Flat's community can be copied into your own library and taken apart.

Ready to get your first score out of Finale? Try Flat for free!