In rosegarden's track view it is no longer possible to jump between tracks by mouse click on audio/midi track name. Instead you have to click into track list, and then move around with cursor up/down. This makes working extremely slow. Feature should work again. Thanks!
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?
CC: (none) => j.alberto.vc, ngompa13
(In reply to Markus Robert Keßler from comment #11) > 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? I hope we not have to do that, if you want to try unofficial package I import some fixes of OpenSuse and make a new build Choose the version/arch of your system from https://copr.fedorainfracloud.org/coprs/katnatek/mgaMentorship/build/6706565/, download and install the <<arch>.rpm package (<arch> can be i586, x86_64,etc and not the src.rpm neither the debug* rpms) If you decide to test, after the test report with reply to this message and remove from your system my package If the package works for you, I'll upload to this bug my changes
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.
(In reply to Markus Robert Keßler from comment #13) > 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. > Test the right package for your system, FYI, I not include the recommendation for qsynth that makes OpenSuse https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/mageia-9-i586/06706565-rosegarden/rosegarden-23.06-1.1.mga9.i586.rpm https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/mageia-9-x86_64/06706565-rosegarden/rosegarden-23.06-1.1.mga9.x86_64.rpm https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/mageia-cauldron-i586/06706565-rosegarden/rosegarden-23.06-1.1.mga10.i586.rpm https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/mageia-cauldron-x86_64/06706565-rosegarden/rosegarden-23.06-1.1.mga10.x86_64.rpm
Tried all from above: https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/mageia-9-i586/06706565-rosegarden/rosegarden-23.06-1.1.mga9.i586.rpm ==> dependencies not fulfilled https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/mageia-9-x86_64/06706565-rosegarden/rosegarden-23.06-1.1.mga9.x86_64.rpm ==> installer forced to additionally install all sort of ruby, then went ahead. Accepted this and tested: ==> same behaviour as shown in video https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/mageia-cauldron-i586/06706565-rosegarden/rosegarden-23.06-1.1.mga10.i586.rpm ==> dependencies not fulfilled https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/mageia-cauldron-x86_64/06706565-rosegarden/rosegarden-23.06-1.1.mga10.x86_64.rpm ==> dependencies not fulfilled
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.
(In reply to Markus Robert Keßler from comment #18) > Tried all from above: > > https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/ > mageia-9-i586/06706565-rosegarden/rosegarden-23.06-1.1.mga9.i586.rpm > > ==> dependencies not fulfilled > > https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/ > mageia-cauldron-i586/06706565-rosegarden/rosegarden-23.06-1.1.mga10.i586.rpm > > ==> dependencies not fulfilled > > > https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/ > mageia-cauldron-x86_64/06706565-rosegarden/rosegarden-23.06-1.1.mga10.x86_64. > rpm > > ==> dependencies not fulfilled Interesting, I can't check in cauldron, but I see what happen for mga9 i586 and check what requires in cauldron to try to find what is missing Thank you for your test
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 katnatek from comment #20) > (In reply to Markus Robert Keßler from comment #18) > > Tried all from above: > > > > https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/ > > mageia-9-i586/06706565-rosegarden/rosegarden-23.06-1.1.mga9.i586.rpm > > > > ==> dependencies not fulfilled > > > > > https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/ > > mageia-cauldron-i586/06706565-rosegarden/rosegarden-23.06-1.1.mga10.i586.rpm > > > > ==> dependencies not fulfilled > > > > > > https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/ > > mageia-cauldron-x86_64/06706565-rosegarden/rosegarden-23.06-1.1.mga10.x86_64. > > rpm > > > > ==> dependencies not fulfilled > > Interesting, I can't check in cauldron, but I see what happen for mga9 i586 > and check what requires in cauldron to try to find what is missing > > Thank you for your test (In reply to Markus Robert Keßler from comment #18) > Tried all from above: > > https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/ > mageia-9-i586/06706565-rosegarden/rosegarden-23.06-1.1.mga9.i586.rpm > > ==> dependencies not fulfilled > > > https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/ > mageia-9-x86_64/06706565-rosegarden/rosegarden-23.06-1.1.mga9.x86_64.rpm > > ==> installer forced to additionally install all sort of ruby, then went > ahead. > Accepted this and tested: > ==> same behaviour as shown in video > > > https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/ > mageia-cauldron-i586/06706565-rosegarden/rosegarden-23.06-1.1.mga10.i586.rpm > > ==> dependencies not fulfilled > > > https://download.copr.fedorainfracloud.org/results/katnatek/mgaMentorship/ > mageia-cauldron-x86_64/06706565-rosegarden/rosegarden-23.06-1.1.mga10.x86_64. > rpm > > ==> dependencies not fulfilled Check what mirror are you using, I run urpmi --test, and not found issues LC_ALL=C urpmi --test /home/katnatek/rpm/RPMS/i586/rosegarden-23.06-1.1.mga9.i586.rpm To satisfy dependencies, the following packages are going to be installed: (test only, installation will not be actually done) Package Version Release Arch (medium "Core Release (distrib1)") liblo7 0.31 2.mga9 i586 liblrdf-common 0.6.1 4.mga9 i586 liblrdf2 0.6.1 4.mga9 i586 ruby 3.1.4 44.mga9 i586 ruby-RubyGems 3.3.26 44.mga9 noarch ruby-io-console 0.5.11 44.mga9 i586 ruby-irb 3.1.4 44.mga9 noarch ruby-json 2.6.1 44.mga9 i586 ruby-psych 4.0.4 44.mga9 i586 ruby-rdoc 6.4.0 44.mga9 noarch sndfile-tools 1.5 2.mga9 i586 (medium "Core Updates (distrib3)") libsndfile-progs 1.2.0 3.1.mga9 i586 (command line) rosegarden 23.06 1.1.mga9 i586 49MB of additional disk space will be used. 13MB of packages will be retrieved. Proceed with the installation of the 13 packages? (Y/n) y https://mirror.math.princeton.edu/pub/mageia/distrib/9/i586/media/core/release/liblo7-0.31-2.mga9.i586.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/i586/media/core/release/sndfile-tools-1.5-2.mga9.i586.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/i586/media/core/release/ruby-json-2.6.1-44.mga9.i586.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/i586/media/core/release/ruby-io-console-0.5.11-44.mga9.i586.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/i586/media/core/release/ruby-3.1.4-44.mga9.i586.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/i586/media/core/release/liblrdf2-0.6.1-4.mga9.i586.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/i586/media/core/release/ruby-irb-3.1.4-44.mga9.noarch.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/i586/media/core/release/liblrdf-common-0.6.1-4.mga9.i586.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/i586/media/core/release/ruby-RubyGems-3.3.26-44.mga9.noarch.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/i586/media/core/release/ruby-psych-4.0.4-44.mga9.i586.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/i586/media/core/release/ruby-rdoc-6.4.0-44.mga9.noarch.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/i586/media/core/updates/libsndfile-progs-1.2.0-3.1.mga9.i586.rpm warning: /home/katnatek/rpm/RPMS/i586/rosegarden-23.06-1.1.mga9.i586.rpm: Header V4 RSA/SHA256 Signature, key ID a1281639: NOKEY The following package has bad signature: /home/katnatek/rpm/RPMS/i586/rosegarden-23.06-1.1.mga9.i586.rpm: Invalid signature (NOT OK (no key): /home/katnatek/rpm/RPMS/i586/rosegarden-23.06-1.1.mga9.i586.rpm: Header V4 RSA/SHA256 Signature, key ID a1281639: NOKEY) Do you want to continue installation ? (y/N) y installing /var/cache/urpmi/rpms/sndfile-tools-1.5-2.mga9.i586.rpm /var/cache/urpmi/rpms/liblo7-0.31-2.mga9.i586.rpm /var/cache/urpmi/rpms/ruby-io-console-0.5.11-44.mga9.i586.rpm /var/cache/urpmi/rpms/ruby-3.1.4-44.mga9.i586.rpm /home/katnatek/rpm/RPMS/i586/rosegarden-23.06-1.1.mga9.i586.rpm /var/cache/urpmi/rpms/ruby-json-2.6.1-44.mga9.i586.rpm /var/cache/urpmi/rpms/liblrdf2-0.6.1-4.mga9.i586.rpm /var/cache/urpmi/rpms/libsndfile-progs-1.2.0-3.1.mga9.i586.rpm /var/cache/urpmi/rpms/ruby-psych-4.0.4-44.mga9.i586.rpm /var/cache/urpmi/rpms/ruby-RubyGems-3.3.26-44.mga9.noarch.rpm /var/cache/urpmi/rpms/ruby-rdoc-6.4.0-44.mga9.noarch.rpm /var/cache/urpmi/rpms/liblrdf-common-0.6.1-4.mga9.i586.rpm /var/cache/urpmi/rpms/ruby-irb-3.1.4-44.mga9.noarch.rpm Preparing... ####################################################################################### Installation is possible I'll try your test procedure with the official package
(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
CC: ngompa13 => (none)
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....