https://rosegardenmusic.com/wiki/ 2026-11-14T00:53:46+00:00 https://rosegardenmusic.com/wiki/ https://rosegardenmusic.com/wiki/_media/wiki:dokuwiki.svg text/html 2026-11-12T21:57:20+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/1.8.0?rev=1794520640&do=diff Planned * Implemented New Features * Blah (Billy-Ray, since rev xxxx) Significant Bug Fixes * Blah (Billy-Ray, since rev xxxx) New Members We'd like to thank the following for their continuing quality contributions, and welcome them to the Rosegarden team! text/html 2026-11-10T17:19:39+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/branching?rev=1794331179&do=diff If you would like to play in developing something new, which may potentially break the software, create a new branch to play with. 1 Creating a new branch Create a new branch by copying the trunk. For example, for a branch called my_branch, do the following (as a single one-line command): text/html 2026-11-10T14:42:42+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/2.0?rev=1794321762&do=diff Planned * Port to QT4 or QT4/KDE4 Implemented New Features * Blah (Billy-Ray, since rev xxxx) Significant Bug Fixes * Blah (Billy-Ray, since rev xxxx) New Members We'd like to thank the following for their continuing quality contributions, and welcome them to the Rosegarden team! text/html 2026-11-09T00:53:21+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/1.6.0?rev=1794185601&do=diff Aim To release Rosegarden 1.6.0 by end of September 2007 - Failed! To release Rosegarden 1.6.0 by end of October 2007- Released 1.6.0-pre1 (string freeze) in November 2, 2007! New aim: To release Rosegarden 1.6.0 few weeks after that ... Finally succeeded! text/html 2026-11-07T05:18:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/overall_code_structure?rev=1794028693&do=diff Rosegarden is split into 3 main parts: Base The base library holds all of the fundamental “music handling” structures, of which the primary ones are Event, Segment, Track, Instrument and Composition. It also contains a selection of utility and helper classes of a kind that is not specific to any particular GUI. Everything here is part of the Rosegarden namespace, and there are no dependencies on KDE or Qt (although it uses the STL heavily). text/html 2026-11-06T20:12:12+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/first_impressions_and_how_to_improve_them?rev=1793995932&do=diff How does Rosegarden appear when first installed and run on a new Linux distribution? I've been so used to fixing problems “in the distribution” with Studio to Go that I no longer really remember what the normal first time user experience on a non-audio-focused distribution is like. However, I do remember that it used to be pretty lousy; that's one reason STG exists in the first place. So, I downloaded Ubuntu 7.10 and gave it a try. (I just used Ubuntu because it's popular and it isn't KDE-based… text/html 2026-11-06T16:04:14+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/eclipsecdt?rev=1793981054&do=diff Eclipse has been a popular IDE for Java developers for a long time, but it also provides an excellent environment for other languages. CDT is the Eclipse IDE for C/C++ developers. This document is a quick tutorial to set up a working development environment for Rosegarden using Eclipse CDT on Linux. text/html 2026-11-05T16:19:48+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/a_new_page?rev=1793895588&do=diff A further test. text/html 2026-11-05T11:30:20+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/unittesting?rev=1793878220&do=diff Unit tests are useful to call code in isolation during development (so you don't need to start the entire GUI to test every change), and for regression tests. A couple of unit tests for Rosegarden have been written in src/test. Building Enable WANT_TEST in ccmake and build the codebase as usual text/html 2026-11-05T06:24:22+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/making_a_noise_by_default?rev=1793859862&do=diff Making a noise by default The most common source of problems for new users of Rosegarden is still a straightforward inability to get any sound out of it. There are two parts to this problem, plus a third related problem: * “Notes” in Rosegarden are MIDI only by default and are not synthesised within the program, so the user needs to run a separate synth or load a plugin and use it explicitly. * To make use of a plugin, or anything else that involves RG actually making the sound, JACK ne… text/html 2026-11-04T16:53:54+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/notes_on_porting_to_qt4?rev=1793811234&do=diff Structuring the work Four sorts of work here: * Preliminary or refactoring work that does not depend on any major Qt4 conversion slog (but that some Qt4 conversion slog may depend on). For example, making the sequencer a thread rather than a process (if we did that). * Major Qt4 conversion slog that can be scripted. * Major Qt4 conversion slog that can't be scripted (dull manual tasks). * The “rewrite bits” -- work that takes serious thought and depends on already having a Qt4 backb… text/html 2026-11-04T13:37:42+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/keeping_gui_elements_updated?rev=1793799462&do=diff Mail archive link Keeping GUI elements updated, e.g. notifying the NotationView if a segment has changed, is done through the RefreshStatus class. This class holds a set of 'observer IDs'. Every Segment carries a RefreshStatus, and every edit part displaying one has an observer ID. Whenever a change is made in a segment, its RefreshStatus is set to 'has changed' for all observer IDs. Then each observer, whenever it's refreshed, checks its status ID to see if the segment it displays has chan… text/html 2026-11-04T03:49:57+00:00 tedfelix (tedfelix@undisclosed.example.com) https://rosegardenmusic.com/wiki/dev:26.12?rev=1793764197&do=diff ROSEGARDEN 26.12 RELEASED The Rosegarden team is proud to announce the release of version 26.12 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 text/html 2026-11-04T03:47:27+00:00 tedfelix (tedfelix@undisclosed.example.com) https://rosegardenmusic.com/wiki/start?rev=1793764047&do=diff Rosegarden Wiki 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://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… text/html 2026-11-04T03:18:54+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/add_or_update_translation?rev=1793762334&do=diff This page is about translating Rosegarden to your language. For developers, there is also page Making strings translatable. This is the current state of translations (see date below) : branches/stable_1_7/po$ bash ../scripts/po-stats Translation status report for Rosegarden project rosegarden.pot has 2322 messages Lang Total Done Fuzzy Pending Status ---- ----- ---- ----- ------- ------ es 2322 2322 0 0 [+++++] fr 2322 2322 0 0 [+++++] it 2322 2322… text/html 2026-11-04T03:08:46+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/notation_editor_improvement_thoughts?rev=1793761726&do=diff Notation editor improvement thoughts This page started out as Bug #1310257 - Notation editor has limitations and may confuse. See also Notation layout, staff types etc - excerpts from another discussion about notation editor reworking. See also Score layout, not just notation layout. text/html 2026-11-04T02:08:40+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/score_layout_not_just_notation_layout?rev=1793758120&do=diff Score layout, not just notation layout Text initially excerpted from RFE #1559811 - more staff grouping options. See also Notation editor improvement thoughts. See also Notation layout, staff types etc. CC: We don't have any staff groupings natively in Rosegarden. The main reason for this is not that the brackets or whatever are hard to represent internally or to draw, but that I failed to come up with a good way for the user to describe what groupings they wanted in the first place. text/html 2026-11-03T09:21:10+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/contributing?rev=1793697670&do=diff There are numerous ways to contribute into Rosegarden. You may * Create a patch (described in this page) * Report a bug * Create a feature request * Add or update translation * Discuss in Rosegarden's mailing lists * Update documentation text/html 2026-11-02T15:02:56+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/development?rev=1793631776&do=diff A place to gather miscellaneous development notes. * See also: HOWTO contribute * See also: Doxygen code documentation * See also: Eclipse/CDT with Rosegarden * See also: UnitTesting Explanatory Snippets These are short explanations that have come up on the Rosegarden developers' mailing list at one time or another, sometimes with a bit more detail added in the wiki. text/html 2026-11-01T21:56:29+00:00 Anonymous (anonymous@undisclosed.example.com) https://rosegardenmusic.com/wiki/preferences_restructuring?rev=1793570189&do=diff Which options are too obvious; which are not obvious enough; which are about right? Key: Too obvious, not obvious enough, about right General/Presentation This is one of the worst config tabs, and it's the first one you see! * Note name style (definitely)