Differences

This shows you the differences between two versions of the page.

--- frequently_asked_questions [2009/12/01 01:50]
michael
+++ frequently_asked_questions [2025/12/01 19:10] (current)
tedfelix [How to get a stack trace for a crash]
@@ Line 1: / Line 1: @@
+====== Frequently Asked Questions for Rosegarden 10.02 and Later ======
-======Frequently Asked Questions for Rosegarden "Thorn" and Later======
+===== General questions =====
-Rosegarden 10.02, codename "Thorn" is in the early alpha stage, and will be released in February of 2010.
+==== What about Windows, OS-X, BSD? ====
-For questions about Rosegarden 1.x, please see the [[dev:1.7.x_faq|Old FAQ]].  (**Note that development on 1.7.x has been suspended, and we are no longer accepting patches or translations updates against that line of code.**)
+Rosegarden is currently an application for **Linux** only.  Since Rosegarden uses Qt 6, it shouldn't be too difficult to support multiple platforms.  However, we are still very dependent on ALSA to provide MIDI infrastructure and JACK to provide an audio interface, and this will not be changing in the near future.
-=====General questions=====
+==== Do I have to be using a particular desktop environment (KDE or whatever)? ====
+No. Rosegarden uses the Qt 6 libraries for various common controls, but you can run it under any window manager or graphical environment you like.  So long as ALSA and JACK are available.
-====What about Windows, OS-X, BSD?====
+==== What are the hardware requirements like? ====
-Rosegarden is currently an application for **Linux** only.  Now that we have ported to Qt 4, and now that Qt is freely available for all platforms without a commercial license, there are fewer obstacles standing in the way of eventually becoming a cross-platform application.  However, we are still very dependent on ALSA to provide MIDI infrastructure and JACK to provide an audio interface, and this will not be changing in the near future.
+Minimal these days.  See [[http://www.rosegardenmusic.com/getting/requirements|requirements]] for more details.
-We would like to run on OS-X, BSD, and similar platforms one day, but a Windows port is unlikely to happen unless someone agrees to hire Michael and pay him a regular salary to develop and support Rosegarden on Windows.
+==== Does it support my soundcard? ====
-====Do I have to be using a particular desktop environment (KDE or whatever)?====
+So long as your soundcard is supported by ALSA you are good.  See the ALSA project's [[http://www.alsa-project.org/alsa-doc|soundcard matrix]].
-No. Rosegarden uses the Qt 4 libraries for various common controls, but you can run it under any window manager or graphical environment you like.  The only marked change in functionality comes when printing or previewing with LilyPond.  This feature requires an external backend to print or preview the resulting .PDF file.  By default, Rosegarden is configured to use lpr for printing and Okular for previewing.  You can change this on **Settings => Configure Rosegarden => General => External Applications** to use either Gtk-LP, lpr, or lp for printing, and Okular, Evince or Acroread for previewing PDF files.  One file printing program and one PDF viewing program from each list of supported backends must be available at runtime in order for these features to work.  (LilyPond is also required!) Otherwise, we aim to be as desktop-neutral as we can be.  We have removed all dependencies on KDE, though we still require JACK and ALSA, and are still tied to the Linux platform for now.
+==== Is it available in my language? ====
+English is fully supported.  Depending on the availability of translators, other languages might also be available.  Lately (2025) we've got translations for Polish, German, and French.
+If you can help out with translating musical or technical documentation (no programming required, but it's quite hard work), please let us know!
-====What are the hardware requirements like?====
+Please take a look at the wiki page dedicated to [[translator:Add or update translation|adding or updating translation]] for complete details.  That page tends to be more up to date than this section of the FAQ.
-Reasonably demanding, because of the mixture of graphical and interactive GUI stuff with precisely timed audio stuff. See [[http://www.rosegardenmusic.com/getting/requirements|requirements]] for more details.
+==== Rosegarden apparently saves in a binary format, where can I find the format definition? ====
+Actually it's just gzipped XML.  You can use zless to look at an .rg file:
+  $ zless file.rg
-====Does it support my soundcard?====
+gzip has a bit of trouble with gzipped files that don't end in .gz, so the easy way to have a look is to use
-Rosegarden uses the ALSA (Advanced Linux Sound Architecture) soundcard drivers. To find out whether your card is supported by ALSA, see the ALSA project's [[http://www.alsa-project.org/alsa-doc|soundcard matrix]].
+  $ gunzip -c somefile.rg >somefile.xml
+===== Compilation or installation problems =====
+==== Rosegarden is crashing at startup ====
-====Is it available in my language?====
+We've not had any reports on this in a very long time.  Please post to the mailing list if you are having problems.
-Fully complete translations are usually provided for British English, Finnish, French, German, Japanese and Spanish with each public release.  Translations for Czech, Dutch, Italian, Swedish, and Russian are usually substantially complete.  Translations for several other languages exist in various states of disrepair, with Welsh at rock bottom with no updates since before Rosegarden 1.0 was released.
+https://sourceforge.net/projects/rosegarden/lists/rosegarden-user
-These translations are provided and maintained by volunteer contributors, and most contributors tend to come and go pretty randomly.  We have had real trouble attracting and keeping translators, and the most complete translations are usually updated by Rosegarden developers who have to double as translators on top of their other responsibilities.
+==== How to get a stack trace for a crash ====
-If you can help out with translating musical or technical documentation (no programming required, but it's quite hard work), please let us know!
+First, make sure you are running a version of rosegarden that was built with debugging turned on.
-Please take a look at the wiki page dedicated to [[translator:Add or update translation|adding or updating translation]] for complete details.  That page tends to be more up to date than this section of the FAQ.
+<code>
+-DCMAKE_BUILD_TYPE=Debug
+</code>
+Without debugging, there will be no symbols in the binary, and the backtrace will be useless.  You'll likely need to build rosegarden on your own to get a debug version.  Instructions can be found here: [[dev:Building Rosegarden from Source]]
-====Rosegarden apparently saves in a binary format, where can I find the format definition ?====
+Open a terminal window, and check to ensure that applications will be able to produce core dumps.  The exact command and syntax may vary from shell to shell, but for bash it is ''ulimit -a'':
-Actually it's just gzipped XML.
+<code>
+$ ulimit -a
-gzip has a bit of trouble with gzipped files that don't end in .gz, so the easy way to have a look is to use
+core file size          (blocks, -c) 0
-<code bash>
+data seg size           (kbytes, -d) unlimited
-  $ gunzip -c somefile.rg > somefile.xml
+scheduling priority             (-e) 20
+...
 </code>
+The above example is quite typical for an end-user desktop system.  Having the "core file size" set to 0 prevents the creation of very large core dump files in unexpected places, and is generally a good thing.  However, this also prevents you from generating a stack trace.  You need to change the limit to something larger than 0, but many systems prevent you from setting this to ''unlimited'', so we suggest
-=====Compilation or installation problems=====
+<code>
+$ ulimit -c 1000000
+</code>
-====Rosegarden is crashing at startup====
+Now start a **debug version** of rosegarden from the command line, and reproduce the crash. You should now have a core file in your current directory. The core file is either named **core** or **core.<//number//>**.
-(The sequencer is no longer a separate process, so this old FAQ is obsolete.  Watch this space for new FAQs related to this topic.)
+Run ''gdb'':
-====How to get a stack trace for a crash====
-(This needs some experimentation.  I'm not sure if KDE's debug handler would come into play for a plain Qt app or not.  I need to play with my environment and see what happens, but I suspect it's now just a question of enabling core dumps.  The bright side is this is easy to test now, since it is simple to get Rosegarden 09 to crash.)
-<del>First export the environment variable KDE_DEBUG as follows (in bash):
 <code>
-  $ export KDE_DEBUG=1
+$ gdb rosegarden <core_file>
 </code>
-Start rosegarden from the command line, and reproduce the crash. You should now have a core file in your current directory. The core file is either named "core" or "core.<number>". Run gdb :
-<code>
-  $ gdb rosegarden <core_file>
-</code>
-Then once you get the gdb prompt, use the command 'where' to get the stack trace, and mail to the authors or to the Rosegarden development mailing list, or include in a bug report.</del>
-====What packages do I need to build this?====
-====Build requirements=====
+Then once you get the gdb prompt, use the command 'bt' to get the stack trace, and mail it to the authors or to the Rosegarden development mailing list, or include it in a bug report.
-Rosegarden requires the following runtime libraries and SDKs to compile:
+==== What packages do I need to build this? ====
-  * Qt 4.3 or later
+==== Build requirements =====
-  * ALSA 1.0 or later
-  * libjack 0.77 or later
-  * LADSPA 1.1 or later
-  * DSSI 0.9 or later
-  * Xft2 2.1 or later
-  * liblo 0.23 or later (0.23 is newer than 0.7)
-  * liblirc 0.8 or later
-  * FFTW version 3
-  * autoconf
-  * pkg-config
+Please see the [[dev:Building Rosegarden from Source]] page for detailed dependency and build information.
-====Runtime requirements====
+==== Runtime requirements ====
-In order to be fully functional and provide the optimal user experience,
+In order to be fully functional and provide the optimal user experience, Rosegarden requires the following external applications.
-Rosegarden requires the following external applications.  We suggest listing
-them as your distro's equivalent of "recommends" level dependencies.  (Yes, this
-is a long list, and yes, we really do use all of these for something.)
-  * perl
   * bash
-  * qsynth AND fluid-soundfont-gm* OR timidity AND freepats*
+  * available, functioning ALSA General MIDI soft synth (QSynth, TiMidity++, etc.) with soundfont (Fluid-Soundfont, Freepats, etc.)
   * lilypond
-  * ocular OR acroread OR kpdf OR evince
+  * ocular OR acroread OR evince
-  * kprinter OR gtklp OR lpr OR lp
+  * gtklp OR lpr OR lp
   * jackd
-  * sox
-  * sndfile-resample
   * flac
-  * oggdec
+  * wavpack/wvunpack
-  * mpg321
-  * libxml-twig-perl
   * qjackctl
-  * DSSI plugins (any your distro carries)
+  * DSSI plugins (any available)
-  * LADSPA plugins (any your distro carries)
+  * LADSPA plugins (any available)
-  [*] the key here being that either softsynth should come with an installed
+===== Main Window and Segment Editing =====
-    soundfont or patchset in order that it can play General MIDI as configured
-    "out of the box"
+==== How do I set a loop? ====
-=====Main Window and Segment Editing=====
+While holding down Shift and the left mouse button, sweep out a loop region in the ruler at the top or bottom of the main composition window. The loop icon in the transport will become enabled and playback will always occur within this loop until you disable it. You can disable the loop by clicking on the loop icon or Shift+left clicking in either loop ruler.
-====How do I set a loop?====
+==== How do I rename a track? ====
-While holding down Shift and and the left mouse button sweep out a loop region in the ruler at the top or bottom of the main composition window. The loop icon in the transport will become enabled and playback will always occur within this loop until you disable it. You can disable the loop by clicking on the loop icon or shift+left clicking in either loop ruler.
-====How do I rename a track?====
 Double-click on the track label.
+==== How do I see the names of the tracks, instead of their instruments? ====
+On the main window go to Settings > View Track Labels.
-====How do I see the names of the tracks, instead of their instruments?====
+==== How do I change the instrument for a track? ====
-On the main window go to //Settings->View Track Labels//
-====How do I change the instrument for a track?====
 Either click with the right mouse button, or click and hold with the left mouse button, on the track/instrument label. A pop-up will appear from which you can choose a new instrument for the track.
+==== How do I listen to a piece at half speed? ====
-====How do I listen to a piece at half speed?====
 If the piece has more than one tempo change, then unfortunately it is not possible to listen at half or double speed.  This feature has been requested since 2002, but does not exist yet.  It is unlikely to be implemented.
 ====How do I rename a segment?====
-Click the "Edit" button next to the segment's name shown in the Segment Parameters box.
+Click the label field in the Segment Parameters box.
+==== How do I stop segments from snapping to the nearest beat when I move or resize them? ====
-====How do I stop segments from snapping to the nearest beat when I move or resize them?====
 Hold down the Shift key while you move or resize the segment. (Shift is also used to enable multiple selection, so sometimes you may have to press Shift only after you start dragging.)
+===== Notation and Matrix Editing =====
+==== Can I get more than one staff at once in the notation editor? ====
-=====Notation and Matrix Editing=====
+Select the segments either by click and drag or Shift+Click.  Then press the N key.
-====Can I get more than one staff at once in the notation editor?====
+==== How do I do something like a two-staff piano part? ====
-The //Open in Notation Editor// option on the main view's //Segments// menu will open all the currently-selected segments together in a single editor. So to open them all, first use the //Edit// menu's //Select All Segments// option, then this one. (You can also edit a subset of segments by selecting them with shift-click on the main view, then using //Open in Notation Editor//.)
-====How do I do something like a two-staff piano part?====
 There are various angles to this question, and there's not any one perfect answer.
-For the best treatise on the subject, please see [[http://rosegarden.sourceforge.net/tutorial/supplemental/piano|Piano Notation by Example]]
+For the best treatise on the subject, please see [[doc:piano_notation_from_midi|Piano Notation from MIDI]].
-====Can I edit all the segments at once in the matrix editor?====
-Yes! (Probably?  This is likely to be working when we release.)
-====Notation rendering is rather slow====
-It can be. Unlike many other notation applications (including the old X11 Rosegarden), we render the full length of each segment to a canvas when the notation editor starts, instead of rendering sections at a
-time when it scrolls. This means scrolling should be smooth and quick but the initial rendering phase relatively slow. This can be a problem for long segments, although for other practical reasons you're
+==== How do I edit all the segments at once in the matrix editor? ====
-probably better off dividing long pieces into more manageable segments anyway.
+Press Ctrl+A and then M.
+==== Notation rendering is rather slow ====
+It can be.  We render the full length of each segment to a canvas when the notation editor starts, instead of rendering sections at a time when it scrolls. This means scrolling should be smooth and quick but the initial rendering phase relatively slow. This can be a problem for long segments, although for other practical reasons you're probably better off dividing long pieces into more manageable segments anyway.
-=====Playback and recording=====
+===== Playback and recording =====
-====ALSA? JACK? Huh?====
+==== ALSA? JACK? Huh? ====
 Rosegarden likes to use the ALSA Linux sound drivers for MIDI communication, and the JACK low-latency audio server for audio. The build system should detect which of these you have available.
@@ Line 201: / Line 160: @@
 If you have (or build with) ALSA but not JACK, you will be able to send and receive MIDI to or from outboard MIDI hardware and other MIDI applications such as soft synths, but you will not be able to use synth plugins in Rosegarden, nor to record or play back audio segments or apply effects plugins.
+==== My soundcard has no built-in MIDI synth and I have no external MIDI devices. How can I get sound? ====
-====My soundcard has no built-in MIDI synth and I have no external MIDI devices. How can I get sound?====
 You need a soft synth! See the next question.
-**EDITING CUTOFF POINT!  EVERYTHING BELOW THIS LINE MAY BE OBSOLETE**
+==== How do I use an ALSA soft synth, such as fluidsynth or Timidity? ====
-====How do I use an ALSA soft synth, such as fluidsynth or Timidity?====
+//This section is obsolete.//
 Well first, here's how to get fluidsynth working with a soundfont. First get [[http://www.fluidsynth.org|fluidsynth]]. Then find a soundfont: one reasonable GM example is Musica Theoria 2, available as mustheory2.sf2 from the Collections area of [[http://www.hammersound.net/|Hammersound]], although it's large and it's packed using some stupid Windows-only format (common problem -- a few of the soundfonts on there are only zipped, though, so have a look around).
 Then run up fluidsynth with
-<code>
   $ fluidsynth -m alsa_seq ./mustheory2.sf2
-</code>
 or equivalent for whichever soundfont you want to use. Alternatively get hold of [[http://qsynth.sourceforge.net/|qsynth]] which provides a nice GUI for fluidsynth.
 If you're relatively short on CPU power, also give it "-R no" to turn off reverb and you'll get a bit more polyphony before it breaks up. (If you're //very// short on CPU power, forget it.) You may find you have to run it as root or else the pitch goes awry, particularly on laptops with variable-speed CPUs.
-Anyway, when fluidsynth is running you should be able to assign tracks to it in Rosegarden. To set a track to one of the soft-synth instruments, right-click on the track label at the left of the track
+Anyway, when fluidsynth is running you should be able to assign tracks to it in Rosegarden. To set a track to one of the soft-synth instruments, right-click on the track label at the left of the track until the instrument menu appears and select the instrument on there. (If you have no other MIDI devices at all, then the soft-synth should be the default device.)
-until the instrument menu appears and select the instrument on there. (If you have no other MIDI devices at all, then the soft-synth should be the default device.)
+You can also use Timidity as an ALSA soft-synth with soundfonts. Run it in ALSA input mode:
-You can also use Timidity as an ALSA soft-synth with soundfonts. Run it in ALSA input mode:
-<code>
   $ timidity -iA
-</code>
 You can also use Timidity to play to JACK with reasonably low latency, with some magic incantation like:
-<code>
   $ timidity -iA -Oj -B2,8
-</code>
 In my experience it takes rather more CPU power than fluidsynth for rather lower-quality output, though I'm sure these things vary a lot depending on how the soundfont is made.
+==== How do I select an Instrument? ====
+You can check which Instrument is selected for your Track by selecting the track and looking at the "Instrument Parameters" pane in the left column.  You can change the Instrument for a Track by right-clicking or clicking and holding on the Track/Instrument label.  A pop up menu will appear from which you can select a different Instrument.
-====How do I select an Instrument?====
+Rosegarden automatically assigns the first available synth device on your soundcard for its default output Instrument when importing MIDI files.
-You can check which Instrument is selected for your Track by making sure that //Settings->Show Track Labels// is unchecked. You can change Instrument for a Track by right-clicking or clicking and holding on the Track/Instrument label. A pop up menu will appear from which you can select a different output Instrument. Rosegarden automatically assigns the first available synth device on your soundcard for its default output Instrument when importing MIDI files.
+==== I've selected a synth Instrument but I don't hear any sound ====
+If you're hearing silence with a Synth device (say "Emuk10k1 Port 0" or "OPL 3") then make sure you've loaded a soundfont for your soundcard. To load soundfonts use the "sfxload" utility. For example the Creative SBLive! soundcard comes with a set of standard soundfonts (2gmgsmt.sf2, 4gmgsmt.sf2, 8mbgmsfx.sf2) and you can load the 8MB soundfont as follows:
+  $ sfxload 8mbgmsfx.sf2
-====I've selected a synth Instrument but I don't hear any sound====
-If you're hearing silence with a Synth device (say "Emuk10k1 Port 0" or "OPL 3") then make sure you've loaded a soundfont for your soundcard. To load soundfonts use the "sfxload" utility. For example the Creative SBLive! soundcard comes with a set of standard soundfonts (2gmgsmt.sf2, 4gmgsmt.sf2, 8mbgmsfx.sf2) and you can load the 8MB soundfont as follows:
-<code>
-  $ sfxload 8mbgmsfx.sf2
-</code>
 For more fun with soundfonts including how to create them for yourself have a look at the [[http://swami.sourceforge.net|Smurf/Swami project]].
 The other classic problem for new users of ALSA is that the mixer settings are either zero or muted. Run alsamixer and check that your levels are okay and unmuted. (Muting is displayed and changed separately from the levels themselves: you can be on 100% but still muted.)
+==== What does "System timer resolution is too low" mean? ====
-====What does "System timer resolution is too low" mean?====
 If you see this message in an error dialog when Rosegarden starts up, then you are probably using a Linux kernel that doesn't offer sufficiently high-resolution system timers for MIDI use.
@@ Line 263: / Line 214: @@
 Your options are:
-. Switch the sequencer to use a different timing source (//Settings -> Configure Rosegarden... -> MIDI -> Sequencer timing source//). The best one in theory is the RTC timer, which is only available if you have snd-rtctimer loaded, but unfortunately that has a habit of totally locking some systems running real-time kernels. Meanwhile, the PCM timers only work if the JACK audio server is running, and suffer jitter corresponding to the JACK buffer size.
+  - Switch the sequencer to use a different timing source (Edit > Preferences... > MIDI > General > Sequencer timing source).  //This probably won't help.//
+  - Recompile your kernel with system timer set to 1000 Hz. Sadly there's no way to change this without a recompile. It's the best solution though.
-. Recompile your kernel with system timer set to 1000 Hz. Sadly there's no way to change this without a recompile. It's the best solution though.
+  - Switch to a different Linux distribution that provides a kernel more appropriate for multimedia use.
+  - Put up with the poorer timing of a 250 Hz timer (if you want to get rid of the warning while continuing to use this timer, set the timer source to "system timer" rather than "(auto)").
-. Switch to a different Linux distribution that provides a kernel more appropriate for multimedia use.
-. Put up with the poorer timing of a 250 Hz timer (if you want to get rid of the warning while continuing to use this timer, set the timer source to "system timer" rather than "(auto)").
-Hopefully future versions of Rosegarden and/or the Linux kernel will provide better ways to solve this problem.
 If you don't want to recompile your kernel and are running (K)Ubuntu, you can choose a lowlatency kernel from the repository (search for it with synaptic or your favorite tool). Install the new kernel and reboot. This will solve the problem and remove the lag.
+==== Only notes at the very start of the composition are played at all ====
-====Only notes at the very start of the composition are played at all====
 If Rosegarden plays notes at time zero but then gets stuck and doesn't play anything else afterwards, you might have a non-running sequencer timer selected.
-Try going to Settings -> Configure Rosegarden... -> MIDI and changing the "Sequencer timing source" setting.
+Try going to Edit > Preferences... > MIDI > General and changing the "Sequencer timing source" setting.
+==== How do I get audio to work? ====
-====How do I get audio to work?====
 If you're using ALSA, then you need to obtain and install [[http://jackit.sourceforge.net/|JACK]] and run jackd before starting the Rosegarden sequencer. If you give jackd the -v option, it will report when Rosegarden succeeds in connecting to it.
 Unfortunately getting the right combination of magic incantations to make JACK work is not always easy. Good values for an SBLive and indeed on the built-in via868 on my Acer laptop as follows:
-<code>
   $ jackd -d alsa -d hw -r 44100 -p 2048 -n 2
-</code>
 This will usually ensure that I don't get any xruns (JACK being unable to process audio in time) and provide reasonable latency. The '-r 44100' option sets the sample rate for the JACK server which will in turn define the rate at which WAV audio files will be recorded. This is important if you want to transfer any of the WAVs directly to CD - 44100 Hz (44.1 kHz) is the sample rate that audio CDs work at.
+==== I'm not seeing the right program names for my MIDI device (or any at all) ====
+Rosegarden has an internal Studio to map your MIDI Program Change information into meaningful instrument labels. You need to set up this mapping in the MIDI device manager (Studio > Manage MIDI Devices > Banks...). Once you've made changes in your current Rosegarden file you can save it as a default studio (replacing your autoload.rg file) so that all your subsequent sessions in Rosegarden utilise your specialised Studio settings.
-====I'm not seeing the right program names for my MIDI device (or any at all)====
+See the [[dev:device_files|Rosegarden Device File (.rgd) Developer's Guide]] for more.
-Rosegarden has an internal Studio to map your MIDI Program Change information into meaningful instrument labels. You need to set this up do this mapping in the MIDI device manager (Studio->Manage MIDI Devices->Banks or Import). Once you've made changes in your current Rosegarden file you can save it as a default studio (replacing your autoload.rg file) so that all your subsequent sessions in Rosegarden utilise your specialised Studio settings.
+==== I've followed all your instructions but I still don't hear any sound ====
+Try this site:
+http://www.tedfelix.com/linux/linux-midi.html
-====I've followed all your instructions but I still don't hear any sound====
+===== Improving Performance =====
-If you've done everything we've suggested above then you can check what devices the sequencer is seeing by running the Rosegarden sequencer up by itself. Try:
+==== I get drop outs or xruns with JACK. How do I improve performance? ====
-<code>
-  $ rosegardensequencer
-</code>
-and examine the output of the screen. The output for JACK and ALSA for an SBLive! should look something like this:
-<code>
-  rosegardensequencer: created plugin manager
-  MappedAudioPluginManager::discoverPlugins - discovering plugins
-  Rosegarden 4-0.9 - AlsaDriver - alsa-lib version 0.9.3
-  AlsaDriver::jackSampleRate - sample rate changed to 44100
-  AlsaDriver::createJackInputPorts - adding input port 1
-  AlsaDriver::createJackInputPorts - adding input port 2
-  AlsaDriver::createJackInputPorts - getting ports
-  AlsaDriver::createJackInputPorts - found 2 JACK physical inputs
-  AlsaDriver::createJackInputPorts - connecting from "alsa_pcm:capture_1" to "rosegarden:in_1"
-  AlsaDriver::createJackInputPorts - connecting from "alsa_pcm:capture_2" to "rosegarden:in_2"
-  AlsaDriver::initialiseAudio - JACK sample rate = 44100Hz
-  AlsaDriver::initialiseAudio - added output port 1 (left)
-  AlsaDriver::initialiseAudio - added output port 2 (right)
-  AlsaDriver::initialiseAudio - found 2 JACK physical outputs
-  AlsaDriver::initialiseAudio - connecting from "rosegarden:out_1" to "alsa_pcm:playback_1"
-  AlsaDriver::initialiseAudio - connecting from "rosegarden:out_1" to "alsa_pcm:playback_2"
-  AlsaDriver::initialiseAudio - JACK playback latency  0.092879R
-  AlsaDriver::initialiseAudio - JACK record latency  0.046439R
-  AlsaDriver::initialiseAudio - initialised JACK audio subsystem
-  ALSA Client information:
+The short answer to this is with care and with some luck. There are various recipes for improving JACK performance. Some are more labour intensive than others. Ask on the rosegarden-user and rosegarden-devel lists for the latest advice and also keep an eye on jackit-devel for more JACK tips.
-,0 - (Rawmidi 0 - EMU10K1 MPU-401 (UART), EMU10K1 MPU-401 (UART))                 (DUPLEX) [ctype 2, ptype 2, cap 127]
+to add somewhere appropriate:  DSSI: no localhost
-,0 - (Emu10k1 WaveTable, Emu10k1 Port 0)          (WRITE ONLY) [ctype 2, ptype 2078, cap 66]
-,1 - (Emu10k1 WaveTable, Emu10k1 Port 1)          (WRITE ONLY) [ctype 2, ptype 2078, cap 66]
-,2 - (Emu10k1 WaveTable, Emu10k1 Port 2)          (WRITE ONLY) [ctype 2, ptype 2078, cap 66]
-,3 - (Emu10k1 WaveTable, Emu10k1 Port 3)          (WRITE ONLY) [ctype 2, ptype 2078, cap 66]
-  Creating device 0 in Play mode for connection 65:0 Emu10k1 Port 0 (write)
+===== Customizing Rosegarden =====
-  Default device name for this device is MIDI soundcard synth
-  Creating device 1 in Play mode for connection 65:1 Emu10k1 Port 1 (write)
-  Default device name for this device is MIDI soundcard synth 2
-  Creating device 2 in Play mode for connection 65:2 Emu10k1 Port 2 (write)
-  Default device name for this device is MIDI soundcard synth 3
-  Creating device 3 in Play mode for connection 65:3 Emu10k1 Port 3 (write)
-  Default device name for this device is MIDI soundcard synth 4
-  Creating device 4 in Play mode for connection 64:0 Rawmidi 0 - EMU10K1 MPU-401 (UART) (duplex)
-  Default device name for this device is MIDI external device
-  Creating device 5 in Record mode for connection 64:0 Rawmidi 0 - EMU10K1 MPU-401 (UART) (duplex)
-  Default device name for this device is MIDI hardware input device
-  Record client set to (64, 0)
-  AlsaDriver::initialiseMidi -  initialised MIDI subsystem
+==== How do I modify keyboard shortcuts? ====
-  rosegardensequencer: RosegardenSequencer - started OK
+Go to Edit > Keyboard Shortcuts....
-</code>
-Note the ALSA device list shows the external MIDI port and the wavetable on-board synth devices. If you're using a soft synth, you should see it here too. All of these will be available in the drop-down Instrument list inside Rosegarden.
-You can also reach this sequencer status information by using the application itself. Go to: Settings -> Configure Rosegarden -> Sequencer status -> Details....
+==== How do I prevent Rosegarden splitting long notes when recording? ====
+There is a setting for that:
+Edit > Preferences > Notation -> When recording MIDI, split-and-tie long notes at barlines
-=====Improving Performance=====
-====I get drop outs or xruns with JACK. How do I improve performance?====
-The short answer to this is with care and with some luck. There are various recipes for improving JACK performance. Some are more labour intensive than others. Ask on the rosegarden-user and rosegarden-devel lists for the latest advice and also keep an eye on jackit-devel for more JACK tips.
-to add somewhere appropriate:  DSSI: no localhost