AppImage does not work with Jack Audio - SOLVED

• Apr 9, 2016 - 01:00
Reported version
2.1
Type
Functional
Severity
S4 - Minor
Status
won't fix
Project
MuseScore

1) Open the AppImage
2) Select Jack Audio as the output and close MuseScore
3) Open MuseScore again:

initScoreFonts 0x37db680
unknown option character l
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2015 Grame.
jackdmp 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
`default' server already active
Failed to open server
JackAudio()::init(): failed, status 0x11
no JACK server found
no audio driver found
Cannot start I/O
sequencer init failed
QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)
QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)

MuseScore will have no sound and will don't appear on Catia (the Jack router I use) to plug it to other applications.
I've tried to install the AppImage but the problem persist

Comments

• Sep 14, 2017 - 10:46

There seems to be a rather fundamental missunderstanding of how jack works.
There are currently two actively maintained versions of jack. Jack's "ecosystem" consists of a server process (jackd) and a library (libjack) used for all communication with that server. What jack does not provide is a protocol to communicate with the server. While all versions of Jack share the same API (.e. an application can dynamically link against any version) it's not possible to use the libjack from one jack version with the server from another version. They just can't (reliably) communicate with each other.
So, to fix this issue one would have to provide AppImages for both versions of jack.
In theory it might be possible to try an detect the needed lib version and link that dynamically, but that seems like a daunting task.

Reply

• Sep 14, 2017 - 19:10
Status (old) active ⇒ won't fix
Status active ⇒ won't fix

Thanks rmattes for that clarification. I'm setting this as "won't fix" because of the problem you describe and because my feeling I expressed earlier that jack is very much a pro thing. Also a few months ago, I did add support for midi output over PortMidi, which I believe was one of the primary reasons someone would need to use musescore with jack, so now I don't think there is a compelling need anymore for Jack on AppImage. For those that still want to connect MuseScore AppImage to jack programs, there are always alsa->jack or pulseaudio->jack bridges to be used as a workaround.

Reply

• Sep 15, 2017 - 08:30

Thank you for dealing with this.
Maybe i got it all wrong, but reading your suggestions and trying them out made me realize that I can not recreate my work flow with appimage 2.1 on linux. I can play musescore with pulseaudio and I can connect my midi keyboard through my sound card+midi connection (not usb) - all this with alsa. but I can not do both: input and playing. in that regard, I dont see Jack as that pro since it provides this simple work flow.
in 2.0.3 on linux, this work flow works perfect with Jack. since linux has AppImage for 2.1 I find it strange that this work flow cant be recreated. OR i might be doing something really basic really wrong...

Reply

• Sep 15, 2017 - 17:44

danwe, you should be able to do mini input and audio output simultaneously without jack. That is true not just for AppImage but also with a regular distro install. If that indeed doesn't work for you, then please make a post on the regular support form (not this issue tracker), maybe include terminal output of "aconnect -i" and "aconnect -o" and "aplay -L".

Reply

• Nov 26, 2017 - 14:10
Title AppImage does not work with Jack Audio ⇒ AppImage does not work with Jack Audio - SOLVED

You are absolutely right. I have managed to make the Appimage output sound trough jack using jack1. My workstation is running Ubuntu Mate 14.04 x86_64.

Steps:

  1. Replace jack2 by jack 1.

fran@ThinkPad-T410:~$ sudo apt-get install jackd1

  1. If you don't use qjackctl, add the parameter -t4500 to ${HOME}/.jackdrc:

fran@ThinkPad-T410:~$ cat .jackdrc
/usr/bin/jackd -t4500 -dalsa -dhw:0 -r44100 -p1024 -n2
fran@ThinkPad-T410:~$

If tou indeed use qjackctl, enter configuration and put value 4500 in the box labeled 'Timeout (msec):', because qjackctl is going to overwrite the former file with its own settings. You can use 4000 too.

And voila, jack output its working:

fran@ThinkPad-T410:~$ bin/MuseScore-2.1-x86_64.AppImage
initScoreFonts 0x2c32410
JACK: sample rate changed: 44100
JackAudio::connect
JackAudio::connect
qt.network.ssl: QSslSocket: cannot resolve SSLv2_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv2_server_method
Ignore SSL error: 6 The certificate has expired

Attachment Size
Setup-JACK Audio Connection Kit.png 123.67 KB
Connections - JACK Audio Connection Kit.png 42.98 KB
Connections - MIDI - JACK Audio Connection Kit.png 37.34 KB

Reply

• Jan 5, 2018 - 15:36

First let me say that the AppImage approach is a big step in the right direction to not to have to maintain dozens of versions for different linux distris.
And musescore has improved incredible over the years. It is a fantastic tool.
But to say "when you want to use jack, wait for the packages" is an easy way out.
Because the problem of this "won't fix" bug is, that there are no more Mscore 2.1 packages for the Ubuntu 16.04LTS. Even if it is an LTS version. For those who want to use jack you' re at a dead end, if you don't compile yourself. (btw.: Imho jack is not a toy for nerds, but an ingenious routing layer) The distributions for musical purposes like Ubuntustudio or AV-Linux use jack2 and to switch back to jack1 might lead to problems not yet known. Is there another work around? What are those "alsa -> jack bridges?" I know the jack midi bridge "a2j", but that is only for the midi signal routing.

Reply

• Jan 5, 2018 - 18:08

Well i tried the ALSA JACK PCM plugin. The test (as recomened by jackaudio.org) worked: aplayer -D pcm.jack 'mysong.wav'. With musescore 2.03 and the Alsa as I/O it works (see pics 2018-01-05 17-42-10.png, 2018-01-05 17-28-55.png). But with musescore.AppImage it does not. See pic.2018-01-05 18-57-44.png.

Attachment Size
Bildschirmfoto_2018-01-05_17-42-10.png 81.02 KB
Bildschirmfoto_2018-01-05_17-28-55.png 57.33 KB
Bildschirmfoto_2018-01-05_18-57-44.png 33.22 KB

Reply