No sound on Linux (MS Basic not found) since update [Temporarily solved]

• Jul 21, 2023 - 02:17

Since yesterday I don't hear any sound on musescore.

I'm on archlinux with musescore 4.1.0, using jack and/or pulseaudio

When I launch it from the console, I get the following messages :
"FluidResolver | resolveSynth: Not found: MS Basic"
There is no soundfont in my home folder > Musescore4/Soundfonts/ (I don't know if there was yesterday before I updated)

Here's the complete output :

$ mscore 
21:09:46.547 | INFO  | main_thread | GlobalModule | onPreInit: log path: /home/user/.local/share/MuseScore/MuseScore4/logs/MuseScore_230720_210946.log
21:09:46.547 | INFO  | main_thread | GlobalModule | onPreInit: === Started MuseScore 4.1.0, build number  ===
21:09:46.548 | WARN  | main_thread | IpcSocket  | connect: failed connect to server
21:09:46.548 | WARN  | main_thread | IpcSocket  | connect: failed connect to server
21:09:46.548 | INFO  | main_thread | IpcSocket  | connect: success connected to ipc server
21:09:46.548 | INFO  | 140278379828928 | IpcServer  | listen: id: "71126e7121f54df38cc45cd360e5231a" 
21:09:46.592 | WARN  | main_thread | DiagnosticsModule | onInit: crash handling disabled
21:09:46.602 | ERROR | main_thread | MuseSamplerLibHandler | MuseSamplerLibHandler: Unable to open MuseSampler library, path: /home/user/.local/share/MuseSampler/lib/libMuseSamplerCoreLib.so
21:09:46.602 | ERROR | main_thread | MuseSamplerResolver | checkLibrary: Incompatible MuseSampler library; ignoring
21:09:46.622 | WARN  | main_thread | AbstractCloudService | readTokens: Could not find the tokens file: /home/user/.local/share/MuseScore/MuseScore4/musescorecom_cred.dat
21:09:46.622 | WARN  | main_thread | AbstractCloudService | readTokens: Could not find the tokens file: /home/user/.local/share/MuseScore/MuseScore4/audiocom_cred.dat
21:09:47.445 | ERROR | main_thread | App        | run: error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

21:09:47.445 | WARN  | main_thread | Qt         | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"
21:09:47.445 | ERROR | main_thread | App        | run: error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

21:09:47.446 | WARN  | main_thread | Qt         | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"
21:09:47.446 | ERROR | main_thread | App        | run: error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

21:09:47.446 | WARN  | main_thread | Qt         | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"
21:09:47.447 | ERROR | main_thread | App        | run: error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

21:09:47.447 | WARN  | main_thread | Qt         | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"
21:09:47.448 | ERROR | main_thread | App        | run: error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

21:09:47.448 | WARN  | main_thread | Qt         | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"
21:09:47.449 | ERROR | main_thread | App        | run: error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

21:09:47.449 | WARN  | main_thread | Qt         | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"
21:09:47.450 | ERROR | main_thread | App        | run: error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

21:09:47.450 | WARN  | main_thread | Qt         | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"
21:09:47.450 | ERROR | main_thread | App        | run: error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

21:09:47.450 | WARN  | main_thread | Qt         | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"
21:09:47.451 | ERROR | main_thread | App        | run: error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

21:09:47.451 | WARN  | main_thread | Qt         | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

(mscore:31920): Pango-WARNING **: 21:09:47.585: failed to create cairo scaled font, expect ugly output. the offending font is 'Cantarell 12'

(mscore:31920): Pango-WARNING **: 21:09:47.585: font_face status is: 

(mscore:31920): Pango-WARNING **: 21:09:47.585: scaled_font status is: out of memory

(mscore:31920): Pango-WARNING **: 21:09:47.586: failed to create cairo scaled font, expect ugly output. the offending font is 'Cantarell 10.7998046875'

(mscore:31920): Pango-WARNING **: 21:09:47.586: font_face status is: 

(mscore:31920): Pango-WARNING **: 21:09:47.586: scaled_font status is: out of memory

(mscore:31920): Pango-WARNING **: 21:09:47.714: failed to create cairo scaled font, expect ugly output. the offending font is 'Cantarell Bold 12'

(mscore:31920): Pango-WARNING **: 21:09:47.714: font_face status is: 

(mscore:31920): Pango-WARNING **: 21:09:47.715: scaled_font status is: out of memory

(mscore:31920): Pango-WARNING **: 21:09:47.716: failed to create cairo scaled font, expect ugly output. the offending font is 'Cantarell Bold 10.7998046875'

(mscore:31920): Pango-WARNING **: 21:09:47.716: font_face status is: 

(mscore:31920): Pango-WARNING **: 21:09:47.716: scaled_font status is: out of memory
21:09:49.667 | INFO  | main_thread | ActionsDispatcher | dispatch: try call action: file-open
21:09:49.831 | INFO  | main_thread | ActionsDispatcher | dispatch: try call action: file-open
21:09:50.244 | INFO  | main_thread | ProjectMigrator | migrateEngravingProjectIfNeed: success migration
21:09:50.448 | ERROR | 140278027499200 | SynthResolver | resolveSynth: invalid audio source params for trackId: 0
21:09:50.453 | ERROR | 140278027499200 | FluidResolver | resolveSynth: Not found: MS Basic
21:09:50.454 | WARN  | 140278027499200 | FluidSynth | init: No preset found on channel 0 [bank=0 prog=56]
21:09:50.454 | WARN  | 140278027499200 | FluidSynth | init: No preset found on channel 0 [bank=0 prog=56]
21:09:50.455 | ERROR | 140278027499200 | SynthResolver | resolveSynth: invalid audio source params for trackId: 1
21:09:50.458 | ERROR | 140278027499200 | FluidResolver | resolveSynth: Not found: MS Basic
21:09:50.459 | WARN  | 140278027499200 | FluidSynth | init: No preset found on channel 0 [bank=0 prog=0]
21:09:50.459 | WARN  | 140278027499200 | FluidSynth | init: No preset found on channel 0 [bank=0 prog=0]
21:09:50.462 | ERROR | 140278027499200 | SynthResolver | resolveSynth: invalid audio source params for trackId: 2
21:09:50.465 | ERROR | 140278027499200 | FluidResolver | resolveSynth: Not found: MS Basic
21:09:50.466 | WARN  | 140278027499200 | FluidSynth | init: No preset found on channel 0 [bank=0 prog=0]
21:09:50.466 | WARN  | 140278027499200 | FluidSynth | init: No preset found on channel 0 [bank=0 prog=0]
21:09:50.467 | ERROR | 140278027499200 | SynthResolver | resolveSynth: invalid audio source params for trackId: 3
21:09:50.470 | ERROR | 140278027499200 | FluidResolver | resolveSynth: Not found: MS Basic
21:09:50.471 | WARN  | 140278027499200 | FluidSynth | init: No preset found on channel 0 [bank=0 prog=0]
21:09:50.471 | WARN  | 140278027499200 | FluidSynth | init: No preset found on channel 0 [bank=0 prog=0]
21:09:50.472 | ERROR | 140278027499200 | SynthResolver | resolveSynth: invalid audio source params for trackId: 4
21:09:50.476 | ERROR | 140278027499200 | FluidResolver | resolveSynth: Not found: MS Basic
21:09:50.476 | WARN  | 140278027499200 | FluidSynth | init: No preset found on channel 0 [bank=0 prog=115]
21:09:50.476 | WARN  | 140278027499200 | FluidSynth | init: No preset found on channel 0 [bank=0 prog=115]
21:10:42.134 | WARN  | main_thread | Qt         | QQmlComponent: Created graphical object was not placed in the graphics scene.
21:10:42.854 | WARN  | main_thread | Qt         | QQmlComponent: Created graphical object was not placed in the graphics scene.
21:10:44.504 | INFO  | main_thread | ActionsDispatcher | dispatch: try call action: diagnostic-save-diagnostic-files
21:10:50.316 | ERROR | main_thread | DiagnosticsActionsController | saveDiagnosticFiles: [3]

The diagnostic detects Muse Sampler Library 0.3.2
I don't use MuseHub

Could you please help ?

Thank you in advance !

Comments

• Aug 24, 2023 - 16:46

When using the supported AppImage, you don't need to revert all the way back to 4.0 - the current version should work fine. So just download from the main page of this site. The problem described here is only using the unsupported third-party build from the Arch repository.

if you are having some sort of issue using the official AppImage on Ubuntu. that's unrelated, so please start a new thread and give more details.

Reply

• Aug 24, 2023 - 16:59

In that case I have news as I get the same symtoms with Ubuntu 22.04. With MU4 there is no sound and no recognition of the midi keyboard. MU3 3.6.2 is fine. One issue is i that I cannot select my Masterkey64 keyboard as an input device. Strangely it shows up as an output dev. All is fine with MU 3.6.2. But I thought you knew about this as there a long discussion on github relating to this. I've spend days playing with MU4 and just can't get sound or MIDI to work. For now I'm using MU3 to input from keyboard then importing into MU4 to get access to the additional features I need.

Reply

• Aug 24, 2023 - 17:15

MIDI input is an unrelated matter and I have no insight into that, but sound should certainly work if you are using the AppImage. Is there someone else where you posted more details about the problem you are experiencing? if not, please start a new thread. Seeing the log when starting the AppImage from the command line will be most useful

Reply

• Aug 24, 2023 - 18:36

Well, yes, I see you posted about the MIDI issue, but that's almost certainly unrelated, and something to do with the drivers for that device. JACK is also unrelated to whether or not playback works. Here we are trying to understand the issue with playback, which should work perfectly when using the supported AppImage. So again, if you are still having playback issues using the supported AppImage, please start a new thread and describe the issue in more detail.

Reply

• Aug 25, 2023 - 09:57

Where do you want me to post this info other than what I've already posted in General Discussion? I can add:
today I tried using the 3.6.2 and 4.1 AppImiages on RHEL 3.8 very mixed results.
3.6.2 I selected ALSA from IO prefs. Managed to get USB keyboard and sound working, though there was big delays in what I did at the keyboard compared with what happened on screen. Then I decided to restart MU3. It looped, had to kill it. Restarted OK. Tried 4.1: no joy at all - it wouldn't come up at all. Went back to 3.6.2. Because on Ubuntu I could only get sound and keyboard working with Port Audio selected from IO prefs, I tried Port Audio to see what difference that would make. As soon as I Apply those changes 3.6.2 on RHEL segment faults. On restarting if I try to reselect ALSA and Apply I still get a segment fault. When convenient I'll reboot RHEL, but that's a work system so can so that right now.

Something isn;t right with sound in general under Linux.

Reply

• Aug 25, 2023 - 13:18

What you posted is about an issue with MIDI input. Again, that has nothing to do with audio output. So please start a new thread with a title reflecting that separate problem. Trying to solve two unrelated problems in one combined thread whose title doesn't even mention the more important problem is not going to go nearly as well as having nice concise well-named threads, one per per problem.

Sound works just fine in general on Linux; we have many thousands of users including myself with no sound issues at all. So again, when you post that new thread, focus on the sound issue - talking about MIDI in that thread will just distract from solving the problem with sound on your machine. When you post that new thread, be sure to say if your machine is using pipewire or some other audio system, and be sure to post the startup log. And be sure to post a sample score just be sure the problem isn't specific to the score instead of your audio system.

Reply

• Aug 25, 2023 - 14:14

Let me repeat my question: I posted about the MIDI issue here: https://musescore.org/en/node/353882
No response. Is that not the right place for that issue?

Now for sound, which I think this thread is about: I have not sound on 4.1, but everything works on 3.6.2. I was led to believe from various discussions on this topic that I needed a fill implementation of pipewire, which I now believe I have. Do we discuss this here or in a new thread, if so which forum?

Reply

• Aug 25, 2023 - 14:20

The Support forum is best when asking for help. MIDI inout isn’t something a lot of people use so not surprising no other Linux users have stepped in to help with that, but everyone uses audio obviously, so you’ll be much more likely to get a response if you ask for help with that. This thread is about an unrelated problem - an issue specific to an unsupported third party version create for Arch. The supported AppImage should work.

So again, if you continue to have problems with audio, please open a new thread with a descriptive title and explain the problem in more detail.

Reply

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