Sustainability of Digital Formats: Planning for Library of Congress Collections

Introduction | Sustainability Factors | Content Categories | Format Descriptions | Contact
Format Description Categories >> Browse Alphabetical List

Finale Enigma Transportable File

>> Back
Table of Contents
Format Description Properties Explanation of format description terms

Identification and description Explanation of format description terms

Full name Finale Enigma Transportable File
Description

According to Finale file extensions and icons (link via Internet Archive), ETF or Enigma Transportable Files, now obsolete, are "an early version of Finale notation files in plain text format. They were used to transfer Finale music notation documents between Windows and Mac...The ability to create ETF files was discontinued in 2007. It has been replaced by the MUS, MUSX, and MusicXML formats...ETF files are automatically converted to MUSX when opened." See History for more information about the evolution of ETF files and the sunsetting of the Finale software application in August 2024.

As described in Enigma Transportable File Specification, Version 98c.0 (for Finale 97 for Mac and Windows), the main building component of ETF files is an "entry" which can be "a note, a chord, or a rest. Entries are streamed together in a doubly linked list that roughly corresponds to a voice on a staff...Each entry can have up to twelve notes." On the page, "each entry is signified by the tag ^eE with the entry number in parentheses. The line containing the ^eE contains information that pertains to the entry as a whole. Information about individual notes within the entry follows on zero or more subsequent lines." ETF defines a list of "entry flags" to describe the notation options available in the Finale software such as "floating rest", "tuplet" and the existence of a "note detail record" (controls note reduction, notehead displacement, accidental displacement, alternate note head). Each entry is identified by a 32 bit hexadecimal value consisting of the bit flags and specific flag name. These flags can be extended: "The extended entry flag is a 16 bit value. Although it is a bit flag like the entry flag, it is represented in the ETF as a decimal rather than hex value. There is no particular reason for this, and it does make the decoding somewhat trickier, but it has been retained to avoid conversion issues." Additional components called "Others, Details, Entry Details" are identified by a "tag (letters after ^ in each line)" and a description of the data. Examples include measure, key, time, tempo, performance data and instrument used. ETF allows for complex textual entries for context such as caret commands to specify style info (font,size,effects), tracking, and special macros like composer, date and page number.

Production phase Used during the creation process and as a middle state for sharing music among collaborators and colleagues that also use this software.
Relationship to other formats
    Affinity to MUS, Finale Legacy Music Notation File
    Affinity to MusicXML_family, MusicXML File Format Family. MusicXML files replaced the functionality of ETF files as a transfer format for notation data in later versions of Finale.

Local use Explanation of format description terms

LC experience or existing holdings As of August 2024, the Library of Congress has a very small number of ETF files (less than 100) in its collections, primarily in the Music Division.
LC preference See the Library of Congress Recommended Formats Statement for format preferences for musical scores and musical notation.

Sustainability factors Explanation of format description terms

Disclosure Limited. Some technical information is available but it is incomplete. Comments welcome.
    Documentation

Enigma Transportable File Specification, Version 98c.0 is available but this is incomplete documentation. According to Enigma Transportable Format (ETF) on MusicNotation.info, "you can download the official ETF documentation if you have registered at least one product from MakeMusic (Coda)" but this is unconfirmed. Comments welcome.

Adoption Obsolete format. ETF is a closed proprietary format which mainly relied on Finale to read and write. According to Finale file extensions and icons (link via Internet Archive), "the ability to create ETF files was discontinued in 2007. It has been replaced by the MUS, MUSX, and MusicXML formats...ETF files are automatically converted to MUSX when opened. www.music-notation.info includes a list of applications that import and export ETF files including Finale as well as etf2ly, an ETF to Lilypond converter but it's unclear if this functionality is still valid. Comments welcome.
    Licensing and patents This is a proprietary format specifically for Finale software which is owned by MakeMusic, formerly owned by Net4Music and first created by Coda Music Software. Patent information is unknown. Comments welcome.
Transparency Requires Finale software to read and write.
Self-documentation

Accessibility Features

ETF files have no specific attributes to support accessibility. Comments welcome.

External dependencies ETF files can only be accessed, viewed or printed by Finale software. Comments welcome.
Technical protection considerations Unknown or unable to confirm due to limited documentation. Comments welcome.

Quality and functionality factors Explanation of format description terms

Sound
Normal rendering This format does not render sound.
Functionality beyond normal rendering Does not render sound or audio bitstreams but instead stores the visual representation of a musical score.
Text
Normal rendering Although not strictly a format for textual content, formats for notated music can be text-based documents and share some functionality that are common with text.
Integrity of document structure ETF represents the semantic structure of a score: key; measures (bars); notes with pitch and duration; lyrics/words, etc.
Integrity of layout and display ETF can represent layout semantics that are important to the display of scores, such as: whether directions should go above or below a staff; spacing for staves; and scaling of features relative to a single measure that can be adjusted to fit a particular pagesize.
Other
Music Notation Components: Attributes (Staves, Clef, Time) All supported.
Music Notation Components: Musical Directions Unclear if supported. Comments welcome.
Music Notation Components: Note Appearance (Tuplet, Stems, Beams, Accidentals, Notations) All supported.
Music Notation Components: Multi-Part Music Unclear if supported. Comments welcome.

File type signifiers and format identifiers Explanation of format description terms

Tag Value Note
Filename extension etf
Finale user guide (link via Internet Archive) as well as PRONOM fmt/398 for Enigma Transportable File (Finale)..
Magic numbers Hex: 454E49474D4120(5452414E53504F525441424C452046494C45|7472616E73706F727461626C652066696C65)
ASCII: ‘ENIGMA' followed either by 'TRANSPORTABLE FILE’ or 'transportable file' and later proceeded by version
See https://www.nationalarchives.gov.uk/PRONOM/fmt/398 for Enigma Transportable File (Finale).
Other See note.  NARA File Format Preservation Plan ID has no corresponding entry as of September 2024.
Pronom PUID fmt/398
See https://www.nationalarchives.gov.uk/PRONOM/fmt/398 for Enigma Transportable File (Finale).
Wikidata Title ID Q58526743
See https://www.wikidata.org/wiki/Q58526743 for Enigma Transportable File (Finale).

Notes Explanation of format description terms

General The Macintosh Repository has many legacy Finale versions for Mac available for download, including Finale 1.0 from 1987.
History

Finale was originally written by Coda Music Technology, owned for a time by Net4Music, and later owned by MakeMusic. In the blog post The end of Finale (link via Internet Archive) posted on August 26th, 2024, MakeMusic announced that it was ending development for Finale software and ending technical support in 2025. Greg Dell'Era states that "four decades is a very long time in the software industry. Technology stacks change, Mac and Windows operating systems evolve, and Finale’s millions of lines of code add up. This has made the delivery of incremental value for our customers exponentially harder over time. Today, Finale is no longer the future of the notation industry—a reality after 35 years, and I want to be candid about this. Instead of releasing new versions of Finale that would offer only marginal value to our users, we’ve made the decision to end its development."

Margaret Cahill's thesis The Translation of Finale’s Enigma File Format for CPNView (link via Internet Archive) documents the history of the ETF format starting with the 1994 formation of a group to form the NIFF (Notation Interchange File Format): "commercial companies felt that it did not meet their needs and so a group of companies involved in p n producing music software decided to come together to devise a standard for music representation that would be specifically designed around their requirements." (p. 2). The participant list included Coda Music Technology who left the group: "At the start of 1995, NIFF 5 was released and at about the same time Coda Music Technology decided to withdraw from the group to concentrate on devising a file format of their own - the ENIGMA transportable file format." (p. 3). On February 8, 1996, Coda Music Technology released very limited documentation on ETF which focuses mainly on the Entry Pool. Cahill reports: "When Coda Music Technology released this documentation they invited questions and input from Finale users about the contents and layout of the file format, so they could gauge the need for data about the file and release further documentation as required. However on requesting information from the technical support at Coda Music Technology they reported that no further documentation would be released. The reason stated is because: 'This is due in large part to the fact that no such a document currently exists: its creation requires that our engineers take time away from their coding duties to document information that is buried in the code itself'." (p. 11).

HandWiki's entry on Software: Finale explains "the lead programmer for Finale version 1.0 in 1988 was Phil Farrand, better known in some circles as an author of Nitpicker's Guides for Star Trek and The X-Files. He wrote the original version software for Coda Music Software, which was later sold to Net4Music and then became MakeMusic. After Finale version 3.7, Finale's marketers made the switch to years as identifiers for each new release, starting with Finale 97. Those early versions of Finale used a file format called Enigma Transportable File with extension ETF." A post in the Finale Forum about ETF files from Peter Thomsen (Thu Jan 20, 2011 9:42 pm) states "The last Finale version that could save as ETF, was Finale 2006. Finale 2007 and later versions can open ETF files, but they can't save as ETF."

The Finale blog entry Welcome to the Finale Blog (link via Internet Archive) by Tom Johnson from August 17, 2009 explains a bit more about ETF and its relationship to ENIGMA: "ENIGMA. Many Finale users around the world have seen this term bantered around the Finale universe, but not many people know what it means. “ENIGMA Transportable File” (ETF) was the original term for a Finale file that could be shared across computer platforms (before this just “worked” as it does today). But wait, there’s more…ready? ENIGMA is an acronym for… the “Environment for the Notation of Intelligent Graphical Musical Algorithms.” Whew, what a mouthful! ENIGMA, as I understand it, was the name originally given to the code used to make Finale. I assume it was homage to the minds that created – and broke – the ENIGMA-encrypted messages in WWII. It was also the earliest name of the Finale software. What a blessing it was changed to Finale upon its release in September 1988. Can you imagine if it hadn’t been?"

Tyler Thorsted in his Obsolete Thor blog entry on Finale formats also mentions ENIGMA: "The first version of Finale was developed for the Macintosh and didn’t have an extension. But by version 3.5 there was a comparable Windows version and the use of the extension .MUS. In order to share the files between the different platforms Finale also created an ETF file, which instead of the binary MUS, the ETF is a plain text “transportable” file. Both formats are based on the Enigma or “Environment for Notation Intuitive Graphic Music Algorithms” format." The Obsolete Thor entry also includes a screenshot of the Finale 1.0 HyperCard HelpStack Glossary stack with a definition of the term ENGIMA.


Format specifications Explanation of format description terms


Useful references

URLs


Last Updated: 09/06/2024