rosegarden-devel Mailing List for Rosegarden

   Proposed Schedule for 26.06:

May 6: Feature Freeze, Testing period (4 weeks) begins
May 20: String Freeze, Translation period (2 weeks) begins
June 3: Rosegarden 26.06

Ted.

On Sunday, 22 March 2026 14:02:27 David Faure wrote:
> Actually the bar is exactly correct in total duration, so the red barline check passes.
> 
> The problem is that the bar contains a 20-tick rest that isn't representable in standard notation,
> but the barline check only looks at the total. The red barline is the wrong mechanism for catching this.
> 
> I think the best option would be a warning at the time of doing the export / print preview (LilypondExporter).
> I'll dig in that direction.

Done in https://github.com/tedfelix/rosegarden-official/pull/44
(I assume only Ted gets notified of those?)

-- 
David Faure, fa...@kd..., http://www.davidfaure.fr

On Sunday, 22 March 2026 11:50:04 David Faure wrote:
> On Sunday, 8 March 2026 20:18:45 Yves Guillemot wrote:
> > Le Sun, 08 Mar 2026 18:36:00 +0100,
> > David Faure <fa...@kd...> a écrit :
> > > Should we somehow warn the user if a bar contains more than it should,
> > > which leads to such lilypond issues? Or does lilypond warn and we
> > > don't transfer those warnings to the user? I saw nothing on stderr.
> > 
> > I remember RG sometimes showed a red colored bar when the timing was
> > incorrect.
> > I can't reproduce it today.
> > Is the bar only colored in a few specific cases ?
> > Is this a new bug ? 
> 
> The code is there (StaffLayout.cpp:752-755), it just doesn't trigger in my case. I'll debug why.
> Thanks for the tip.

Actually the bar is exactly correct in total duration, so the red barline check passes.

The problem is that the bar contains a 20-tick rest that isn't representable in standard notation,
but the barline check only looks at the total. The red barline is the wrong mechanism for catching this.

I think the best option would be a warning at the time of doing the export / print preview (LilypondExporter).
I'll dig in that direction.

-- 
David Faure, fa...@kd..., http://www.davidfaure.fr

On Sunday, 8 March 2026 20:18:45 Yves Guillemot wrote:
> Le Sun, 08 Mar 2026 18:36:00 +0100,
> David Faure <fa...@kd...> a écrit :
> > Should we somehow warn the user if a bar contains more than it should,
> > which leads to such lilypond issues? Or does lilypond warn and we
> > don't transfer those warnings to the user? I saw nothing on stderr.
> 
> I remember RG sometimes showed a red colored bar when the timing was
> incorrect.
> I can't reproduce it today.
> Is the bar only colored in a few specific cases ?
> Is this a new bug ? 

The code is there (StaffLayout.cpp:752-755), it just doesn't trigger in my case. I'll debug why.
Thanks for the tip.

> LilyPond warns, but when you use "Print preview..." the LilyPond output
> is hidden.

Should we then pop up a dialog with the warnings?
I volunteer to implement that, if you guys agree with this approach.

I just tested with another rg file of mine and the lilypond export triggered
no warnings, so hopefully we won't get too many false positives. But if it
happens, we can add some builtin filtering on the type of warning.

> To see it, you have to export to LilyPond, then manually run LilyPond on
> the exported file.

Good tip for debugging this currently (thanks!), but that doesn't seem very user-friendly ;-)

-- 
David Faure, fa...@kd..., http://www.davidfaure.fr

Le Sun, 08 Mar 2026 18:36:00 +0100,
David Faure <fa...@kd...> a écrit :
> Should we somehow warn the user if a bar contains more than it should,
> which leads to such lilypond issues? Or does lilypond warn and we
> don't transfer those warnings to the user? I saw nothing on stderr.

I remember RG sometimes showed a red colored bar when the timing was
incorrect.
I can't reproduce it today.
Is the bar only colored in a few specific cases ?
Is this a new bug ? 

LilyPond warns, but when you use "Print preview..." the LilyPond output
is hidden.
To see it, you have to export to LilyPond, then manually run LilyPond on
the exported file.
   
> 
> Here's the reason why the tuplet on these notes got lost:
> there's a bug ;)
> If you select that triplet plus the 8th note that follows
> and press Ctrl+B to beam them together, the "3" disappears.
> This is how the problem happened in the first place.
> 
> Filed as https://sourceforge.net/p/rosegarden/bugs/1773/
> 

I confirm this bug.

On Sunday, 8 March 2026 19:27:19 David Faure wrote:
> shouldn't the TrackEditor be deleted when a document is deleted?

OK found it. It's part of the RosegardenMainwidget, which is deleted via
deleteLater(), i.e. too late.

Fix suggested at https://github.com/tedfelix/rosegarden-official/pull/36

-- 
David Faure, fa...@kd..., http://www.davidfaure.fr

On Sunday, 8 March 2026 17:32:06 Lorenzo Sutton wrote:
> Interestingly with the latest (git build) version of rosegarden that .rg 
> file segfaulted rosegarden here a couple of times then opened OK.

Yep. This is the reason for the crash (according to valgrind) :

==85711== Invalid read of size 8
==85711==    at 0x4ED2863: getFirstVisibleBar (RulerScale.cpp:46)
==85711==    by 0x4ED2863: Rosegarden::SimpleRulerScale::getXForTime(long) const (RulerScale.cpp:239)
==85711==    by 0x4D2A1EC: Rosegarden::TrackEditor::slotSetPointerPosition(long) (TrackEditor.cpp:417)
==85711==    by 0x6F2CFE0: call (qobjectdefs_impl.h:461)
==85711==    by 0x6F2CFE0: void doActivate<false>(QObject*, int, void**) (qobject.cpp:4273)
==85711==    by 0x4A2FD52: activate<void, long int> (qobjectdefs.h:319)
==85711==    by 0x4A2FD52: Rosegarden::CompositionPosition::changed(long) (moc_CompositionPosition.cpp:142)
==85711==    by 0x4D5803C: Rosegarden::CompositionPosition::slotSetDocumentTime() (CompositionPosition.cpp:93)
==85711==    by 0x6F1E9EB: QObject::event(QEvent*) (qobject.cpp:1413)
==85711==    by 0x5976257: QApplicationPrivate::notify_helper(QObject*, QEvent*) (qapplication.cpp:3305)
==85711==    by 0x4D581F8: Rosegarden::RosegardenApplication::notify(QObject*, QEvent*) (RosegardenApplication.cpp:49)
==85711==    by 0x6EC1D47: QCoreApplication::notifyInternal2(QObject*, QEvent*) (qcoreapplication.cpp:1109)
==85711==    by 0x6EC5909: QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (qcoreapplication.cpp:1904)
==85711==    by 0x407EEA: main (main.cpp:727)

==85711==  Address 0x24535ee8 is 472 bytes inside a block of size 1,784 free'd
==85711==    at 0x484C999: operator delete(void*, unsigned long) (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==85711==    by 0x4D8B625: Rosegarden::RosegardenMainWindow::setDocument(Rosegarden::RosegardenDocument*) (RosegardenMainWindow.cpp:1366)
==85711==    by 0x4D8B8BB: Rosegarden::RosegardenMainWindow::openFile(QString const&, Rosegarden::RosegardenMainWindow::ImportType) (RosegardenMainWindow.cpp:1446)
==85711==    by 0x407E39: main (main.cpp:714)

==85711==  Block was alloc'd at
==85711==    at 0x4848F3F: operator new(unsigned long) (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==85711==    by 0x4D78A5D: Rosegarden::RosegardenMainWindow::newDocument(bool, QString const&) (RosegardenMainWindow.cpp:8759)
==85711==    by 0x4D900E8: Rosegarden::RosegardenMainWindow::RosegardenMainWindow(bool, Rosegarden::StartupLogo*) (RosegardenMainWindow.cpp:409)
==85711==    by 0x407D5D: main (main.cpp:695)
 
Decrypted:
* CompositionPosition::documentLoaded does QTimer::singleShot(0, this, &CompositionPosition::slotSetDocumentTime);
* RosegardenMainWindow deletes the document (but not the CompositionPosition or TrackEditor) and creates a new document instead
* When the timer fires, CompositionPosition::slotSetDocumentTime()  ends up calling code in a TrackEditor whose m_doc has been deleted.

Proof using debug output (with comments added at the end):
[RosegardenDocument] RosegardenDocument CTOR this= Rosegarden::RosegardenDocument(0x358537d0) // initial doc
[PluginFactory] enumerateAllPlugins() end.
[TrackEditor] TrackEditor::slotSetPointerPosition( 0 ) this= Rosegarden::TrackEditor(0x35bb9a70) m_doc= 0x358537d0 // OK
[RosegardenDocument] RosegardenDocument CTOR this= Rosegarden::RosegardenDocument(0x35c5cfb0) // new doc
[RosegardenDocument] RosegardenDocument DTOR this= Rosegarden::RosegardenDocument(0x358537d0) // delete the initial doc
[TrackEditor] TrackEditor::slotSetPointerPosition( 15344 ) this= Rosegarden::TrackEditor(0x35bb9a70) m_doc= 0x358537d0 // WE JUST DELETED THAT ONE: LIKELY CRASH
[TrackEditor] TrackEditor::slotSetPointerPosition( 15344 ) this= Rosegarden::TrackEditor(0x35b91780) m_doc= 0x35c5cfb0 // when we're lucky, we keep going with the new doc

Not sure how to fix though.
A singleShot(0) is safe against the recipient being deleted. But here it's not getting deleted, only the document is.
But that seems weird: if a TrackEditor points to a document, and each document ends up creating a TrackEditor (I added debug output about that too),
shouldn't the TrackEditor be deleted when a document is deleted?

-- 
David Faure, fa...@kd..., http://www.davidfaure.fr

Oh, thanks!

Should we somehow warn the user if a bar contains more than it should,
which leads to such lilypond issues? Or does lilypond warn and we don't
transfer those warnings to the user? I saw nothing on stderr.

Here's the reason why the tuplet on these notes got lost:
there's a bug ;)
If you select that triplet plus the 8th note that follows
and press Ctrl+B to beam them together, the "3" disappears.
This is how the problem happened in the first place.

Filed as https://sourceforge.net/p/rosegarden/bugs/1773/

This is the second bug related to triplets I found today :-)
The first one is https://sourceforge.net/p/rosegarden/bugs/1772/

PS: Qt6 build fix at https://github.com/tedfelix/rosegarden-official/pull/33

On Sunday, 8 March 2026 17:41:18 Yves Guillemot wrote:
> It seems there is too much notes in the first bar.
> I presume "D bE D" in the third beat should be a tuplet.
> For some reason these notes have the right durations but are not in a
> tuplet.
> Once this is modified, LilyPond works fine.
> 
> Yves
> 
> 
> Le Sun, 08 Mar 2026 15:32:52 +0100,
> David Faure <fa...@kd...> a écrit :
> 
> > I'm confused. The attached rg file prints on a single line,
> > while other rg files I created long ago print just fine.
> > 
> > Is this a bug, or am I missing a parameter somewhere?
> > 
> > If nobody has any idea I'll investigate further ;)
> > 
> 
> 


-- 
David Faure, fa...@kd..., http://www.davidfaure.fr

It seems there is too much notes in the first bar.
I presume "D bE D" in the third beat should be a tuplet.
For some reason these notes have the right durations but are not in a
tuplet.
Once this is modified, LilyPond works fine.

Yves


Le Sun, 08 Mar 2026 15:32:52 +0100,
David Faure <fa...@kd...> a écrit :

> I'm confused. The attached rg file prints on a single line,
> while other rg files I created long ago print just fine.
> 
> Is this a bug, or am I missing a parameter somewhere?
> 
> If nobody has any idea I'll investigate further ;)
> 

On 08/03/2026 15:32, David Faure wrote:
> I'm confused. The attached rg file prints on a single line,
> while other rg files I created long ago print just fine.
>
> Is this a bug, or am I missing a parameter somewhere?
>
> If nobody has any idea I'll investigate further ;)

Interestingly with the latest (git build) version of rosegarden that .rg 
file segfaulted rosegarden here a couple of times then opened OK.

And yes with various LilyPond versions also produced similar results.

Lorenzo

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

I'm confused. The attached rg file prints on a single line,
while other rg files I created long ago print just fine.

Is this a bug, or am I missing a parameter somewhere?

If nobody has any idea I'll investigate further ;)

-- 
David Faure, fa...@kd..., http://www.davidfaure.fr

Yes, I totally agree with you. This is one of the moments when I realize 
how impossible it is in the GNU/Linux cosmos to satisfy everyone's needs 
and how hard it is for committed programmers.

Greetings, Michael

Am 25.01.26 um 16:04 schrieb Ted Felix:
>   I kind of figured it was something like that since I hadn't seen 
> this issue.  There are so many ways external pieces can make our stuff 
> not work right.  The only way we can keep on top of this stuff is if 
> everyone is testing with different configurations. Thanks for staying 
> on top of this.
>
> Ted.
>
> On 1/24/26 5:07 PM, Babarosa wrote:
>> Hi there!
>>
>> On 6th November i wrote "... Both the MIDI- and Audio-Mixer windows 
>> are not resizable, therefore the rightmost menu entry (Help) in the 
>> MIDI- Mixer is only reachable by clicking the double arrow symbol. "
>>
>> This behavior has gone today by changing my desktop theme from a gtk2 
>> to a gtk3 version :-)
>>
>> Both mixer menus and tracks are fully visible now!
>>
>> Greetings, Michael
>>
>

   I kind of figured it was something like that since I hadn't seen this 
issue.  There are so many ways external pieces can make our stuff not 
work right.  The only way we can keep on top of this stuff is if 
everyone is testing with different configurations.  Thanks for staying 
on top of this.

Ted.

On 1/24/26 5:07 PM, Babarosa wrote:
> Hi there!
> 
> On 6th November i wrote "... Both the MIDI- and Audio-Mixer windows are 
> not resizable, therefore the rightmost menu entry (Help) in the MIDI- 
> Mixer is only reachable by clicking the double arrow symbol. "
> 
> This behavior has gone today by changing my desktop theme from a gtk2 to 
> a gtk3 version :-)
> 
> Both mixer menus and tracks are fully visible now!
> 
> Greetings, Michael
> 

Hi there!

On 6th November i wrote "... Both the MIDI- and Audio-Mixer windows are 
not resizable, therefore the rightmost menu entry (Help) in the 
MIDI-Mixer is only reachable by clicking the double arrow symbol. "

This behavior has gone today by changing my desktop theme from a gtk2 to 
a gtk3 version :-)

Both mixer menus and tracks are fully visible now!

Greetings, Michael

You can also use an lv2 plugin for the metronome sound (eg. avldrums)
The procedure (install an lv2 drum synthesizer first):

1. open rosegarden
2. Select track 10 (the ususal drum track)
3. Select Device: "Synth plugin"
4. In the Instrument parameters select a drum synth (eg. avldrums)
5. Open Studio->Manage Metronome
6. Select as device "Synth plugin"
7. Select instrument #10

You should now get a metronome beat.

   Philip

On 25/11/2025 15:42, Ted Felix wrote:
>   I put up a new screenshot for the metronomes section.
>
> https://www.rosegardenmusic.com/wiki/doc:manual-en#metronomes
>
> Ted.
>
> On 11/25/25 9:28 AM, Ted Felix wrote:
>> On 11/24/25 12:11 PM, David Faure wrote:
>>> BTW bug report for the documentation:
>>> https://www.rosegardenmusic.com/wiki/doc:manual-en#metronomes
>>> has a broken link to a screen capture called "rg-metronome.png"
>>> (https://rosegardenmusic.com/wiki/rg-metronome.png)
>>
>>    I will have a look.  Thanks.
>
>
>
> _______________________________________________
> Rosegarden-devel mailing list
> Ros...@li... - use the link below to 
> unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-devel

   I put up a new screenshot for the metronomes section.

https://www.rosegardenmusic.com/wiki/doc:manual-en#metronomes

Ted.

On 11/25/25 9:28 AM, Ted Felix wrote:
> On 11/24/25 12:11 PM, David Faure wrote:
>> BTW bug report for the documentation:
>> https://www.rosegardenmusic.com/wiki/doc:manual-en#metronomes
>> has a broken link to a screen capture called "rg-metronome.png"
>> (https://rosegardenmusic.com/wiki/rg-metronome.png)
> 
>    I will have a look.  Thanks.

On 11/24/25 12:11 PM, David Faure wrote:
> Anyhow I have now created a fork on github and pushed a PR,
> it's so much simpler to use what one already knows ;)

   Absolutely.  That's why I'm offering both to encourage more 
contributions.

> My next step is to figure out how to make it send a metronome sound
> that doesn't sound like a note on a piano but more like a "click"....
> I'm assuming there must be a way, but I know very little about MIDI,
> maybe I first need to install a drums sound on the Nord Piano 6...

   I think that's the issue.  The Nord 6 doesn't appear to do drums.  I 
would recommend running fluidsynth and using that for the metronome 
sound.  Or if you have another keyboard that does drums, that would work 
too.

> BTW bug report for the documentation:
> https://www.rosegardenmusic.com/wiki/doc:manual-en#metronomes
> has a broken link to a screen capture called "rg-metronome.png"
> (https://rosegardenmusic.com/wiki/rg-metronome.png)

   I will have a look.  Thanks.

Ted.

On Monday, 24 November 2025 13:52:25 Ted Felix wrote:
> You should be pushing to your own remote, not mine.

Ah! Hehe. Given that the github URL does contain "tedfelix",
it didn't surprise me to use a sf.net URL with "tedfelix" in it ;-)

>    The instructions aren't clear that the "git clone" command needs to 
> be modified to use the fork you just made.  I will update it.

I messed up, I read too fast (because I know a lot about git itself, so a lot
of the wiki page was trivial), and I failed to realize I should actually create a fork on sf.net.
That's entirely my fault, the wiki page is quite clear about this, actually.

Anyhow I have now created a fork on github and pushed a PR,
it's so much simpler to use what one already knows ;)

PS: I'm using rosegarden connected to a MIDI keyboard for the first time ever,
until now I was only writing music with mouse and (computer) keyboard.
My next step is to figure out how to make it send a metronome sound
that doesn't sound like a note on a piano but more like a "click".... 
I'm assuming there must be a way, but I know very little about MIDI,
maybe I first need to install a drums sound on the Nord Piano 6...

BTW bug report for the documentation:
https://www.rosegardenmusic.com/wiki/doc:manual-en#metronomes
has a broken link to a screen capture called "rg-metronome.png"
(https://rosegardenmusic.com/wiki/rg-metronome.png)

-- 
David Faure, fa...@kd..., http://www.davidfaure.fr

   I added the following text to the wiki page:

"There are two official repos for Rosegarden and you can fork and submit 
changes via either of them. The primary repo is at sourceforge 
https://sourceforge.net/p/rosegarden/git/ci/master/tree/ . The secondary 
is at github: https://github.com/tedfelix/rosegarden-official . The 
following steps are for sourceforge. The github steps are similar."

   And I updated the git clone command to look suspicious:

git clone ssh://youruserid@git.code.sf.net/u/youruserid/rosegarden 
rosegarden-git

   Hopefully that's better.  Please review.

https://www.rosegardenmusic.com/wiki/dev:using_git#fork_the_repo

Ted.

On 11/24/25 7:52 AM, Ted Felix wrote:
> On 11/23/25 6:37 AM, David Faure wrote:
>> I'd like to contribute a small compile fix, but I'm confused about how 
>> to proceed.
>>
>> * https://github.com/tedfelix/rosegarden-official is called "official" 
>> but isn't mentioned in
>> https://www.rosegardenmusic.com/wiki/dev:using_git#making_changes
> 
>    You can contribute there if you prefer github.  I'll add it to that 
> page.
> 
>> * If I follow the instructions on that wiki, I can fetch from my 
>> ssh://dfaure_kde@ remote,
>> but I can't push to it.
>>
>> error: remote unpack failed: unable to create temporary object directory
>> To ssh://git.code.sf.net/u/tedfelix/rosegarden
>>   ! [remote rejected]     fix_ninja_build -> fix_ninja_build (unpacker 
>> error)
>> error: failed to push some refs to 'ssh://git.code.sf.net/u/tedfelix/ 
>> rosegarden'
> 
>    That looks like permissions.  You should be pushing to your own 
> remote, not mine.  I'm guessing the remote is pointing to the wrong 
> place.  Take a look at the output of this:
> 
> $ git remote -v
> 
>    It might show origin pointing to "ssh://tedfelix@git.code.sf.net/u/ 
> tedfelix/rosegarden".  That should point to your fork on sourceforge 
> instead.  It can be changed with "git remote set-url".
> 
>    The instructions aren't clear that the "git clone" command needs to 
> be modified to use the fork you just made.  I will update it.
> 
> Ted.
> 
> 
> 
> _______________________________________________
> Rosegarden-devel mailing list
> Ros...@li... - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-devel

On 11/23/25 6:37 AM, David Faure wrote:
> I'd like to contribute a small compile fix, but I'm confused about how to proceed.
> 
> * https://github.com/tedfelix/rosegarden-official is called "official" but isn't mentioned in
> https://www.rosegardenmusic.com/wiki/dev:using_git#making_changes

   You can contribute there if you prefer github.  I'll add it to that page.

> * If I follow the instructions on that wiki, I can fetch from my ssh://dfaure_kde@ remote,
> but I can't push to it.
> 
> error: remote unpack failed: unable to create temporary object directory
> To ssh://git.code.sf.net/u/tedfelix/rosegarden
>   ! [remote rejected]     fix_ninja_build -> fix_ninja_build (unpacker error)
> error: failed to push some refs to 'ssh://git.code.sf.net/u/tedfelix/rosegarden'

   That looks like permissions.  You should be pushing to your own 
remote, not mine.  I'm guessing the remote is pointing to the wrong 
place.  Take a look at the output of this:

$ git remote -v

   It might show origin pointing to 
"ssh://tedfelix@git.code.sf.net/u/tedfelix/rosegarden".  That should 
point to your fork on sourceforge instead.  It can be changed with "git 
remote set-url".

   The instructions aren't clear that the "git clone" command needs to 
be modified to use the fork you just made.  I will update it.

Ted.

Hello everyone,

I'd like to contribute a small compile fix, but I'm confused about how to proceed.

* https://github.com/tedfelix/rosegarden-official is called "official" but isn't mentioned in
https://www.rosegardenmusic.com/wiki/dev:using_git#making_changes

* If I follow the instructions on that wiki, I can fetch from my ssh://dfaure_kde@ remote,
but I can't push to it.

error: remote unpack failed: unable to create temporary object directory
To ssh://git.code.sf.net/u/tedfelix/rosegarden
 ! [remote rejected]     fix_ninja_build -> fix_ninja_build (unpacker error)
error: failed to push some refs to 'ssh://git.code.sf.net/u/tedfelix/rosegarden'

Thanks,

-- 
David Faure, fa...@kd..., http://www.davidfaure.fr

<div style="font-family: 'verdana'; font-size: 12px; color: #000;">Thank you for having a look at it!</div>
<div style="font-family: 'verdana'; font-size: 12px; color: #000;">&nbsp;</div>
<div style="font-family: 'verdana'; font-size: 12px; color: #000;">@ mixer windows</div>
<div style="font-family: 'verdana'; font-size: 12px; color: #000;">I'll try with different Xfce themes then. Maybe there is a difference when using Qt6.</div>
<div style="font-family: 'verdana'; font-size: 12px; color: #000;">&nbsp;</div>
<div style="font-family: 'verdana'; font-size: 12px; color: #000;">@ controller moves</div>
<div style="font-family: 'verdana'; font-size: 12px; color: #000;">Sorry, I thought they were shown. I guess I mixed it up with other softwares.&nbsp;</div>
<div style="font-family: 'verdana'; font-size: 12px; color: #000;">&nbsp;</div>
<div style="font-family: 'verdana'; font-size: 12px; color: #000;">@ channel-&nbsp; and keypressure ruler</div>
<div style="font-family: 'verdana'; font-size: 12px; color: #000;">I see, didn't get that before.</div>
<div style="font-family: 'verdana'; font-size: 12px; color: #000;">&nbsp;</div>
<div style="font-family: 'verdana'; font-size: 12px; color: #000;">Sorry for the noise :-)</div>
<div style="font-family: 'verdana'; font-size: 12px; color: #000;">Greetings, Michael</div>
<div style="font-family: 'verdana'; font-size: 12px; color: #000;"><span style="background-color: #ffffff;">&nbsp;</span></div>
<div id="sub-body-container" style="margin: 10px 5px 5px 10px; padding: 10px 0px 10px 10px; border-left: 2px solid rgb(195, 217, 229);">
<div style="margin: 0px 0px 10px;">
<div><strong>Gesendet: </strong>Montag, 10. November 2025 um 17:24</div>
<div><strong>Von: </strong>"Ted Felix" &lt;te...@te...&gt;</div>
<div><strong>An: </strong>Babarosa &lt;bab...@gm...&gt;, rosegarden-devel &lt;ros...@li...&gt;</div>
<div><strong>Betreff: </strong>Re: [Rosegarden-devel] Proposed Schedule for 25.12</div>
</div>
On 11/6/25 5:00 PM, Babarosa wrote:<br>&gt; Both the MIDI- and Audio-Mixer windows are not resizable, therefore the <br>&gt; rightmost menu entry (Help) in the MIDI-Mixer is only reachable by <br>&gt; clicking the double arrow symbol.<br><br>For me the Help menu item is right next to the Transport menu item. <br>I wonder who is trying to move it to the right. Xfce maybe? I'm not <br>sure what we can do about this.<br><br>&gt; MIDI-Controller moves are not shown in realtime in the MIDI-Mixer window.<br><br>They never were. That would be a feature request. The MIDI mixer <br>only shows the initial settings from the MIDI "Instrument Parameters" <br>panel. RG's handling of control changes is pretty limited.<br><br>&gt; The new feature "show channel pressure/key pressure events" in the <br>&gt; matrix window as a ruler doesn't seem to work here. They are greyed out <br>&gt; in the menu, even I do a "select all events". I see these events in the <br>&gt; event list editor though.<br><br>As Philip mentioned, you'll need to add those two to the device's <br>controllers before they appear.<br><br>Ted.<br><br></div>

On 11/6/25 5:00 PM, Babarosa wrote:
> Both the MIDI- and Audio-Mixer windows are not resizable, therefore the 
> rightmost menu entry (Help) in the MIDI-Mixer is only reachable by 
> clicking the double arrow symbol.

   For me the Help menu item is right next to the Transport menu item. 
I wonder who is trying to move it to the right.  Xfce maybe?  I'm not 
sure what we can do about this.

> MIDI-Controller moves are not shown in realtime in the MIDI-Mixer window.

   They never were.  That would be a feature request.  The MIDI mixer 
only shows the initial settings from the MIDI "Instrument Parameters" 
panel.  RG's handling of control changes is pretty limited.

> The new feature "show channel pressure/key pressure events" in the 
> matrix window as a ruler doesn't seem to work here. They are greyed out 
> in the menu, even I do a "select all events". I see these events in the 
> event list editor though.

   As Philip mentioned, you'll need to add those two to the device's 
controllers before they appear.

Ted.

On 11/7/25 7:36 AM, Philip Leishman via Rosegarden-devel wrote:
> The mixers seem to have changed a lot since the last release (Ted ?). I 
> have attached screenshots from 25.06 and now. The fixed size is also new.

   Yep.  That's me.  Was working on making them fully scalable.  I'll 
have a look at the issues Michael has identified on Tuesday.

Ted.

On 06/11/2025 23:00, Babarosa via Rosegarden-devel wrote:
> Hi!
>
> I compiled the latest git code version just now and did my usual 
> tests. Thank you for your work and the massive updated feature list.
>
> I am using Debian 12.11 64bit with Xfce and am building Rosegarden 
> using the Qt5 package set.
>
> What did I find out:
>
> Both the MIDI- and Audio-Mixer windows are not resizable, therefore 
> the rightmost menu entry (Help) in the MIDI-Mixer is only reachable by 
> clicking the double arrow symbol.
The mixers seem to have changed a lot since the last release (Ted ?). I 
have attached screenshots from 25.06 and now. The fixed size is also new.

>
> MIDI-Controller moves are not shown in realtime in the MIDI-Mixer window.
>
> The new feature "show channel pressure/key pressure events" in the 
> matrix window as a ruler doesn't seem to work here. They are greyed 
> out in the menu, even I do a "select all events". I see these events 
> in the event list editor though.
>
> The playback of my standard test file with audio tracks, 16 midi 
> tracks, several lv2 instruments performs rock solid.
>
> I will start working on the german translation on November 19th.
>
> Greetings Michael
>
> Am 28.10.25 um 17:45 schrieb Ted Felix:
>
>> Proposed Schedule for 25.12:
>>
>> November 5: Feature Freeze, Testing period (4 weeks) begins
>> November 19: String Freeze, Translation period (2 weeks) begins
>> December 3: Rosegarden 25.12
>>
>> Ted.
>>
>>
>>
>> _______________________________________________
>> Rosegarden-devel mailing list
>> Ros...@li... - use the link below to 
>> unsubscribe
>> https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
>
>
> _______________________________________________
> Rosegarden-devel mailing list
> Ros...@li... - use the link below to 
> unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-devel