Muse sequencer has several bugs like broken Step Recording. In the changelog they are listed and marked to be fixed: https://github.com/muse-sequencer/muse/blob/4.2.0/src/ChangeLog For instance: 31.07.2023 - Fixed midi remote control: Don't accept note-offs. (Tim) Symptoms were: Double step-record entries, transport record toggling, double play etc. - Changed all references to the app's url, help url etc. (Website has changed). Created ORGANIZATION_URL, ORGANIZATION_HELP_URL, ORGANIZATION_CODE_REPO_URL in config.h.in Would be nice to see the package bebuilt. Thanks!
Thank you for this helpful report. https://github.com/muse-sequencer/muse/releases/download/4.2.1/muse-4.2.1.tar.gz is the download. Assigning to DavidG who maintains this SRPM.
Assignee: bugsquad => geiger.david68210
Done for Cauldron!
Also updating muse to the latest upstream release 4.2.1 with several bud fixes. Assigning to QA, Packages in 9/Core/Updates_testing: ====================== muse-4.2.1-1.mga9 From SRPMS: muse-4.2.1-1.mga9.src.rpm
Assignee: geiger.david68210 => qa-bugs
Keywords: (none) => advisoryCC: (none) => marja11
From what I have tested so far, the bugs are gone. Thank you!
Status: NEW => RESOLVEDResolution: (none) => FIXED
It should be first validate by the QA team so reopened this bug.
Resolution: FIXED => (none)CC: (none) => geiger.david68210Status: RESOLVED => REOPENED
Created attachment 14327 [details] Messages in terminal I get some errors running in terminal with both versions current and testing But the application start I never use before this application, so I don't know how to use it to see if works
I get a few WARNINGS, not errors. -- This is normal. If you skip every app that throws warnings (which you only see when run on commandline) you will find yourself without OS
(In reply to Markus Robert Keßler from comment #7) > I get a few WARNINGS, not errors. -- This is normal. > > If you skip every app that throws warnings (which you only see when run on > commandline) you will find yourself without OS I service industrial machines. If i am to ignore warnings my customer finds himself without a machine. - Or without an arm or worse... What are all missing files intended for? I see it complain about realtime. Real time is important for sampling and playing notes with best time resolution Also "Cannot allocate memory" does not seem optimal.
CC: (none) => fri
Just verified: The former version 4.1 also throws all that "cannot allocate memory" warnings. Even Ubuntu Studio is concerned. Nevertheless, it works. And, you say > If i am to ignore warnings my customer finds himself without a machine. That's right, but, WE are the customer. And we know about the warnings. Besides this, I do not know of even one single Professional musician using semiprofessional tools like Muse or, even worse, Rosegarden. Rosegarden in MGA9 repo does not work at all, since you cannot even set output port and channel. Pointless to discuss about. The solution for professional users would be to run Cakewalk in Wine -- which works -- but then you have to mess around with WineASIO drivers and timing issues.
CC: (none) => andrewsfarm
Is fine for the reporter and due to the fact that behavior in terminal is the same in current and testing version, I set the ok Let to Thomas the final decision
Whiteboard: (none) => MGA9-64-OK
We have other apps that throw warnings - try running Thunderbird from the command line sometime, for example. Or Gimp. Since the warnings are in both new and old versions, they are not a new regression. And since the application is reported to be operating as expected despite the warnings, I'm going to go ahead with the validation. @Robert: Even if professionals are unlikely to use "semi-professional" tools like this one, that doesn't mean we should just ignore any and all warnings that might show up. I would even say that perhaps the semi-professionals and/or amateurs might be more dependent on our careful scrutiny of the tools than their professional colleagues.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
I agree. Just saying it is not easy to QA when there are so much warnings, and not at the same time info on how to what they mean. In my car the engine lamp have been lit ten years because of a bogus self check, which masks now anytime there are a real issues... Maybe interested users should check and eventually open bugs fur such upstream. While talking about Rosegarden, I see you Markus test it too, good :) Any progress from upstream there? Bug 32632 - Rosegarden, right mouseclick on trackname no longer opens context menu Bug 32576 - Rosegarden mouse-based jumping between tracks no longer possible
I know some/many applications produce warnings that not affect the work I present this case just because the complaints is about files related to application (lv2 plugins) But if the reporter says it works is fine for me
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2024-0043.html
Resolution: (none) => FIXEDStatus: REOPENED => RESOLVED