Setting-Up MuseScore on the Raspberry Pi

Thanks for that information on soundfont installation. Yes, I have:

/home/pi/Documents/MuseScore2/Soundfonts/TimGM6mb.sf2

I've now also read one or two other posts on the topic, and have clicked the 'Add' button in the Synthesizer window, highlighted the new sfont in the resulting pop-up window, clicked on it and seen it install as the first entry in the Synthesizer window.

Sadly, on try-out the new mini-footprint sfont makes little or no improvement to playback.

With the new sfont, the system monitor memory use is much the same as before, circa 35% and when playback is in operation one of the 4 cores is running at 100% while the other 3 range 0-15% with the 100% load being swapped to a different core every few seconds.

Interestingly in terms of work load, Firefox appears to run quite acceptably on RPi3\Ubuntu, with the load spreadout over the 4 cores.

Also it occurred to me that I should experimenting with other audio for comparison. Thus far a downloaded mp3 file has played without complaint... but will try out more over next few days.

Best regards, Philip.

Not sure about trying another Linux variety for many reasons:

1) Ubuntu-MATE (16.04) which I have installed is the version recommended on the MuseScore website for running MuseScore 2.0.3 on RPi2/3. (I believe Raspian doesn't have everything MuseScore 2.0.3 needs. I do have MuseScore 1.3 running on Raspian but that is nowhere so good as ms2.)

2) I thought Ubuntu-MATE is a relatively light weight distribution.

3) It has been tough getting this far, I wouldn't relish doing it all again.

4) Early days yet to be thinking of changing the system, it makes sense to explore the MuseScore I have before moving on. The score display is excellent quality. I'm gradually testing out various import and export features... so far midi import and export, PDF export and xml export are working fine.

The major glitch, playback, appears to result from the load the synthesizer places on the system. Without playback, the system monitor shows the 4 cores working in a similar manner to when other programs are running. It is only when playback is attempting to function that the 100% loading appears. However, I don't know enough about computers to tell whether this is a 'red herring' or the source of the playback problem. The pattern of core usage shown in the system monitor while in playback mode, also occurs in the first couple of minutes after switching on the computer but otherwise is not present. Attached (hopefully) are four png images of the system monitor.

Assuming there isn't enough horsepower to run the synthesizer my next move is to try and find out about 'JACK'... which I hope means I can link up a MIDI module for playback?

Best regards and thanks, Philip.

shoogle,

Thank you for the post about your upgrade and the work you have done. Unfortunately I don't feel confident (or competent) enough to test the software. I'm new to Linux; indeed, until reading your post I had never heard of PPA. Thus I fear my ignorance might well contrive to produce an unhelpful outcome for all.

Best regards, Philip.

Thanks for that thought. I have tried playback both with and without the Navigator, but no improvement.
Best regards, Philip.

shoogle,

Now have backup SD card copied and have installed the PPA version of MuseScore upon it.

The PPA musescore appears to be a good step forward on the RPi3... more testing to be done. Playback is much improved and the menus seem quicker to display (not totally sure about the menus).

For playback the top listed soundfont on the Fluid tab is TimGM6mb.sf2 which I assume the PPA version picked up from the earlier AppImage installation, and the I/O tab shows PulseAudio.

For tests, after starting up the computer I load mscore alone -- no other programs running -- load my test score (four independent parts recorders & viol, 100+ measures), don't use the navigator, select the first note, select looped playback and enter playback mode. Now with the PPA version I get good playback sound, no cracking, popping and stuttering; but as playback continues, for maybe 1,2,3 loops... sooner or later it freezes. I can unfreeze playback by jiggling the volume in the Sound Preferences window and playback will continue again (though perhaps without the play cursor).

My (most un-expert) impression is that the PPA version is falling just within the playback capacity of the RPi3 (in contrast to the AppImage version which is beyond it). Indeed, the moment I load the System Monitor for a screen shot, playback freezes. Attached is a screen shot covering playback with the PPA version... which does show a different (less stressed) pattern of core use. However, the playback quality is low for the period covered by the screen shot because both the System Monitor and Screen shot Utility are also running!

When closing mscore after playback problems it will usually refuse to quit and I get a window labelled 'Marco' which allows me to select 'Force Quit'... which then does the job.

I will continue testing and report back some more. Also I now have a USB/MIDI cable for experiments with JACK.

Best regards, Philip.

@ericfontainejazz Thank you for all that information... it is particularly good to know that satifactory playback on the RPi, via MIDI, is possible.

Given the present difficulties with sound synthesis on the RPi, MIDI device playback seems the best way to go.

I now have a Tie Midi USB 1in/1out interface (from Bax-shop.co.uk product No. 9000-0021-7817)... but so far have not been able to get MIDI info to flow. I'm using QjackCtl. I attach screen shots of QjackCtl's connection windows (ALSAtab, Audio, MIDItab), QjackCtl's Settings windows (Advanced, Parameters) and mscore's Preferences->I/O tab.

At present I'm just getting very poor quality audio playback... sounds like humming through paper on a comb! Nothing going to my MIDI module. Playback is rather slower than the tempo indicated (MM92) but the play-cursor is moving correctly and there is no stutter/popping.

No problem not reading entire thread... it'll soon rival War and Peace.

I would be most grateful for guidance about your successful set up.

Best regards and thanks, Philip.

@ericfontainejazz, many thanks... but alas, still no MIDI output.

First I tried 'raw' in QjackCtl's parameters window, with JACK option still selected in MuseScores I/O window... but no change to MIDI/sound output.

Next I changed MuseScores I/O window to ALSA and experimented with aconnect:

aconnect -l
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
Connecting To: 15:0, 128:0
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
Connecting To: 128:1
client 15: 'OSS sequencer' [type=kernel]
0 'Receiver '
Connected From: 0:1
client 20: 'USB MIDI Interface' [type=kernel]
0 'USB MIDI Interface MIDI 1'
Connecting To: 128:1
client 128: 'MuseScore' [type=user]
1 'MuseScore Port-0'
Connected From: 14:0, 20:0
2 'MuseScore Port-0'

aconnect 128:0 20:0
Connection failed (Operation not permitted)

sudo aconnect 128:0 20:0
[sudo] password for xyz:
Connection failed (Operation not permitted)

sudo aconnect 128:1 20:0
[sudo] password for xyz:
Connection failed (Operation not permitted)

I tried both 128:0 and 128:1 but no luck either way. MuseScore is present (client 128) but it is not clear if this is a MIDI port? Client 20 is labelled MIDI but not 128.

All suggestions and advice gratefully received, Philip.

Further update @ericfontainejazz many thanks...

Command output:

aconnect -li
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
Connecting To: 15:0, 128:0
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
Connecting To: 128:1
client 20: 'USB MIDI Interface' [type=kernel]
0 'USB MIDI Interface MIDI 1'
Connecting To: 128:1
client 128: 'MuseScore' [type=user]
2 'MuseScore Port-0'

aconnect -lo
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
Connecting To: 128:1
client 20: 'USB MIDI Interface' [type=kernel]
0 'USB MIDI Interface MIDI 1'
Connecting To: 128:1
client 128: 'MuseScore' [type=user]
1 'MuseScore Port-0'
Connected From: 14:0, 20:0

I infer from the above that:

128:1 is MuseScores MIDI output, and

20:0 is the USB MIDI interface input.

Therefore... aconnect 128:1 20:0 ...is the command needed to get MuseScore's MIDI data to the module, but it produces:

Connection failed (Operation not permitted)

My next move is to experiment with the MIDI module (Actually it is two modules a Yamaha MU15 and Roland SC-88vl both rather old timers). So far both with PC serial connection or switched to MIDI connection is not not working... and both ways produce on the module's display: 'errIlegalData'.

The note input (which is working) travels down a separate wire from keyboard direct to the Tie USB MIDI interface... there are two wires, MIDI input and MIDI output joining up at the USB connector.

Wish the dunce luck, Philip.

@ericfontainejazz... success, instant success... that is sound from MIDI-modules with vmpk.

client 20: 'USB MIDI Interface' [type=kernel]
0 'USB MIDI Interface MIDI 1'
Connecting To: 128:1
Connected From: 128:2, 129:0
client 128: 'MuseScore' [type=user]
1 'MuseScore Port-0'
Connected From: 14:0, 20:0
2 'MuseScore Port-0'
Connecting To: 20:0
client 129: 'VMPK Output' [type=user]
0 'VMPK Output '
Connecting To: 20:0
client 130: 'VMPK Input' [type=user]
0 'VMPK Input '

Thanks for that advice.

So the USB interface is not the problem and further down the line the modules are OK (15 years of trouble-free use with RISCOS Sibelius). Thus the problem appears to be up-stream. Looking in the handbook I'm wondering if there is something that needs to be switched on or switched off in MuseScore like for example 'Edit->Preferences->Port Audio' ?

But still no MIDI-sound from MuseScore, even though the terminal indicates they are connected.

Regarding the (apparent) effect of the USB interface on audio synthesis, it has not completely cured the stutter/crackle/popping. This morning sound quality was poor some crackle and one or two freezes (cured by sound slider wiggle) but in the afternoon glorious sound quality and no freeze/stutter. I'll test some more.

Two other features I've noticed:

1) In continuous view playback the play position cursor, after reaching the end of the first 'screenful' jumps back just one measure and only after that measure jumps to the left for the second 'screenful'.

2) If there has been 'troubled' playback MuseScore will not quit without persuasion... usually just a wiggle of the Sound Preferences slider releases a moment of sound before the quit proceeds. Sometimes 'Marco' intervenes and forces a quit.

Best regards, Philip.

@ericfontainejazz Sorry for delayed response.

Indeed, I have been unable to get hardware usb midi output from either the PPA or AppImage version of MuseScore. As VMPK has no trouble transmitting midi through the USB interface it is presumably a problem with MuseScore.

However, I am able to use MIDI keyboard input and get acceptable audio synthesis most of the time. The PPA version of MuseScore appears to me to give somewhat better overall performance. In both versions the playback cursor is a note ahead of the sound and with midi keyboard input the note appears on screen well before the sound. I still get the impression that having the usb interface connected improves the audio output (but this may be a red herring).

Although MuseScore 2 on the RPi3 appears a work in progress, I think I can get enough out of it, in its present state, to persevere... and of course to look for improvements to come... both in hardware and software.

Best regards, and thank to you all, Philip.

Further comments on Setting-Up MuseScore on the Raspberry Pi.

I'm beginning to get a little experience using ms (PPA version) on the RPi3B, and as issues come up I shall note them down here as an addendum.

Early days of course, but overall I've been might impressed by this music editor. Everything I've tried so far has worked fine, if a little slowly in places, excepting of course for playback.

MIDI keyboard input works a treat. However, with a playback lag-time of about half a second it's most distracting to hear notes sound when you are playing in others further on. I've turned it off: Edit->Preferences->Note Input. Un-checking 'Play notes when editing'. Additionally this hopefully stops any playback glitch halting note input. Just very occasionally note input freezes when the synthesiser stumbles... requiring a Ubuntu 'Sound Preferences' volume slider wiggle to free up the system.

Also impressed with Ubuntu-MATE: Runs OK on the RPi3 for a relatively undemanding user like me... and no stability problems. I set up MuseScore and a PDF for MIDI input in the morning and let it run all day... coming back to it now and then to work on the score and otherwise turning off the monitor and keyboard. However, one question I haven't solved yet is how to get the Ubuntu display to full screen HDMI. I guess from RISCOS it will be 'disable_overscan=1' in some config file... but where?

Best regards, Philip.

To answer my own overscan margin question, from an internet search:
Open a terminal window and make a backup of /boot/config.txt

sudo cp /boot/config.txt /boot/config.txt.backup

You will prompted for your password.
Open config.txt for editing.

sudo nano /boot/config.txt

config.txt is loaded into the terminal window, scroll down to 'Overscan Video Settings' and un-comment

#disable_overscan=1 (i.e. Remove the #)

In my config file it's on line 369. Leave all other overscan parameters commented out.
#overscan_left=10
#overscan_right=10
#overscan_top=15
#overscan_bottom=15
These can be used to adjust screen position if disable-overscan=1 doesn't work.

Save and exit. You are prompted for Y/N answer.

CTRL+SHIFT+X
SHIFT+Y (to save followed by RETURN to confirm config.txt file name)
RETURN

Reboot

sudo reboot

On most monitors/TVs this should remove the black borders and make the desktop fill the whole screen. It worked for me using Ubuntu-MATE 16.04 on the Raspberry Pi 3B.

Nigel,

I'm not a regular user of Raspian/Linux and have no great knowledge of these matters, but what worked for me, when installing Musescore 2 on the Pi 3B, were the commands provided by Shoogle in his post dated 24th June, 2016 further up this thread. The commands , I believe, install a Pi friendly version of the AppImage from Shoogle's personal archive.

The PPA software worked back in June last year, hopefully it is still OK. If you do give the commands a go, I would be interested to hear how you get on.

Good luck, Philip (pjpy)

Nigel,

After turning off the computer last night I realised that I hadn't said that back in June 2016, you needed to be running UbuntuMATE 16.04 (rather than Raspian) on the Pi 3 for MuseScore 2.0.3 have all the resources/components it needs. I don't know if it is still the case today, or for that matter, what is OS/resources are required with regard to ms 2.1.

Philip.