Overview: Perfect Layout, v2.4, macOS/Windows

Perfect Layout v2.4 includes 42 new features, improvements and fixes and makes Perfect Layout compatible with the new Finale 27 SMuFl fonts.
The chronological list of changes in the sub-versions 2.40, 2.41, 2.42, 2.43, 2.44, 2.45, 2.46 is available here.
v2.x customers and customers who bought the full version of Perfect Layout v1.x after the 27th of March 2020 are eligible for a free update. For all other users the update is available through our online shop.
Please read our FAQ on how to install the update, especially on Windows.

                          
For Perfect Layout PDF Examples click here

Perfect Layout now has user dialogs in English, German, French, Polish and Italian.
A Spanish and Japanese version are also included, but still in beta state.


List of Improvements (until latest version v2.46)

New features:
-Gold: New option added to the Alignment tab: "Move Rehearsal and Tempo Expressions in Piano Staves from Between Staves to Above Group". If expressions in these categories were assigned below the top staff although the category default alignment is "Above Staff", then these expressions will be moved to above the staff. This feature had already been in before, but can now be deactivated in the Gold version.
-New option on the "Reset/Hide" tab: "Make Nearly Horizontal Custom Lines Horizontal". This feature had been implemented and active before. Now it's also possible to deactivate it.
-Finale 27 support: the new Finale SMuFl fonts are supported by Perfect Layout
-Accidental placement on chords with seconds is horizontally improved - though not in all cases yet:


Improved:
-Better detection of "Number" expressions and their usage (e.g. fingering, fret/string numbers, measure numbers, rehearsal numbers etc.).
-Expressions colliding with measure-centered measure numbers below staff are not moved beyond the measure numbers anymore
-Trill custom lines with long texts fields (up to 14 letters) are now correctly recognized. In previous version the limit was 9 letters. Usually 8 letter should be sufficient for long texts like "tr 1/2". Try to avoid to unnecessary spaces or a complex layout of these symbols.
-Improved horizontal placement on multiple accidentals if the accidental font has a right margin (e.g. Opus Std)
-Windows: On slow internet connections better detection of available plug-in updates.
-If a rehearsal letter plus two rehearsal/tempo texts were attached to the same measure position, in some cases the rehearsal texts now get an improved horizontal position.
-Measure number placement below tablature staves with 6 lines
-Empty measures followed by invisible measures are not merged into one large multi-measure rest, but now only the empty measures are taken into account.
-Added more music fonts to the list of known music fonts
-The German version of Finale uses different default folders than all other international versions. Unfortunately JW Lua can't access the configuration files settings, so it's always a little guess if it's the correct folder. The detection algorithm has been made more stable now. As users have reports German Finale installations where both the original folder "Configuration Files" and the German Folder "Konfigurationsdateien" have been present, make sure to check this and delete unnecessary configuration files folders. Otherwise Perfect Layout's font engine might not work correctly as it depends on the MacSymbolFonts.txt file.
-The fonts Bach, Kodaly and Bach4JP are now set to be non-MacSymbolFonts.txt fonts. On Windows this didn't make a difference, but on macOS Finale seems to have weird problems with these fonts in MacSymbolFonts.txt mode.
-Improved glissandi positioning when using the "Solid Line" tool instead of the Tab Slide or Glissando tool
-Improved spacing of lyrics on slash staff style measures with hidden notes
-In some cases improved vertical placement of very wide rehearsal/tempo marks that span multiple measures
-Improved vertical alignment between two piano staves if an expressive text is visually connected with a dynamic expression
-Scores with lots of pages (typically more than 50) are drastically improved in processing speed (up to 100%).
-Improved Spanish translation
-Better distance of lyrics under 1-line slash staff style notation
-Improved placement of some hairpins before low notes with articulations below
-Finale 27 support: time signature glyphs are now taken from the unicode block in SMuFl documents
-Finale 27 support: the macOS progress bar now displays Fin27 instead of Fin26.
-Improved spacing of lyrics on slash staff style measures with hidden notes
-Improved PDF manual


Fixed:
-MacOS: the 5-staff line symbol didn't show up correctly, if the Kodaly font was added to MacSymbolFonts.txt. Fixed now.
-On scores with lots of hidden staves (probably more than 30) in rare cases the vertical score balancing lead to a vanishing of the "Distance Between Systems Space" above of the top system of a page.
-If a multi-movement piano score includes an identical part with a different system layout, page texts with movement names assigned to pages could occur on the wrong place in the score. Fixed now. However it is very much recommended to not use page texts assigned to pages for movement names, but texts assigned to measures to avoid this confusion when parts are used.
-On complex trills constructed through custom smart lines and many "baselines" changes in text area in some cases the trill line was still vertically placed with collisions. Fixed now.
-In very rare cases an error message could occur when using expressions with non-existing symbols from a music font.
-When a grace note was attached to voice 2 to instead of the voice 1 note directly (don't do that as there is absolutely no reason for it), in some cases the metrics from a tie above the staff were calculated wrong which could lead to tempo marks colliding with the tie.
-MacOS: Internal update made more stable. The error message 9 and 12 should usually not occur anymore.
-When using a translation of Perfect Layout (and not the English original) a certain "Font missing" error message would sometimes show weird symbols. Fixed now.
-When the accidental font was different than any other used music font in that document, an error message could occur. Fixed now.
-On very badly formatted MusicXML documents an error message could occur (The document where this happened used multiple expressions (!) for each chord (each letter one expression) and some of them were also assigned to the wrong staff and different measure positions - probably the result from an OCR software). Fixed now.
-The automatic plug-in updater on Windows sometimes left a new folder inside the Finale plug-in folder. Fixed now.
-In very rare cases an error message could occur on hidden hairpins below ties. Fixed now.
-In very rare cases a staff overlap could occur on colliding note with accidentals. Fixed now.
-In rare cases (if the measure in the staff below has word extension smart shapes) a hairpin with a tie/slur collision was not corrected. Fixed now
-In rare cases there could be an error message on MusicXML imported documents using one of Finale's hide notes staff style when exporting the document to MusicXML
-Correct measure number placement in first measure if "Measure Number at Start of Staff System" is set to alignment "Center" and "Every 1 measure measures beginning with measure 1" is activated too.

System requirements:

  • Finale® 2014, 2014.5, v25, v26, v27 for 64bit Windows 7, 8, 10 or MacOS (tested in 10.13 - 10.15 and 11.0/Intel, according to some users also working in 10.11/10.12)
  • Minimum 4 GB RAM, for huge orchestra scores exceeding about 20.000 frame assignments 8-12 GB RAM and Finale® v25, v26 or v27 are required, otherwise the plug-in may run out of memory.
  • About 125 MB of free hard drive space, plus space for the font annotation files dependent on the number of fonts that are installed
  • For the installation/(de-)activation you need a user with administration rights
  • Internet connection during the installation and update process, and an email address to receive the activation code or an installed email program to request the activation code.
  • MacOS only: the MacOS version also requires an internet connection during the processing of the plug-in
  • MacOS only: You need to give system permission to use the Terminal app and System Events for displaying the plug-in's progress bar (optional)
  • Windows only: Powershell must be installed (it is installed by default on Windows unless the user has removed it manually)
  • The faster the processor speed, the faster the plug-in (see this comparison). The plug-in is single-threaded, so multiple cores do not speed up the processing.
  • Data Privacy: For the activation and license validation of the software some data will be stored on our servers. For more info read Data Privacy at Elbsound.studio and the EULA