Sure that this is no upstream design decission?

Since v22.06, there have been 22.12, 22.12.1, latest 23.06.
 https://www.rosegardenmusic.com/wiki/dev:23.06
shows bug fixes & improvements.

Thanks to DavidG, this is already in Cauldron. I think we should start here by updating the package. Then ask Markus to test the new version; no-one here is likely to know how to drive it.

Assignee: bugsquad => geiger.david68210

Glad to do that. Looking forward to test -- thanks!

Thank you DavidG, i see you pushed rosegarden-23.06-1.mga9 to buildsystem 14 hours ago, please get it from updates testing :)

CC: (none) => fri

Hi,
seen the following:

(- more up to date surface, looking good! But)

- mouse-based focussing of tracks still not working
- new bug: whatever track selected for recording, rosegarden always jumps to track 1 and records there

Please check with upstream, if bugs came in there,
and in worst case, roll back to 22.12 as in Ubuntu, where these things work.

Thanks!

@Markus,

§ can you check with upstream if these are known problems, and if they have workarounds?

§ Meanwhile, I see Rosegarden is available as Flatpak, can you try/use that meanwhile?  https://wiki.mageia.org/en/Flatpak

For better understanding the misbehaviour, please see
https://www.dipl-ing-kessler.de/tmp/rosegarden-bug-32576.mp4
So, everyone can test this, also

Please open a new bug upstream at https://sourceforge.net/p/rosegarden/bugs/

David, please re-read what I've written about openconnect.
It makes no sense, if a normal user like me, just a little nobody, creates a bug report upstream.
Would you please be so kind and do that for us?

Besides that, I was wondering why even the latest Ubuntu is using an "outdated" version like rosegarden 22.12. But now we see, that this is done by good reason. This seems to be the newest *working* version.
Thanks!

Markus, David have very much in his hands, and it is more valuable for upstream to get a direct feedback from users, who know how to operate and test the software.

If they have a forum, also discuss there, i.e why ubuntu is not at latest version.

I've only few time, so, let's see.

But, just one question:
If we, in the meantime, roll back to the last working version 22.12 (see Ubuntu), so, how can autoupdater / mcc replace a newer version with an older one?
Is this possible at all?

Yes, if you provide the package/s, I can try the next release candidate/s.
B.t.w.: There's hope that these bugs get fixed soon, since they are so obvious, that others must have found them, too.

For others reading this:
Temporary workaround to "record always on track 1" bug:
Leave track 1 empty, do recording, then move the data from track 1 to target.
Temporary workaround to "track not mouse-selectable" bug:
Just click in track view and move cursor up / down to navigate to target track.

To clarify the situation:

if our current 22.06 release in our stable repo and if the new 23.06 release in testing repo doesn't fix this issue it is just impossible that the 22.12 fixes it!!

So if there is an upstream regression you have to file a new bug directly upstream to find what is going wrong since release 22.06 with them.

To exclude the possibility, that there's something wrong with my box (since in the early days of MGA9 there were lots of crashes also on my machine), the safest way would be, if someone else tries the same as shown in my video.
Setup and testing should be done in less than 5 minutes.

> if our current 22.06 release in our stable repo and if the new 23.06
> release in testing repo doesn't fix this issue it is just impossible
> that the 22.12 fixes it!!

Wrong conclusion. Correct only if same distro.

Maybe someone who is familiar with deb package format looks into 22.12 and tells us what the colleagues from Ubuntu have done here to make it work.

So the next step is that someone else tries at at least the current "stable" version as shown here:

    https://www.dipl-ing-kessler.de/tmp/rosegarden-bug-32576.mp4

We have to be sure that the misbehaviour is not limited to my box.

Hi, thanks from my side also for providing the test candidates.

As said, when MGA9 came out, it was so crappy that sometimes multiple crashes occured per day, so, someone has to re-do the test with "stable".

This will make clear, if this is a generic problem, or if I have to reinstall...

Just install vkeybd and rosegarden,
go into "studio" ==> "manage midi devices", on bottom select virtual keyboard as input, and then start a recording on track > 1.
Also, try to select random tracks via mouse click, rather than via cursor.

Then please report the outcome

(In reply to Markus Robert Keßler from comment #21)
> Hi, thanks from my side also for providing the test candidates.
> 
> As said, when MGA9 came out, it was so crappy that sometimes multiple
> crashes occured per day, so, someone has to re-do the test with "stable".
> 
> This will make clear, if this is a generic problem, or if I have to
> reinstall...
> 
> Just install vkeybd and rosegarden,
> go into "studio" ==> "manage midi devices", on bottom select virtual
> keyboard as input, and then start a recording on track > 1.
> Also, try to select random tracks via mouse click, rather than via cursor.
> 
> Then please report the outcome

What you select of this whe you install vkeybd
1- timidity-patch-freepats-20060219-23.mga9.noarch: Patch set for MIDI audio synthesis (para instalar)
 2- timidity-patch-fluid-3.1-16.mga9.noarch: Pro-quality General Midi sound font in GUS patch format (para instalar)
 3- timidity-patch-gravis-1.0-38.mga9.noarch: Instruments for the timidity midi->wave converter/player (para instalar)


I choose 1 but I don't see the virtual keyboard as option

Hi,

> What you select of this whe you install vkeybd

choose any of these 3, this makes no difference. Virtual keyboard will be installed always and can be used. We only use it as midi events source here

(In reply to Markus Robert Keßler from comment #19)
> So the next step is that someone else tries at at least the current "stable"
> version as shown here:
> 
>     https://www.dipl-ing-kessler.de/tmp/rosegarden-bug-32576.mp4
> 
> We have to be sure that the misbehaviour is not limited to my box.
You must have vkeybd running to can select as input
I not get any sound, but if the desired behavior is that after the first stop and select other track, the record should continue in that track instead of the first, then I confirm the bug

Definitive, you must ask help to upstream

Can you jump from track to track via mouse?

(In reply to Markus Robert Keßler from comment #26)
> Can you jump from track to track via mouse?

Not sure what you mean sorry, I never before used this software, I make the same as in the video and get the same result

> I make the same as in the video and get the same result

Yes, that's it, bingo! Second bug found...

Obsoleting the comments related to my unofficial build to reduce the noise in this bug

B.t.w.: I won't open another ticket, but

Hydrogen Drums in mga9 is also buggy.

It takes MIDI data as input and input detector flashes, but these input notes are never processed. Hence, Hydrogen cannot be driven by a master keyboard or even a sequencer. Nothing to hear. It can only be used standalone.

The good news:

I have tested the candidate from Cauldron. It can be installed as MGA10 on MGA9 without re-packaging. And the above works here.

You could: copy hydrogen-1.2.2-1.mga10.x86_64.rpm to mga9 (update-testing, or just update since it is now tested), either as 10 or after re-packaging into mga9.
hydrogen drumkits is the same in cauldron anyway.

(In reply to Markus Robert Keßler from comment #30)
> B.t.w.: I won't open another ticket, but
> 
> Hydrogen Drums in mga9 is also buggy.
> 
> It takes MIDI data as input and input detector flashes, but these input
> notes are never processed. Hence, Hydrogen cannot be driven by a master
> keyboard or even a sequencer. Nothing to hear. It can only be used
> standalone.
> 
> The good news:
> 
> I have tested the candidate from Cauldron. It can be installed as MGA10 on
> MGA9 without re-packaging. And the above works here.
> 
> You could: copy hydrogen-1.2.2-1.mga10.x86_64.rpm to mga9 (update-testing,
> or just update since it is now tested), either as 10 or after re-packaging
> into mga9.
> hydrogen drumkits is the same in cauldron anyway.

Please open a new bug for that.

Workaround / temporary solution see

https://bugs.mageia.org/show_bug.cgi?id=32632

(In reply to Markus Robert Keßler from comment #32)
> Workaround / temporary solution see
> 
> https://bugs.mageia.org/show_bug.cgi?id=32632

Are you serious?? it really becomes nonsense!

You can't ask others users to install a very old and outdated package from mga7
 just because you think the new versions don't work the way as you want and because you don't want to open a new bug report upstream.

(In reply to David GEIGER from comment #33)
> (In reply to Markus Robert Keßler from comment #32)
> > Workaround / temporary solution see
> > 
> > https://bugs.mageia.org/show_bug.cgi?id=32632
> 
> Are you serious?? it really becomes nonsense!
> 
> You can't ask others users to install a very old and outdated package from
> mga7
>  just because you think the new versions don't work the way as you want and
> because you don't want to open a new bug report upstream.

I agree should open bug in upstream, Mageia can't do nothing to it....

David I backported rosegarden-24.06-2 and looks like this particular bug is fixed

Assigning to QA,

Package in 9/Core/Updates_testing:
======================
rosegarden-24.06-1.mga9

From SRPMS:
rosegarden-24.06-1.mga9.src.rpm

Depends on: (none) => 32632
Assignee: geiger.david68210 => qa-bugs

RH mageia 9 x86_64

LC_ALL=C urpmi rosegarden vkeybd qjackctl 
In order to satisfy the 'timidity-instruments[== 2]' dependency, one of the following packages is needed:
 1- timidity-patch-freepats-20060219-23.mga9.noarch: Patch set for MIDI audio synthesis (to install)
 2- timidity-patch-fluid-3.1-16.mga9.noarch: Pro-quality General Midi sound font in GUS patch format (to install)
 3- timidity-patch-gravis-1.0-38.mga9.noarch: Instruments for the timidity midi->wave converter/player (to install)
What is your choice? (1-3) 1
Package qjackctl-0.9.9-1.mga9.x86_64 is already installed
To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch    
(medium "Core Release (distrib1)")
  lib64lo7                       0.31         2.mga9        x86_64  
  lib64lrdf2                     0.6.1        4.mga9        x86_64  
  lib64qt6core5compat6           6.4.1        3.mga9        x86_64  
  liblrdf-common                 0.6.1        4.mga9        x86_64  
  qt5compat6                     6.4.1        3.mga9        x86_64  
  rosegarden                     22.06        2.mga9        x86_64  
  sndfile-tools                  1.5          2.mga9        x86_64  
  timidity++                     2.15.0       3.mga9        x86_64  (recommended)
  timidity-patch-freepats        20060219     23.mga9       noarch  (recommended)
  vkeybd                         0.1.18d      13.mga9       x86_64  
(medium "Core Updates (distrib3)")
  libsndfile-progs               1.2.0        3.1.mga9      x86_64  
49MB of additional disk space will be used.
35MB of packages will be retrieved.
Proceed with the installation of the 11 packages? (Y/n) y


    https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/timidity++-2.15.0-3.mga9.x86_64.rpm
    https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/liblrdf-common-0.6.1-4.mga9.x86_64.rpm         
    https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/lib64qt6core5compat6-6.4.1-3.mga9.x86_64.rpm   
    https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/vkeybd-0.1.18d-13.mga9.x86_64.rpm              
    https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/lib64lrdf2-0.6.1-4.mga9.x86_64.rpm             
    https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/timidity-patch-freepats-20060219-23.mga9.noarch.rpm
    https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/qt5compat6-6.4.1-3.mga9.x86_64.rpm             
    https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/lib64lo7-0.31-2.mga9.x86_64.rpm                
    https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/rosegarden-22.06-2.mga9.x86_64.rpm             
    https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/sndfile-tools-1.5-2.mga9.x86_64.rpm            
    https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/updates/libsndfile-progs-1.2.0-3.1.mga9.x86_64.rpm     
installing lib64qt6core5compat6-6.4.1-3.mga9.x86_64.rpm timidity-patch-freepats-20060219-23.mga9.noarch.rpm lib64lrdf2-0.6.1-4.mga9.x86_64.rpm vkeybd-0.1.18d-13.mga9.x86_64.rpm lib64lo7-0.31-2.mga9.x86_64.rpm rosegarden-22.06-2.mga9.x86_64.rpm qt5compat6-6.4.1-3.mga9.x86_64.rpm libsndfile-progs-1.2.0-3.1.mga9.x86_64.rpm sndfile-tools-1.5-2.mga9.x86_64.rpm timidity++-2.15.0-3.mga9.x86_64.rpm liblrdf-common-0.6.1-4.mga9.x86_64.rpm from /var/cache/urpmi/rpms
Preparing...                     ##################################################################################################
     1/11: liblrdf-common        ##################################################################################################
     2/11: lib64lrdf2            ##################################################################################################
     3/11: sndfile-tools         ##################################################################################################
     4/11: libsndfile-progs      ##################################################################################################
     5/11: qt5compat6            ##################################################################################################
     6/11: lib64qt6core5compat6  ##################################################################################################
     7/11: lib64lo7              ##################################################################################################
     8/11: timidity-patch-freepats
                                 ##################################################################################################
     9/11: timidity++            ##################################################################################################
    10/11: vkeybd                ##################################################################################################
    11/11: rosegarden            ##################################################################################################

Run qjackctl
Run vkeybd
Run rosegarden 
Confirm this bug, I start a record on track 1, stop record, disable track 1, enable  track 2 , start to record again , the record jumps again to track 1 instead of  track 2 as expected

I also confirm bug#32632

Update to testing version without issues

Repeat the test the record now continues on track 2
Regards bug#32632 the contextual menu works now but is a few tricky, for Midi devices just allow select from devices you did work before or the list is just the default piano device

For me both bug are fixed and is OK
I hope get confirmation from Markus, but I think we can finally give green light

CC: (none) => andrewsfarm
Whiteboard: (none) => MGA9-64-OK

OK, giving this a couple of days to give Marcus a chance to check in.

Nothing from Marcus; validating on the basis of katnatek's test.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

rosegarden-23.06-1.mga9 was pushed in bug #32632

CC: (none) => dan
Status: NEW => RESOLVED
Resolution: (none) => FIXED