jojo-schmitz / batch_export Goto Github PK

• [Improvement]: Allow to export the files to the dedicated folder when even parsing subdirs
• [Improvement]: Export the main score when only the parts are to be exported and there are no parts
• [Improvement]: New option to rename the files when exported

• [Improvment] Apply! button in the log preview panel;
• [Bug] More dark mode tweaks

• [Improvment] Choose to export the main score, the score and its parts or (new) only the parts;
• [Bug] Exporting a score which was opened on a part (instead of the main score) threw an error
• [Bug] Exporting a score which was new and unsaved threw an error

1. Select "Batch Convert" (formerly "Batch Export") from the Plugins menu
2. Select the in- and output format(s), or just use the default (*.mscz to *.pdf)
3. Decide whether or nor you want to also work on subdirectories of the one you'll select in the next step and check/uncheck the corresponding box
4. Browse to the folder containing the files you wish to export
5. Select "Convert!"
6. Confirm the dialog box that shows which files have been converted

You can prevent a part from being exported by prefixing its name by a ".". E.g. A part labelled ".forTest" will not be exported.

You have define how to build the folder structure. Accepted characters and keywords are:

• "/" as folder separator
• Any character except %*?"<>:|
• Any of the following keywords:
  • "%TITLE%" : as defined in the score properties
  • "%LYRICIST%" : as defined in the score properties
  • "%COMPOSER%" : as defined in the score properties
  • "%ARRANGER%" : as defined in the score properties (*)
  • "%WORKNUMBER%" : as defined in the score properties
  • "%MOVEMENTNUMBER%" : as defined in the score properties
  • "%MOVEMENTTITLE%" : as defined in the score properties
  • "%YEAR%" : year part of the creation date
  • "%PART%" : "scores" or "parts" depending that a score is exported or one of its subparts
  • "%FORMAT%" : the format of exported file. E.g. "pdf"

What if a file does not provide a value for a properties used in the export structure ?

• if ARRANGER is missing, then the export will try using COMPOSER instead
• You can either skip the file by unselecting "With missing properties"
• You can include the file and replace the missing property by a default string, by selecting "With missing properties" and providing a replacement string such as "unspecified"

Example : In order to export all the scores in a folder named from its composer property (e.g. export all John Coltrane scores in a "John Coltrane" subfolder), use "%COMPOSER%" as folder structure.

• Musescore 4.0 is not supported for now (it shows the UI in 4.x, but doesn't convert anything yet)
• You may need to have a score already open in order for the Plugins menu to be active. Fixed in MuseScore 2.0+ (and resurfaced in 4.0)
• In MuseScore 2.0.1+ make sure you don't have a score open, that you want the plugin to process, because it won't be able to load it then.
• The scores for which files were exported may be left open in tabs. If so, you'd need to close them manually. Fixed with MuseScore 1.2+
• These open tabs will be labeled "untitled". Fixed in MuseScore 2.0+ and not an issue anymore with MuseScore 1.2+, see above
• The 2.x version of this plugin needs at least 2.0.1
• The 3.x version of this plugin needs at least 3.0.2
• If you're on macOS and the file dialog for step 4 above does not show up, try using the Mac version of the plugin which is in the branch 'mac' (for 3.0, actually that version seems to run fine in Windows too) or mac-2.x (for 2.x).
• All files processed by the plugin for MuseScore 2.0+ will be listed in the 'Recent File' menu.

These issues are fixed with the above mentioned versions, and without re-installing the plugin.

This plugin now comes with translations of the dialogs into German, French (thanks to lgvr123, lasconic and JLWALTENER), Spanish (thanks to jorgk), Italian (thanks to Shoichi) and Simplified Chinese (thanks to David Copperfield), for all other language settings in MuseScore, it remains English. More translations are welcome, just contact us for including them.

The idea for this plugin stems from a question in the forum. See also this discussion about the 2.0 version

NO WARRANTY THE PROGRAM IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND...