MSCORE(1) | General Commands Manual | MSCORE(1) |
mscore
, musescore
— MuseScore 2 sheet music editor
mscore |
[-deFfhIiLmnOPRstvw ] [-a
| --use-audio driver]
[-b | --bitrate
bitrate] [-c |
--config-folder pathname]
[-D | --monitor-resolution
DPI] [-E |
--install-extension extension
file] [-j | --job
file.json] [-M |
--midi-operations file]
[-o | --export-to
file] [-p |
--plugin name]
[-r | --image-resolution
DPI] [-S |
--style style]
[-T | --trim-image
margin] [-x |
--gui-scaling factor]
[--debug ] [--dump-midi-in ]
[--dump-midi-out ]
[--experimental ]
[--export-score-parts ]
[--factory-settings ]
[--force ] [--help ]
[--layout-debug ]
[--load-icons ]
[--long-version ]
[--new-score ] [--no-midi ]
[--no-synthesizer ]
[--no-webview ]
[--revert-settings ]
[--template-mode ]
[--test-mode ] [--version ]
[file ...] |
MuseScore
is a Free and Open Source
WYSIWYG cross-platform multi-lingual music composition and notation
software, released under the GNU General Public Licence (GPLv2).
Running mscore
without any extra options
launches the full graphical MuseScore program and opens any files specified
on the command line.
The options are as follows:
-a
|
--use-audio
driverjack
,
alsa
, portaudio
,
pulse
-b
|
--bitrate
bitrate-c
|
--config-folder
pathname-D
|
--monitor-resolution
DPI-d
|
--debug
-E
|
--install-extension
extension file-e
is also specified-e
|
--experimental
-F
|
--factory-settings
-R
option-f
|
--force
-h
|
--help
-I
|
--dump-midi-in
-i
|
--load-icons
-j
|
--job
file.json-L
|
--layout-debug
-M
|
--midi-operations
file-m
|
--no-midi
-n
|
--new-score
-O
|
--dump-midi-out
-o
|
--export-to
file-P
|
--export-score-parts
-o
option, append
each part's pages to the created PDF file. If the score has no parts, all
default parts will temporarily be generated automatically.-p
|
--plugin
name-R
|
--revert-settings
-F
option-r
|
--image-resolution
DPIDefault: 300 DPI (actually, the value of “Resolution” of the PNG option group in the Export tab of the preferences)
-S
|
--style
style-o
option-s
|
--no-synthesizer
-T
|
--trim-image
margin-t
|
--test-mode
-v
|
--version
-w
|
--no-webview
-x
|
--gui-scaling
factor--long-version
--template-mode
MuseScore supports the automatic Qt command line options (see below).
The argument to the -j
option must be the
pathname of a file comprised of a valid JSON document honouring the
following specification:
in
plugin
plugin
and
out
must be given.out
plugin
and
out
must be given.flac
mid
mlog
mp3
mpos
mscx
mscz
musicxml
mxl
ogg
pdf
png
Individual files, one per score page, with a hyphen-minus followed by the page number placed before the file extension, will be generated.
spos
svg
wav
xml
See below for an example.
SKIP_LIBJACK
XDG_CONFIG_HOME
XDG_DATA_HOME
XDG_DOCUMENTS_DIR
Note that MuseScore also supports the normal Qt environment
variables such as QT_QPA_GENERIC_PLUGINS
,
QT_QPA_PLATFORM
,
QT_QPA_PLATFORMTHEME
,
QT_QPA_PLATFORM_PLUGIN_PATH
,
QT_STYLE_OVERRIDE
, DISPLAY
,
etc.
/usr/share/mscore-2.3/ contains the application support data (demos, instruments, localisation, system-wide plugins, soundfonts, styles, chords, templates and wallpapers). In the Debian packages, system-wide soundfonts are installed into /usr/share/sounds/sf2/, /usr/share/sounds/sf3/ or /usr/share/sounds/sfz/, respectively, instead.
The per-user data (extensions, plugins, soundfonts, styles, templates) and files (images, scores) are normally installed into subdirectories under $XDG_DOCUMENTS_DIR/MuseScore2/ but may be changed in the configuration. Note that snapshot, alpha and beta versions use MuseScore3Development instead of MuseScore2 in all of these paths.
$XDG_CONFIG_HOME/MuseScore/MuseScore2.ini contains the user preferences, list of recently used files and their locations, window sizes and positions, etc. See above for development version paths.
$XDG_DATA_HOME/data/MuseScore/MuseScore2/ contains updated localisation files downloaded from within the program, plugin information, cached scores, credentials for the musescore.com community site, session information, synthesiser settings, custom key and time signatures and shortcuts. See above for development version paths.
Convert a score to PDF from the command line:
mscore
-o
'My Score.pdf' 'My
Score.mscz'
Run a batch job converting multiple documents:
mscore
-j
job.json
This requires the file job.json in the current working directory to have content similar to the following:
[ { "in": "Reunion.mscz", "out": "Reunion-coloured.pdf", "plugin": "colornotes.qml" }, { "in": "Reunion.mscz", "out": [ "Reunion.pdf", [ "Reunion (part for ", ").pdf" ], "Reunion.musicxml", "Reunion.mid" ] }, { "in": "Piece with excerpts.mscz", "out": [ "Piece with excerpts (Partitura).pdf", [ "Piece with excerpts (part for ", ").pdf" ], "Piece with excerpts.mid" ] } ]
The last part of the job would, for example, cause files like “Piece with excerpts (part for Violin).pdf” to be generated alongside the conductor's partitura and a MIDI file with the full orchestra sound, whereas the equivalent part of the Reunion conversion will be silently ignored (because the Reunion piece (a MuseScore demo) has no excerpts defined).
https://musescore.org/sites/musescore.org/files/midi_import_options_0.xml
is a sample MIDI import operations file for the -M
option.
The mscore
utility exits 0 on
success, and >0 if an error occurs.
fluidsynth(1), midicsv(1), timidity(1), qtoptions(7)
Please check first to if the bug you're encountering has already been reported. If you just need help with something, then please use the support forum (see above) instead.
MuseScore attempts to implement the following standards:
MuseScore was split off the MusE sequencer in 2002 and has since become the foremost Open Source notation software.
MuseScore is developed by Werner Schweer and others.
This manual page was written by mirabilos ⟨tg@debian.org⟩.
The automatic Qt command line options are removed from the argument vector before the application has a chance at option processing; this means that an invocation like
mscore
-S
-reverse
has no chance at working because the
-reverse
is removed by Qt first.
MuseScore does not honour /etc/papersize.
Probably some more; check the project's bug tracker (cf. SEE ALSO).
March 20, 2019 | MuseScore |