rosegarden-user Mailing List for Rosegarden

Well done! Thanks everyone :-)

Lorenzo

On 03/06/2026 14:57, Ted Felix wrote:
> 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]
>   * 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]
>   * 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]
>
>
>
> _______________________________________________
> Rosegarden-user mailing list
> Ros...@li... - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user

Congrats and thanks to all developers and contributors.

I notice that RG is not currently accepting donations.

I wonder why that is. I often give smallish amounts to

similar O/S projects...

Chuck.


On 03/06/2026 13:57, Ted Felix wrote:
> 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]
>   * 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]
>   * 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]
>
>
>
> _______________________________________________
> Rosegarden-user mailing list
> Ros...@li... - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user

Congrats and thanks to all developers and contributors.

I notice that RG is not currently accepting donations.

I wonder why that is. I often give smallish amounts to

similar O/S projects...

Chuck.


On 03/06/2026 13:57, Ted Felix wrote:
> 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]
>   * 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]
>   * 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]
>
>
>
> _______________________________________________
> Rosegarden-user mailing list
> Ros...@li... - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user

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]
   * 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]
   * 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]

   Strange behavior like this feels like you need to do a full rebuild. 
Delete your build directory, make a new one, run cmake again and try a 
fresh build.  I've been having weird problems a lot lately.  Not sure 
what they changed in the compiler and/or linker.

   Let us know if that doesn't solve it.

Ted.

On 5/13/26 12:44 PM, chuck elliot wrote:
> I am getting strange behaviour of the draw cursor when editing a segment
> 
> in the matrix editor. The cursor seems to be trying to create notes without
> 
> mouse buttons being pressed and some notes that result can't be deleted.
> 
> A 'ghost' note or a 'real' one is being generated and extended at the 
> cursor tip as I move
> 
> it around. ESC stops this but an undeletable note is created.
> 
> This is a new build of 26.06 from github. I have replicated in Debian 
> and Fedora
> 
> systems. Problem is absent in 24.12 working on same .rg file.
> 
> It's not obviously related to any new features or bug fixes.
> 
> Chuck.
> 
> 
> 
> On 06/05/2026 15:53, Ted Felix wrote:
>> Rosegarden 26.06 will be released on June 3.  Please test the latest 
>> version in git as much as possible.  See the release notes for areas 
>> that need testing:
>>
>> https://www.rosegardenmusic.com/wiki/dev:26.06
>>
>>   Let me know if you have any questions about the release notes and I 
>> will elaborate.
>>
>>   If you've not built Rosegarden before, give it a shot and let us 
>> know if you run into trouble.  We'll walk you through it.  The 
>> instructions on the wiki should help you through the build process:
>>
>> https://www.rosegardenmusic.com/wiki/dev:building_rosegarden_from_source
>>
>>   To help out with testing 26.06 you can either download a source 
>> snapshot, or use git to stay up to date with the latest.
>>
>> Thanks.
>> Ted.
>>
>>
>>
>> _______________________________________________
>> Rosegarden-user mailing list
>> Ros...@li... - use the link below to unsubscribe
>> https://lists.sourceforge.net/lists/listinfo/rosegarden-user
> 
> 
> _______________________________________________
> Rosegarden-user mailing list
> Ros...@li... - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user

Not really important , just a 'cosmetic' mismatch with the sound nr you select , and the sound nr shown on the midi-device.



________________________________
Van: Ted Felix <te...@te...>
Verzonden: zondag 24 mei 2026 16:52
Aan: ros...@li... <ros...@li...>
Onderwerp: Re: [Rosegarden-user] Can the instrument nr under instrument parameters be changed to start from 0

On 5/23/26 5:26 PM, eddy mulder wrote:
> I have a instrument defined with multiple banks ..
> Each bank has 100 registrations...
> So bank 1 is 100-199 , In the instrument definition you can click on the
> nr , and then numbering starts with 0 which is then logical if you want
> to select sound 100 (so bank 1 intrument 00).
> When back at the sequencer windows and select the newly defined
> instrument and look at the instrument parameters .the 1st program nr is
> then 1 can this be changed the numbering starts with 0 ?
   Rosegarden does not offer such a feature, and I can see that this
ends up being confusing.  The convention in MIDI is that Program Change
#1 (to the user) is actually Program Change #0 to the hardware.

   If the program number is really important, include it in the name.
It will look odd, but at least it will clear up the confusion.

Ted.



_______________________________________________
Rosegarden-user mailing list
Ros...@li... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user

On 5/23/26 5:26 PM, eddy mulder wrote:
> I have a instrument defined with multiple banks ..
> Each bank has 100 registrations...
> So bank 1 is 100-199 , In the instrument definition you can click on the 
> nr , and then numbering starts with 0 which is then logical if you want 
> to select sound 100 (so bank 1 intrument 00).
> When back at the sequencer windows and select the newly defined 
> instrument and look at the instrument parameters .the 1st program nr is 
> then 1 can this be changed the numbering starts with 0 ?
   Rosegarden does not offer such a feature, and I can see that this 
ends up being confusing.  The convention in MIDI is that Program Change 
#1 (to the user) is actually Program Change #0 to the hardware.

   If the program number is really important, include it in the name. 
It will look odd, but at least it will clear up the confusion.

Ted.

I have a instrument defined with multiple banks ..
Each bank has 100 registrations...
So bank 1 is 100-199 , In the instrument definition you can click on the nr , and then numbering starts with 0 which is then logical if you want to select sound 100 (so bank 1 intrument 00).
When back at the sequencer windows and select the newly defined instrument and look at the instrument parameters .the 1st program nr is then 1 can this be changed the numbering starts with 0 ?


Regards

Eddy

   String freeze for 26.06 begins today and lasts for two weeks.  Please 
submit translations by Tuesday, 2 June 2026.  Rosegarden 26.06 is 
scheduled for Wednesday, 3 June 2026.

   .ts files have been updated against the latest code.  Get the latest 
from git and start translating.

https://www.rosegardenmusic.com/wiki/dev:building_rosegarden_from_source

   Be sure to use Qt5 when working on translations:

     $ QT_SELECT=qt5 linguist

   If you don't have a fork, you can send .ts files directly to me, or 
post to the patches tracker.

https://sourceforge.net/p/rosegarden/patches/

   Compressed with gzip or xz would be very much appreciated.  Diffs are 
even better.

Thanks.
Ted.

Hi Philip!
Thank you for asking and offering help, I am sure some libraries are missing, so probably no big problem here.
At the moment I don't have the time to solve, but the upcoming translation is due to arrive :-)

Greetings, Michael


> Gesendet: Donnerstag, 14. Mai 2026 um 12:36
> Von: "Philip Leishman via Rosegarden-user" <ros...@li...>
> An: ros...@li...
> Betreff: Re: [Rosegarden-user] Rosegarden in distros?
>
> I have a virtual machine with Trixie. I had no problem compiling with Qt6,
> 
> Can you be more specific about the errors ?
> 
>  &nbsp; Philip
> 
> On 14/05/2026 12:06, MST via Rosegarden-user wrote:
> &gt; Hello everyone!
> &gt;
> &gt; I tried to compile the latest code for the upcoming german translation in Debian 13 with qt6. I was not able to compile RG in Debian 13 because of several qt6 error messages. Trying to adept the code, I finally gave up and reinstalled Debian 12 with qt5 to prepare for the translation. Time will show.
> &gt;
> &gt; Greetings, Michael
> &gt;
> &gt;
> &gt;&gt; Gesendet: Mittwoch, 13. Mai 2026 um 19:20
> &gt;&gt; Von: "Will Godfrey" <wil...@mu...>
> &gt;&gt; An: ros...@li...
> &gt;&gt; Betreff: [Rosegarden-user] Rosegarden in distros?
> &gt;&gt;
> &gt;&gt; I nearly allways have issues with QT when trying to compile Rosegarden, and
> &gt;&gt; notice it doesn't seem to appear on any of the debian-based distros.
> &gt;&gt;
> &gt;&gt; Is there a particular reason for that? We might get more users if it appeared
> &gt;&gt; on their distros.
> &gt;&gt;
> &gt;&gt; -- 
> &gt;&gt; Will J Godfrey
> &gt;&gt; {apparently no longer an 'elderly', now a 'senior'. Is that promotion?}
> &gt;&gt; https://willgodfrey.bandcamp.com/
> &gt;&gt; http://yoshimi.github.io
> &gt;&gt; Say you have a poem and I have a tune.
> &gt;&gt; Exchange them and we can both have a poem, a tune, and a song.
> &gt;&gt;
> &gt;&gt;
> &gt;&gt;
> &gt;&gt; _______________________________________________
> &gt;&gt; Rosegarden-user mailing list
> &gt;&gt; Ros...@li... - use the link below to unsubscribe
> &gt;&gt; https://lists.sourceforge.net/lists/listinfo/rosegarden-user
> &gt;
> &gt; _______________________________________________
> &gt; Rosegarden-user mailing list
> &gt; Ros...@li... - use the link below to unsubscribe
> &gt; https://lists.sourceforge.net/lists/listinfo/rosegarden-user
> 
> 
> 
> _______________________________________________
> Rosegarden-user mailing list
> Ros...@li... - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user</wil...@mu...>

Le Fri, 15 May 2026 10:43:45 -0700,
Mike Witt <ms...@gm...> a écrit :

> Does anyone here know of a way to scan sheet music, or read an
> existing PDF file, and get it into LilyPond?

You can try Audiveris then Rosegarden:

.pdf -> [Audiveris] -> .mxl -> [unzip] -> .xml -> [Rosegarden] -> .ly

Does anyone here know of a way to scan sheet music, or read an existing  
PDF file, and get it into LilyPond?

I have a virtual machine with Trixie. I had no problem compiling with Qt6,

Can you be more specific about the errors ?

   Philip

On 14/05/2026 12:06, MST via Rosegarden-user wrote:
> Hello everyone!
>
> I tried to compile the latest code for the upcoming german translation in Debian 13 with qt6. I was not able to compile RG in Debian 13 because of several qt6 error messages. Trying to adept the code, I finally gave up and reinstalled Debian 12 with qt5 to prepare for the translation. Time will show.
>
> Greetings, Michael
>
>
>> Gesendet: Mittwoch, 13. Mai 2026 um 19:20
>> Von: "Will Godfrey" <wil...@mu...>
>> An: ros...@li...
>> Betreff: [Rosegarden-user] Rosegarden in distros?
>>
>> I nearly allways have issues with QT when trying to compile Rosegarden, and
>> notice it doesn't seem to appear on any of the debian-based distros.
>>
>> Is there a particular reason for that? We might get more users if it appeared
>> on their distros.
>>
>> -- 
>> Will J Godfrey
>> {apparently no longer an 'elderly', now a 'senior'. Is that promotion?}
>> https://willgodfrey.bandcamp.com/
>> http://yoshimi.github.io
>> Say you have a poem and I have a tune.
>> Exchange them and we can both have a poem, a tune, and a song.
>>
>>
>>
>> _______________________________________________
>> Rosegarden-user mailing list
>> Ros...@li... - use the link below to unsubscribe
>> https://lists.sourceforge.net/lists/listinfo/rosegarden-user
>
> _______________________________________________
> Rosegarden-user mailing list
> Ros...@li... - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user

Hello everyone!

I tried to compile the latest code for the upcoming german translation in Debian 13 with qt6. I was not able to compile RG in Debian 13 because of several qt6 error messages. Trying to adept the code, I finally gave up and reinstalled Debian 12 with qt5 to prepare for the translation. Time will show.

Greetings, Michael


> Gesendet: Mittwoch, 13. Mai 2026 um 19:20
> Von: "Will Godfrey" <wil...@mu...>
> An: ros...@li...
> Betreff: [Rosegarden-user] Rosegarden in distros?
>
> I nearly allways have issues with QT when trying to compile Rosegarden, and
> notice it doesn't seem to appear on any of the debian-based distros.
> 
> Is there a particular reason for that? We might get more users if it appeared
> on their distros.
> 
> -- 
> Will J Godfrey
> {apparently no longer an 'elderly', now a 'senior'. Is that promotion?}
> https://willgodfrey.bandcamp.com/
> http://yoshimi.github.io
> Say you have a poem and I have a tune.
> Exchange them and we can both have a poem, a tune, and a song.
> 
> 
> 
> _______________________________________________
> Rosegarden-user mailing list
> Ros...@li... - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user

Most pro audio oriented Ubuntu users will probably opt for UbuntuStudio
which does include RG. UbuntuStudio is available as its own install media
or as a meta package to add on to vanilla Ubuntu.

https://wiki.ubuntu.com/UbuntuStudio/PackageList

Sequencing

   - rosegarden - music editor and MIDI/audio sequencer


In bog standard Ubuntu, RG is not in the main repo, but is available via
the universe repo. Less than optimal exposure.

https://packages.ubuntu.com/search?keywords=rosegarden&searchon=names&suite=resolute&section=all
Package rosegarden

   - resolute (26.04LTS) <https://packages.ubuntu.com/resolute/rosegarden>
   (sound): music editor and MIDI/audio sequencer [*universe*]
   1:25.12-2: amd64 arm64 armhf ppc64el riscv64 s390x


Most of the QT grief when building RG on Ubuntu has to do with non-standard
locations for the QT libs. Haven't built it there for a while, so the
details have gone a bit hazy on me.
Presumably, the make files could be configured to look for the QT files in
the appropriate location when building in Ubuntu. Not sure if this has been
done already. Mostly just building it in arch linux in recent years and
this is not an issue.


On Wed, May 13, 2026 at 11:44 AM Thorsten Alteholz <ros...@al...>
wrote:

> Hi Will,
>
> On 13.05.26 19:20, Will Godfrey wrote:
> > I nearly allways have issues with QT when trying to compile Rosegarden,
> and
> > notice it doesn't seem to appear on any of the debian-based distros.
> >
> > Is there a particular reason for that? We might get more users if it
> appeared
> > on their distros.
>
> at least [1] exists. Probably not always the latest version ...
>
>     Thorsten
>
> [1] https://tracker.debian.org/pkg/rosegarden
>
>
>
> _______________________________________________
> Rosegarden-user mailing list
> Ros...@li... - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user
>

Hi Will,

On 13.05.26 19:20, Will Godfrey wrote:
> I nearly allways have issues with QT when trying to compile Rosegarden, and
> notice it doesn't seem to appear on any of the debian-based distros.
>
> Is there a particular reason for that? We might get more users if it appeared
> on their distros.

at least [1] exists. Probably not always the latest version ...

    Thorsten

[1] https://tracker.debian.org/pkg/rosegarden

Hi Will,

it's available in RPiOS/Raspbian versions of Debian.

I don't know about Ubuntu etc...

chuck@dipper:~ $ apt list rosegarden
rosegarden/stable,now 1:24.12.1-1 arm64 [installed]
rosegarden/stable 1:24.12.1-1 armhf

Regards,

Chuck



On 13/05/2026 18:20, Will Godfrey wrote:
> I nearly allways have issues with QT when trying to compile Rosegarden, and
> notice it doesn't seem to appear on any of the debian-based distros.
>
> Is there a particular reason for that? We might get more users if it appeared
> on their distros.
>

I nearly allways have issues with QT when trying to compile Rosegarden, and
notice it doesn't seem to appear on any of the debian-based distros.

Is there a particular reason for that? We might get more users if it appeared
on their distros.

-- 
Will J Godfrey
{apparently no longer an 'elderly', now a 'senior'. Is that promotion?}
https://willgodfrey.bandcamp.com/
http://yoshimi.github.io
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.

I am getting strange behaviour of the draw cursor when editing a segment

in the matrix editor. The cursor seems to be trying to create notes without

mouse buttons being pressed and some notes that result can't be deleted.

A 'ghost' note or a 'real' one is being generated and extended at the 
cursor tip as I move

it around. ESC stops this but an undeletable note is created.

This is a new build of 26.06 from github. I have replicated in Debian 
and Fedora

systems. Problem is absent in 24.12 working on same .rg file.

It's not obviously related to any new features or bug fixes.

Chuck.



On 06/05/2026 15:53, Ted Felix wrote:
> Rosegarden 26.06 will be released on June 3.  Please test the latest 
> version in git as much as possible.  See the release notes for areas 
> that need testing:
>
> https://www.rosegardenmusic.com/wiki/dev:26.06
>
>   Let me know if you have any questions about the release notes and I 
> will elaborate.
>
>   If you've not built Rosegarden before, give it a shot and let us 
> know if you run into trouble.  We'll walk you through it.  The 
> instructions on the wiki should help you through the build process:
>
> https://www.rosegardenmusic.com/wiki/dev:building_rosegarden_from_source
>
>   To help out with testing 26.06 you can either download a source 
> snapshot, or use git to stay up to date with the latest.
>
> Thanks.
> Ted.
>
>
>
> _______________________________________________
> Rosegarden-user mailing list
> Ros...@li... - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user

   Rosegarden 26.06 will be released on June 3.  Please test the latest 
version in git as much as possible.  See the release notes for areas 
that need testing:

https://www.rosegardenmusic.com/wiki/dev:26.06

   Let me know if you have any questions about the release notes and I 
will elaborate.

   If you've not built Rosegarden before, give it a shot and let us know 
if you run into trouble.  We'll walk you through it.  The instructions 
on the wiki should help you through the build process:

https://www.rosegardenmusic.com/wiki/dev:building_rosegarden_from_source

   To help out with testing 26.06 you can either download a source 
snapshot, or use git to stay up to date with the latest.

Thanks.
Ted.

On 4/13/26 12:09 PM, Ted Felix wrote:
> 3. Use autoload.rg.  If your setup doesn't change, you can save it as an 
> autoload.rg file (in ~/.local/share/rosegarden/autoload) and it will 
> come up immediately on rg launch as the default initial composition.
   Hadn't even realized, rg can do this for you: Studio > Save Current 
Document as Default Studio.

Ted.

On 13/04/2026 22:10, chris wrote:
> Ah, now I get the notion, and even what Lorenzo suggested. The idea is 
> to predefine *tracks* for each synth.
> 
> Ok, this surely can be useful if you have just a handful of synths, but 
> in this case we're talking about a couple of dozens (I kid you not). I'd 
> have two or three screen heights full of unused tracks. Of course, I 
> don't need all those synths in every song - but I like to have 
> everything at my disposal, without having to think about ports, 
> connections, and channels.
> 
[...]>
> It's a pity that it is only at track level where channels aka 
> instruments come into play. That's why I initially had the thought of 
> having predefined devices with all channel settings - I wouldn't care if 
> I had a crowded *studio* definition list, since I don't get to see that 
> during working on a song.

What you seem to need is output filtering, which is a feature per se IMHO...
If, as it seems, you don't mind getting your hands greasy with code, you 
could look into Pure data for something like this ;-)

Lorenzo


> 
> 
> regards
> 
> Chris
> 
> 
> On 13/04/2026 18:09, Ted Felix wrote:
>> On 4/11/26 6:11 PM, chris wrote:
>>> What I am looking for is a way to represent this setup in Rosegarden.
>>
>>   Create a Device for each synth.  Connect those devices to the 
>> appropriate MIDI interface.  Then select the appropriate instruments 
>> (channels).  Sounds like you've got that working.
>>
>>> The closest I found are home-grown MIDI devices.
>>> As I can see, I can define MIDI devices with the proper out port - 
>>> but have to use a paper cheat sheet with the correct channel(s) for 
>>> each.
>>
>>   There are three ways to remember your setup.  (Perhaps this is the 
>> "environment" you mentioned?)
>>
>> 1. Once you've got everything configured, save it as an .rg file. 
>> Let's say "studio.rg" for this example.  Then on your next 
>> composition, use Studio > Import Studio From File... and specify 
>> studio.rg.  Now you have your setup (environment?) in your new 
>> composition.
>>
>> 2. Save your composition as a template using File > Save As 
>> Template... Then use File > Open Template... to get to that starting 
>> point.
>>
>> 3. Use autoload.rg.  If your setup doesn't change, you can save it as 
>> an autoload.rg file (in ~/.local/share/rosegarden/autoload) and it 
>> will come up immediately on rg launch as the default initial composition.
>>
>>> Is there a way to limit MIDI device definitions to specific channels 
>>> (sometimes only one, sometimes more, but rarely all 16) ?
>>
>>   No.
>>
>> Ted.
>>
>>
>>
>> _______________________________________________
>> Rosegarden-user mailing list
>> Ros...@li... - use the link below to unsubscribe
>> https://lists.sourceforge.net/lists/listinfo/rosegarden-user
> 
> 
> _______________________________________________
> Rosegarden-user mailing list
> Ros...@li... - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user

On 13/04/2026 18:17, Ted Felix wrote:
> > A quick look at some *.cpp files looked more clear and promising 
> than I expected.
>
>   Looks can definitely be deceiving. 

Just like with women. Oh, I digress...


> There are parts of this code that are completely mind-numbing.  Have a 
> look at MappedBufMetaIterator and see how your opinion shifts. Just 
> the name gives me a headache. 

Ok, the name may be weird. But if you want to write any multi-track 
sequencer - at one point or another you need to collect and combine 
events from all tracks, in order to be played in time.

It actually doesn't look any worse than what I found when beginning my 
last (and final) day-time job. A multi-core microcontroller/DSP project 
with multiple threads and extensive real-time core-to-core 
communication, including ethernet interface to the outside world. And 
almost no internal documentation...

Well, and now I have time for the really important things in life, like 
making music :-)


Chris

Ah, now I get the notion, and even what Lorenzo suggested. The idea is 
to predefine *tracks* for each synth.

Ok, this surely can be useful if you have just a handful of synths, but 
in this case we're talking about a couple of dozens (I kid you not). I'd 
have two or three screen heights full of unused tracks. Of course, I 
don't need all those synths in every song - but I like to have 
everything at my disposal, without having to think about ports, 
connections, and channels.

That approach could even be nice if I could *import* single tracks from 
such a default composition, but alas...


By the way, that's more or less the workflow I used with Logic. I had a 
full-blown studio definition with all synths, but almost no tracks. When 
starting a new song, I would open that default song file, and SaveAs it 
to the new song.

The Logic 'environment' is something like Rosegarden's studio, but 
including channel settings. There can be single channel devices, or 
multi-channel ones, where you can individually define which channels are 
to be used. And it's these device objects that are assigned to a track. 
When selecting a multi-channel device, there is a sub-menu with the 
available channels aka parts (it's obvious that you have to deal 
explicitly with channels in those cases).


It's a pity that it is only at track level where channels aka 
instruments come into play. That's why I initially had the thought of 
having predefined devices with all channel settings - I wouldn't care if 
I had a crowded *studio* definition list, since I don't get to see that 
during working on a song.


regards

Chris


On 13/04/2026 18:09, Ted Felix wrote:
> On 4/11/26 6:11 PM, chris wrote:
>> What I am looking for is a way to represent this setup in Rosegarden.
>
>   Create a Device for each synth.  Connect those devices to the 
> appropriate MIDI interface.  Then select the appropriate instruments 
> (channels).  Sounds like you've got that working.
>
>> The closest I found are home-grown MIDI devices.
>> As I can see, I can define MIDI devices with the proper out port - 
>> but have to use a paper cheat sheet with the correct channel(s) for 
>> each.
>
>   There are three ways to remember your setup.  (Perhaps this is the 
> "environment" you mentioned?)
>
> 1. Once you've got everything configured, save it as an .rg file. 
> Let's say "studio.rg" for this example.  Then on your next 
> composition, use Studio > Import Studio From File... and specify 
> studio.rg.  Now you have your setup (environment?) in your new 
> composition.
>
> 2. Save your composition as a template using File > Save As 
> Template... Then use File > Open Template... to get to that starting 
> point.
>
> 3. Use autoload.rg.  If your setup doesn't change, you can save it as 
> an autoload.rg file (in ~/.local/share/rosegarden/autoload) and it 
> will come up immediately on rg launch as the default initial composition.
>
>> Is there a way to limit MIDI device definitions to specific channels 
>> (sometimes only one, sometimes more, but rarely all 16) ?
>
>   No.
>
> Ted.
>
>
>
> _______________________________________________
> Rosegarden-user mailing list
> Ros...@li... - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user

On Mon, 13 Apr 2026 12:17:22 -0400
Ted Felix <te...@te...> wrote:
>   Looks can definitely be deceiving.  There are parts of this code that 
>are completely mind-numbing.  Have a look at MappedBufMetaIterator and 
>see how your opinion shifts.  Just the name gives me a headache.
>Ted.

Ah yes. The problem with ancient inherited code.
You have my sympathy!

-- 
Will J Godfrey
{apparently no longer an 'elderly', now a 'senior'. Is that promotion?}