Documentation

Check out the tour for some quick information about MusE. There are also some tutorials on the Tutorials page which should help you get into MusE. There is also a demos page that we hope will soon be filled with good demonstrations of what MusE can do.

The current (or rather, not so current...) documentation is on the Manual page. The FAQ Frequently asked questions

Installation instructions

Check the Installation page for basic instructions on how to compile and install MusE. When starting from the developer version, be sure to check out the SVN page for information about how to get it working.

Showcase

Want to see more of what MusE looks like, check the Screenshots page.

Community

There are lots of people using MusE for recording and creating music and other creative activities. Some of the people using and creating MusE regularily meet online.

We very much encourage people to take part in the further development of MusE check the Helping out page for ideas and other information about what you can do.

Do you want write access to the WIKI? please ask on the mailing list.

Forum

As of 10th of february 2011 we now have a forum (tada!, we have finally entered the new millenium) as an alternative discussion medium. It is available here: http://sourceforge.net/apps/phpbb/lmuse/

Mailing Lists

If you want to get in touch with this part of the commmunity be sure to register on one or more of the mailing lists listed here: The MusE mailing lists

IRC chat

MusE now has it's own IRC chat channel where some of the developers and users hang out. For instant access do try it!

The channel is called #lmuse. There are lots of specifically tailored IRC clients, though if you are not a regular IRC user an easy way to access the page is through a web-based client, for instance: http://webchat.freenode.net/.

Bug reporting / Troubleshooting

Report a bug if you found a bug or want to request a feature.

Bugs that cause muse to crash (segfault) are sometimes very hard to reproduce for the developers. To fix the bug somekind of hint where the error lies is needed.

Here are some basic rules for better being able to give error reports:

• Setup your shell such that it can create core dump files (basically a memory dump that contains the program when the error happened.

This can be done with the command ulimit -c unlimited for bash shells.

It is recommended to add this to command to the .bashrc file in your home dir. That way you will always get core files. (note that this is true for all programs started)

• Build muse with debug symbols.

This can be changed by editing the CMakeLists.txt or using the cmake-gui tool to set CMAKE_BUILD_TYPE to debug

After having enabled core dump creation and provoking a crash the memory of the program is written to a file called "core". gdb <path to muse2 binary> core allows you to get usable information, for instance a backtrace for the crash point bt.

Example:

gdb /usr/local/bin/muse2 core

$ bt

There is also a heavyDebug parameter ("muse2 -DD") which can be used to let MusE print more verbose debugging information.

Misc

Tools / Programs which you should know!
Links to MusE related things
Art MusE related fan art