Lorenzo

Hi! Finally managed to re-build latest git and can confirm this is now fixed for both grid and quantize dropdowns. Thanks!

You guys were quicker than my feedback :-) I tested the latest git and: solved for the grid, still there beyond 1/8 for the quantize.

Sorry, I forgot to specify.. KDE Plasma and X11 Lorenzo On Sun, 26 Apr 2026, 10:32 Philip Leishman, lman@users.sourceforge.net wrote: I cannot reproduce this. Are you running with kde? I believe this is the default for CacyOS. X11 or Wayland ? [bugs:#1778] https://sourceforge.net/p/rosegarden/bugs/1778/ Matrix editor grid dropdown selection condensed and unreadable Status: open Group: None Created: Sat Apr 25, 2026 04:30 PM UTC by Lorenzo Last Updated: Sat Apr 25, 2026 04:30 PM UTC Owner: nobody...

Matrix editor grid dropdown selection condensed and unreadable

Indeed the composition start was at bar 1 now... But the tempo and and meter were at bar 0. What I was seeing was before moving these to bar 1. So I'm assuming the calculation is being made with 120 BPM? Anyway it's in the file I attached ;)

Some updates with additional testing TL;DR - completely 'resetting' the tempo and change (146.00 BPM) and time signature placing them at measure 1 seems to have fixed the issue for this and the 'original' file (which also has segments). This was achieved by completely deleting both the tempo and time signatures and re-adding them at measure 1. Because... one thing I noticed: Regarding that file having time signature and tempo at measure 0 - indeed it has, but I noticed something weird. If I open...

I did some additional tests with both Rosegarden 'stable' (25.12) and git. So the affected file continues to be problematic even if deleting all segments (see attached file). In Rosegarden git it exhibits the issue of being unable to go to measure 1. In Rosegarden 'stable' I can at least go to measure 1. In both the sync with ardour doesn't work. I tried creating in ardour an empty session with same BPM (146) and 5/4 and sync is completely off in both versions of rosegarden.

No moving the start to 1 doesn't recover. I'm also noticing (via other threads) that this and playhead issues is somewhat composition dependent, so I think it would be important (besides a < 1 start time) to understand what in the composition can affect the behaviour. What I mean is what in a specific composition can affect transport / playhead issues?