MuseScore Nightly ARM

• Mar 27, 2016 - 16:16

Hi, yesterday I received a file with with MuseScore Nightly from ericfontainejazz. Thanks for it!! I tried to execute it in Arch Linux in a Terminal, but no luck so far. It tells me: error while loading shared libraries: libfuse.so.2: cannot open shared object file: No such a file or directory.

Should I copy the nightly file to a specific location? Can you please help?

Thank you

Comments

• Mar 27, 2016 - 23:16

Hi Dusan,

Thanks for this information. AppImages should work "right out of the box" on pretty much all Linux system, but Arch is a bit of an exception because it doesn't include many libraries. It looks like you need to install FUSE to get it to work, but on most distributions FUSE would be included by default. I don't have Arch myself, but I think the command you need is:

pacman -S fuse

If any other libraries are missing then we can put them inside the AppImage so that they are provided for you, but FUSE is needed to gain access to the files inside the AppImage so it needs to be installed on the system separately.

Once fuse is installed you can check to see if any other libraries are missing by running this command from the directory where the AppImage is located:

./MuseScore*.AppImage check-depends > arch-dependencies.txt

This will create the file "arch-dependencies.txt" in the same directory as the AppImage. You can then upload this file here on the forum (click "File attachments" when you go to leave a comment).

Reply

• Mar 28, 2016 - 16:54

Hi Peter, thank you for your advice. I have installed Fuse, then I had to make it executable by sudo chmod 777 fuse and then I executed the nightly file and it worked fine. I have 3 things now:

1/ I have actually downloaded 2 nightly files from Eric's given link, the very AppImage file and also this one: MuseScoreNightly-201603261315-armcross-9b68d75-armhf.AppImage.zsync Should I use also the second one?

2/ Just an information: today I reinstalled Arch Linux on my tablet, installed stable MuseScore from repos, but the stable MuseScore doesn't launch at all for some reasons. The nightly MuseScore launches.

3/ I have noticed that in the nightly MuseScore in the transposing instruments (like Tenor Sax) all input notes are colored in red, even though they are not out of range. Where can I report these minor problems? Here?

Many thanks

Reply

• Mar 28, 2016 - 17:57

Are you sure the notes are not out of range? You;ve checked the clef and the status of the Concert Pitch button and are positive these are what you expect? Can you check the same score on another computer to see if this is ARM-specific?

If you continue to have issues with this, probably best to start a new thread and attach the specific score you are having trouble with and explain where the problem is.

Reply

• Mar 28, 2016 - 21:07

Thank you Marc for your reply. I have made a new thread here: https://musescore.org/en/node/103906

What about the 1st question in my comment above yours? Can you please find out? It is probably a question to ericfontainejazz.

"EDIT: I cannot make the Jack server run in the MuseScore nightly version - it used to work in the stable version, though. The problem will be probably connected with the fact that the MuseScore stable version downloaded from a repo cannot be launched at all in the updated version of Arch Linux. When executing the stable version of MuseScore in Terminal, it tells me: ./mscore: error while loading shared libraries: libQt5QuickWidgets.so.5: cannot open shared object file: No such file or directory

Can you please advice how to fix it?"

Thank you

Reply

• Mar 29, 2016 - 00:14

1/ You don't need the .zync file, it doesn't do anything currently. It will be useful when we have a mechanism for automatic upgrades in place, but we haven't got there just yet.

2/ It looks like the Arch package is missing a dependency. Try installing the package "qt5-declarative" via pacman.

3/ Thanks for the information about the transposing instruments. It's possible that @ericfont has already noticed this and fixed it, or will be able to fix it now without much difficulty. If you spot any more problems then just mention them on this page for now. If we can't fix it immediately then we'll ask you to make an issue on the tracker.

Please do run this command and upload the resulting file to the forum. You'll need to run it from the directory containing the AppImage. (Use "cd" to get there.)

./MuseScore*.AppImage check-depends > arch-dependencies.txt

This checks that the AppImage has everything it needs to work properly. It would be great if you could also try running some of the plugins from the plugins menu and report here if any of them fail, ideally with any messages that were displayed on the terminal when it failed.

Reply

• Mar 31, 2016 - 12:12

Hi, attached please find the text file with dependencies.

I have installed "qt5-declarative", but still no luck, MuseScore from a repo doesn't start, now it says: ./mscore: error while loading shared libraries: libQt5WebKit.so.5: cannot open shared object file: No such file or directory.

I remember that the older stable MuseScore from a repo was using Qt5.5.1 and launched Ok. The debug version of MuseScore used Qt5.5.1 and launched Ok. The present nightly MuseScore uses Qt5.3.2 and launches Ok. The present stable MuseScore (which doesn't start] is installing Qt5.6.0 and doesn't launch. Also the errors are always around Qt. So it looks that Qt is again the problem. What if I tried to install the previous version of MuseScore? I mean to downgrade? I tried to find on net how to downgrade, but did not understand, sorry. Can you please help with the downgrade? I would love to hear MuseScore play again:-)

Thank you

Attachment Size
arch-dependencies.txt 4.16 KB

Reply

• Mar 31, 2016 - 13:51

Regarding musescore from arch repo, I believe that the musescore arch linux package dependency list is in error, becuase qt5-webkit should be a dependency of musescore, and automatically installed if musescore is installed. I'm able to reproduce the same error you had. If I first uninstall qt5-webkit and musescore, and then try installing musescore, I notice that it never asks to install qt5-webkit (but it should):

sudo pacman -S musescore
resolving dependencies...
looking for conflicting packages...
Packages (1) musescore-2.0.2-3
Total Installed Size:  52.53 MiB
:: Proceed with installation? [Y/n]

And then if I try to execute mscore without qt5-webkit, I get:

[e@m4500 ~]$ mscore 
mscore: error while loading shared libraries: libQt5WebKitWidgets.so.5: cannot open shared object file: No such file or directory

After reinstalling qt5-webkit, mscore from repo is able to run just fine.

ADDENDUM: It seems that this packaging bug has already been reported to arch linux by someone else, just yesterday! https://bugs.archlinux.org/task/48760?project=5&cat%5B0%5D=33&string=mu…

Reply

• Mar 31, 2016 - 17:38

Yes I noticed, but it is hard to respond to multiple things that are unrelated at the same time (it would have been easier to respond if you created a separate forum issue for the issue regarding the arch linux musescore package not having qt5-webkit, since that has nothing to do with ARM or Nightly AppImages).

Regarding jack, I'm not sure that Jack has really been tested on the AppImages. We also don't have plain Alsa sans-Pulse working on the AppImages. Maybe I should have tested these things...but I have to recongure my computer as a Alsa sans-pulse or Jack sans-pulse.

Anyway, in my current setup on ArchLinux x86_64 Mate w/PulseAudio, I am noticing a hang for a few seconds when go to preferences and select jack:


jackd 0.124.1
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details


JACK is running in realtime mode, but you are not allowed to use realtime scheduling.
Please check your /etc/security/limits.conf for the following line
and correct/add it if necessary:

  @audio          -       rtprio          99

After applying these changes, please re-login in order for them to take effect.

You don't appear to have a sane system configuration. It is very likely that you
encounter xruns. Please apply all the above mentioned changes and start jack again!

and then after a few seconds, it apparently times out and reports:

JackAudio()::init(): failed, status 0x11
no JACK server found
no audio driver found
Cannot start I/O
sequencer init failed

and I of course don't have sound until I revert back to pulse. So I think I need to make a seperate issue for this and look into...maybe trying on a live cd with a jack-only distro like KXStudio...I'll try that now and report back...

Reply

• Mar 31, 2016 - 18:37

Tested Lubuntu x86-64 live cd, which doesn't have pulse audio, and I find that audio works after switching to ALSA. So I suppose these x86* AppImages do work with ALSA-only systems... (although I think that's not true for the arm images...)

When I try Jack in Lubuntu, I don't actually get a hang (like I got on my arch linux x86-64 machine), but I get a similar error output, only difference is status is "0x1" instead of "0x11":

JackAudio()::init(): failed, status 0x1
no JACK server found
no audio driver found
Cannot start I/O
sequencer init failed

Of course audio won't work now with jack selected, since Lubuntu live doesn't have jack.

Reply

• Mar 31, 2016 - 18:53

ok, no worries, yes really I was just saying it is hard for me to respond to multiple things simultaenously in one message.

So if apparently jack works on arm, then I guess the issue we need to tackle is how musescore behaves if jack is not actually installed but user selects jack in preferences?

Reply

• Mar 31, 2016 - 22:35

Well, I am not sure if I understand. I think jack is installed in my chroot - I think I install it by jack2 package or qtjackctl package or not? As a test I can run qtjackctl and make the jack server active by pressing start button for jack server - if everything goes well, qtjackctl says: jack server is running.

For MuseScore it is important that jack2 package (maybe also qtjackctl, I am not sure now, but jack2 probably is enough) is installed and then Play button becomes active and Synthesizer can be opened (before making the Play button active the Synthesizer could not be opened). So I think MuseScore communicates with jack server, even though there is no sound going out from it.

The debug MuseScore also communicated with the Jack server. What about just fixing the chord display and transposing instruments in the debug version, because jack works here?

"EDIT: Or just fixing enormously long stems in the repo MuseScore, where everything else is fine, would not be possible?"

Thank you

Reply

• Mar 31, 2016 - 23:33

I don't think I fully understand what you are saying:

>> "The debug MuseScore also communicated with the Jack server. What about just fixing the chord display and transposing instruments in the debug version, because jack works here?"

That debug binary I sent you a month ago is out of date, and was just a test. When 2.0.3 release comes out on arch linux (as well as every other linux distro that ships 2.0.3), the binary you get from the arch linux repo will have these bug fixes regarding stems and transposing that we fixed.

Now the problem with the Jack (& alsa) in the ARM AppImage exists because it was difficult enough to get the ARM AppImages working in the first place, so I never really got down to even testing all configurations. The ARM AppImages do work with pulseaudio, which is the default anyway. But if you are patient, arch linux is usually very quick about updating their packages, so you should be able to download 2.0.3 release from the repo soon (although I don't know when exactly). In the meantime I'm going to have to test out the same configuration you are using: arch linux chroot inside android using jack server. But thanks for testing this stuff out.

There is also another library bug which I couldn't get working with my current ARM AppImage Dockerfile setup: any plugins which open a new window will cause a crash. I'm thinking of fixing this by compiling and including qt 5.6 in the AppImage, instead of using the older qt 5.3.2.

Reply

• Apr 1, 2016 - 00:08

I wanted to see how the AppImage works in a jack-only distro on x86-64, so I booted a live cd of KXstudio, and I notice that the AppImage won't work with jack. Saying similar messages 

Fialed ot open server
JackAudio()::init(): failed, status 0x11
no Jack server found
no audio driver found
cannot start I/O

If I then install the official KXstudio musescore packge, I'm able to run jack with that package just fine. So clearly AppImages don't work with jack, currently, x86 or arm.

Reply

• Apr 1, 2016 - 07:11

including qt 5.6 in the AppImage
I believe it's a bad idea. You will have other problem (Webkit is deprecated for example...). So it's better to stick with 5.3 or ideally move to Qt5.4.2 which is the version we use for Windows and Mac and so recommend for any other build.

Reply

• Apr 1, 2016 - 15:42

Regarding the Qt versions in my tablet: my current MuseScore repo version for ARM already uses Qt5.6.0 and it is MuseScore 2.0.2. It is neccesary to install qt5webkit to make MuseScore start and then everything is fine.

With Qt5.4.2 in my tabet I have troubles, because keyboard works incorectly. With Qt5.3.2 Jack doesn't work, which is the only way I can make MuseScore play a nice sound, Pulse is choppy even with a low sound quaity. Qt5.5.1 is fine, both keyboard woks fine and Jack is working.

So for my tablet with not powerful processor only Qt5.5.1 and Qt5.6.0 is is good. If the AppImage cannot work with it, no peoblem, I will wait for the MuseScore 2.0.3.

Thank you

Reply

• Apr 1, 2016 - 15:50

arch linux always has latest packages, which is why it already has qt5.6. I believe that there have been quite a few qt-bug fixes regarding arm/android/chroot. Like I said, I'll probably update the arm app images to use latest qt right after the 2.0.3 comes out, but I don't want to change that now.

>> "With Qt5.3.2 Jack doesn't work"

Ok, but I'm not sure that is Qt's fault, but rather possibly the fact that Jack doesn't work with AppImages currently.

Reply

• Apr 1, 2016 - 16:12

"With Qt5.3.2 Jack doesn't work"
Yes, it is not clear what is the reason. Only right now I noticed that Jack did not work after only installing jack2 package, but it needed to start qjackctl to use a "dummy" driver and start the jack server with a button of the qjackcltl. And the package is called qjackctl, so perhaps "q" in the name has something to do with "qt"?

Reply

• Apr 1, 2016 - 16:18

well jack always requires you to start the jack server before using apps with it.

qjackcontrol starts a server and communicates with the server uses Qt for displaying a nice GUI, so you don't have to manually type hard-to-remember terminal commands or use text file configs.

Reply

• Apr 1, 2016 - 17:30

Ok, I see. So I will wait now for 2.0.3 from a repo and this should have fixes and Jack working. In the meantime I will check again working with Pulse just in case it is better for my tbl with Nightly.

What about the Synthesizer inside MuseScore? When I use jack, the Play button becomes active and I can access the Synth. I see volume bar working hard when playing a score, the volume peaks are just great. But I don't hear any sound... So it looks like MuseScore is not able to use the soundfonts

When I needed to play a midi file in the chroot, I needed to make a configuration for soundfonts. I downloaded Timidity player with freepats soundfont. At the end of the installation process I was advised to copy /etc/timidity++/timidity-freepats.cfg to /etc/timidity++/timidity.cfg. Then somebody from Archlinux ARM advised to copy "dir /usr/share/timidity/freepats" and also "source /etc/timidity++/freepats/freepats.cfg" to the file mentioned earlier. What about MuseScore and soundfonts? Could such a writing help? Is there some MuseScore configuration file where to write perhaps something about soundfonts?

Thanks

Reply

• Apr 1, 2016 - 17:45

>> "When I use jack, the Play button becomes active and I can access the Synth. I see volume bar working hard when playing a score, the volume peaks are just great. But I don't hear any sound... So it looks like MuseScore is not able to use the soundfonts"

No, that is the incorrect conclusion. The fact that you see the volume bar moving means that indeed yes the soundsfonts are working. Everything is probably working correctly on musescore's binary. If you are using a dummy jack server, then the audio is being sent to the dummy jack, and then thrown away by the dummy server.

Regarding AppImages, note that as I said before, I don't think we ever setup jack to work properly with jack...I don't know are you still using jack here.

>> "When I needed to play a midi file in the chroot, I needed to make a configuration for soundfonts"

I don't understand this paragraph. Are you still using the dummy jack server? Or are you using a real Jack server? Are you hearing audio? Note that musescore has a default basic soundfont that should be working out of the box.

Reply

• Apr 1, 2016 - 21:55

Sorry for misunderstanding. In the previous comment I was speaking only about the MuseScore from repo where I can use jack. In AppImage I was not able to make jack run.

Reg. the last paragraph: For this I think I don't use any jack. I have just installed a timidity++ player, then soundfonts, the command was "timidity{++,-freepats}. Then I had to make a configuration for the installed soundfonts which I described before. And now I can play any midi file in the chroot and the sound is great. I mentioned this because I thought that perhaps some configuration reg. soundfonts could have been done for repo MuseScore so that I can hear sound from MuseScore, because I hear a great sound from timidity++ player. So I believe there must be some way for repo MuseScore play nicely when timidity++ (and also Qsynth using soundfont-fluid package) plays great.

Reg. the second paragraph: So the sound goes to the dummy jack server and then is thrown away. Where that I don't hear anything? For what is Jack audio? I ask not to torture you, but to try to help the repo MuseScore's synth hear.

What is actually the mechanism in repo MuseScore in working with dummy jack server? Is it this: MuseScore produces jack midi, this goes to dummy jack server and it sends it to Qsynth?

Thank you

Reply

• Apr 1, 2016 - 22:37

I haven't been following this completely, so maybe I'm missing something obvious, but why are you messing with timidity or installing soundfonts at all? Are you saying that by default, just using the AppImage version MuseScore with all default settings you aren't hearing sound? You should be. So if you aren't hearing hearing sound, try running with "-F" to revert to factory settings and see if that restores sound (you might have bad settings left over from a previous installation that is causing problems). Again, don't mess with timidity or jack or anything at all - you aren't supposed to have to do *any* of that. Sound should just work right out of the box, and it does for me.

If you still don't have sound after the "-F", then let's try to work on figuring out why.

If I'm misunderstanding and you do have sound from MuseScore but have some special reason to be wanting to use jack or timidity, then never mind :-)

Reply

• Apr 1, 2016 - 23:40

Unfortunately I have no sound coming from repo MuseScore, there was never any sound, -F doesn't help, please note that I use chroot in an Android ARM tablet. "EDIT: The only partly working solution is to mark Jack in Preferences." When using Jack in Preferences, the Play button is active, I can access Synthesizer, I see volume peaks when a score is played, but no sound out.

The reason why I mentioned timidity++ is that something similar what I did with timidity might help MuseScore to play a sound. The story is that I could not hear any midi file played in my chroot so I downloaded timidity and had to make a additional script for soundfonts used by timidity and then finally I heard timidity play a midi file. So I was wondering that perhaps some additional script for the MuseScore soundfonts (or anything else) may help to hear MuseScore play, even though MuseScore should play out of a box. If timidity plays a MIDI file and also Qsynth and other synth play nicely in my chroot, why not the synth from MuseScore?

The only way I can make MuseScore hear play a score is to run a dummy jack server, then connect MuseScore using Jack Connection Kit to a Qsynth and then I hear a nice sound. In my tablet I did not find any other way to hear MuseScore play a score nicely - Pulseaudio is choppy. How did you make MuseScore play?

Reply

• Apr 2, 2016 - 00:04

If you aren't getting sound from MuseScore, you need to address that first. I am not sure why you are running within a chroot - perhaps you could start by explaining that? I am on a Chromebook so I run under a chroot as well, in order to have a full working Ubuntu environment (the "crouton" scripts). As I recall, I needed to do a few things to get sound working in MuseScore, like make sure /dev/snd/seq existed and had write permissions. Maybe something with ALSA too. I actually have to run "chmod a+w /dev/snd/seq" every time I reboot. Or at least I used too; maybe it would work without that by now, but I still do it out of habit. Whatever I did with ALSA setup, I only did the once, so I don't remember what it was or if it turned out to actually have been necessary. Or maybe it was "cras" (a Chrome-specific process, I think) that I had to mess with once. Sorry, it was a couple of days of trial and error, and aside from /dev/snd/seq, I just don't know what ended up being the actual solution and what was just spinning my wheels.

As for JACK, that is not something you can just enable in MuseScore exepct to hear results from. You need to actually install JACK and configure it to accept MuseScore as an input device and something else as an output device, or something like that. So when you talk about running a "dummy jack server", there is nothing "dummy" about it - you need to actually run JACK if you want to use it. Sounds like you got it to work, then, which is great.

Reply

• Apr 2, 2016 - 06:06

theres a lot of stuff going on in this thread, and since different configurations start getting talked about, it starts to get confusing.

Note, audio in an android chroot is not a simple matter of having write permission to /dev/snd/seq, because the chroot is much more isolated, so can't get direct access, to my knowledge. There is also no x-server in android. The solution I found worked nicely was using X-Server XSDL app which sets up a xserver and a pulse audio server in the android app, which you need to point musescore to use via environment variables. DusanP was using Jack and is going over VNC, an alternative solution. (I don't know why using Jack and not alsa, since the VNC should copy the audio either way). But the AppImages don't seem to work well with jack anyway, cause I don't think we tested. Anway, I'd suggest to DusanP if using VNC to just use ALSA output (at a low bitrate) in musescore, and see it works over VNC.

Reply

• Apr 2, 2016 - 18:23

Hi Eric, with my VNC viewer I cannot use Alsa, because when in Preferences I mark Alsa, the Play button in not active and I also cannot access the Synth - simply MuseScore doesn't communicate with Alsa in my tablet (and also no communication with PulseAudio and Portaudio). The only working solution in my tablet is mark Jack in Preferences (then Play button becomes active and I can play a score), start Qsynth and connect MuseScore with Qsynth using Jack Connection Kit (qjackctl package).

The above mentioned works only in repo MuseScore or debug version of MuseScore. In Nightly MuseScore (AppImage file) nothing works for me to play a score - the Play button is always inactive. It is all with the use of VNC viewer.

If I used X-server, I could use PulseAudio (probably all repo, debug version or nightly), but the sound is choppy even with a very low bitrate and the sound quality (due to the low bitrate) is very low.

Reply

• Apr 2, 2016 - 18:03

Hi Marc, I run chroot, because I don' t know any other way how to run editable MuseScore in an Android tablet. Is there any other? I have Arch Linux chroot here.

/dev/snd/seq doesn't exist in my files, and this is why there are many error messages. But how to create it? In /dev/snd/ I have only: 4 files: controlC0, pcmC0D0c, pcmC0D0p and timer.

By "dummy jack server" I mean a jack server running on driver called "dummy" (within Jack Connection Kit, which is qjackctl package). So do you say that when I enable Jack in the MuseScore Preferences, have a working Jack server (Jack Connection Kit runs the server), then MuseScore will not play itself? Why is Jack audio in the Preferences then?

Thank you

Reply

• Apr 2, 2016 - 18:27

OK, I know nothing of Android tablets, so I can't be of much help here. I guess the basic principle is similar to why I run a chroot on my Chromebook - so have access to a full Linux environment by a series of hacks the product wasn't really designed to handle. Sounds like the chroot environment on your tablet is more crippled than the one on my Chromebook, which is unfortunate.

JACK does not make music by itself; it is just a way for multiple programs to communicate with each other. Simply running JACK and expecting to get sound is kind of like taking a MIDI keyboard that has no built-in sounds, plugging a MIDI cable in to the back, and expecting to get sound. You still need to plug the other end of that cable into something capabke of making sound. JACK is like the MIDI cable; it isn't the thing that makes sound.

You can can enable JACK in the Musecore's preferences, which basically tells MuseScore, "start communicating with JACK". But you have to actually have JACK running in order for this do anything, and you have to something connected to the other end. That is, you need to be running JACK (the cable), *and* a program capable of making sound, *and* you need to have all three programs (MuseScore, JACK, and the sound-producing program) configured to talk to each other in this way (that is, you have to actually plug the cable in).

If Timidity++ knows how to communicate with JACK in that way, and you are able to get sound out of Timidity++ on your machine, then great - problem solved. Just run JACk, tell MuseScore to send output to JACK, tell Timidity++ to get input from JACK, tell JACK to make the connections. Assuming JACK is indeed working with MuseScore, and that is what I guess isn't clear, because it isn't clear if you've actully set up all this or if you are just thinking that running JACK is good enough.

Reply

• Apr 2, 2016 - 23:10

Ok Marc, I understand: MuseScore - Jack - some external Synth. It seems to me that as the 3rd part of the chain it can be also MuseScore, though: MuseScore sends signal to jack server and jack should send it back to MuseScore to play sound with a MuseScore synth. I may be wrong, sorry. In the Jack Connection Kit I see this possible connection:

for Midi (see attachment Midi): Output: mscore midi, Input: fluid-midi (which is external Qsynth) or mscore-midi (the MuseScore synth?). MuseScore synth doesn't produce any sound, Qsynth plays.

It seems to me that Jack can work also differently with MuseScore, because in the Jack Connection Kit I see this possible connection:

for Audio (see attachment Audio): Output: mscore (MuseScore Jack audio?) or system, Input: system (left playback or right playback);

So perhaps one day it will be possible to have in a tablet like mine just MuseScore "EDIT:(maybe plus Jack Connection Kit, but very likely this would not be necessary)" and it will play itself either using Jack Audio connections or Jack Midi connections (see the possible connections for Audio or Midi above). At present it is not possible.

When I start MuseScore in the Terminal (with Jack marked in the Preferences), I receive errors. I don't understand most of them, I understand only one: jack is looking for a file "doc_C.qhc":
/usr/share/mscore-2.0/manual/doc_C.qhc
and cannot find it:
cannot setup data for help engine: Cannot open collection file: /usr/share/mscore-2.0/manual/doc_C.qhc
because the file is not there. I am not sure if this is of any importance.

Well, it would be great if I did not have to use 3 applications to play a score (MuseScore, Jack Connection Kit and Qsynth), because starting and configuring all the 3 applications is not so comfortable and the tablet battery is not very powerful, but I can manage.

Thank you

Attachment Size
Midi.jpg 446.69 KB
Audio.jpg 518.03 KB

Reply

• Apr 3, 2016 - 14:01

You don't need 3 applications to play a score... Using Jack is absolutely optional. Go to Edit >Preferences and choose anything but Jack and you will need to other software but MuseScore to hear some music. if your chroot can use ALSA, do use alsa, same if it can use Pulse Audio.

Also, using "Jack" only is misleading. MuseScore can use Jack MIDI, and in this case, MuseScore sends midi to Jack, and then Jack sends it to a synthesizer. But Jack can also receive audio generated by MuseScore and sends this audio to the system.

In any case, again, you don't need Jack to have playback in MuseScore. If you have no use of Jack for adding effects (Jack audio), or use external synthesizers (Jack MIDI), then don't use jack.

Reply

• Apr 3, 2016 - 17:35

Hi, please note that I use MuseScore in Android tablet chroot. Well, I am afraid I have to use 3 applications, I have not found any other working solution in my tablet so far (and it has been weeks of searching). You can see the reasons in this discussion earlier and also in this issue somewhere from the middle: https://musescore.org/en/node/96256

Quickly summarized: When using VNC viewer, when I choose Pulseaudio, Portaudio and Alsa in the Preferences, the Play button remains inactive. When choosing Jack, the Play button becomes active, but no sound is going out from MuseScore. For this reason I must start Qsynth and connect it with MuseScore using Jack Connection Kit. In the Jack Connection Kit (see the attachments in the previous comment) I see that MuseScore generates Jack audio, but after connecting it to system no sound goes out. I also see that MuseScore generates midi and this could be connected back to MuseScore (to its synth probably), but after connecting no sound goes out. Only if I connect MuseScore midi to Qsynth (fluidsynth-midi), I can hear sound (see the attachment in this comment).

When using X-server viewer, Pulseadio works. Unfortunately in my tablet the sound is choppy. Even with low bit-rate (resulting in low quality sound) the sound is choppy or often choppy.

So there are options not to use 3 applications, but unfortunately they don't work. Or would you advise what to do to make MuseScore play itself in an Android chroot? Perhaps adapt some scripts in MuseScore for Android chroot?

Attachment Size
MuseScore_Jack.jpg 486.08 KB

Reply

• Apr 3, 2016 - 18:28

Qsynth uses Jack server (see the attachment in the previous comment, this a picture from a Jack Connection Kit where there are only applications using Jack). "EDIT: Qsynth is here displayed as fluidsynth-midi."

What do you mean by "is Jack talking to ALSA"? In Qsynth I choose for midi driver: Jack and for audio: ALSA. Is this what you meant?
Thank you

Reply

• Apr 3, 2016 - 21:54

I think the best way to have non-choppy low-latency audio in android is #104636: implement OpenSL ES audio driver backend for android so that not going through multiple layers of overhead. This might also mean I need to figure out how to get AppImages to run in android without having to install a full linux distro inside of a chroot. As I mentioned there, I'll first try getting a simpler AppImage like leafpad to run inside android. Hopefully will work if get all library dependencies in the AppImage, and might have to link with Android's libbionic instead of GNU's libc. Also I would want musescore to work nicely when not using a window manager #104641: be able to close all popup windows when running musescore without window manager so can directly use an android X-Server like XSDL.

Reply

• Apr 4, 2016 - 10:42

It sounds great.
In the meantime I have downloaded TimGM6mb soundfonts for MuseScore to use it with PulseAudio, now I try to Add it, but it doesn't appear in the Synth window and I cannot find it in the chroot. Do you have an idea where it is stored in the chroot? Thanks

"EDIT: I have already downloaded the soundfont to a Desktop and saved it in a chroot in a location that I know. Then Add it in MuseScore, unfortuantely the sound on 4000 irregular, with 8000 already choppy."

"EDIT: I have also noticed that when using Pulseaudio with X-server, I can use the hardware Volume of the Android tablet, whereas if I use VNC and Jack (which connects MuseScore with the Qsynth running on Alsa audio driver), I cannot use the hardware Volume of the Android tablet, I must use the software buttons within chroot."

Reply

• Apr 4, 2016 - 18:50

Like I said I think need to remove these multiple layers of overhead in order to get good audio on android, by implementing OpenSL ES. I would say until then, you will just have to tolerate the irregular/choppy audio.

Regarding the hardware Volume button only working with Pulseaudio with X-Server, and not VNC, that has nothing to do with PulseAudio versus Jack/Alsa or even X-Server vs VNC. Rather, the lack of hardware volume button support is probably a limitation of whatever VNC app you are using. Apparently the hardware volume button is implemented by Xserver-XSDL.

Reply

• Apr 11, 2016 - 23:08

Hi Dusan,
2.0.3 has been released now so you should stop using the nightly or development builds (if you haven't already) and get the stable version from the Download page. Of course, you are more than welcome to continue testing nightly builds, but you shouldn't use them for your regular score editing because they are likely to cause compatibility problems. Never save a score using a nightly build, at least not if you want it to work in a stable build!
Thanks for your persistence in getting MuseScore working on ARM!

Reply

• Apr 12, 2016 - 21:57

Hi Peter,
Thank you for letting me know. I actually knew that MuseScore 2.0.3 has been released, because I was offered it on my Desktop and it is already installed on my Desktop. I checked in Arch Linux a few minutes before I read your comment for the MuseScore 2.0.3 for ARM using "sudo -S musescore" and it told me: warning: musescore 2.0.2-3 is up to date --reinstalling
so I did not re-install the 2.0.2-3 version in my tablet.

Only when I used "sudo pacman -Syu", it told me that there is musescore 2.0.3, so I have already installed it. And everything which did not work previously, works now: transposing instruments, audio (Pulseaudio and Jack), stems of notes are correct, chords displayed correctly - thank you very much!

Reply

Do you still have an unanswered question? Please log in first to post your question.