AppImage for MusE (experimental)

[kybos]

Hi all,

After a long and painful struggle I managed to create an (apparently working) AppImage .

I feel it's important to offer some possibility especially for Debian/Ubuntu based system users to get a more current version of the software than that offered by the official repos (which is usually pretty outdated).

It would be nice if interested people could check it out and test it on their various Linux systems, and perhaps give some feedback.
It will not run on very old systems (like Ubuntu 16.04), because of missing dependencies for MusE itself.

Of course it's not meant for production work, it' just a snapshot of the current master. Coding changes were necessary to make AppImage creation work, so it can't be done for the current stable release.

https://github.com/muse-sequencer/muse/ ... 4.AppImage

Cheers
kybos

[oscillator]

This is a really good idea I think!

I've tried it on my standard Debian 10 Buster/XFCE4 laptop, and it runs without any issues. Starts quickly too. I've tried to open a couple of old projects, edited softsynths, brought up editing windows etc. Without issues.

Great work!

BTW I use the current master for all my production work. Can't go back to the time before the tabbed interface!

[kybos]

Thanks for the testing, sounds promising.

BTW: We are planning a new release (3.2?) to come out very soon, so there should be an "official" version with all the recent UI rework before long.

[oscillator]

BTW: We are planning a new release (3.2?) to come out very soon, so there should be an "official" version with all the recent UI rework before long.

Nice!

[kybos]

I forgot to mention (for people not acquainted with AppImages):
You must make the file executable after download. On CLI:

> chmod +x MusE-master-x86_64.AppImage

Or set the flag in your preferred file manager.

[oscillator]

Is the idea to set up some kind of automatic production of daily (weekly?) AppImages?

I download the master about once a month and compile, which isn't that complicated, and I get all the good new stuff. But an AppImage would be easier for many people, of course.

Out of curiousity, what code changes were necessary?

[kybos]

Is the idea to set up some kind of automatic production of daily (weekly?) AppImages?

Yes, that was exactly the idea. And of course I will create AppImages for the releases too.

Out of curiousity, what code changes were necessary?

The code must be made "relocateable", i.e. paths to internal resources (libs, themes etc.) must be adjusted.

[oscillator]

Is the idea to set up some kind of automatic production of daily (weekly?) AppImages?

Yes, that was exactly the idea. And of course I will create AppImages for the releases too.

Sounds great! Thumbs up!

[oscillator]

@kybos, I found a small problem with the AppImage (using it right now for a new song, thought it would be a good test):

In the MIDI piano roll editor, the Plugins menu with the Python scripts is not shown.

[kybos]

That's not the AppImage.
I removed this menu in master because it was a duplicate of Midi->Plugins.
It should be called Scripts anyway IMO, to make it clear that it contains the scripts from the global and user scripts/ folder.

[oscillator]

I removed this menu in master because it was a duplicate of Midi->Plugins.
It should be called Scripts anyway IMO, to make it clear that it contains the scripts from the global and user scripts/ folder.

Ah, I see! And I agree that it should be renamed.

[pitaraujo]

Thanks. I have the AppImage running in Manjaro side by side with version 3.1.1.2.

[garvalf]

thanks for this AppImage! It's the way to go for releasing software on Linux! Packages in distribution are cool, for sure, but it's great for having up to date software on our linux systems.

Muse is pretty easy to compile, however I find it even more convenient to download and use the appimage now!