rosegarden-bugs Mailing List for Rosegarden

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Ubuntu; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/dev:release_process?rev=1780455122
New Revision        : https://www.rosegardenmusic.com/wiki/dev:release_process
Date of New Revision: 2026/06/03 12:23
Edit Summary        : [Deliver] 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -217,16 +217,18 @@
  
    * https://github.com/tedfelix/rosegarden-official/releases
    * Click on "Draft a new release".
    * Current version section of the CHANGELOG will need to be copied to the description field and reformatted to markdown.
+   * Add the tarball.
  
  CodeBerg
  
    * https://codeberg.org/rosegarden/rosegarden/releases
    * Click on the New Release button.
    * Specify an existing tag name.
    * Release title: Rosegarden xx.xx
    * Copy markdown description from github.
+   * Add the tarball.
  
  ==== Update Website ====
  
  Update the website to point to the new version.  The website can be updated by committing changes to the website directory in svn.  These are automatically uploaded to the web server.  The webpages use Server Side Includes (SSI), so you'll need to set up a web server to test before uploading changes.


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Ubuntu; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/dev:release_process?rev=1771443538
New Revision        : https://www.rosegardenmusic.com/wiki/dev:release_process
Date of New Revision: 2026/06/03 02:52
Edit Summary        : [Release Eve] 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -84,8 +84,10 @@
    <translation type="unfinished">
  
  //Might be nice to upgrade ts-untrans to mark all blank as unfinished.  Then we can just review that and fix the ones that should be blank.//
  ===== Release Eve =====
+ 
+ ==== email Reminder ===
  
  On the eve of the release, send out a reminder for any last minute contributions and translations.
  
  ==== Pending Changes ====


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Ubuntu; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/dev:26.06?rev=1780430177
New Revision        : https://www.rosegardenmusic.com/wiki/dev:26.06
Date of New Revision: 2026/06/02 19:56
Edit Summary        : [ROSEGARDEN 26.06 RELEASED] 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -1,11 +1,9 @@
  ====== ROSEGARDEN 26.06 RELEASED ======
  
- The Rosegarden team is proud to announce the release of version 26.06
- of Rosegarden, a MIDI sequencer that features a rich understanding of
- music notation along with basic support for digital audio.
+ The Rosegarden team is proud to announce the release of version 26.06 of Rosegarden, a MIDI sequencer that features a rich understanding of music notation along with basic support for digital audio.
  
-   http://www.rosegardenmusic.com/
+ http://www.rosegardenmusic.com/
  
  Included in this release...
  
  ===== Bug Fixes =====


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Ubuntu; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/dev:26.06?rev=1778078986
New Revision        : https://www.rosegardenmusic.com/wiki/dev:26.06
Date of New Revision: 2026/06/02 19:56
Edit Summary        : 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -1,9 +1,11 @@
  ====== ROSEGARDEN 26.06 RELEASED ======
  
- The Rosegarden team is proud to announce the release of version 26.06 of Rosegarden, a MIDI sequencer that features a rich understanding of music notation along with basic support for digital audio.
+ The Rosegarden team is proud to announce the release of version 26.06
+ of Rosegarden, a MIDI sequencer that features a rich understanding of
+ music notation along with basic support for digital audio.
  
- http://www.rosegardenmusic.com/
+   http://www.rosegardenmusic.com/
  
  Included in this release...
  
  ===== Bug Fixes =====
@@ -48,8 +50,9 @@
    * Event List Editor: Fix edit not leaving event selected.  [c6ec410702]
    * Matrix: Fix matrix velocity can end up 0.  Bug #1777.  [af83558f8e]
    * Matrix: Fix unreadable grid dropdown in Native theme.  Bug #1778.  [6f886727a6]
    * Matrix: Fix unreadable quantize dropdown in Native theme.  Bug #1778.  [29193b7a03]
+   * Notation: Fix crash with Make Triplet (Ctrl+R).  Bug #1781.  [6bf63b0f3d]
  
  ===== New Features =====
  
    * rgd: Added support for alternative bank select approaches for synths like the Yamaha TG77 and Oberheim Matrix-1000.  Feature Request #542.  [b9c94293c5] [5b03a6285c]


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : ---
New Revision        : https://www.rosegardenmusic.com/wiki/dev:26.06
Date of New Revision: 2026/05/06 14:49
Edit Summary        : created
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

====== ROSEGARDEN 26.06 RELEASED ======

The Rosegarden team is proud to announce the release of version 26.06 of Rosegarden, a MIDI sequencer that features a rich understanding of music notation along with basic support for digital audio.

http://www.rosegardenmusic.com/

Included in this release...

===== Bug Fixes =====

  * LV2: Fix memory leaks.  Bug #1748.  [8139069f92]
  * cmake: Set LV2 minimum version to 1.18.0.  [e78887fc13]
  * LV2: Improved handling of GTK2 plugins.  Feature Request #541.  [6c6b5e39ba]
  * Fix duplicate menu items in "Set Entry Velocities" window.  Bug #1752.  [95e52f0e64]
  * Fix empty profile dump with no profiling.  Bug #1755.  [90d2c00a16]
  * Add missing #include <QObject>.  Bug #1746  [b714afbaa4]
  * cmake: Make lv2 optional.  Patch #84.  [c519c57ab2]
  * cmake: Rename DISABLE_LILV -> DISABLE_LV2.  [2d2824cc84]
  * cmake: Add DISABLE_PCH.  [04e36f6ea4]
  * cmake: Fix broken CMAKE_BUILD_TYPE.  [c149ea9a66]
  * Matrix: Fixed crash on large horizontal zoom.  Bug #1761.  [853313edcf]
  * Matrix: Fixed horizonatal zoom range issue.  Bug #1761.  [4a34375a33]
  * Matrix: Fix vertical zoom range issue.  [807cd89374]
  * Matrix: Improve HV wheel behavior.  [0ef1e21deb] [566f984873]
  * Matrix: Fix preview play for tied notes.  Bug #1764.  [e9ed4f1221]
  * AudioPluginDialog: Improve Editor button behavior.  Editor button is now disabled if JACK isn't up.  An error message is provided via the button's tooltip when it is disabled.  [fbaa3ec6b1]
  * MIDI Mixer: Handle changes to the number of devices without closing the window.  [520641f59c]
  * MIDI Mixer: Fix garbage in meters.  [254e75a45f]
  * MIDI Mixer: Handle changes to the number of controllers.  [faeb4238be]
  * Audio File Manager: Fix unload not working on selected WAV files.  Bug #1766.  [8626e2ec58]
  * main window: Fix toolbar tool buttons not responding to tool changes via the context menu.  [6d33d9d5ed]
  * main window: Fix context menu tool items enabled at the wrong time.  [212f1ba128]
  * main window: Disable VU meters on muted and archived tracks.  Bug #1767.  [1ff36b47e4] [5ed9c5248c]
  * main window: Make rotary tooltip dynamic.  Bug #1768.  [d39555d401]
  * metronome: Use bar velocity for preview.  [3f773b79b0]
  * MusicXML: Fix crash when importing MusicXML.  PR #32.  [92f9b3b426]
  * Notation: Fix erasing triplet note.  Bug #1772.  [5a0d019c45]
  * Tranzport: Disabled support for Frontier Design Group's TranzPort DAW Control.  See README for instructions on re-enabling and let us know if you are using this.  [44dab8314b]
  * Notation: Fix select and delete notes in tuplets.  Bug #1772.  [ff57686630] [81541588f7]
  * Notation: Fix inserting tuplet note at beginning.  Bug #1772.  [de410d7937]
  * main window: Fix scroll to follow playback.  When it is off, the display will not scroll.  Turn it on and the display will jump to where the cursor is.  Bug #1774.  [254f9824ce]
  * examples: Make all channels fixed.  PR #45.  [6b2824a52d]
  * Notation: Fix beaming a selection that contains a tuplet losing the tuplet.  Bug #1773.  [80af019789]
  * Notation: Improve rendering of mixed beam/tuple group.  Bug #1773.  [905859fc05]
  * Event List Editor: Fix initial selection in event editor.  Bug #1777.  [af81698a7c]
  * Editors: Remove "Durations" from rescale menu items.  Bug #1771.  [91a1a718f5]
  * Event List Editor: Select new event after insert.  [5131ab73df]
  * Event List Editor: Fix edit not leaving event selected.  [c6ec410702]
  * Matrix: Fix matrix velocity can end up 0.  Bug #1777.  [af83558f8e]
  * Matrix: Fix unreadable grid dropdown in Native theme.  Bug #1778.  [6f886727a6]
  * Matrix: Fix unreadable quantize dropdown in Native theme.  Bug #1778.  [29193b7a03]

===== New Features =====

  * rgd: Added support for alternative bank select approaches for synths like the Yamaha TG77 and Oberheim Matrix-1000.  Feature Request #542.  [b9c94293c5] [5b03a6285c]
  * matrix: Remember velocity for each segment.  [7e3ecfa101]
  * main window toolbar: Added metronome button to the transport toolbar.  [2fcbb1426f]
  * main window: Make "End" key jump to the end of the segments on first press, and to the end of the composition on the second press.  [42ba3c6341]
  * Rulers: Add "Set to Default" to context menu.  Also accessible via middle mouse button in select and move tools.  [5a2efddfb3]
  * lilypond: Add warning about too-short durations that will lead to lilypond errors.  PR #44.  [a11a8343f8]
  * Event List Editor: Add Edit > Paste At...  [b3682ef93c]


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/start?rev=1777907958
New Revision        : https://www.rosegardenmusic.com/wiki/start
Date of New Revision: 2026/05/06 14:47
Edit Summary        : [Release Notes] 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -12,8 +12,9 @@
  //Note that developer pages are in the "dev:" namespace, formal project documentation is in the "doc:" namespace, and pages for translators are in the "translator:" namespace.  General user pages do not have any particular namespace; call them whatever you like.//
  
  ===== Release Notes =====
  
+   * Release notes for [[dev:26.06]]
    * Release notes for [[dev:25.12]]
    * Release notes for [[dev:25.06]]
    * Release notes for [[dev:24.12.1]]
    * Release notes for [[dev:24.12]]


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/doc:companion-en?rev=1772485649
New Revision        : https://www.rosegardenmusic.com/wiki/doc:companion-en
Date of New Revision: 2026/05/04 15:10
Edit Summary        : 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -31,9 +31,9 @@
  All of this flexibility means you can use Rosegarden as the center of a very powerful home studio and music composition solution for Linux.
  
  === About This Book ===
  
- This book will take you, the reader, on a tour of Rosegarden.  It will introduce you to its features, and then show you a variety of ways to use of these features in real-world situations.
+ This book will take you, the reader, on a tour of Rosegarden.  It will introduce you to its features, and then show you a variety of ways to use these features in real-world situations.
  
  The Linux novice will have questions that this book does not answer.  I leave you to turn to the support community for your particular flavor of Linux for help with matters of installation, hardware configuration, and so forth.  I assume that you have general knowledge of how to maintain your Linux box on a day to day basis, and that you have already installed Rosegarden-4 1.0 or later.  (If you installed a "rosegarden" package, and the application you see does not resemble the one covered in this book in the slightest, then you have found Rosegarden's ancient ancestor.)
  
  Each chapter is loosely divided into two parts. The first half details the mechanical side of making use of various controls in order to manipulate data in some way. The latter half focuses on demonstrating how to use these controls to achieve common musical goals.  There are special NOTE: and TIP: sections set off throughout the text to draw special attention to tips, tricks, caveats, and, in some cases, workarounds.
@@ -74,11 +74,11 @@
    * a JACK-compatible soundcard
  
  ===== Producing Sound =====
  
- Many users have written to ask why they are unable to get Rosegarden to make any noise. It is the most common question asked on the rosegarden-user mailing list by far, and is especially troublesome for those newly migrating to Linux from Windows® . Before we start Rosegarden for the first time, I want to explain what is necessary to pave the way, and have a good first experience. Some of you already know all this, and those of you who do are invited to jump ahead to the next chapter, where the interesting part begins.
+ Many users have written to ask why they are unable to get Rosegarden to make any noise. It is the most common question asked on the rosegarden-user mailing list by far, and is especially troublesome for those newly migrating to Linux from Windows®. Before we start Rosegarden for the first time, I want to explain what is necessary to pave the way, and have a good first experience. Some of you already know all this, and those of you who do are invited to jump ahead to the next chapter, where the interesting part begins.
  
- The topic of sound covers two distinct areas that may or may not be codependent, depending on the hardware and software you have available. One the one hand, there are several requirements that must be met in order to play MIDI with Rosegarden, and on the other, it's necessary to get the JACK server up and running reliably in order to make use of Rosegarden's audio features. A working JACK server is also required to play MIDI with synth plugins, or to play more than one ALSA software synth at a time. Getting Rosegarden to make noise can be a complicated business, but hopefully I can help you deal with whatever set of circumstances you have before you. I cannot, however, cover every detail of getting every card working with every distribution. I'm afraid I have to leave some questions unanswered, lest this chapter become a book unto itself. 
+ The topic of sound covers two distinct areas that may or may not be codependent, depending on the hardware and software you have available. On the one hand, there are several requirements that must be met in order to play MIDI with Rosegarden, and on the other, it's necessary to get the JACK server up and running reliably in order to make use of Rosegarden's audio features. A working JACK server is also required to play MIDI with synth plugins, or to play more than one ALSA software synth at a time. Getting Rosegarden to make noise can be a complicated business, but hopefully I can help you deal with whatever set of circumstances you have before you. I cannot, however, cover every detail of getting every card working with every distribution. I'm afraid I have to leave some questions unanswered, lest this chapter become a book unto itself. 
  
  Here is a roadmap showing all the possible ways to produce sound with Rosegarden at a glance. It's quite daunting, I know, but I hope I can help you make sense of it:
  
  ==== Playing MIDI ====
@@ -100,9 +100,9 @@
  If you're fortunate enough to have such equipment, then you probably already have some idea how to hook it up to your computer. If the equipment has the ability to produce sound on its own, as some MIDI keyboards do, then you may wish to use those speakers for MIDI playback. If your MIDI equipment has no speakers, or if you intend to record the audio output from this equipment, you may wish to connect the audio output from your keyboard or sound module to an audio input jack on your soundcard. This will allow you to route everything through the soundcard's mixer. There are several choices for external MIDI interfaces.
  
  === Joystick Port MIDI Adapters ===
  
- The simplest, least expensive route is the joystick port MIDI adapter. These plug into the joystick port  found on many common AC97 soundcards, and on some on-board audio solutions.  The most typical adapter you will find in music stores is a simple Y cable, but nicer products are available which have LEDs to show MIDI activity.  With the right adapter in hand, all that remains is to plug the adapter into your joystick/MIDI port, connect your equipment to the box or cable using standard 5-pin DIN MIDI cables. With most AC97 soundcards, including the Sound Blaster Live!, it's only a matter of making sure the snd-seq-midi and snd-rawmidi modules are loaded (using whatever mechanism your particular distribution provides for that function.)
+ The simplest, least expensive route is the joystick port MIDI adapter. These plug into the joystick port found on many common AC97 soundcards, and on some on-board audio solutions.  The most typical adapter you will find in music stores is a simple Y cable, but nicer products are available which have LEDs to show MIDI activity.  With the right adapter in hand, all that remains is to plug the adapter into your joystick/MIDI port, connect your equipment to the box or cable using standard 5-pin DIN MIDI cables. With most AC97 soundcards, including the Sound Blaster Live!, it's only a matter of making sure the snd-seq-midi and snd-rawmidi modules are loaded (using whatever mechanism your particular distribution provides for that function.)
  
  USB MIDI
  
  USB is supplanting traditional MIDI cabling, and several manufacturers are producing keyboards that plug directly into your computer using standard USB cables. There are also devices available which provide multi-port MIDI interfaces . These interfaces attach to your computer using a USB cable, and they provide several traditional 5-pin MIDI sockets.
@@ -120,9 +120,9 @@
  Pedro and Chris both report that the mAudio MidiSport interfaces are more difficult to get working. Pedro reports that "some of them require a firmware program to be loaded into the device's RAM before you can use it. There are GPL firmwares (package ezusbmidi) for the 1-port and 2-port devices (up to Midisport2x2), they are provided as RPM packages for Red Hat by CCRMA, and for Mandrake by Thac. There are also ready to use packages from AGNULA/Debian and Gentoo. Or you can tweak and compile the firmware from its sources." Chris reports that users with 2.6-series kernels may have difficulty using these devices. Pedro suggests that you have a look at the "zero config environment" information available from CCRMA if you are running Red Hat or Fedora.
  
  MIDI without External Hardware
  
- For those without external hardware to use, there are two remaining categories. A few soundcards have built-in MIDI playback capability that ALSA can use. Everyone else will have to use some kind of software synth.  Unfortunately, if you are coming from a Windows®  background, there is a very good probability that your soundcard used to play MIDI perfectly well under Windows®, but it has no ability to do so under Linux out of the box.  The difference is that most such soundcards (in fact, the vast majority of common soundcards on the market) have a software synthesizer built into their Windows® driver, so that the user is never really aware that the MIDI playback capability is coming from software.  In Linux, you have the choice to run any of several software synthesizers to provide this same capability, but you will have to take steps on your own behalf to bring this about, because it is not automatic or transparent.
+ For those without external hardware to use, there are two remaining categories. A few soundcards have built-in MIDI playback capability that ALSA can use. Everyone else will have to use some kind of software synth.  Unfortunately, if you are coming from a Windows® background, there is a very good probability that your soundcard used to play MIDI perfectly well under Windows®, but it has no ability to do so under Linux out of the box.  The difference is that most such soundcards (in fact, the vast majority of common soundcards on the market) have a software synthesizer built into their Windows® driver, so that the user is never really aware that the MIDI playback capability is coming from software.  In Linux, you have the choice to run any of several software synthesizers to provide this same capability, but you will have to take steps on your own behalf to bring this about, because it is not automatic or transparent.
  
  === Cards That Do Have Synth Support under ALSA ===
  
  None are still relevant in 2010.
@@ -142,9 +142,9 @@
  If these "-midi" modules are not loaded, then you can often get the MIDI subsystem up by simply issuing a modprobe snd-seq-midi command, which pulls in all or most of the other modules it needs.  Check back with KInfoCenter, or a similar utility, to see if you have something listed for "Midi devices" now, or issue a pmidi -l command, and look for something with "64:0" in the name.  If this modprobe command has the desired effect, check into your distro's particular mechanisms for configuring your system to load these extra modules at boot time, which often involves editing files in the /etc directory.
  
  QSynth
  
- The least complicated way to get one of these cards to play MIDI is to use QSynth. It is a simple to use ALSA soft synth that takes MIDI data as input and uses .sf2 format soundfonts to produce audio output. In its simplest configuration, it can use ALSA for audio output, avoiding the need to run JACK. If you already need or want to run JACK, it can connect its output to JACK instead. In this configuration, you can also use a variety of other ALSA soft synths such as Hydrogen and Aeolus, all sharing the same audio output. QSynth is the most useful for general music production, and so it is my focus here, but the others are well worth your time to check out.  (In particular, I wish I had had time to cover Aeolus.  It is a pipe organ simulator that does a simply spectacular job.)
+ The least complicated way to get one of these cards to play MIDI is to use QSynth. It is a simple-to-use ALSA soft synth that takes MIDI data as input and uses .sf2 format soundfonts to produce audio output. In its simplest configuration, it can use ALSA for audio output, avoiding the need to run JACK. If you already need or want to run JACK, it can connect its output to JACK instead. In this configuration, you can also use a variety of other ALSA soft synths such as Hydrogen and Aeolus, all sharing the same audio output. QSynth is the most useful for general music production, and so it is my focus here, but the others are well worth your time to check out.  (In particular, I wish I had had time to cover Aeolus.  It is a pipe organ simulator that does a simply spectacular job.)
  
  ==== Configure the Audio Driver ====
  
  The first decision you need to make is whether to use ALSA or JACK for output. I will cover starting and configuring of the JACK audio server in detail in a moment.  If you have a slow computer, you may not be able to run QSynth through JACK, and you will have to run without JACK, and run Rosegarden without its audio or synth plugin capabilities enabled.  No matter which option you choose, both are configured via the Setup button. In this example, I'm using JACK. Take special note that I have adjusted the sample rate to match the sample rate I'm using with JACK, which is 48,000 Hz (for reasons I will explain directly.) Also note that I have checked [x] Auto Connect JACK Outputs. This allows QSynth to make its own default connection with JACK, which is very convenient.
@@ -162,15 +162,15 @@
  In order to play audio you will need to run JACK. 
  
  === What is JACK? ===
  
- JACK is short for the “Jack Audio Connection Kit.” JACK is a flexible audio server that allows its client applications to share the audio hardware seamlessly, and to share a common transport. It provides flexible mechanisms for routing inputs and outputs to and from client applications using a jack-and-cable metaphor. It is geared toward the audio professional who wants to get the lowest possible latency and the best possible performance out of his or her hardware.  Whether your own goals are professional or not, you still need JACK to get audio out of  Rosegarden (although you can still do MIDI work without it under most circumstances.)
+ JACK is short for the “Jack Audio Connection Kit.” JACK is a flexible audio server that allows its client applications to share the audio hardware seamlessly, and to share a common transport. It provides flexible mechanisms for routing inputs and outputs to and from client applications using a jack-and-cable metaphor. It is geared toward the audio professional who wants to get the lowest possible latency and the best possible performance out of his or her hardware.  Whether your own goals are professional or not, you still need JACK to get audio out of Rosegarden (although you can still do MIDI work without it under most circumstances.)
  
  === Look After Your Kernel ===
  
  It is theoretically possible to run JACK and Rosegarden with an ordinary stock kernel as installed by any distro, but I have never obtained acceptable results, even on machine with quite high specs.  It is simply impossible to throw enough CPU after the problem, and you will not obtain acceptable results until you look after your kernel.  I strongly recommend that you leave aside the kernel question entirely, and run something like Fervent's Studio..to go! (http://www.ferventsoftware.com), AGNULA's DeMuDi (http://www.agnula.org), or Planet CCRMA (http://ccrma.stanford.edu/planetccrma/software/).  You can also obtain suitable kernels from either AGNULA or the Planet to retrofit existing installations.
  
- I think that perhaps in another year or so, this question will be easy for anyone to solve using any off the shelf distro, merely by changing a few configuration options along the way.  In the meantime, running, or borrowing packages from a specialized music distro is a great way to save yourself having to deal with the headaches that still exist as of this writing.  For my own part, I use the 2.4.25-multimedia kernel from AGNULA, because it was installable as a retrofit package for my existing Debian system.  However, Studio..to go! ships with a suitably tweaked up 2.6 kernel that works quite well.  The difference between these two is a toss-up as of today, but I expect that the newer 2.6 kernels will quickly become the better choice.
+ I think that perhaps in another year or so, this question will be easy for anyone to solve using any off-the-shelf distro, merely by changing a few configuration options along the way.  In the meantime, running, or borrowing packages from a specialized music distro is a great way to save yourself having to deal with the headaches that still exist as of this writing.  For my own part, I use the 2.4.25-multimedia kernel from AGNULA, because it was installable as a retrofit package for my existing Debian system.  However, Studio..to go! ships with a suitably tweaked up 2.6 kernel that works quite well.  The difference between these two is a toss-up as of today, but I expect that the newer 2.6 kernels will quickly become the better choice.
  
  Starting and Tweaking JACK
  
  The simplest way to control your JACK server is to use QJackCtl. It is a very useful utility that provides a convenient way to start and stop your JACK server, to play with various configuration parameters to find the best combination for your hardware, and to manage JACK connections between applications.
@@ -204,21 +204,21 @@
  Let's begin by starting Rosegarden, and having a look at the main window. This is where you get an overall view of your work, and control a number of settings and parameters.
  
  ==== The Main Window ====
  
- A Rosegarden document is called a composition. The main window is primarily dedicated to editing at the composition level, so most of these tools affect your document in a broad way. This is where you name tracks and assign instruments to them, create and manipulate segments, and watch a broad overview of playback. (I will explain these concepts in more detail later on.) This is also where you configure segment parameters such as label and color. Tempo and time signature settings exist a composition level, and they may be edited here in the main window using the tempo ruler.
+ A Rosegarden document is called a composition. The main window is primarily dedicated to editing at the composition level, so most of these tools affect your document in a broad way. This is where you name tracks and assign instruments to them, create and manipulate segments, and watch a broad overview of playback. (I will explain these concepts in more detail later on.) This is also where you configure segment parameters such as label and color. Tempo and time signature settings exist at the composition level, and they may be edited here in the main window using the tempo ruler.
  
  ==== Special Toolbars ====
  
  One of the first things you might notice about Rosegarden is that there are several toolbars at the top of the main window. In addition to the usual standard controls shared by most KDE applications, there are several toolbars specific to Rosegarden. You'll choose various tools for selecting and manipulating segments from the Tools Toolbar (Select, Move, Resize, New, Erase, Split), a subset of transport tools available in the Transport Toolbar (toggled off by default), tracks can be added, deleted or moved with the Tracks Toolbar, and once a segment has been created, you can use the Editors Toolbar to open it in one of the three available editors. You'll also find icons to start the Quantizer, the Studio configuration dialog, the Synth Plugin manager, the audio file manager, and the MIDI and audio mixers.
  
  At the end of it all is the Zoom Slider, which is used to change the magnification of the Segment Canvas:
-  
+ 
  ==== The Tracklist ====
  
  Rosegarden is a track-based sequencer. Each entry in the tracklist is a separate track that can have individualized settings for several different parameters. Each track has a label and an output assignment, and can be used to record, play, and manipulate either MIDI or audio data, but never both.
  
- Instrument vs. Name
+ === Instrument vs. Name ===
  
  The tracklist can be configured to display either the name you've assigned to the track, or the name of the instrument to which it is connected. Toggle this behavior with Settings -> Show Track Labels. I will explain more about this later on, in Managing Instrument Parameters.
  
  Here we see how instrument assignments are displayed on the tracklist. In this example, the tracks are configured to play using instruments #1 and #2, respectively, on the "Roland SC-33" device.
@@ -234,15 +234,15 @@
  === Changing the Track Name ===
  
  To change the track name, double click on the label. A dialog should appear, allowing you to enter a new name.
  
- Adding, Removing, Moving Tracks
+ === Adding, Removing, Moving Tracks ===
  
  The tools on the Tracks Toolbar  can be used to move tracks up and down, to delete them, or to create new tracks. It is not possible to copy an entire track.
  
  ==== Segments and Segment Parameters ====
  
- Rosegarden compositions are made up of segments, and editing at the composition level involves dragging them around and rearranging them within tracks. Segments are a universal container that may hold either MIDI events or audio data. Segments are rather similar to layers in an image editing program such as the GIMP.  MIDI segments can be cut, pasted, split, recombined, overlapped, flattened, and pretty much rearranged at will, and are very flexible.  Audio segments behave in many of the same ways, but they are more limited in the ways they can be modified.
+ Rosegarden compositions are made up of segments, and editing at the composition level involves dragging segments around and rearranging them within tracks. Segments are a universal container that may hold either MIDI events or audio data. Segments are rather similar to layers in an image editing program such as the GIMP.  MIDI segments can be cut, pasted, split, recombined, overlapped, flattened, and pretty much rearranged at will, and are very flexible.  Audio segments behave in many of the same ways, but they are more limited in the ways they can be modified.
  
  === Creating a New Segment ===
  
  You can begin recording (audio or MIDI) to create a segment, but I'll get into that a bit later. For now, why not draw one from scratch?
@@ -256,17 +256,17 @@
  Use the  cursor to select a segment:
   
  Drag it to a new track:
  
- Hold down Ctrl while dragging it back,and make a copy:
+ Hold down Ctrl while dragging it back, and make a copy:
  
  === Splitting and Joining ===
  
  Use the  cursor to split one of the segments, then switch to the  and drag one of the pieces so that it overlaps the segment on the other track. By default, this will snap to whole beat positions within the bar, but you can override that behavior by holding down the Shift key while dragging.
  
  Highlighting the smaller of two overlapping segments can sometimes be a bit tricky, but once accomplished, you can use Segments -> Join to combine several segments into one, rather like flattening the layers in an image editing program.
  
- This can also merge MIDI events from several different tracks into a single segment. The events will combine, and merge onto a segment on whichever track is currently active.
+ This can also merge MIDI events from several different tracks into a single segment. The events will combine and merge onto a segment on whichever track is currently active.
  
  Audio segments can be split, but they cannot be resized, joined or merged. If you split an audio segment, you can undo that operation to revert it to its original state, but you cannot, for example, cut out the middle and splice the ends back together. Neither can you merge two overlapping audio segments into one, nor merge audio and MIDI segments together.  Audio segments are always associated with a file on disk, usually in the audio path for this particular composition, and changing the length of the segment does not affect the underlying file in any way.
  
  === Split by Pitch ===
@@ -358,9 +358,9 @@
  You can display the time signature as cut or common time, and make the time signature hidden. You should probably always leave "Correct the durations of the following measures" checked unless you have a good reason to do otherwise. 
  
  ==== Document Markers ====
  
- Markers are special events that can be used to mark of particular passages in the music at a composition level. They appear on the ruler, and can be edited from Composition -> Edit Markers... Issuing this command summons the marker editor dialog. In this example, I've already created a sample pair. The "Marker Name" portion is what appears on the ruler, and the "Marker description" is for the informational purposes of the composer only.
+ Markers are special events that can be used to mark particular passages in the music at a composition level. They appear on the ruler and can be edited from Composition -> Edit Markers.... Issuing this command summons the marker editor dialog. In this example, I've already created a sample pair. The "Marker Name" portion is what appears on the ruler, and the "Marker description" is for the informational purposes of the composer only.
  
  The Manage Markers Dialog
  
  === Creating a New Marker ===
@@ -388,9 +388,9 @@
  The autosave interval defaults to 60 seconds. Configure it via the Settings menu. If you notice Rosegarden grabbing a lot of your CPU time for no apparent reason, it is probably autosave, and you might want to increase the interval, or turn this feature completely off. It can become quite cumbersome when working on very large compositions.
  
  ===== The Studio =====
  
- Now that you have a general idea how Rosegarden works, now is a good time to think about telling Rosegarden something about the MIDI equipment you wish to use. People who intend to use Rosegarden purely for audio work are free to skip this chapter entirely.
+ Now that you have a general idea how Rosegarden works, now is a good time to think about telling Rosegarden something about the MIDI equipment you wish to use. <del>People who intend to use Rosegarden purely for audio work are free to skip this chapter entirely.</del>
  
  Before we get started, some of you might need some basic background information so that you can dive into this with some understanding of the concepts I am about to explain. If you are new to MIDI, or if anything in this chapter leaves you scratching your head, you might want to read through my MIDI Primer in Appendix B.
  
  ==== What is a Studio? ====
@@ -446,13 +446,13 @@
  In this example, I have both a hardware record device and a software record device. These devices were created spontaneously when Rosegarden detected the associated duplex read and virtual read connections. I have marked both of them "Current" and I can record events from either one of them, or both of them at the same time.
  
  === Play Devices ===
  
- Play devices are where all the fun, and all the complexity is. As I have mentioned elsewhere, they can be MIDI keyboards, sound modules, software synths, samplers, and pretty well anything else that can take MIDI input, such as KAMix. (Synth plugins are somewhat different. There is a single synth plugin device into which any and all plugins are plugged, and it is not a MIDI play device. I will cover synth plugins in the next chapter.)
+ Play devices are where all the fun, and all the complexity, is. As I have mentioned elsewhere, they can be MIDI keyboards, sound modules, software synths, samplers, and pretty well anything else that can take MIDI input, such as KAMix. (Synth plugins are somewhat different. There is a single synth plugin device into which any and all plugins are plugged, and it is not a MIDI play device. I will cover synth plugins in the next chapter.)
  
  The Easy Road (General MIDI Only)
  
- If you have only one play device, and it only uses straight General MIDI programs, then you are probably ready to go out of the box. If you start Rosegarden with no file to open, it opens a default blank document, called autoload.rg. Initially, this will be the system default that was installed with Rosegarden. It will load a set of basic General MIDI programs and controllers, and will route output from this device to the first available play connection. The device a the top of the list is always the default device.
+ If you have only one play device, and it only uses straight General MIDI programs, then you are probably ready to go out of the box. If you start Rosegarden with no file to open, it opens a default blank document, called autoload.rg. Initially, this will be the system default that was installed with Rosegarden. It will load a set of basic General MIDI programs and controllers, and will route output from this device to the first available play connection. The device at the top of the list is always the default device.
  
  Typically this play connection will be routed to the correct destination for your MIDI data. If not, all you should have to do is adjust the routing table by dialing appropriate connections into the associated combo boxes. For example, if Rosegarden defaults to routing your output to "64:0 (duplex)" and you do not have any external equipment attached to your computer, you probably want to change this to point to either 65:0 or something like 128:0 as appropriate.
  
  The Harder Road (Loading Device Definitions from the Library)
@@ -528,9 +528,9 @@
  Before you make this document your default, you might want to have a look at some other document-specific settings. These aren't a part of the Studio, but they're saved in autoload.rg, and any new documents you create will start life with these defaults. To edit them, use Composition -> Edit -> Document Properties.
  
  === Lilypond Headers ===
  
- The About tab starts off with some default properties. You can modify or delete these, and you can add new properties. The four defaults will be translated into Lilypond during an export. If you wish to use any other strings in your Lilypond headers, you can add them here by creating properties of that name, then binding your custom strings with them.. For example, "instrument," "dedication," or "poet."  (Get the source code and have a look at gui/lilypondio.cpp for a complete list of the currently- supported headers, if you require more information.)
+ The About tab starts off with some default properties. You can modify or delete these, and you can add new properties. The four defaults will be translated into Lilypond during an export. If you wish to use any other strings in your Lilypond headers, you can add them here by creating properties of that name, then binding your custom strings with them. For example, "instrument," "dedication," or "poet."  (Get the source code and have a look at gui/lilypondio.cpp for a complete list of the currently-supported headers, if you require more information.)
  
  Audio Directory
  
  From the Audio tab, you can configure a new directory for audio files. Rosegarden will use this path for recording new files, and it's the first place it will look when you import audio segments. By default, this is ~/rosegarden. If this path doesn't exist, you won't be able to record audio, so either create that directory or configure Rosegarden to look somewhere else here.
@@ -608,9 +608,9 @@
  ==== Setting Initial Track Volume and Other Parameters ====
  
  These initial controllers here inside the instrument provide the mechanism whereby you configure initial volume, pan, and similar settings for the track (if supported by the equipment, and properly configured into the device.) Any tracks that are routed to play through this instrument will share this instrument's parameters. 
  
- If you change these knobs in the middle of playing a composition, the new settings should take effect immediately. However, they are still only initial settings for the instrument, and the new setting will be in effect after you've rewound the composition to the beginning.. If, for example, you want to change the pan setting in the middle of a composition, you must do it by inserting controller events from the event list editor, or from a controller ruler in either the matrix or notation editors, as I will explain in due course.
+ If you change these knobs in the middle of playing a composition, the new settings should take effect immediately. However, they are still only initial settings for the instrument, and the new setting will be in effect after you've rewound the composition to the beginning.  If, for example, you want to change the pan setting in the middle of a composition, you must do it by inserting controller events from the event list editor, or from a controller ruler in either the matrix or notation editors, as I will explain in due course.
  
  === Audio Instrument Parameters ===
  
  If you want to use a track for audio, you'll need to make it an audio track by routing it to the "Audio" device. (If you do not have an "Audio" device available, please ensure that your JACK server is running.)


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/start?rev=1777907924
New Revision        : https://www.rosegardenmusic.com/wiki/start
Date of New Revision: 2026/05/04 15:19
Edit Summary        : [Release and Testing Notes] 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -10,9 +10,9 @@
  If you wish to add any new documentation or update anything in here, please contact us on the [[https://sourceforge.net/projects/rosegarden/lists/rosegarden-devel|dev mailing list]] to request access.
  
  //Note that developer pages are in the "dev:" namespace, formal project documentation is in the "doc:" namespace, and pages for translators are in the "translator:" namespace.  General user pages do not have any particular namespace; call them whatever you like.//
  
- ===== Release and Testing Notes =====
+ ===== Release Notes =====
  
    * Release notes for [[dev:25.12]]
    * Release notes for [[dev:25.06]]
    * Release notes for [[dev:24.12.1]]


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/dev:release_notes_archive?rev=1683403609
New Revision        : https://www.rosegardenmusic.com/wiki/dev:release_notes_archive
Date of New Revision: 2026/05/04 15:19
Edit Summary        : 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -1,6 +1,17 @@
  ====== Release Notes Archive ======
  
+   * Release notes for [[dev:22.12.1]]
+   * Release notes for [[dev:22.12]]
+   * Release notes for [[dev:22.06]]
+   * Release notes for [[dev:21.12]]
+   * [[dev:21.12 Testing Notes]]
+   * Release notes for [[dev:21.06.1]]
+   * Release notes for [[dev:21.06]]
+   * [[dev:21.06 Testing Notes]]
+   * Release notes for [[dev:20.12]]
+   * [[dev:20.12 Testing Notes]]
+   * Release notes for [[dev:20.06]]
    * Release notes for [[dev:19.12]]
    * Release notes for [[dev:19.06]]
    * Release notes for [[dev:18.12]]
    * Release notes for [[dev:18.06]]


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/start?rev=1771393359
New Revision        : https://www.rosegardenmusic.com/wiki/start
Date of New Revision: 2026/05/04 15:18
Edit Summary        : [Release and Testing Notes] 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -19,19 +19,8 @@
    * Release notes for [[dev:24.12]]
    * Release notes for [[dev:24.06]]
    * Release notes for [[dev:23.12]]
    * Release notes for [[dev:23.06]]
-   * Release notes for [[dev:22.12.1]]
-   * Release notes for [[dev:22.12]]
-   * Release notes for [[dev:22.06]]
-   * Release notes for [[dev:21.12]]
-   * [[dev:21.12 Testing Notes]]
-   * Release notes for [[dev:21.06.1]]
-   * Release notes for [[dev:21.06]]
-   * [[dev:21.06 Testing Notes]]
-   * Release notes for [[dev:20.12]]
-   * [[dev:20.12 Testing Notes]]
-   * Release notes for [[dev:20.06]]
    * [[dev:Release Notes Archive]]
  
  ===== Documentation =====
  


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/doc:companion-en?rev=1772216588
New Revision        : https://www.rosegardenmusic.com/wiki/doc:companion-en
Date of New Revision: 2026/03/02 21:07
Edit Summary        : 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -113,8 +113,9 @@
  
  USB MIDI Interfaces
  
  The Edriol UM-2 and mAudio MidiSport 2x2 are known to work under Linux. I have no experience with such things myself, I'm afraid, so I can only provide second-hand information.
+ 
  Pedro Lopez-Cabanillas, a contributing Rosegarden developer, reports that getting the Edriol UM-2 working is as simple as plugging in the USB cable and loading the snd-usb-audio module, which should probably be loaded automatically by hotplug.
  
  Pedro and Chris both report that the mAudio MidiSport interfaces are more difficult to get working. Pedro reports that "some of them require a firmware program to be loaded into the device's RAM before you can use it. There are GPL firmwares (package ezusbmidi) for the 1-port and 2-port devices (up to Midisport2x2), they are provided as RPM packages for Red Hat by CCRMA, and for Mandrake by Thac. There are also ready to use packages from AGNULA/Debian and Gentoo. Or you can tweak and compile the firmware from its sources." Chris reports that users with 2.6-series kernels may have difficulty using these devices. Pedro suggests that you have a look at the "zero config environment" information available from CCRMA if you are running Red Hat or Fedora.
  
@@ -397,9 +398,9 @@
  Every native Rosegarden composition (.rg) file contains a studio definition in addition to all the nuts and bolts stuff of music. The studio is a definition of every MIDI device Rosegarden can detect during the course of editing the composition. (Everything that was there at the start, plus any new devices that become available during the course of editing; as when starting something like ZynAddSubFX or Aeolus in the middle of working on a composition, for example.) It comprises information about the device itself, and about how data is routed into or out of it.
  
  ==== What is a Connection? ====
  
- Rosegarden has an integrated MIDI router to manage the flow of raw MIDI events into and out of ports provided by the underlying ALSA infrastructure. You can think of this as something like the sort of router often used to share a broadband internet connection. Unlike ethernet, however, MIDI is not bidirectional over the same cable. As a consequence of this, all connections in Rosegarden are unidrectional; even if both connections belong to the same physical piece of hardware. Connections will be displayed as one of "read," "write," or "duplex." In this diagram, connections are represented by black arrows that point in the direction data will flow through them. Rosegarden's MIDI router allows you to rearrange these connections as you require, to change what is connected where.
+ Rosegarden has an integrated MIDI router to manage the flow of raw MIDI events into and out of ports provided by the underlying ALSA infrastructure. You can think of this as something like the sort of router often used to share a broadband internet connection. Unlike Ethernet, however, MIDI is not bidirectional over the same cable. As a consequence of this, all connections in Rosegarden are unidirectional; even if both connections belong to the same physical piece of hardware. Connections will be displayed as one of "read," "write," or "duplex." In this diagram, connections are represented by black arrows that point in the direction data will flow through them. Rosegarden's MIDI router allows you to rearrange these connections as you require, to change what is connected where.
   
  ==== What is a Device? ====
  
  A device is a sort of virtual model of an individual piece of MIDI equipment. Equipment, in this sense, can be full-fledged external MIDI hardware, internal hardware like the Sound Blaster Live!, or virtual hardware like QSynth or Virtual Keyboard. Each device encapsulates information about the capabilities of a piece of equipment, and allows you to make use of those capabilities from within Rosegarden. In effect, the better the job you do of describing a particular device in Rosegarden, the better control you will have over that device.
@@ -471,9 +472,9 @@
  "Soft Synth 2" in the above example is a soundfont based card or soft synth. The simplest, most accurate way to define a device model for a synth of this type is to load the banks of program names directly out of the soundfont's .sf2 file itself. Simply set the Filter: to "Soundfont" and browse to the location of the soundfont you've loaded into your synth.
  
  === Once You've Made Your Choice ===
  
- Regardless of whether you elected to load a stock device from the Library, or loaded the programs out of a .sf2 file, you will need to make a few decisions how to procede.
+ Regardless of whether you elected to load a stock device from the Library, or loaded the programs out of a .sf2 file, you will need to make a few decisions how to proceed.
  
  If the file contains models of more than one device, you can choose which one to import. You also have various choices about which bits to import, and whether to merge new banks into existing ones or replace them completely. Everything should be self-evident after a little experimentation.
  
  The Hardest Road: Creating a List of Programs from Scratch
@@ -653,9 +654,9 @@
  == FluidSynth's External Editor ==
  
  There are no knobs for this one, and everything must be done using the external GUI.
  
- Click on the  button.
+ Click on the ? button.
  
  You'll need to load a soundfont into it with the  button.
  
  == Selecting a Program ==
@@ -823,11 +824,9 @@
  Let's start with an empty segment one measure long, and I'll show you the basics. Draw your segment, select it, and then right click on it and choose "Open in Matrix Editor" from the resulting context menu. You'll see something like this:
  
  === The Insertion Cursor ===
  
- [del]
- 
- If you take a second look at the rulers, you should see that the one toward the top of the screen has a magenta cast. This ruler is for controlling the insertionl cursor, which is a magenta version of the playback pointer. You can set it in the same fashion you set the playback pointer, and the two cursors function independently of each other. The insertionl cursor sets the destination for certain operations.  The bottom ruler controls the playback pointer and sets loops, just as both rulers do in the main window.[/del]
+ <del>If you take a second look at the rulers, you should see that the one toward the top of the screen has a magenta cast. This ruler is for controlling the insertionl cursor, which is a magenta version of the playback pointer. You can set it in the same fashion you set the playback pointer, and the two cursors function independently of each other. The insertionl cursor sets the destination for certain operations.  The bottom ruler controls the playback pointer and sets loops, just as both rulers do in the main window.</del>
  
  ==== Entering New Notes ====
  
  Now let's do a little one bar loop for demonstration purposes. Just like on the main window, the  cursor is used to create something new from scratch. In this case, of course, we're entering notes.


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/frequently_asked_questions?rev=1772484667
New Revision        : https://www.rosegardenmusic.com/wiki/frequently_asked_questions
Date of New Revision: 2026/03/02 20:52
Edit Summary        : [ALSA? JACK? Huh?] 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -156,9 +156,9 @@
  ==== 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.
  
- 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.
+ 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 within Rosegarden, 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? ====
  
  You need a soft synth! See the next question.


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/frequently_asked_questions?rev=1772484165
New Revision        : https://www.rosegardenmusic.com/wiki/frequently_asked_questions
Date of New Revision: 2026/03/02 20:51
Edit Summary        : [I've selected a synth Instrument but I don't hear any sound] 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -200,9 +200,12 @@
  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
  
- For more fun with soundfonts including how to create them for yourself have a look at the [[http://swami.sourceforge.net|Smurf/Swami project]].
+ For more fun with soundfonts including how to create them for yourself have a look at Polyphone:
+ 
+   * https://www.polyphone.io
+   * https://github.com/davy7125/polyphone - source
  
  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? ====


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/frequently_asked_questions?rev=1764616237
New Revision        : https://www.rosegardenmusic.com/wiki/frequently_asked_questions
Date of New Revision: 2026/03/02 20:42
Edit Summary        : [What does "System timer resolution is too low" mean?] 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -213,8 +213,9 @@
  
  Your options are:
  
    - Switch the sequencer to use a different timing source (Edit > Preferences... > MIDI > General > Sequencer timing source).  //This probably won't help.//
+   - See if your distro offers another kernel with a 1000Hz timer.  This is oftentimes labeled "low-latency".
    - 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)").
  


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/keyboard_shortcuts?rev=1651853242
New Revision        : https://www.rosegardenmusic.com/wiki/keyboard_shortcuts
Date of New Revision: 2026/02/27 18:38
Edit Summary        : 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -1,13 +1,15 @@
- ====== Introduction ======
+ ====== Keyboard Shortcuts ======
  
  This Wiki page is intended to eventually document all keyboard shortcuts in Rosegarden. For now, this is only a rough outline of what the page should look like in the end. Please add to it / adjust it as you see fit.
  
  The main window shortcuts should now all be listed. Please use the contents of [[keyboard_shortcuts_txt|this page]] to help finish this Wiki page.
  
- ====== Keyboard Shortcuts ======
  ===== Rosegarden Main Window =====
+ 
  ==== File ====
+ 
+ ^ Function      ^ Shortcut       ^ Note          ^
  |New File  | ctrl+n||
  |Open File  | ctrl+o||
  |Open Recent| ctrl+r|Open the most recently opened Rosegarden project (top of the list)|
  |Save  | ctrl+s||
@@ -15,8 +17,9 @@
  |Close active file  | ctrl+w||
  |Close Rosegarden  | ctrl+q||
  
  ==== Edit ====
+ 
  ^ Function      ^ Shortcut       ^ Note          ^
  |Undo  | ctrl+z||
  |Redo  | ctrl+shift+z||
  |Cut  | ctrl+x||
@@ -29,23 +32,27 @@
  |Insert range...  | ctrl+shift+ins||
  |Select all segments  | ctrl+a||
  
  ==== View ====
+ 
  ^ Function      ^ Shortcut       ^ Note          ^
  |Toggle Show transport   |t||
  |Toggle show Special Parameters  | p||
  
  ==== Composition ====
+ 
  ^ Function      ^ Shortcut       ^ Note          ^
  |Edit markers...  | ctrl+k||
  |Set quick marker at playback position  | ctrl+shift+m||
  |Jump to quick marker  | ctrl+m||
  
  ==== Studio ====
+ 
  ^ Function      ^ Shortcut       ^ Note          ^
  | No shortcuts |||
  
  ==== Segment ====
+ 
  ^ Function      ^ Shortcut       ^ Note          ^
  |Toggle repeat  | ctrl+shift+r|When checked, any selected segments will repeat until they run into another segment, or the end of the composition.|
  |Open in default editor  | return|Opens the selected segment in the default editor|
  |Open in matrix editor   | m||
@@ -58,8 +65,9 @@
  |Jog right  | alt+right||
  |Join  | ctrl+j|Joins two selected segments together (select multiple segments by holding shift while clicking them)|
  
  ==== Tracks ====
+ 
  ^ Function      ^ Shortcut       ^ Note          ^
  |Add track  | ctrl+t||
  |Add tracks...  | ctrl+shift+t||
  |Remove track  | ctrl+d||
@@ -71,8 +79,9 @@
  |Toggle mute/unmute track  | u|In Rosegarden version 10.10. (Ubuntu Studio 10.04)|
  |Toggle arm/unarm track for recording  | r||
  
  ==== Tools ====
+ 
  ^ Function      ^ Shortcut       ^ Note          ^
  | Select and Edit mode  | F2     | |
  |Draw mode  | F3 ||
  | Erase mode  | F4||
@@ -88,29 +97,28 @@
  |Scroll to follow playback  | pause|Moves the displayed part of the composition to follow the playback pointer|
  |Panic  | ctrl+alt+p|Stop playback, send All Sound Off instruction to connected MIDI instruments|
  
  ==== Help ====
+ 
  ^ Function      ^ Shortcut       ^ Note          ^
  |Rosegarden manual  | F1||
  
  ==== Shortcuts not in the Menu ====
+ 
  ^ Function      ^ Shortcut       ^ Note          ^
  |Toggle Receive External  | shift+p|Under Special Parameters. Use program changes from an external source to manipulate these controls (only valid for the currently-active track)|
- 
  
  ===== Notation Editor =====
- ^ Function      ^ Shortcut       ^ Note          ^
- | Row 1 Col 1    | Row 1 Col 2     | Row 1 Col 3        |
- | Row 2 Col 1    | some colspan (note the double pipe) ||
- | Row 3 Col 1    | Row 3 Col 2     | Row 3 Col 3        |
+ 
+ //Needs work.//
  
  ===== Matrix Editor =====
+ 
  ==== Shortcuts not in the Menu ====
+ 
  ^ Function      ^ Shortcut       ^ Note          ^
  |Copy Note  | ctrl+click|Drag to copy a note|
  
  ===== Program-Wide Shortcuts =====
  
- ^ Function      ^ Shortcut       ^ Note          ^
- | Start/Pause Playback    | ctrl+enter     | |
- | Row 2 Col 1    | some colspan (note the double pipe) ||
- | Row 3 Col 1    | Row 3 Col 2     | Row 3 Col 3        |
+ //Needs work.//
+ 


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/doc:companion-en?rev=1772134886
New Revision        : https://www.rosegardenmusic.com/wiki/doc:companion-en
Date of New Revision: 2026/02/27 18:23
Edit Summary        : 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -433,9 +433,9 @@
  The reality of Rosegarden's MIDI router is a bit less intuitive than the diagram I presented earlier. Here is that same diagram with the ALSA port numbers included.
  
  NOTE: The diagram does not exactly represent the same set of devices and connections depicted in the dialog box snapshot above.
  
- You might wonder about the strange names and numbers. ALSA assigns numbers to ports in three ranges. 64: means it is an external MIDI port on the first soundcard, which might be connected to a MIDI keyboard, sound module, or other noise producing gadget through some sort of cable. 65: means it is a virtual port with a supported internal synth such as the Sound Blaster Live! on the other side. Software synths like Hydrogen, ZynAddSubFX and the like will take numbers at the time they're started, on a first-come, first served basis starting at 128:. In addition to the number, most of these will have some kind of vaguely descriptive text component, such as "Emu10k1 Port 0 (write)." These names are provided by the underlying kernel driver, and don't always make a lot of sense. That's why Rosegarden allows you give your devices a proper name.
+ You might wonder about the strange names and numbers. ALSA assigns numbers to ports in three ranges. 64: means it is an external MIDI port on the first soundcard, which might be connected to a MIDI keyboard, sound module, or other noise producing gadget through some sort of cable. 65: means it is a virtual port with a supported internal synth such as the Sound Blaster Live! on the other side. Software synths like Hydrogen, ZynAddSubFX and the like will take numbers at the time they're started, on a first-come, first served basis starting at 128:. In addition to the number, most of these will have some kind of vaguely descriptive text component, such as "Emu10k1 Port 0 (write)." These names are provided by the underlying kernel driver, and don't always make a lot of sense. That's why Rosegarden allows you to give your devices a proper name.
  
  === Record Devices ===
  
  Record devices are MIDI keyboards, virtual keyboards, MIDI guitars and the like. As record devices are rather less complicated, I will cover them first. With a record device, you have no capabilities to describe. The only thing Rosegarden can do is read data from it, or not. You may name these if you wish, but the Record devices section of this dialog is the only place where you will see the names, and I never bother to name mine.
@@ -1474,13 +1474,13 @@
  You have polished off your composition, and now you want to share it with the world.  If you wish to reach the largest possible audience, the best way to distribute your finished product is as an audio file that can be played by anyone, regardless of the platform and software they have available.  This is a particularly good approach if your composition uses any audio, or makes use of any unusual MIDI equipment you might have.
  
  Many packages similar to Rosegarden call this feature "bounce to disk."  Rosegarden does not have a bounce to disk feature per se.  It is possible to use Rosegarden to record its own output back into itself to produce such a file, but I do not like to do this because I find it tedious to go fish out the RG-AUDIO-00??.wav file from the composition's audio path and then rename it.  Instead, I prefer to do this phase of the work using external applications.
  
- Built-In Mastering Tools
+ ==== Built-In Mastering Tools ====
  
  While it lacks a bounce to disk feature for the final step of the process, Rosegarden does provide several tools which are particularly useful at mastering time.  It has a mixer for MIDI, a mixer for audio, and an audio submaster architecture which can be used to route audio from various sources through the same set of controls.  These tools make it easy to survey the whole of your composition from one convenient place, and to make adjustments to the instrument parameters for all the tracks in your composition.
  
- The MIDI Mixer
+ === The MIDI Mixer ===
  
  Click on the  icon to open the MIDI mixer.  It will appear with the tab representing your first MIDI playback device in focus:
  
  There is a handy transport toolbar at the top.  Each of the 16 instruments has knobs for any controllers you have defined (and which are configured to have a slot in the Instrument Parameters box; refer back to the Studio chapter for details), VU meters to show output levels during playback, and a volume slider for controlling channel volume.  Remember that these instruments are associated with MIDI channels, but there is not necessarily a one to one correspondence between instrument numbers and channel numbers, depending on how you have assigned everything elsewhere.
@@ -1488,83 +1488,83 @@
  Across the bottom, each of your available playback devices has its own tab.  In this case, all the MIDI in this particular composition is played via my "SB Live 1" device, so I want to bring that into focus instead.  Next, I hit the play button on the transport to watch the VU meters, and to verify that I'm on the right tab.  Notice that I only have three controllers defined for this device, so only three knobs are available.
  
  Now I have played with the mix a little, and I also added a custom controller in the studio, just to demonstrate that it would show up here.
  
- The Audio Mixer
+ === The Audio Mixer ===
  
  The audio mixer contains banks of controls for each synth plugin and each audio instrument that is assigned to a track, along with sliders for master output volume and master recording level, and any submasters you have created.  Unlike the MIDI mixer, which always displays 16 instruments per tab, the audio mixer only shows you instruments that are actually assigned to tracks by default.  If you find the mixer window is too large for comfort, you might want to go delete any unused audio and synth plugin tracks before opening it.  This will keep it as small as possible.
  
  Click on the ? icon to open the audio mixer. 
  
  The audio mixer, just like its MIDI counterpart, provides a combined view of all the individual Instrument Parameters boxes for the various instruments.  However, unlike the MIDI mixer, this one has some important functionality that isn't available anywhere else within Rosegarden.
  
- The Audio Mixer Settings Menu
+ == The Audio Mixer Settings Menu ==
  
  In addition to the rather obvious toggles that allow you to switch off various mixer elements as desired, you will also find two important things hiding here on the Settings menu.
  
- Number of Stereo Inputs
+ == Number of Stereo Inputs ==
  
  The first is the control for the number of stereo inputs.  By default, Rosegarden creates two inputs.  If configured to create default JACK connections automatically, it connects one pair of these inputs to  "alsa-pcm" and leaves a free pair for whatever other purpose you might dream up.   In this first screenshot, you can see this setting left at its default, and you can see the standard default state of affairs in QJackCtl's audio connection manager.
  
  If you need more inputs for some reason, create them here, then go hook them up as required.  For example, navigate to Settings -> Number of Stereo Inputs -> 8 Inputs, then go check out QJackCtl's connection manager again.  Now there are eight pairs of inputs, numbered 1 through 8 available for routing in various ways among other JACK applications.
  
- Number of Submasters
+ == Number of Submasters ==
  
  You might have noticed that both the synth plugin and audio Instrument Parameters boxes have myserious controls called Out:, and that the audio box also has an In: control.
                            
  Up until now, these controls have not been particularly useful, because you have only had the default of one single master audio bus.  If you go to Settings -> Number of Submasters -> 2 Submasters, you can create a pair of submasters, and give those mysterious controls some reason to exist.  After doing so, the mixer changes slightly.  Now you can see Sub 1 and Sub 2 added at the right side of the panel.
  
  Sub-masters are secondary audio buses that can be used to route more than one instrument through a shared bank of controls, and then on out through the master.  The sub-masters are useful for grouping similar instruments together, so that you can control them as one unit.
  
- Mixing Down
+ ==== Mixing Down ====
  
  Now that you understand the tools available, you can play with the mixers until you achieve just the right sound you are looking for.  If you have external audio sources coming in through the soundcard in real time, as is the case, for example, with my Sound Canvas, then you may need to adjust your soundcard's mixer as well to achieve the best overall effect.
  
  One thing to pay particular attention to at this stage is the VU meters on the audio mixer.  In the next shot, you can see that both Audio #5 and the Master are spiking out badly.  No harm comes from this while playing everything in real-time, and I hear no clipping, thanks to the magic of JACK.  However, if I were to record this to disk in this state, the results would be horrible.  I need to play with this mix to bring everything back out of the red before the final recording.
  
- Bouncing to Disk
+ === Bouncing to Disk ===
  
  Now that the mixdown is complete, you can capture the final result to disk, and can then go on to do post-processing if desired.  My utility of choice for this purpose is Time Machine.  It is simple, and it just works. 
  
- Recording with Time Machine
+ === Recording with Time Machine ===
  
  If you have gotten everything else in line, and have created a handy wrapper for Time Machine as suggested above, then these last steps really couldn't be easier.  Start Time Machine.  A window appears with a sort of green bullseye shape in it, like this:
  
- Making Connections
+ === Making Connections ===
  
  There are VU meters across the bottom, so you can see what Time Machine is hearing.  If you hit play on the Rosegarden transport, you will see that it isn't hearing anything yet.  Unlike some of the other applications I have featured so far, Time Machine does not set up any JACK connections by default.  You need to go hook up its outputs with QJackCtl.
  
- Checking for Signs of Life
+ === Checking for Signs of Life ===
  
  Now you should be all set to record as far as Time Machine and Rosegarden are concerned.  Hit play on the transport and watch the VU meters to see if there are any unexpected surprises.  If it still does not hear anything, then perhaps you need to adjust your soundcard's mixer configuration as well.  I just found that I did not have my soundcard's mixer configured to capture the Wave channel.  I corrected this, then hit play on the transport, then had another look at Time Machine.  It's alive!
       
- Tweaking the Final Level
+ === Tweaking the Final Level ===
  
  Time Machine's VU meter has the final word in determining what sort of recording you're going to get.  First I cranked everything up through the roof.  Notice how the VU meter is spiked at 0 dB.
  
- Recording
+ === Recording ===
  
  Click the big green button, and Time Machine will do its thing, and turn into a big orange button.  If you're looking at your desktop, you should see a file pop up immediately.  These files have rather awkward names based on the date and time of the recording, which is yet another reason why I prefer to run Time Machine off of my desktop.  I find it convenient to rename this gibberish to something more meaningful immediately, so I don't lose track of which recording is which.
  
  Click the big orange button to turn it back into a big green button again, and stop the recording.  I realize that Time Machine is terribly complex when compared to a simple application like Rosegarden, so I apologize for not being able to find an audio recorder that's easier to use.
  
- Tweaking
+ === Tweaking ===
  
  I will come back to using a wave editor just a bit later, but here is what that capture looked like.  This recording is severely clipped.  There is no salvaging this complete garbage, and it makes me glad I didn't have my speakers turned on throughout this little demonstration.
  
  If you wind up in a situation like this, you need to play with your mix in Rosegarden and in your soundcard's mixer as well, and bring the levels down off the ceiling.  I find I usually obtain good results if I shoot for the sound centering around -10 dB, with no peaks higher than -5 dB, but it is sometimes necessary to aim even lower.
  
  I obtained a much better recording this time, although I still need to play with the overall mix to bring the low passages and the high passages into better proportion with each other, and to improve the left-heavy balance. 
      
- Post Production
+ ==== Post Production ====
  
  Now that you have a recording on your desktop, you will need to do some post-production work on it.  Time Machine actually records the five seconds preceding your pressing the big green button, and you will have to cut this lead-in off the front.  You may also wish to add a fade out, or run the results through a dedicated mastering application like JAMin.  (I had intended to demonstrate JAMin, because it looks useful, but if you are even capable of understanding what to do with that, you probably use Ardour for your audio work, and you probably aren't reading this book anyway.  I really can't make heads or tails of it, in truth.)
  
- Choosing an Audio Editor
+ === Choosing an Audio Editor ===
  
  What editor to use is a somewhat complicated question.  There are a number of good editors available, all with different strengths and weaknesses.  Chief among them are Sweep, Audacity and ReZound.  As of this writing, however, I can only find one editor, ReZound, that is properly JACK-aware.  Depending on your hardware, you may find that you cannot run non-JACK audio applications while JACK is running, so you may have to stop JACK before editing audio with Sweep or Audacity.
  
- ReZound
+ === ReZound ===
  
  Even though it is JACK aware, my reZound package did not know how to cope with JACK out of the box.  I found it necessary to intervene manually, and pass it a command line option to steer it in the right direction.  If you find yourself in a similar situation (as will be obvious by having a look in QJackCtl's connection manager to see if ReZound appears there) the quickest way to get there is to use an Alt+F2 Run Command box, and enter "rezound –audio-method=jack" into the box.
  
  The first time you run it this way, it asks you how you want it to make JACK connections.  The defaults are probably fine.
@@ -1572,9 +1572,9 @@
  Verify that the connections were made by having a look at QJackCtrl's connection manager:
  
  Now start ReZound, load the file off your desktop, and highlight the extra bit of silence at the beginning, use Edit -> Cut to get rid of it, and you're well on your way.  Unfortunately, showing you how to do more than this with ReZound is well beyond the scope of this book.
  
- Sweep
+ === Sweep ===
  
  Sweep is my favorite editor for doing fade outs.  I cannot find a way to accomplish the same thing with ReZound.  To do a fade out with Sweep, grab some suitable length of squiggle on the right side of the sample...
  
  Then use Process -> Echo ... Feedback -> Fade Out to apply a LADSPA plugin...
@@ -1582,33 +1582,35 @@
  ...and presto, the volume fades off quietly into the sunset, just like this book is about to do.
  
  I will leave it at that, and leave you to go on to play with this for yourself from here.  Now, before I wrap this up completely, I want to make some important announcements concerning good housekeeping lessons I have learned the hard way.
  
- Recommended Housekeeping
+ ==== Recommended Housekeeping ====
  
  I tend to forget that hitting Ctrl+Z to undo a botched audio recording does not actually make the associated audio file go away, and neither does deleting an audio segment.  The segment disappears, but the file remains loaded in the audio file manager, and it remains on disk.
  
  I have found it quite tedious trying to clean up this mess, so I have developed a recipe for my own use, which I now share with you. 
  
- Unload Unused Audio Files
+ === Unload Unused Audio Files ===
  
  Unloading the audio files from the audio file manager is the first step in the makeshift housekeeping solution I have come up with.  
  
  Click on the ? icon to open the audio file manager.
  
  Now use Edit -> Unload All Unused Audio Files to unload the files that are no longer associated with audio segments on the segment canvas.
  
- Remove Files Not Contained in the Composition
+ === Remove Files Not Contained in the Composition ===
  
  Now that you have removed the unused audio files from the file manager, save your file.  Get the rg-clean-audio script from http://rosegarden.sourceforge.net/tutorial/scripts/rg-clean-audio and save it to disk.  Use the script carefully, and only if you dare!!  I cranked it out expressly for this book, and I only tested it once!
  
  Go to a command line.  (I'm sorry.)  Make it executable by running:
  
+ <code>
  chmod +x rg-clean-audio
+ </code>
  
- Then run the script against the .rgd file you just saved.  I am running this against emergence.rg but you should of course substitue the name of your own file:
+ Then run the script against the .rgd file you just saved.  I am running this against emergence.rg but you should of course substitute the name of your own file:
  
- ./rg-clean-audio ~/emergence.rg
+   * ./rg-clean-audio ~/emergence.rg
  
  A sample run of the script looks like this:
  
  <code>


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/doc:companion-en?rev=1772134195
New Revision        : https://www.rosegardenmusic.com/wiki/doc:companion-en
Date of New Revision: 2026/02/26 19:41
Edit Summary        : More Header Adjustments
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -237,21 +237,21 @@
  Adding, Removing, Moving Tracks
  
  The tools on the Tracks Toolbar  can be used to move tracks up and down, to delete them, or to create new tracks. It is not possible to copy an entire track.
  
- Segments and Segment Parameters
+ ==== Segments and Segment Parameters ====
  
  Rosegarden compositions are made up of segments, and editing at the composition level involves dragging them around and rearranging them within tracks. Segments are a universal container that may hold either MIDI events or audio data. Segments are rather similar to layers in an image editing program such as the GIMP.  MIDI segments can be cut, pasted, split, recombined, overlapped, flattened, and pretty much rearranged at will, and are very flexible.  Audio segments behave in many of the same ways, but they are more limited in the ways they can be modified.
  
- Creating a New Segment
+ === Creating a New Segment ===
  
  You can begin recording (audio or MIDI) to create a segment, but I'll get into that a bit later. For now, why not draw one from scratch?
  
  Use the  tool to create a new segment. Click and drag it out to the desired length:
   
  Now that a segment exists, you can open it with one of the three editors. I will return to that idea later on.
  
- Moving and Copying
+ === Moving and Copying ===
  
  Use the  cursor to select a segment:
   
  Drag it to a new track:
@@ -267,9 +267,9 @@
  This can also merge MIDI events from several different tracks into a single segment. The events will combine, and merge onto a segment on whichever track is currently active.
  
  Audio segments can be split, but they cannot be resized, joined or merged. If you split an audio segment, you can undo that operation to revert it to its original state, but you cannot, for example, cut out the middle and splice the ends back together. Neither can you merge two overlapping audio segments into one, nor merge audio and MIDI segments together.  Audio segments are always associated with a file on disk, usually in the audio path for this particular composition, and changing the length of the segment does not affect the underlying file in any way.
  
- Split by Pitch
+ === Split by Pitch ===
  
  If you have a segment where the treble and bass parts are jumbled together, you might wish to split this at middle C or thereabouts. You can use Segments -> Split and Join -> Split by Pitch and then make your selections for split point, clef handling, etc. from the resulting dialog. By default, this feature attempts to split the segment intelligently, so that you can hopefully avoid winding up with treble notes in the bass part, and bass notes in the treble part.
  
  Once split, the two segments will overlap exactly on the same track. It is impossible to select a segment that lies completely underneath another segment, so it is probably a good idea to move one of the two halves into a different track.
@@ -283,9 +283,9 @@
  After you have created a segment, you can edit various parameters from the Segment Parameters box to the left: 
  
  Every segment can have a unique label and color. In this example, I've chosen the most obvious color to use for this French horn part, but colors are entirely user-configurable, and these defaults are only suggestions. I'll explain how to configure custom colors later on, in the Studio chapter.
  
- Repeats
+ === Repeats ===
  
  Every segment can be made to repeat. It will keep repeating until the end of the document, or until another segment is encountered in the track; whichever comes first. These are displayed between repeat signs ( |: :| ) in the notation editor.
  
  You can turn all repeats into copies at once with Segments -> Turn Repeats into Copies, or you can turn individual repeats into copies by double clicking on the light colored repeat rectangles.
@@ -293,29 +293,29 @@
  === Segment Quantizer ===
  
  Changing the setting in this box will immediately quantize all notes in this segment to the selected grid position. It will move the start times forward or back to align them with the next closest beat at the desired resolution. It will not change note durations in any way.
  
- Transposing Instruments
+ === Transposing Instruments ===
  
  If you wish to write notation for transposing instruments, you can dial a transposition setting into the Transpose box. This will cause the part to sound in a different range from written. A typical Bb trumpet part, for example, should have -2 here.
  
- Delay
+ === Delay ===
  
  The Delay setting allows you to knock the timing of a segment out of sync on purpose.  There is no negative delay, so if a situation arises where you wish to create a negative delay, you can accomplish this by putting a positive delay on all the other segments.
  
- Getting Around in the Composition
+ ==== Getting Around in the Composition ====
  
  If you've been following along thus far, you don't actually have anything useful to play. This might be a good time to load one of the sample files from the Rosegarden Library. The first time you use the File -> Open menu, you should be looking at the Library. If not, there should be an icon in the SpeedBar that will direct you to these files.
  
  The highlighted file in the above screen capture is my own creation. "Perfect Moment" is the name of a yellow rose, and it also describes my mood at the time I composed that.  It was the first composition I ever completed using Rosegarden.
  
- The Playback Pointer
+ === The Playback Pointer ===
  
  Notice that there is a vertical blue bar running vertically across the segment canvas. That bar is the playback pointer, and as it sweeps across the canvas, you'll hear the events as it passes over them.
  
  While you can't grab it and move it around directly, you can position it at any arbitrary point in the composition by clicking along the dark gray portion of the ruler at the top, or you can use the transport to move it around. If you don't see it, play with the transport or the ruler until you coax it out of hiding.
  
- Loops
+ === Loops ===
  
  You can loop a portion of the composition. Set the loop region by holding Shift and clicking on the gray portion of the ruler, then dragging the white bar.
  
  ==== The Transport ====
@@ -349,39 +349,39 @@
  To add a new tempo, click the  icon, and you'll be presented with a dialog like this:
  
  By default, new events you add here will be inserted at the point in time where you clicked to open the Tempo and Time Signature editor. You can change this by adjusting the "Time of tempo change" parameters, if you wish.
  
- New Time Signature
+ === New Time Signature ===
  
  Use the  icon, and you'll be presented with a dialog like:
  
  You can display the time signature as cut or common time, and make the time signature hidden. You should probably always leave "Correct the durations of the following measures" checked unless you have a good reason to do otherwise. 
  
- Document Markers
+ ==== Document Markers ====
  
  Markers are special events that can be used to mark of particular passages in the music at a composition level. They appear on the ruler, and can be edited from Composition -> Edit Markers... Issuing this command summons the marker editor dialog. In this example, I've already created a sample pair. The "Marker Name" portion is what appears on the ruler, and the "Marker description" is for the informational purposes of the composer only.
  
  The Manage Markers Dialog
  
- ==== Creating a New Marker ====
+ === Creating a New Marker ===
  
  Click on the Add button to create a new marker. A raw default marker will appear on the list spontaneously.
  
  To edit it, or to edit an existing marker, double click on it. An editor like this will appear, allowing you to set the name and description, and adjust the time at which this marker will display.
  
- ==== Markers In Position ====
+ === Markers In Position ===
  
  After closing out the manager dialog, the markers you created will appear on the ruler.
  
  ==== Miscellany ====
  
  There are a few main window features that don't quite fit in anywhere else, yet which bear special mention.
  
- Importing and Merging Other Compositions
+ === Importing and Merging Other Compositions ===
  
  Several options are available for importing and merging material from other sources. On the File -> Import menu, you can import standard MIDI files (*.mid) and Hydrogen (*.h2song) files. On the File -> Merge menu, you can merge these and other data sources (including native Rosegarden composition (*.rg) files) into the existing composition.
  
- Autosave
+ === Autosave ===
  
  If you have a power outage or the like, the next time you start Rosegarden and attempt to load the file you were working on, you'll be presented with the option of loading the autosave file instead. If you hadn't yet saved the file, you'll find it in your ~/autosave directory with a basic name of "untitled."
  
  The autosave interval defaults to 60 seconds. Configure it via the Settings menu. If you notice Rosegarden grabbing a lot of your CPU time for no apparent reason, it is probably autosave, and you might want to increase the interval, or turn this feature completely off. It can become quite cumbersome when working on very large compositions.
@@ -395,9 +395,9 @@
  ==== What is a Studio? ====
  
  Every native Rosegarden composition (.rg) file contains a studio definition in addition to all the nuts and bolts stuff of music. The studio is a definition of every MIDI device Rosegarden can detect during the course of editing the composition. (Everything that was there at the start, plus any new devices that become available during the course of editing; as when starting something like ZynAddSubFX or Aeolus in the middle of working on a composition, for example.) It comprises information about the device itself, and about how data is routed into or out of it.
  
- What is a Connection?
+ ==== What is a Connection? ====
  
  Rosegarden has an integrated MIDI router to manage the flow of raw MIDI events into and out of ports provided by the underlying ALSA infrastructure. You can think of this as something like the sort of router often used to share a broadband internet connection. Unlike ethernet, however, MIDI is not bidirectional over the same cable. As a consequence of this, all connections in Rosegarden are unidrectional; even if both connections belong to the same physical piece of hardware. Connections will be displayed as one of "read," "write," or "duplex." In this diagram, connections are represented by black arrows that point in the direction data will flow through them. Rosegarden's MIDI router allows you to rearrange these connections as you require, to change what is connected where.
   
  ==== What is a Device? ====
@@ -435,9 +435,9 @@
  NOTE: The diagram does not exactly represent the same set of devices and connections depicted in the dialog box snapshot above.
  
  You might wonder about the strange names and numbers. ALSA assigns numbers to ports in three ranges. 64: means it is an external MIDI port on the first soundcard, which might be connected to a MIDI keyboard, sound module, or other noise producing gadget through some sort of cable. 65: means it is a virtual port with a supported internal synth such as the Sound Blaster Live! on the other side. Software synths like Hydrogen, ZynAddSubFX and the like will take numbers at the time they're started, on a first-come, first served basis starting at 128:. In addition to the number, most of these will have some kind of vaguely descriptive text component, such as "Emu10k1 Port 0 (write)." These names are provided by the underlying kernel driver, and don't always make a lot of sense. That's why Rosegarden allows you give your devices a proper name.
  
- Record Devices
+ === Record Devices ===
  
  Record devices are MIDI keyboards, virtual keyboards, MIDI guitars and the like. As record devices are rather less complicated, I will cover them first. With a record device, you have no capabilities to describe. The only thing Rosegarden can do is read data from it, or not. You may name these if you wish, but the Record devices section of this dialog is the only place where you will see the names, and I never bother to name mine.
  
  Rosegarden can record from any number of inputs simultaneously. It will create a record device for every read connection it detects. Each of these can be set to be an active record device by toggling the associated checkbox.


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/doc:companion-en?rev=1771905117
New Revision        : https://www.rosegardenmusic.com/wiki/doc:companion-en
Date of New Revision: 2026/02/26 19:29
Edit Summary        : 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -1,5 +1,7 @@
- ====== Introduction to the New Rosegarden Companion ======
+ ====== The New Rosegarden Companion ======
+ 
+ ===== Introduction to the New Rosegarden Companion =====
  
  The original //Rosegarden Companion// started life in 2002, when the modern incarnation of Rosegarden was still very young, and still developing at a fast pace.  The first version of this book was published in 2005 by Bomots.de, just after Rosegarden 1.0 released.  The print edition of this book has long since been languishing on the remainder table, and it was, in the words of its publisher, "a total financial failure."
  
  This new edition is long overdue.  As there is no money in writing obscure books about obscure applications for obscure operating systems, //The New Rosegarden Companion// is being developed here on the Rosegarden Wiki, and anyone may edit it.  This new edition started life by pasting all the text from the last version of the text as it existed prior to signing the publication contract.  It has been stripped of all images, which were all horribly obsolete, and of any text that was specifically added to the work under contract.
@@ -7,15 +9,15 @@
  It will evolve very slowly from here to become a new introduction to the newest incarnation of Rosegarden, which has evolved yet again to become a pure Qt application as of version 10.02.  Many things have changed in that time, and many things have remained the same.  The core material is still mostly relevant, but this text needs major renovation on a scale that will probably take years to complete.  As of this first publication, that process has only just begun, and you can expect a great deal of this material to be horribly obsolete and misleading.
  
  D. Michael McIntyre, 22 December, 2010, current version 10.10
  
- ===== Road Map =====
+ ==== Road Map ====
  
  The first phase of this operation is to find all the chapter and section headings, and format them for the wiki.  After spending a couple of hours on this task, I have concluded that there is no way I am going to get the nesting right on the first pass, so I'm not even going to try.  After the nesting of headings has settled down, I will begin working through the material section by section, starting with the most obsolete information, and working backwards.  Eventually, the book will get all new images shot in the "Thorn" style.
  
  That is, if this work is ever complete, which doesn't seem very likely, in truth.
  
- ===== What is Rosegarden? =====
+ ==== What is Rosegarden? ====
  
  Rosegarden, is a versatile, Open Source music creation tool. It combines aspects of a MIDI (Musical Instrument Digital Interface) sequencer, an audio sequencer, and a notation editor into one convenient, powerful, easy to use package that provides users with a consistent and intuitive interface. 
  
  Rosegarden makes use of two powerful and flexible subsystems available to Linux. For MIDI operations, Rosegarden employs the ALSA (Advanced Linux Sound Architecture) MIDI sequencer infrastructure for routing in-coming and out-going MIDI events. It can record from any number of inputs simultaneously, and out-going events can be routed to any of myriad MIDI clients.
@@ -27,9 +29,9 @@
  Rosegarden provides three distinct ways of viewing, editing, and entering MIDI events, including a powerful notation editor that provides many advanced features not typically found in the notation facility of MIDI sequencers. Underneath these three editors, Rosegarden provides a segment-based mechanism for arranging blocks of MIDI and audio data on a canvas that brings something akin to the flexibility of a layer-based image editing program to the realm of music.
  
  All of this flexibility means you can use Rosegarden as the center of a very powerful home studio and music composition solution for Linux.
  
- ==== About This Book ====
+ === About This Book ===
  
  This book will take you, the reader, on a tour of Rosegarden.  It will introduce you to its features, and then show you a variety of ways to use of these features in real-world situations.
  
  The Linux novice will have questions that this book does not answer.  I leave you to turn to the support community for your particular flavor of Linux for help with matters of installation, hardware configuration, and so forth.  I assume that you have general knowledge of how to maintain your Linux box on a day to day basis, and that you have already installed Rosegarden-4 1.0 or later.  (If you installed a "rosegarden" package, and the application you see does not resemble the one covered in this book in the slightest, then you have found Rosegarden's ancient ancestor.)
@@ -37,9 +39,9 @@
  Each chapter is loosely divided into two parts. The first half details the mechanical side of making use of various controls in order to manipulate data in some way. The latter half focuses on demonstrating how to use these controls to achieve common musical goals.  There are special NOTE: and TIP: sections set off throughout the text to draw special attention to tips, tricks, caveats, and, in some cases, workarounds.
  
  Menu options and references to some dialog pages or tabs are formatted in bold, with arrows indicating the progression through the layers of menus. For example, if I say to use File -> Import -> Import MIDI File this means to begin at the "File" menu, find "Import" on this menu and hover on it until the submenu opens out, then click on "Import MIDI File."
  
- ==== Equipment and Software Required ====
+ === Equipment and Software Required ===
  
  Many people are running Rosegarden successfully on older, slower hardware. However, your CPU can't be too fast, and you can't have too much RAM or hard disk space.  I suggest a 1.0 GHz machine with at least 256 MB of RAM as a minimum starting place.  You can get by with less if you  do not do much audio work, and if you have a CPU-friendly way of playing MIDI.  The more resources your computer can bring to the table, however, the more you will be able to do successfully and enjoyably with Rosegarden. The following is a quick list of basic requirements you will need to satisfy in order to be able to do different kinds of work with Rosegarden.
  
  For MIDI recording:
@@ -70,17 +72,17 @@
  
    * a properly-configured, running JACK server, and
    * a JACK-compatible soundcard
  
- ====== Producing Sound ======
+ ===== Producing Sound =====
  
  Many users have written to ask why they are unable to get Rosegarden to make any noise. It is the most common question asked on the rosegarden-user mailing list by far, and is especially troublesome for those newly migrating to Linux from Windows® . Before we start Rosegarden for the first time, I want to explain what is necessary to pave the way, and have a good first experience. Some of you already know all this, and those of you who do are invited to jump ahead to the next chapter, where the interesting part begins.
  
  The topic of sound covers two distinct areas that may or may not be codependent, depending on the hardware and software you have available. One the one hand, there are several requirements that must be met in order to play MIDI with Rosegarden, and on the other, it's necessary to get the JACK server up and running reliably in order to make use of Rosegarden's audio features. A working JACK server is also required to play MIDI with synth plugins, or to play more than one ALSA software synth at a time. Getting Rosegarden to make noise can be a complicated business, but hopefully I can help you deal with whatever set of circumstances you have before you. I cannot, however, cover every detail of getting every card working with every distribution. I'm afraid I have to leave some questions unanswered, lest this chapter become a book unto itself. 
  
  Here is a roadmap showing all the possible ways to produce sound with Rosegarden at a glance. It's quite daunting, I know, but I hope I can help you make sense of it:
  
- ===== Playing MIDI =====
+ ==== Playing MIDI ====
  
  MIDI under Linux is quite a complicated subject. The available hardware falls into three broad categories, each with its own special considerations. External MIDI hardware, internal hardware with ALSA support, and internal hardware without ALSA support. The latter category splits into ALSA soft synths and synth plugins, which are similar, but slightly different.
  
  What's in My Computer?
@@ -96,9 +98,9 @@
  By far the least complicated, and most expensive way to play MIDI under Linux is to use real MIDI equipment. This can include keyboards, sound modules, and perhaps even MIDI guitars. A wide range of equipment is available for this purpose, ranging from comparatively inexpensive consumer keyboards to professional quality gear. The cost ranges from hundreds to thousands of dollars however, and this is not the way to go unless you are serious about MIDI.
  
  If you're fortunate enough to have such equipment, then you probably already have some idea how to hook it up to your computer. If the equipment has the ability to produce sound on its own, as some MIDI keyboards do, then you may wish to use those speakers for MIDI playback. If your MIDI equipment has no speakers, or if you intend to record the audio output from this equipment, you may wish to connect the audio output from your keyboard or sound module to an audio input jack on your soundcard. This will allow you to route everything through the soundcard's mixer. There are several choices for external MIDI interfaces.
  
- ==== Joystick Port MIDI Adapters ====
+ === Joystick Port MIDI Adapters ===
  
  The simplest, least expensive route is the joystick port MIDI adapter. These plug into the joystick port  found on many common AC97 soundcards, and on some on-board audio solutions.  The most typical adapter you will find in music stores is a simple Y cable, but nicer products are available which have LEDs to show MIDI activity.  With the right adapter in hand, all that remains is to plug the adapter into your joystick/MIDI port, connect your equipment to the box or cable using standard 5-pin DIN MIDI cables. With most AC97 soundcards, including the Sound Blaster Live!, it's only a matter of making sure the snd-seq-midi and snd-rawmidi modules are loaded (using whatever mechanism your particular distribution provides for that function.)
  
  USB MIDI
@@ -119,13 +121,13 @@
  MIDI without External Hardware
  
  For those without external hardware to use, there are two remaining categories. A few soundcards have built-in MIDI playback capability that ALSA can use. Everyone else will have to use some kind of software synth.  Unfortunately, if you are coming from a Windows®  background, there is a very good probability that your soundcard used to play MIDI perfectly well under Windows®, but it has no ability to do so under Linux out of the box.  The difference is that most such soundcards (in fact, the vast majority of common soundcards on the market) have a software synthesizer built into their Windows® driver, so that the user is never really aware that the MIDI playback capability is coming from software.  In Linux, you have the choice to run any of several software synthesizers to provide this same capability, but you will have to take steps on your own behalf to bring this about, because it is not automatic or transparent.
  
- ==== Cards That Do Have Synth Support under ALSA ====
+ === Cards That Do Have Synth Support under ALSA ===
  
  None are still relevant in 2010.
  
- ==== Cards That Do Not Have Synth Support under ALSA ====
+ === Cards That Do Not Have Synth Support under ALSA ===
  
  This is really the "everything else" category. It includes too many soundcards to list; each with its own set of modules.  Almost all of these will show up as some flavor of "ac97" in addition to whatever chipset-specific name they have. The Sound Blaster PCI and Ensoniq AudioPCI cards (ens-1370, ens-1371, ens-1373), and integrated snd-intel8x0 and snd-via82xx are probably the most common, but soundcards that fall into this category are legion. The process for getting them to play MIDI is similar in all cases.
  
  Check your Modules
@@ -141,29 +143,29 @@
  QSynth
  
  The least complicated way to get one of these cards to play MIDI is to use QSynth. It is a simple to use ALSA soft synth that takes MIDI data as input and uses .sf2 format soundfonts to produce audio output. In its simplest configuration, it can use ALSA for audio output, avoiding the need to run JACK. If you already need or want to run JACK, it can connect its output to JACK instead. In this configuration, you can also use a variety of other ALSA soft synths such as Hydrogen and Aeolus, all sharing the same audio output. QSynth is the most useful for general music production, and so it is my focus here, but the others are well worth your time to check out.  (In particular, I wish I had had time to cover Aeolus.  It is a pipe organ simulator that does a simply spectacular job.)
  
- ===== Configure the Audio Driver =====
+ ==== Configure the Audio Driver ====
  
  The first decision you need to make is whether to use ALSA or JACK for output. I will cover starting and configuring of the JACK audio server in detail in a moment.  If you have a slow computer, you may not be able to run QSynth through JACK, and you will have to run without JACK, and run Rosegarden without its audio or synth plugin capabilities enabled.  No matter which option you choose, both are configured via the Setup button. In this example, I'm using JACK. Take special note that I have adjusted the sample rate to match the sample rate I'm using with JACK, which is 48,000 Hz (for reasons I will explain directly.) Also note that I have checked [x] Auto Connect JACK Outputs. This allows QSynth to make its own default connection with JACK, which is very convenient.
  
- ==== Loading a SoundFont ====
+ === Loading a SoundFont ===
  
  Finally, it's necessary to load at least one soundfont. These are the same .sf2 soundfonts used by the SB Live! series of cards, and they are loaded via a different tab on the same setup page.
  
- ===== Synth Plugins =====
+ ==== Synth Plugins ====
  
  It is also possible to play using synth plugins. There is a FluidSynth-DSSI plugin that provides essentially the same functionality as QSynth, except that it's integrated directly into Rosegarden. I will describe it in detail when I talk about assigning instruments to tracks, because its configuration and use is entirely internal to Rosegarden. For the moment it is sufficient to know that it exists, and that it requires a working JACK audio server in order to function.
  
- ===== Playing Audio =====
+ ==== Playing Audio ====
  
  In order to play audio you will need to run JACK. 
  
- ==== What is JACK? ====
+ === What is JACK? ===
  
  JACK is short for the “Jack Audio Connection Kit.” JACK is a flexible audio server that allows its client applications to share the audio hardware seamlessly, and to share a common transport. It provides flexible mechanisms for routing inputs and outputs to and from client applications using a jack-and-cable metaphor. It is geared toward the audio professional who wants to get the lowest possible latency and the best possible performance out of his or her hardware.  Whether your own goals are professional or not, you still need JACK to get audio out of  Rosegarden (although you can still do MIDI work without it under most circumstances.)
  
- ==== Look After Your Kernel ====
+ === Look After Your Kernel ===
  
  It is theoretically possible to run JACK and Rosegarden with an ordinary stock kernel as installed by any distro, but I have never obtained acceptable results, even on machine with quite high specs.  It is simply impossible to throw enough CPU after the problem, and you will not obtain acceptable results until you look after your kernel.  I strongly recommend that you leave aside the kernel question entirely, and run something like Fervent's Studio..to go! (http://www.ferventsoftware.com), AGNULA's DeMuDi (http://www.agnula.org), or Planet CCRMA (http://ccrma.stanford.edu/planetccrma/software/).  You can also obtain suitable kernels from either AGNULA or the Planet to retrofit existing installations.
  
  I think that perhaps in another year or so, this question will be easy for anyone to solve using any off the shelf distro, merely by changing a few configuration options along the way.  In the meantime, running, or borrowing packages from a specialized music distro is a great way to save yourself having to deal with the headaches that still exist as of this writing.  For my own part, I use the 2.4.25-multimedia kernel from AGNULA, because it was installable as a retrofit package for my existing Debian system.  However, Studio..to go! ships with a suitably tweaked up 2.6 kernel that works quite well.  The difference between these two is a toss-up as of today, but I expect that the newer 2.6 kernels will quickly become the better choice.
@@ -171,9 +173,9 @@
  Starting and Tweaking JACK
  
  The simplest way to control your JACK server is to use QJackCtl. It is a very useful utility that provides a convenient way to start and stop your JACK server, to play with various configuration parameters to find the best combination for your hardware, and to manage JACK connections between applications.
  
- ==== Configuring the JACK Server ====
+ === Configuring the JACK Server ===
  
  To change how your JACK server is configured, use the Setup button. The process that follows will probably be tedious and time-consuming, but once you have discovered the "magic numbers" for your hardware, everything should continue to work thereafter. The tweaked kernel you installed allows JACK to have higher than normal priority, and this requires root privileges. You should configure JACK to start using "jackstart" so that you can run Rosegarden and JACK as an ordinary user.
  
  The settings displayed are those that work best for me on my Sound Blaster Live!, and you may well have some fiddling to do from here. If you have more than one soundcard, you may need to twiddle the "Interface" setting. I don't actually have any experience in such a situation, so you are on your own to experiment in that case.
@@ -195,23 +197,23 @@
  Rosegarden will establish sane default connections automatically. So will QSynth and Hydrogen, if you've configured them to do so. ZynAddSubFX, Time Machine, and perhaps the majority of other JACK-aware applications do not do this. To see and change the connections, click on the Connections button. Making or breaking connections is a process of highlighting one or more items in the left pane and one or more items in the right pane, then using the Connect or Disconnect buttons as required.
  
  Items in the left pane are output ports, and items in the right pane are input ports.  Some applications, such as Rosegarden, make both input and output ports available, so they appear in both lists.  Others, such as Hydrogen, only provide output, while still others, such as Time Machine, only provide input.
  
- ====== The First Look Around ======
+ ===== The First Look Around =====
  
  Let's begin by starting Rosegarden, and having a look at the main window. This is where you get an overall view of your work, and control a number of settings and parameters.
  
- ===== The Main Window =====
+ ==== The Main Window ====
  
  A Rosegarden document is called a composition. The main window is primarily dedicated to editing at the composition level, so most of these tools affect your document in a broad way. This is where you name tracks and assign instruments to them, create and manipulate segments, and watch a broad overview of playback. (I will explain these concepts in more detail later on.) This is also where you configure segment parameters such as label and color. Tempo and time signature settings exist a composition level, and they may be edited here in the main window using the tempo ruler.
  
- ===== Special Toolbars =====
+ ==== Special Toolbars ====
  
  One of the first things you might notice about Rosegarden is that there are several toolbars at the top of the main window. In addition to the usual standard controls shared by most KDE applications, there are several toolbars specific to Rosegarden. You'll choose various tools for selecting and manipulating segments from the Tools Toolbar (Select, Move, Resize, New, Erase, Split), a subset of transport tools available in the Transport Toolbar (toggled off by default), tracks can be added, deleted or moved with the Tracks Toolbar, and once a segment has been created, you can use the Editors Toolbar to open it in one of the three available editors. You'll also find icons to start the Quantizer, the Studio configuration dialog, the Synth Plugin manager, the audio file manager, and the MIDI and audio mixers.
  
  At the end of it all is the Zoom Slider, which is used to change the magnification of the Segment Canvas:
   
- ===== The Tracklist =====
+ ==== The Tracklist ====
  
  Rosegarden is a track-based sequencer. Each entry in the tracklist is a separate track that can have individualized settings for several different parameters. Each track has a label and an output assignment, and can be used to record, play, and manipulate either MIDI or audio data, but never both.
  
  Instrument vs. Name
@@ -219,17 +221,17 @@
  The tracklist can be configured to display either the name you've assigned to the track, or the name of the instrument to which it is connected. Toggle this behavior with Settings -> Show Track Labels. I will explain more about this later on, in Managing Instrument Parameters.
  
  Here we see how instrument assignments are displayed on the tracklist. In this example, the tracks are configured to play using instruments #1 and #2, respectively, on the "Roland SC-33" device.
  
- ==== Track LEDs ====
+ === Track LEDs ===
  
  Here we see the labels. One track has not yet had a name assigned, so it remains "<untitled>".
  
  Each track has two LEDs. The blue one is the track mute. If the blue LED is glowing, the track will be heard during playback. All of the blue LEDs can be turned on or off all at once with Tracks -> Mute All and -> Un-Mute All.
  
  The red LED lights up to indicate that the affected track is armed as the destination for recording operations.
  
- ==== Changing the Track Name ====
+ === Changing the Track Name ===
  
  To change the track name, double click on the label. A dialog should appear, allowing you to enter a new name.
  
  Adding, Removing, Moving Tracks
@@ -255,9 +257,9 @@
  Drag it to a new track:
  
  Hold down Ctrl while dragging it back,and make a copy:
  
- ==== Splitting and Joining ====
+ === Splitting and Joining ===
  
  Use the  cursor to split one of the segments, then switch to the  and drag one of the pieces so that it overlaps the segment on the other track. By default, this will snap to whole beat positions within the bar, but you can override that behavior by holding down the Shift key while dragging.
  
  Highlighting the smaller of two overlapping segments can sometimes be a bit tricky, but once accomplished, you can use Segments -> Join to combine several segments into one, rather like flattening the layers in an image editing program.
@@ -271,13 +273,13 @@
  If you have a segment where the treble and bass parts are jumbled together, you might wish to split this at middle C or thereabouts. You can use Segments -> Split and Join -> Split by Pitch and then make your selections for split point, clef handling, etc. from the resulting dialog. By default, this feature attempts to split the segment intelligently, so that you can hopefully avoid winding up with treble notes in the bass part, and bass notes in the treble part.
  
  Once split, the two segments will overlap exactly on the same track. It is impossible to select a segment that lies completely underneath another segment, so it is probably a good idea to move one of the two halves into a different track.
  
- ==== Segment Previews ====
+ === Segment Previews ===
  
  You can get some sense of what that bit of music is like just by looking at the segment display, which is a useful visual aid when dragging things around. If this feature is not turned on, turn it on with Settings -> Segment Previews. This displays a miniature “piano roll” for MIDI segments, and a drawing of the wave form for audio segments.
  
- ==== Segment Parameters ====
+ === Segment Parameters ===
  
  After you have created a segment, you can edit various parameters from the Segment Parameters box to the left: 
  
  Every segment can have a unique label and color. In this example, I've chosen the most obvious color to use for this French horn part, but colors are entirely user-configurable, and these defaults are only suggestions. I'll explain how to configure custom colors later on, in the Studio chapter.
@@ -287,9 +289,9 @@
  Every segment can be made to repeat. It will keep repeating until the end of the document, or until another segment is encountered in the track; whichever comes first. These are displayed between repeat signs ( |: :| ) in the notation editor.
  
  You can turn all repeats into copies at once with Segments -> Turn Repeats into Copies, or you can turn individual repeats into copies by double clicking on the light colored repeat rectangles.
  
- ==== Segment Quantizer ====
+ === Segment Quantizer ===
  
  Changing the setting in this box will immediately quantize all notes in this segment to the selected grid position. It will move the start times forward or back to align them with the next closest beat at the desired resolution. It will not change note durations in any way.
  
  Transposing Instruments
@@ -315,9 +317,9 @@
  Loops
  
  You can loop a portion of the composition. Set the loop region by holding Shift and clicking on the gray portion of the ruler, then dragging the white bar.
  
- ===== The Transport =====
+ ==== The Transport ====
  
  You should have a separate, floating Transport window like this one. If it's not visible, then toggle it on with Settings -> Show Transport.
  
  Most of these should be self-explanatory. If you can't figure out what any of the buttons do, hover over them a bit, and context-sensitive help will pop up.
@@ -335,15 +337,15 @@
  The solo button forces the Transport to play only whatever track is currently selected at the moment, independently of its mute state. (To "solo" more than one part, you'll need to set the mute for tracks individually, or by using Tracks -> Mute All Tracks and then un-muting the parts you desire.)
  
  The loop button causes the Transport to loop within the white region defined on the ruler.
  
- ===== Time and Tempo =====
+ ==== Time and Tempo ====
  
  As I mentioned, the time signature and tempo are global to the entire composition. I'll discuss another way to manipulate these in another chapter, but here and now you can manipulate both time signature and tempo to your heart's content from the main window.
  
  The tempo ruler changes color to indicate changes in tempo. When a change occurs, the tempo is displayed along the top half of the ruler, and the time signature is displayed across the bottom. If you double click this ruler, the Tempo and Time Signature editor will appear.
  
- ==== New Tempo ====
+ === New Tempo ===
  
  To add a new tempo, click the  icon, and you'll be presented with a dialog like this:
  
  By default, new events you add here will be inserted at the point in time where you clicked to open the Tempo and Time Signature editor. You can change this by adjusting the "Time of tempo change" parameters, if you wish.
@@ -359,19 +361,19 @@
  Markers are special events that can be used to mark of particular passages in the music at a composition level. They appear on the ruler, and can be edited from Composition -> Edit Markers... Issuing this command summons the marker editor dialog. In this example, I've already created a sample pair. The "Marker Name" portion is what appears on the ruler, and the "Marker description" is for the informational purposes of the composer only.
  
  The Manage Markers Dialog
  
- ===== Creating a New Marker =====
+ ==== Creating a New Marker ====
  
  Click on the Add button to create a new marker. A raw default marker will appear on the list spontaneously.
  
  To edit it, or to edit an existing marker, double click on it. An editor like this will appear, allowing you to set the name and description, and adjust the time at which this marker will display.
  
- ===== Markers In Position =====
+ ==== Markers In Position ====
  
  After closing out the manager dialog, the markers you created will appear on the ruler.
  
- ===== Miscellany =====
+ ==== Miscellany ====
  
  There are a few main window features that don't quite fit in anywhere else, yet which bear special mention.
  
  Importing and Merging Other Compositions
@@ -383,51 +385,51 @@
  If you have a power outage or the like, the next time you start Rosegarden and attempt to load the file you were working on, you'll be presented with the option of loading the autosave file instead. If you hadn't yet saved the file, you'll find it in your ~/autosave directory with a basic name of "untitled."
  
  The autosave interval defaults to 60 seconds. Configure it via the Settings menu. If you notice Rosegarden grabbing a lot of your CPU time for no apparent reason, it is probably autosave, and you might want to increase the interval, or turn this feature completely off. It can become quite cumbersome when working on very large compositions.
  
- ====== The Studio ======
+ ===== The Studio =====
  
  Now that you have a general idea how Rosegarden works, now is a good time to think about telling Rosegarden something about the MIDI equipment you wish to use. People who intend to use Rosegarden purely for audio work are free to skip this chapter entirely.
  
  Before we get started, some of you might need some basic background information so that you can dive into this with some understanding of the concepts I am about to explain. If you are new to MIDI, or if anything in this chapter leaves you scratching your head, you might want to read through my MIDI Primer in Appendix B.
  
- ===== What is a Studio? =====
+ ==== What is a Studio? ====
  
  Every native Rosegarden composition (.rg) file contains a studio definition in addition to all the nuts and bolts stuff of music. The studio is a definition of every MIDI device Rosegarden can detect during the course of editing the composition. (Everything that was there at the start, plus any new devices that become available during the course of editing; as when starting something like ZynAddSubFX or Aeolus in the middle of working on a composition, for example.) It comprises information about the device itself, and about how data is routed into or out of it.
  
  What is a Connection?
  
  Rosegarden has an integrated MIDI router to manage the flow of raw MIDI events into and out of ports provided by the underlying ALSA infrastructure. You can think of this as something like the sort of router often used to share a broadband internet connection. Unlike ethernet, however, MIDI is not bidirectional over the same cable. As a consequence of this, all connections in Rosegarden are unidrectional; even if both connections belong to the same physical piece of hardware. Connections will be displayed as one of "read," "write," or "duplex." In this diagram, connections are represented by black arrows that point in the direction data will flow through them. Rosegarden's MIDI router allows you to rearrange these connections as you require, to change what is connected where.
   
- ===== What is a Device? =====
+ ==== What is a Device? ====
  
  A device is a sort of virtual model of an individual piece of MIDI equipment. Equipment, in this sense, can be full-fledged external MIDI hardware, internal hardware like the Sound Blaster Live!, or virtual hardware like QSynth or Virtual Keyboard. Each device encapsulates information about the capabilities of a piece of equipment, and allows you to make use of those capabilities from within Rosegarden. In effect, the better the job you do of describing a particular device in Rosegarden, the better control you will have over that device.
  
  For example, if you have a nice keyboard attached to your computer, but you accept Rosegarden's default General MIDI device definition for it, you will be unable to make use of any of the keyboard's advanced features from within Rosegarden until you make your device definition more accurate. Conversely, telling Rosegarden you have a Roland JV-88 does not make it so, and if you assign any instruments to programs that are not actually available on the connected equipment, you will hear no sound. (More about instruments in the next chapter.)
  
  A device like the following is typical of either QSynth or a Sound Blaster Live! after loading an uncomplicated soundfont. It includes a basic set of controllers (which are dependent on the capabilities of either QSynth or the Sound Blaster, both of which do support a limited number of controllers, and actually have nothing to do with the soundfont per se), a set of standard General MIDI programs loaded into bank 0 0, and a set of Roland GS-style extra drum kits loaded into bank 1 0.
  
- ===== Putting Connections and Devices Together =====
+ ==== Putting Connections and Devices Together ====
  
  A studio can consist of just one device, and perhaps for many of you that is all the complexity you will ever need. The real power, however, lies with Rosegarden's ability to manage numerous devices simultaneously. A studio is, in effect, a collection of device descriptions and a routing table ensuring that the right devices are connected to the right MIDI equipment on the other end.
  
- ==== A Typical QSynth Studio ====
+ === A Typical QSynth Studio ===
  
  Another typical, simple setup involves using QSynth for MIDI playback and VKeybd for input. You can start either of these after starting Rosegarden, and Rosegarden will detect them and make a play connection and a record connection available, along with an empty play device.
  
- ==== A More Complex Studio ====
+ === A More Complex Studio ===
  
  This is what my own studio looks like when I have QSynth, Hydrogen, and ZynAddSubFX running, along with my Roland Sound Canvas and my Sound Blaster Live!. It looks horribly complex on paper, and it would look even worse if I drew out every single bank of GS variations, and did a better job of representing the fact that, while the same soundfont happens to be loaded into both the Sound Blaster and QSynth, that doesn't have to be the case. No matter how it looks, this is actually quite simple to use day to day, believe it or not. Rosegarden makes this easy.
  
  Notice that I have controllers for the Sound Blaster, for QSynth, and for the Roland (the "External MIDI GS Synth"), but I do not have any controllers defined for Hydrogen or ZynAddSubFX. That's because, to the best of my knowledge, neither of those soft synths knows how to do anything with controllers. They both have their own control panels that must be twiddled manually, and that sort of thing can't be automated from within Rosegarden.
  
- ==== Configuring Your Own Studio ====
+ === Configuring Your Own Studio ===
  
  The first step in this process is to open the main Studio dialog. Composition -> Studio -> Manage MIDI Devices... or by clicking on the ? icon.
  
  You'll be presented with a dialog that resembles this one, except, of course, that this one has already largely been configured to suit my own default studio. It is divided into two sections; one for play devices, and one for record devices, and their associated connections. It also shows you how each of these devices is connected to internal, external, and software synths. In this example, I have a device named "Roland SC-33" connected to "64:0 EMU101K MPU-401 (UART) (duplex)" and four "SB Live (n)" devices connected to each of 65:0 through 65:3, which are the four output ports on my SB Live!, with their associated write connections. I also have three generic spots reserved for soft synths, named "Soft Synth 1" through "Soft Synth 3", one of which is currently connected to KAMix, an ALSA mixer client that can be controlled via MIDI. These are empty devices that I created with the New button.
  
- ===== Connections =====
+ ==== Connections ====
  
  The reality of Rosegarden's MIDI router is a bit less intuitive than the diagram I presented earlier. Here is that same diagram with the ALSA port numbers included.
  
  NOTE: The diagram does not exactly represent the same set of devices and connections depicted in the dialog box snapshot above.
@@ -441,9 +443,9 @@
  Rosegarden can record from any number of inputs simultaneously. It will create a record device for every read connection it detects. Each of these can be set to be an active record device by toggling the associated checkbox.
  
  In this example, I have both a hardware record device and a software record device. These devices were created spontaneously when Rosegarden detected the associated duplex read and virtual read connections. I have marked both of them "Current" and I can record events from either one of them, or both of them at the same time.
  
- ==== Play Devices ====
+ === Play Devices ===
  
  Play devices are where all the fun, and all the complexity is. As I have mentioned elsewhere, they can be MIDI keyboards, sound modules, software synths, samplers, and pretty well anything else that can take MIDI input, such as KAMix. (Synth plugins are somewhat different. There is a single synth plugin device into which any and all plugins are plugged, and it is not a MIDI play device. I will cover synth plugins in the next chapter.)
  
  The Easy Road (General MIDI Only)
@@ -459,17 +461,17 @@
  In this example, you can see that I have already imported some programs from the soundfont I use on my SB Live!, and I have named the four devices "SB Live! (1)" through "SB Live! (4)" for my own convenience. This soundfont has programs available in four banks, which are displayed as the branches of the tree. The LSB column is not visible in this snapshot, but the bank names tell most of the tale. I named the last one "Percussion" to set it apart, because that is where this soundfont stores the drum kits.
  
  You can also see that I have a device called "Soft Synth 2" highlighted, and I'm looking at the empty list of programs that make up Rosegarden's virtual model for this device. Unlike internal and external MIDI equipment, Rosegarden assigns connections to soft synths on a first-come, first serve basis, based on the order in which the applications are started. It is very easy to wind up with something named "Hydrogen" that is actually connected to QSynth. I find I prefer to give these things generic names and assign the connections manually as required, because I start and stop soft synths as I need them.
  
- === Loading a Device from the Library ===
+ == Loading a Device from the Library ==
  
  If you're lucky, the growing Rosegarden Library already contains a set of bank and program definitions to suit your hardware. To try your luck, click the Import... button. You will initially be presented with a list of .rgd files from the Library, which was installed along with Rosegarden itself, but you can, of course, browse to other locations. You can import banks from both regular Rosegarden Composition (.rg) files, and from Rosegarden Device (.rgd) files. If you don't find anything suitable, you will probably have to start from scratch, as I will explain later on.
  
  Turning a SoundFont into a Device
  
  "Soft Synth 2" in the above example is a soundfont based card or soft synth. The simplest, most accurate way to define a device model for a synth of this type is to load the banks of program names directly out of the soundfont's .sf2 file itself. Simply set the Filter: to "Soundfont" and browse to the location of the soundfont you've loaded into your synth.
  
- ==== Once You've Made Your Choice ====
+ === Once You've Made Your Choice ===
  
  Regardless of whether you elected to load a stock device from the Library, or loaded the programs out of a .sf2 file, you will need to make a few decisions how to procede.
  
  If the file contains models of more than one device, you can choose which one to import. You also have various choices about which bits to import, and whether to merge new banks into existing ones or replace them completely. Everything should be self-evident after a little experimentation.
@@ -479,41 +481,41 @@
  If none of the device models in the library are suitable, and you can't turn the program names from a soundfont into a device, then you will need to get to work creating your own. You can use an existing file from the library as a starting point, or you can create a new device definition completely from scratch.
  
  Even if you have no real need to start from scratch, you may wish to read through this material anyway, in order to better understand how some of the devices in the Library are put together.
  
- === Naming the Device ===
+ == Naming the Device ==
  
  So that you can avoid confusion, you probably want to replace Rosegarden's default "Anonymous MIDI Device 3" type name with something more meaningful. Simply double click on the existing name and give your virtual model a more descriptive one.
  
  Now that your "Anonymous External Device" has become a "Roland SC-33" or what have you, you probably want add a description of its available programs and controllers to Rosegarden's model.
  
- === Why Name Programs and Controllers? ===
+ == Why Name Programs and Controllers? ==
  
  Depending on the capabilities of this device, it might not matter whether you define named program changes or not. However, if you do intend to transmit programs, bank changes or controllers to the equipment--even if you only want to use numbers--you need to define something here. Rosegarden's model of your equipment will only include what you define here, and anything you leave empty will not be available for your use. If you don't let Rosegarden know that program number 97 can play something, it will never allow you set a track to use that program number.
  
- === Gathering Information ===
+ == Gathering Information ==
  
  The key to success here is having as much information about the equipment as possible. You need to know what programs it can use, and how the banks are numbered. If you have no idea, you may have to try loading "raw-numbers.rgd" from the Library, which I created as a way of providing a generic everything to everyone placeholder just to fill up the slots and allow program changes to be transmitted. Beyond the essential fact that you must understand your equipment to describe it, there are really only two special cases worth mentioning here.
  
- === Variations ===
+ == Variations ==
  
  Some equipment uses a method of sorting programs into banks in such a way that the programs in bank 0 0 are the standard General MIDI instruments, and the programs in the remaining banks are variations on those instruments. Roland's GS standard is a prime example of this. Bank 0 0, program 1 is "Piano 1" and bank 0 8, program 1 is "Piano 1w." In order to make it easy to take advantage of this relationship, Rosegarden offers the ability to display programs in secondary banks as variations. You may choose to enable this, and to show the variation list based on either the LSB or MSB value.
  
- === The Percussion Checkbox ===
+ == The Percussion Checkbox ==
  
  The [x] Percussion checkbox is used to tell Rosegarden that a particular bank contains named drum kits, rather than more conventional programs.  In many cases, this will be true for the 1:0 bank.  Checking this box will tell the Instrument Parameters box (which you will see a bit later on) which banks have drum kits in them.
  
  Finally, you may have noticed that Rosegarden only allows you one set of program changes per bank address. The exception to this rule is that you may define a parallel set of program changes if the [x] Percussion box is checked. For example, if you have a synth that interprets standard program changes in bank 0 0 on channel 10 as drum kit changes (like GS) then you can tell Rosegarden how to use them.
  
  The process is a bit fiddly. First you have to use the Add button to create a new, empty bank. It will take a number other than 0 0 because 0 0 is already in use. Check the [x] Percussion box for this new bank, and then dial its LSB and MSB values back down to 0 0 (or wherever they need to be for your implementation) and enter the names of drum kits as programs.
  
- === Send in Your Device Descriptions ===
+ == Send in Your Device Descriptions ==
  
  Once you've defined the names for your program changes, you can save the device definition to disk with the Export... button.
  
  If you think anyone else might benefit from having the instrument definition, you can mail it to me at dmm...@us... and I will add it to our growing collection of user contributions.
  
- ==== Custom Controllers ====
+ === Custom Controllers ===
  
  Rosegarden should create a few basic default controllers for you. If you have special requirements, or if some of these controllers don't function on the piece of equipment for which you're defining the device, you may wish to edit these defaults by clicking the Control Events button.
  
  If your equipment can't use any of these controllers, you probably want to delete them. If there are controllers missing, you can add them one by one. Use the Add button. This will create a new entry using default values. Double click it, and you should be presented with a dialog similar to this one.
@@ -523,9 +525,9 @@
  Default Document Properties
  
  Before you make this document your default, you might want to have a look at some other document-specific settings. These aren't a part of the Studio, but they're saved in autoload.rg, and any new documents you create will start life with these defaults. To edit them, use Composition -> Edit -> Document Properties.
  
- ==== Lilypond Headers ====
+ === Lilypond Headers ===
  
  The About tab starts off with some default properties. You can modify or delete these, and you can add new properties. The four defaults will be translated into Lilypond during an export. If you wish to use any other strings in your Lilypond headers, you can add them here by creating properties of that name, then binding your custom strings with them.. For example, "instrument," "dedication," or "poet."  (Get the source code and have a look at gui/lilypondio.cpp for a complete list of the currently- supported headers, if you require more information.)
  
  Audio Directory
@@ -545,9 +547,9 @@
  Composition -> Studio -> Save Current Document as Default Studio will save the current document as your local autoload.rg file. This becomes the default for all new documents you create, but it will have no effect on documents that you've already created, or documents you load from other sources. The studio belongs to each individual composition.
  
  This default studio is just like any ordinary .rg file, and that means any segments, track labels, instrument assignments, etc. that you have in the current document will be saved, and will subsequently be loaded each time you create a new document.
  
- ===== Managing Instruments =====
+ ==== Managing Instruments ====
  
  You want to play a particular track using a hammered dulcimer, or else you've got an audio track that needs some EQ. In either case, you need an introduction to the instrument. Instruments are configured with the Instrument Parameters box, and any number of tracks can be assigned to play via the same instrument. 
  
  Instruments
@@ -587,29 +589,29 @@
  Simple General MIDI Instruments
  
  At the simple end, assigning a "Harpsichord" program to a basic General MIDI device only requires that you use the Program combo box to pick out the appropriate name.
  
- ===== GS Program and Variation Instruments =====
+ ==== GS Program and Variation Instruments ====
  
  With any of the GS devices from the Library, you can dial in both the program and variation. For example, "Church Org 3" is a variation of "Church Org 1." In order to get here, dial "Church Org 1" into the Program combo box, and then dial through the possible variations with the Variation combo box.
  
- ===== Drum Instruments =====
+ ==== Drum Instruments ====
  
  Most MIDI equipment has some way of playing drums using a bank of percussion sounds that are mapped to various pitches on the keyboard. Basic General MIDI equipment has only one standard drum kit, and you most likely need not do more than assign an instrument to output on channel 10 in order to make use of it. Most higher-end equipment and many soundfonts offer alternatives to this standard kit.
  
  If your studio is correctly configured, you should be able to dial up a drum kit simply by toggling the [x] Percussion checkbox, and then dialing in an appropriate program.  In order for this to work, at least one bank has to have its own bank editor level [x] Percussion box checked.  The two checkboxes are interrelated.
  
- ===== Controller Knobs =====
+ ==== Controller Knobs ====
  
  You may change the default controller values by adjusting the knobs. The tool tip explains how to use them just as well as I could.
  
- ===== Setting Initial Track Volume and Other Parameters =====
+ ==== Setting Initial Track Volume and Other Parameters ====
  
  These initial controllers here inside the instrument provide the mechanism whereby you configure initial volume, pan, and similar settings for the track (if supported by the equipment, and properly configured into the device.) Any tracks that are routed to play through this instrument will share this instrument's parameters. 
  
  If you change these knobs in the middle of playing a composition, the new settings should take effect immediately. However, they are still only initial settings for the instrument, and the new setting will be in effect after you've rewound the composition to the beginning.. If, for example, you want to change the pan setting in the middle of a composition, you must do it by inserting controller events from the event list editor, or from a controller ruler in either the matrix or notation editors, as I will explain in due course.
  
- ==== Audio Instrument Parameters ====
+ === Audio Instrument Parameters ===
  
  If you want to use a track for audio, you'll need to make it an audio track by routing it to the "Audio" device. (If you do not have an "Audio" device available, please ensure that your JACK server is running.)
  
  Audio instruments have different controls available in the Instrument Parameters box.
@@ -617,47 +619,47 @@
  They have a mono/stereo toggle, ( ) and various controls for adding plugins and adjusting levels.
  
  If you wish to assign LADSPA plugins to the instrument, you may use one of the "<no plugin>" buttons to summon a dialog similar to this one. You can narrow in on what you want using the Category: selector, and then dial in a particular plugin with the Plugin: selector. As you dial through these, the knobs in the bottom half of this dialog box will change to reflect the controls that are available for this particular plugin; ranging from one knob to a screen full of them. You can layer up to five plugins for each instrument in the "Audio" device, hardware allowing. Some plugins are particularly expensive in their use of your system's resources, so using too many may cause performance problems.
  
- ==== Synth Plugin Instrument Parameters ====
+ === Synth Plugin Instrument Parameters ===
  
  As mentioned in the introduction, Rosegarden was the first sequencer for Linux to employ the new DSSI plugin architecture. If you have your JACK server running, and your Rosegarden package was built with DSSI support enabled, you should have a "Synth plugin" device available.  Each of the 16 synth plugin instruments can take a different synth plugin, and can have up to five LADSPA plugins layered on top of the basic sound the synth plugin produces.
  
  Begin by routing a track first to this device, and then to one of the 16 available instruments.
  
- ==== Select a Synth Plugin ====
+ === Select a Synth Plugin ===
  
  After routing a track to a synth plugin instrument, the Instrument Parameters box will show a new set of controls. These are similar to the controls for audio instruments. To configure this synth plugin instrument, begin by clicking on the "<no synth>" button.
  
  After first clicking the button, you will need to dial in one of the plugins you have installed.  I cannot possibly cover all the plugins available, but the concepts I am demonstrating with these select plugins  apply broadly to any of them.
  
- === Xsynth ===
+ == Xsynth ==
  
  After dialing the Plugin combo box to "Xsynth DSSI Plugin" the dialog box will transform itself into something like this:
  
  I have to leave it up to you to play with the knobs and discover how to twiddle this into making interesting noises. This synth plugin is not nearly as complex as something like ZynAddSubFX, for example, but having it effectively built right into Rosegarden has some advantages.
  
  no need to tinker with JACK routing, since it plays through Rosegarden's JACK connection settings for the knobs are saved with the composition, which allows you to dial up custom patches and save them with your file without having to fool with the external editor with 16 plugin instruments, you can have 16 Xsynths if you want, each with its own patch, and its own set of LADSPA plugins
  
- === Xsynth's External Editor ===
+ == Xsynth's External Editor ==
  
  If you click on the  button you can use Xsynth's external editor to manage its controls in a different way, change several parameters, and to manage your collection of custom patches. While it isn't necessary to do this, you may find it useful to save named presets to disk, and you might find the plugin's own native GUI is slightly more informative with respect to what the various knobs are for. (In particular, the native GUI tells you what kind of wave form the various numbers represent, while Rosegarden's plugin interface does not.) The GUI is an independent module unrelated to Rosegarden, which is why the look and feel are so different.
  
- === FluidSynth ===
+ == FluidSynth ==
  
  FluidSynth-DSSI is a plugin built around the same underlying engine that powers QSynth. The plugin implementation isn't quite as friendly to use as QSynth, but it affords most of the same functionality in a package that's integrated directly into Rosegarden's user interface.
  
  After dialing the Plugin combo box to "FluidSynth-DSSI Plugin" the dialog box will transform itself into something like this:
  
- === FluidSynth's External Editor ===
+ == FluidSynth's External Editor ==
  
  There are no knobs for this one, and everything must be done using the external GUI.
  
  Click on the  button.
  
  You'll need to load a soundfont into it with the  button.
  
- === Selecting a Program ===
+ == Selecting a Program ==
  
  After you have loaded a soundfont, you can use the Program combo box to dial in any of the programs available in the soundfont. This interface does not separate them into individual banks in the same fashion you saw elsewhere. Instead, all available programs in the entire soundfont are presented within one top to bottom list.
  
  Obviously, you can only have one program per plugin, so if you want to play both a flute and a guitar, you will need to assign two different tracks to the Synth plugin instrument, and configure both of these to use Fluidsynth-DSSI.  The plugin itself is smart enough to run only one instance of itself in this situation, so you will not be running two copies of the plugin, both competing for system resources.
@@ -671,55 +673,55 @@
  There are three different ways to record with Rosegarden. If you come from a MIDI background, the most obvious thing to do is plug in your MIDI keyboard and hit the record button to record a MIDI segment in the currently-selected track. If audio is your aim, you'll want to set your mixer recording source and get to work. On the other hand, if you are not very good at playing keyboard instruments, you might be more interested in step recording.
  
  I will cover step recording later on. For now my focus is on recording operations that can be performed from the main window.
  
- ===== Recording MIDI =====
+ ==== Recording MIDI ====
  
  You can record MIDI from any source that Rosegarden recognizes as a record device, as I mentioned in some detail in a previous chapter.
  
  To recap briefly, click the  icon to have a look at your current studio, then look at the "Record devices" section of the dialog. Any inputs you have available will appear in this list, and you may set any number of them as active recording sources by toggling the Current checkboxes for each of them. In this example, I have both the external MIDI port on my soundcard and Virtual Keyboard available, and marked as active.
  
- ===== Create a MIDI Track =====
+ ==== Create a MIDI Track ====
  
  You most likely already have plenty of MIDI tracks, but it bears mentioning for the sake of completeness that you must route a track's output to a MIDI or synth plugin device in order for that track to become a MIDI track, and therefore capable of serving as a destination for MIDI recording operations. Please review previous chapters if you have any questions about instrument assignment.
  
- ===== Recording Audio =====
+ ==== Recording Audio ====
  
  Audio recording is considerably more involved than MIDI, but it can become second nature after a bit of practice getting everything in order beforehand.
  
- ==== Set a New Audio Path! ====
+ === Set a New Audio Path! ===
  
  If you wish to record audio, the first thing you should do is create a new directory for the files, and set the audio record path for this composition to that directory via Composition -> Edit Document Properties -> Audio. This dialog also shows you how much space you have remaining on the target storage device (typically a hard disk, though it might be a USB memory stick if you are using Studio..to go!), and estimates how much room you have to store audio files.
  
  Rosegarden writes files with names like "RG-AUDIO-00001.wav" to this directory. Every botched take, every empty recording where you got the mixer set wrong, every goof in the world will get a new filename with a new number. If you don't sort your audio files into directories grouped by project, you'll eventually wind up with a horrible mess to sort out, with little choice but to audition each and every one of them to find out what is what. Discipline in remembering to choose a new audio path for each new project really pays off in the long run, by allowing you to avoid this problem. (After years of ignoring this advice in my own work, I now have a 2 GB ~/rosegarden directory full of who knows what, with completely meaningless filenames.  Learn from my mistake!)  Additionally, if you keep all files associated with a particular project in one place, it greatly facilitates going back at the end of the day to clean up any bad takes, so they don't waste disk space.  I will deal with a bit of that later on.
  
- ==== Create an Audio Track ====
+ === Create an Audio Track ===
  
  You may already have audio tracks, but in the event that you don't, merely route a track to an instrument belonging to the Audio device, as previously described.
  
- ===== Configure the Mixer =====
+ ==== Configure the Mixer ====
  
  If you want to record audio, you n...
 
[truncated message content]

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/doc:companion-en?rev=1771904698
New Revision        : https://www.rosegardenmusic.com/wiki/doc:companion-en
Date of New Revision: 2026/02/24 03:51
Edit Summary        : Fix tables
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -1717,9 +1717,9 @@
  | 3 | Honky-tonk Piano |
  | 4 | Electric Piano 1 |
  | 5 | Electric Piano 2 |
  | 6 | Harpsichord |
- | 7 | Clavi
+ | 7 | Clavi |
  
  Chromatic Percussion
  
  | 8 | Celesta |
@@ -1743,149 +1743,149 @@
  | 23 | Tango Accordion |
  
  Guitars
  
- 24 Acoustic Guitar (nylon)
- 25 Acoustic Guitar (steel)
- 26 Electric Guitar (jazz)
- 27 Electric Guitar (clean)
- 28 Electric Guitar (muted)
- 29 Overdriven Guitar
- 30 Distortion Guitar
- 31 Guitar harmonics
+ | 24 | Acoustic Guitar (nylon) |
+ | 25 | Acoustic Guitar (steel) |
+ | 26 | Electric Guitar (jazz) |
+ | 27 | Electric Guitar (clean) |
+ | 28 | Electric Guitar (muted) |
+ | 29 | Overdriven Guitar |
+ | 30 | Distortion Guitar |
+ | 31 | Guitar harmonics |
  
  Bass
  
- 32 Acoustic Bass
- 33 Fingered Bass
- 34 Picked Bass
- 35 Fretless Bass
- 36 Slap Bass 1
- 37 Slap Bass 2
- 38 Synth Bass 1
- 39 Synth Bass 2
+ | 32 | Acoustic Bass |
+ | 33 | Fingered Bass |
+ | 34 | Picked Bass |
+ | 35 | Fretless Bass |
+ | 36 | Slap Bass 1 |
+ | 37 | Slap Bass 2 |
+ | 38 | Synth Bass 1 |
+ | 39 | Synth Bass 2 |
  
  Orchestral
  
- 40 Violin
- 41 Viola
- 42 Cello
- 43 Contrabass
- 44 Tremolo Strings
- 45 Pizzicato Strings
- 46 Orchestral Harp
- 47 Timpani
+ | 40 | Violin |
+ | 41 | Viola |
+ | 42 | Cello |
+ | 43 | Contrabass |
+ | 44 | Tremolo Strings |
+ | 45 | Pizzicato Strings |
+ | 46 | Orchestral Harp |
+ | 47 | Timpani |
  
  Ensembles
  
- 48 String Ensemble 1
- 49 String Ensemble 2
- 50 SynthStrings 1
- 51 SynthStrings 2
- 52 Choir Aahs
- 53 Voice Oohs
- 54 Synth Voice
- 55 Orchestra Hit
+ | 48 | String Ensemble 1 |
+ | 49 | String Ensemble 2 |
+ | 50 | SynthStrings 1 |
+ | 51 | SynthStrings 2 |
+ | 52 | Choir Aahs |
+ | 53 | Voice Oohs |
+ | 54 | Synth Voice |
+ | 55 | Orchestra Hit |
  
  Brass
  
- 56 Trumpet
- 57 Trombone
- 58 Tuba
- 59 Muted Trumpet
- 60 French Horn
- 61 Brass Section
- 62 SynthBrass 1
- 63 SynthBrass 2
+ | 56 | Trumpet |
+ | 57 | Trombone |
+ | 58 | Tuba |
+ | 59 | Muted Trumpet |
+ | 60 | French Horn |
+ | 61 | Brass Section |
+ | 62 | SynthBrass 1 |
+ | 63 | SynthBrass 2 |
  
  Reeds
  
- 64 Soprano Sax
- 65 Alto Sax
- 66 Tenor Sax
- 67 Baritone Sax
- 68 Oboe
- 69 English Horn
- 70 Bassoon
- 71 Clarinet
+ | 64 | Soprano Sax |
+ | 65 | Alto Sax |
+ | 66 | Tenor Sax |
+ | 67 | Baritone Sax |
+ | 68 | Oboe |
+ | 69 | English Horn |
+ | 70 | Bassoon |
+ | 71 | Clarinet |
  
  Pipes
  
- 72 Piccolo
- 73 Flute
- 74 Recorder
- 75 Pan Flute
- 76 Blown Bottle
- 77 Shakuhachi
- 78 Whistle
- 79 Ocarina
+ | 72 | Piccolo |
+ | 73 | Flute |
+ | 74 | Recorder |
+ | 75 | Pan Flute |
+ | 76 | Blown Bottle |
+ | 77 | Shakuhachi |
+ | 78 | Whistle |
+ | 79 | Ocarina |
  
  Synth Leads
  
- 80 Lead 1 (square)
- 81 Lead 2 (sawtooth)
- 82 Lead 3 (calliope)
- 83 Lead 4 (chiff)
- 84 Lead 5 (charang)
- 85 Lead 6 (voice)
- 86 Lead 7 (fifths)
- 87 Lead 8 (bass + lead)
+ | 80 | Lead 1 (square) |
+ | 81 | Lead 2 (sawtooth) |
+ | 82 | Lead 3 (calliope) |
+ | 83 | Lead 4 (chiff) |
+ | 84 | Lead 5 (charang) |
+ | 85 | Lead 6 (voice) |
+ | 86 | Lead 7 (fifths) |
+ | 87 | Lead 8 (bass + lead) |
  
  Synth Pads
  
- 88 Pad 1 (new age)
- 89 Pad 2 (warm)
- 90 Pad 3 (polysynth)
- 91 Pad 4 (choir)
- 92 Pad 5 (bowed)
- 93 Pad 6 (metallic)
- 94 Pad 7 (halo)
- 95 Pad 8 (sweep)
+ | 88 | Pad 1 (new age) |
+ | 89 | Pad 2 (warm) |
+ | 90 | Pad 3 (polysynth) |
+ | 91 | Pad 4 (choir) |
+ | 92 | Pad 5 (bowed) |
+ | 93 | Pad 6 (metallic) |
+ | 94 | Pad 7 (halo) |
+ | 95 | Pad 8 (sweep) |
  
  Synth FX
  
- 96 FX 1 (rain)
- 97 FX 2 (soundtrack)
- 98 FX 3 (crystal)
- 99 FX 4 (atmosphere)
- 100 FX 5 (brightness)
- 101 FX 6 (goblins)
- 102 FX 7 (echoes)
- 103 FX 8 (sci-fi)
+ | 96 | FX 1 (rain) |
+ | 97 | FX 2 (soundtrack) |
+ | 98 | FX 3 (crystal) |
+ | 99 | FX 4 (atmosphere) |
+ | 100 | FX 5 (brightness) |
+ | 101 | FX 6 (goblins) |
+ | 102 | FX 7 (echoes) |
+ | 103 | FX 8 (sci-fi) |
  
  Ethnic
  
- 104 Sitar
- 105 Banjo
- 106 Shamisen
- 107 Koto
- 108 Kalimba
- 109 Bag pipe
- 110 Fiddle
- 111 Shanai
+ | 104 | Sitar |
+ | 105 | Banjo |
+ | 106 | Shamisen |
+ | 107 | Koto |
+ | 108 | Kalimba |
+ | 109 | Bag pipe |
+ | 110 | Fiddle |
+ | 111 | Shanai |
  
  Percussive
  
- 112 Tinkle Bell
- 113 Agogo
- 114 Steel Drums
- 115 Woodblock
- 116 Taiko Drum
- 117 Melodic Tom
- 118 Synth Drum
- 119 Reverse Cymbal
+ | 112 | Tinkle Bell |
+ | 113 | Agogo |
+ | 114 | Steel Drums |
+ | 115 | Woodblock |
+ | 116 | Taiko Drum |
+ | 117 | Melodic Tom |
+ | 118 | Synth Drum |
+ | 119 | Reverse Cymbal |
  
  Sound Effects
  
- 120 Guitar Fret Noise
- 121 Breath Noise
- 122 Seashore
- 123 Bird Tweet
- 124 Telephone Ring
- 125 Helicopter
- 126 Applause
- 127 Gunshot
+ | 120 | Guitar Fret Noise |
+ | 121 | Breath Noise |
+ | 122 | Seashore |
+ | 123 | Bird Tweet |
+ | 124 | Telephone Ring |
+ | 125 | Helicopter |
+ | 126 | Applause |
+ | 127 | Gunshot |
  
  ====== Legal ======
  
  "Roland" and "GS" are the property of the Roland Corporation. "Yamaha" and "XG" are the property of the Yamaha Corporation. "General MIDI" and GM are the property of the MIDI Manufacturers Association. "Cakewalk" is the property of Twelve Tone Systems, Inc. "Logic" is the property of Emagic Soft- und Hardware GmbH. "Windows" is the property of Microsoft.  Apologies to any others I have failed to credit for their property.
  


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36
IP Address          : 69.255.11.108
Hostname            : 69.255.11.108
Old Revision        : https://www.rosegardenmusic.com/wiki/dev:device_files?rev=1771557567
New Revision        : https://www.rosegardenmusic.com/wiki/dev:device_files
Date of New Revision: 2026/02/23 18:48
Edit Summary        : [Controls Tags] 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -33,9 +33,9 @@
  The ''<program>'' tags define the program changes (sounds) within a bank.
  
  ==== Controls Tags ====
  
- ''<controls>'' tags define the controllers that the device honors.  From GM.rgd:
+ ''<controls>'' tags define the controllers that the device honors.  Here's a basic set to start with:
  
  <code xml>
  <controls>
      <control name="Pan" type="controller" description="&lt;none&gt;"
@@ -55,8 +55,14 @@
               colourindex="4" ipbposition="-1" />
      <control name="PitchBend" type="pitchbend" description="&lt;none&gt;"
               min="0" max="16383" default="8192" controllervalue="1"
               colourindex="4" ipbposition="-1" />
+     <control name="Expression" type="controller" description="&lt;none&gt;"
+              min="0" max="127" default="127" controllervalue="11"
+              colourindex="2" ipbposition="-1"/>
+     <control name="Sustain" type="controller" description="&lt;none&gt;"
+              min="0" max="127" default="0" controllervalue="64"
+              colourindex="4" ipbposition="-1"/>
  </controls>
  </code>
  
  The ''<control>'' tags define each controller.  The above set of six controllers will be in almost every .rgd file and should appear as above.


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36
IP Address          : 73.132.202.108
Hostname            : 73.132.202.108
Old Revision        : https://www.rosegardenmusic.com/wiki/dev:device_files?rev=1737491563
New Revision        : https://www.rosegardenmusic.com/wiki/dev:device_files
Date of New Revision: 2026/02/20 03:19
Edit Summary        : [Checklist] 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -191,8 +191,9 @@
    * Make sure the ''<librarian>'' tag has your name and contact info.
    * Remove any ''<metronome>'' tags.
    * Remove any ''<instrument> ... </instrument>'' tags.
    * Make sure the Expression control's default="127".
+   * Make sure the Volume control's default="100".
    * Make sure the ''<device>'' tag's name is set to the name of the synth.
    * Make sure the ''<device>'' tag's connection="".
    * Sanity check importing the .rgd file and make sure everything is there.
  


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36
IP Address          : 73.132.202.108
Hostname            : 73.132.202.108
Old Revision        : https://www.rosegardenmusic.com/wiki/dev:development?rev=1771555913
New Revision        : https://www.rosegardenmusic.com/wiki/dev:development
Date of New Revision: 2026/02/20 02:55
Edit Summary        : 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -92,15 +92,15 @@
    * [[Overall code structure]]
    * [[dev:creating_events.txt|Creating Events and their properties]]
    * [[dev:how_a_note_becomes_a_sound|How a note becomes a sound]]
    * [[dev:units.txt|Pitch and time units for Events]]
-   * [[http://rosegarden.svn.sourceforge.net/viewvc/rosegarden/trunk/docs/code/iterators.txt?view=markup|Iterating over Events in segments and compositions]] (Need to rescue from svn.  See NOTE above.)
+   * [[https://sourceforge.net/p/rosegarden/code/HEAD/tree/branches/obsolete/docs/code/iterators.txt|Iterating over Events in segments and compositions]] (Need to rescue from svn.  See NOTE above.)
    * [[dev:xml_format| XML format]]
  ====Notation====
  
-   * [[http://rosegarden.svn.sourceforge.net/viewvc/rosegarden/trunk/docs/data_struct/tuplets.txt?view=markup|Triplet/tuplet event storage properties]] (Need to rescue from svn.  See NOTE above.)
-   * [[http://rosegarden.svn.sourceforge.net/viewvc/rosegarden/trunk/docs/data_struct/sets.txt?view=markup|Notation event grouping terminology]] (Need to rescue from svn.  See NOTE above.)
-   * [[http://rosegarden.svn.sourceforge.net/viewvc/rosegarden/trunk/docs/code/notation_layout.txt?view=markup|Notation layout procedure]] (Need to rescue from svn.  See NOTE above.)
+   * [[https://sourceforge.net/p/rosegarden/code/HEAD/tree/branches/obsolete/docs/data_struct/tuplets.txt|Triplet/tuplet event storage properties]] (Need to rescue from svn.  See NOTE above.)
+   * [[https://sourceforge.net/p/rosegarden/code/HEAD/tree/branches/obsolete/docs/data_struct/sets.txt|Notation event grouping terminology]] (Need to rescue from svn.  See NOTE above.)
+   * [[https://sourceforge.net/p/rosegarden/code/HEAD/tree/branches/obsolete/docs/code/notation_layout.txt|Notation layout procedure]] (Need to rescue from svn.  See NOTE above.)
  
  ====Sequencer====
  
    * [[Recording from multiple MIDI ports]] (but not onto multiple tracks simultaneously - this document predates that work) (was branches/obsolete/docs/code/multiport_recording.txt)


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36
IP Address          : 73.132.202.108
Hostname            : 73.132.202.108
Old Revision        : https://www.rosegardenmusic.com/wiki/dev:development?rev=1683403545
New Revision        : https://www.rosegardenmusic.com/wiki/dev:development
Date of New Revision: 2026/02/20 02:51
Edit Summary        : [Documents in Subversion] 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -80,13 +80,13 @@
    * [[Making strings translatable]]
  
  =====Documents in Subversion=====
  
- There are several plain-text documents found in the Rosegarden source code repository ([[http://rosegarden.svn.sourceforge.net/viewvc/rosegarden/trunk/docs/|browse]]).
+ https://sourceforge.net/p/rosegarden/code/HEAD/tree/branches/obsolete/docs/
  
- These ones are either vaguely interesting, or at least not hopelessly out of date:
+ There are several plain-text documents found in the old Rosegarden svn repository.
  
- **NOTE I didn't realize this page simply linked to SVN.  These documents are no longer available.  We should just move them into the wiki and update them as we go, but I am not going to finish that anytime soon.  The documents that have not yet been rescued can be found in http://rosegarden.svn.sourceforge.net/viewvc/rosegarden/branches/obsolete/docs/ **
+ These ones are either vaguely interesting, or at least not hopelessly out of date:
  
  ====Basics====
  
    * [[Overall code structure]]


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36
IP Address          : 73.132.202.108
Hostname            : 73.132.202.108
Old Revision        : https://www.rosegardenmusic.com/wiki/dev:release_process?rev=1768423491
New Revision        : https://www.rosegardenmusic.com/wiki/dev:release_process
Date of New Revision: 2026/02/18 19:38
Edit Summary        : [Deliver] 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -204,19 +204,27 @@
  ==== Deliver ====
  
  SourceForge
  
-   - Create new version directory on sf
-   - Upload the tarball to sf
-   - Upload the current version section of the CHANGELOG to sf as README.
-   - Update sourceforge to point to the new version.  Use the "i" icon to the right of the file.  Set "Default Download For:" to Tux.
+   * https://sourceforge.net/projects/rosegarden/files/rosegarden/
+   * Create new version directory on sf
+   * Upload the tarball to sf
+   * Upload the current version section of the CHANGELOG to sf as README.
+   * Update sourceforge to point to the new version.  Use the "i" icon to the right of the file.  Set "Default Download For:" to Tux.
  
  GitHub
  
-   * Create a release.
-   * Click on Releases in the right column.
-   * Click on "Draft New Release".
-   * README will need to be copied to the description field and reformatted to markdown.
+   * https://github.com/tedfelix/rosegarden-official/releases
+   * Click on "Draft a new release".
+   * Current version section of the CHANGELOG will need to be copied to the description field and reformatted to markdown.
+ 
+ CodeBerg
+ 
+   * https://codeberg.org/rosegarden/rosegarden/releases
+   * Click on the New Release button.
+   * Specify an existing tag name.
+   * Release title: Rosegarden xx.xx
+   * Copy markdown description from github.
  
  ==== Update Website ====
  
  Update the website to point to the new version.  The website can be updated by committing changes to the website directory in svn.  These are automatically uploaded to the web server.  The webpages use Server Side Includes (SSI), so you'll need to set up a web server to test before uploading changes.


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36
IP Address          : 73.132.202.108
Hostname            : 73.132.202.108
Old Revision        : https://www.rosegardenmusic.com/wiki/start?rev=1770738633
New Revision        : https://www.rosegardenmusic.com/wiki/start
Date of New Revision: 2026/02/18 05:42
Edit Summary        : [Rosegarden Wiki] 
User                : tedfelix

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -3,9 +3,10 @@
  This is the Wiki for the Rosegarden MIDI sequencer.  Useful links:
  
    * https://sourceforge.net/projects/rosegarden/ - Main downloads and support.
    * http://www.rosegardenmusic.com/ - Website with various info.
-   * https://github.com/tedfelix/rosegarden-official - Secondary source code and support.
+   * https://codeberg.org/rosegarden/rosegarden - Alternate source code and support.
+   * https://github.com/tedfelix/rosegarden-official - Alternate source code and support.
  
  If you wish to add any new documentation or update anything in here, please contact us on the [[https://sourceforge.net/projects/rosegarden/lists/rosegarden-devel|dev mailing list]] to request access.
  
  //Note that developer pages are in the "dev:" namespace, formal project documentation is in the "doc:" namespace, and pages for translators are in the "translator:" namespace.  General user pages do not have any particular namespace; call them whatever you like.//


-- 
This mail was generated by DokuWiki at
https://www.rosegardenmusic.com/wiki/