-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Muse Sounds are not discovered #100
Comments
Try |
Doesn't work unfortunately. |
I have looked into what app shows in console and it seems like the first problem is inability to load the It looks like the correct environment variable is |
I'm also having this problem. I've tried the above suggestion, and it also doesn't work for me. This is using Linux Mint 21.1. I would love to see this fixed, as AppImages are wonky. It would be even better if Musescore or someone would just offer a simple .deb file repository or PPA, as I've never been a fan of things like Flatpaks, AppImages, Snaps, etc. But this is where things are now, so we're just left to deal with the mess. |
You can get the Muse Hub .deb and probably install MuseScore from there. But I don't recommend it as it's not sandboxed and MuseHub is proprietary |
On Linux, Muse Hub only handles the Muse Sounds packages. It doesn't have any options for downloading Musescore itself. There is an old PPA, but it currently only goes through version 3.2, with some slightly newer code backported to it. It doesn't support version 4 yet, as far as I can see. The only options for version 4 that I can find are the official AppImage or the Flatpak. No .debs or any other native distro package formats from what I can see. |
I have also found the appImage of MuseScore 4 to load MuseSounds loaded from the MuseHub .deb without issue. The Flatpak version however doesn't seem to recognise them (shown as inactive). This is on Ubuntu 22.10. I saw on a separate issue that people have solve the issue of MuseSounds not loading on Fedora by linking the I wonder if a similar thing could be achieved by actually linking this |
What worked for me was moving libMuseSamplerCoreLib.so to my home directory and setting MUSESAMPLER_PATH to point to it. The reason it can't work out of the box with Flatpak is that /usr/lib doesn't get mounted into the container, even with |
Thanks. I copied the library file and tried I think that I'll have to stick with the appImage until the flatpak is fixed. |
@Batwam, how do you know that MuseScore uses the |
it's in the closed source part. you'll get a warning if you don't set it |
correct, you get the following error if you don't define it: by the way. I am also getting the following which I ignored as they are usually nice to haves only.
|
Well, this issue is kinda dead but I do have an update! I've managed to get MuseScore to recognise both the sampler library as well as the instruments as well (as in they appear in the menu selection in the mixer) but I haven't yet been able to actually use the sounds because MuseScore crashes upon trying to select a MuseSounds instrument I get this error Other notes:
This might be because flatpak doesn't allow you to access root directory folders but I'm not entirely sure on that. I have both the library and instruments within my home folder and given flatpak access to those folder as well |
@Noxellar it's because libopus in the freedesktop runtime is compiled without custom mode support, whereas libMuseSamplerCoreLib is built against debain which ships libopus with custom mode support. I don't think Muse Sounds even require custom mode, but it's incompatible nevertheless. You can build your own version of libopus and bundle it with the MuseScore flatpak |
I believe that this issue needs discussing with MuseScore and MuseHub developers. Probably with where currently MuseHub downloads these files the problem cannot be solved, but also probably these locations are not the optimal ones for storing these files under Linux in general. Could the flatpak package maintainer reach out to MuseScore developers in order to try to find the solution? The maintainer could suggest them what location would be the best for these files, so that any sandboxed packaging formats could work – maybe they would be willing to change it to help. Or find a way to have flatpaks for both MuseScore and MuseHub on FlatHub with default configurations set in such a way that installing both these tools from flatpak would make it work out of the box. |
It looks like MuseScore 4.2 and Muse Sounds Manager (updated and renamed Muse Hub for Linux) may have solved some blockers here. Firstly, the Muse Sounds default download target is now moved to user's home directory, which makes it accessible for Flatpak. Secondly, the Also, some issues in MuseScore project regarding Flatpak are being assigned and discussed (#17016, #19722, 20459), so things are moving and maybe even they would consider an official Flatpak package. |
Managed to scramble a fix (and a Muse Sounds Manager Flatpak package along the way, just for the fun of it!) for this issue. Currently requires musescore/MuseScore@be54d1f (I backported it to |
Looks like the commit has been merged on April 9. Now a new Flatpak has been released with 4.3.1, does it contains the fix? The Muse Sampler library is still "not found", but is there some manual tweaking that could make it work? (like copying or lining some files?) |
It appears that the commit didn't make it to 4.3.1 for some reason. It has been on |
Are you sure? Consider handbrake (via flatpak list):
People can optionally install the IntelMediaSDK add-on which adds certain features to Handbrake. Couldn't Muse Hub be released as a similar add-on? |
AFAICS the commit is present in the latest 4.4.2 branch, so this should now be usable
Do you have any update on this? Okay, I found a source, I'll test MuseScore compiled with |
Hi all, we now provide a .tar.gz build of Muse Sounds Manager (v2) with the built in auto updater disabled. It can be found here: http://muse-cdn.com/Muse_Sounds_Manager_x64.tar.gz Version is 2.0.3.659. The above url will always point towards the latest version, but we're looking into providing stable version links as well. I'm happy to help out if any support is needed for building a flatpak. I have no experience with this. Hopefully the tar will be useful. |
That's a problem because the checksum will change. BTW we support aarch64 too. |
flatpak version in flathub for automatic updates would definitely be preferred (as long as the sandboxing doesn't prevent the 2 apps from "talking" to each other...). I'm using the deb as the moment, don't think I have used any app installed using a tar.gz in the last 15 years to be honest. |
I currently have the MuseScore 4.0 Flatpak installed. I have downloaded the muse-hub and Muse Sounds, but the sounds are visible only in AppImage version.
I had a look at the PR comments with the 4.0 update – yet I expect it is a highly important feature and it would not be good to give it up easily.
I'll leave this issue here. It would be best if the Flatpak maintainers could reach out to MuseScore developers to find a way to discover the resources from muse-hub.
Currently even if I grant permissions to all files via Flatseal, Muse Sounds are not discovered.
Also: I believe that as we have this (unfortunately closed-source) Muse Hub thing, creating another flatpak of it might be the good idea.
The text was updated successfully, but these errors were encountered: