Manual
Introduction
Installation
Invoking MusE
Window Reference Guide
Creating your setup
Getting Started
Software synthesizers coming with MusE
External Software synthesizers
Postproduction
Reference Information

Invoking MusE

MusE is invoked from the command line by typing in:

 muse

Optionally, you can use command line options of the form:

 muse <options> <midifile>

<options> : see section xyz? below for details on options. <midifile> can be either a standard MIDI file or a MusE file (*.med, *.med.gz or *.med.bz2).

Command Line Options

MusE accepts some options as listed below:

  • -a start in midi-only mode
  • -d debug mode: no threads
  • -D debug mode: enable some debug messages
  • -m debug mode: trace midi Input
  • -M debug mode: trace midi Output
  • -s debug mode: trace sync
  • -P n set real ime priority to n (default: 50)
  • -p don't load LADSPA plugins
  • -v print version

Example:
"muse -m -a mysong.med" will add trace midi input, only use midi and open mysong.med on startup.

File Types Recognized by MusE

MusE Configuration File ("~" refers to your home directory aka "/home/tux")

  ~/.MusE

Hidden Project File; stores list of last projects

  ~/.musePrj

MusE song file; internal MusE format

  .med

midi file; can be imported

  .mid

karaoke: midi file with additional information; some types can be imported

  .kar

Stored midi parts, these are an alternative way of storing structures in muse.

  .mpt

Stored plugin presets

  .pre
 

Hint: In some versions < 0.6.3 MusE loaded the old configuration from ~/.musePrj or ~/.MusE and because it didn't work then you could have also tried removing or at least moving this files out of the way temporary for testing purposes.

Powered by MediaWiki