MusE Sequencer forum
Jack problems? - Printable Version

+- MusE Sequencer forum (http://muse-sequencer.org/forum)
+-- Forum: MusE Forum (http://muse-sequencer.org/forum/forumdisplay.php?fid=5)
+--- Forum: Getting Help (http://muse-sequencer.org/forum/forumdisplay.php?fid=3)
+--- Thread: Jack problems? (/showthread.php?tid=156)

Pages: 1 2


Jack problems? - oswaldm - 07-17-2016

Hi,

Since a few days when I start up Muse it displays "Jack has detected a performance problem which has lead to MusE being disconnected" with a few hints on possible causes. Jack is still running, other applications (e.g. Ardour) are running perfectly fine, just Muse is not able to start up. 

I have this on 2.2.1 and also on 3.0.0pre1, no matter if I then click "restart" or "cancel" after a few clicks it either hangs or crashes.

Some output from the terminal (muse3 running under gdb):

Code:
[New Thread 0x7fffd50f3700 (LWP 16565)]
MusE:initJackAudio: jack_get_version() returned zeros. Setting version major to 1.
RtcTimer::setTimerFreq(): cannot set freq 1024 on /dev/rtc: Permission denied
 precise timer not available, check file permissions and allowed RTC freq (/sys/class/rtc/rtc0/max_user_freq)
AlsaTimer::initTimer(): best available ALSA timer: system timer
[New Thread 0x7fffd4413700 (LWP 16566)]


...

Code:
MusE: MidiJackDevice::open failed creating input port name jack-midi-0_in
MusE: MidiJackDevice::open failed creating output port name jack-midi-1_out
MusE: MidiJackDevice::open failed creating input port name jack-midi-1_in
MusE: MidiJackDevice::open failed creating output port name jack-midi-2_out
MusE: MidiJackDevice::open failed creating input port name jack-midi-2_in
MusE: MidiJackDevice::open failed creating output port name jack-midi-3_out
MusE: MidiJackDevice::open failed creating input port name jack-midi-3_in
MusE: MidiJackDevice::open failed creating output port name jack-midi-4_out
MusE: MidiJackDevice::open failed creating input port name jack-midi-4_in
MusE: MidiJackDevice::open failed creating output port name jack-midi-5_out
MusE: MidiJackDevice::open failed creating input port name jack-midi-5_in
MusE: MidiJackDevice::open failed creating output port name jack-midi-6_out
MusE: MidiJackDevice::open failed creating input port name jack-midi-6_in
MusE: MidiJackDevice::open failed creating input port name jack-midi-7_in
Connected to session bus, unique name is ":1.171"
JACK: buffersize changed 2048
MusE: JackAudioDevice::realtimePriority: JACK is not running realtime
midi thread 16556 _NOT_ running SCHED_FIFO
Audio::shutdown()
Panic! no _client!
Panic! no _client!
Panic! no _client!
Panic! no _client!
Panic! no _client!
Panic! no _client!


The Jack buffersize is correct, but Jack is for sure running in realtime.

After some clicks it crashes here:


Code:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff793f1ba in MusEGui::MPConfig::songChanged (this=0xcc34a70, flags=262144) at /home/oswald/Projects/music/muse/muse3/muse/confmport.cpp:1258
1258                                    MusEGlobal::audioDevice->deviceType() !=
(gdb)
(gdb) bgt
Undefined command: "bgt".  Try "help".
(gdb) bt
#0  0x00007ffff793f1ba in MusEGui::MPConfig::songChanged (this=0xcc34a70, flags=262144) at /home/oswald/Projects/music/muse/muse3/muse/confmport.cpp:1258
#1  0x00007ffff793ee05 in MusEGui::MPConfig::MPConfig (this=0xcc34a70, parent=0x8aa5e0) at /home/oswald/Projects/music/muse/muse3/muse/confmport.cpp:1184
#2  0x00007ffff7941855 in MusEGui::MusE::configMidiPorts (this=0x8aa5e0) at /home/oswald/Projects/music/muse/muse3/muse/confmport.cpp:1827
#3  0x00007ffff4a489ee in MusEGui::TList::portsPopupMenu (this=0x96c5a0, t=0xc997320, x=232, y=20, allClassPorts=false) at /home/oswald/Projects/music/muse/muse3/muse/arranger/tlist.cpp:1136
#4  0x00007ffff4a4c5d2 in MusEGui::TList::mousePressEvent (this=0x96c5a0, ev=0x7fffffffbe70) at /home/oswald/Projects/music/muse/muse3/muse/arranger/tlist.cpp:1974
#5  0x00007ffff63bec12 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#6  0x00007ffff4a4418e in MusEGui::TList::event (this=0x96c5a0, event=0x7fffffffbe70) at /home/oswald/Projects/music/muse/muse3/muse/arranger/tlist.cpp:211



I see that jackd2 has been updated (version 2:1.9.11~20160620~trusty1), but as I said all other applications are running normally, just Muse seems to have problems.

Any ideas?

lg,
Michael


RE: Jack problems? - spamatica - 07-18-2016

Hi Michael,

That's wierd. If you didn't change anything I can't see why it suddenly should start to misbehave.
You could try to temporarily move away the ~/.config/MusE/MusE.cfg file to make sure it's not some setting in it that affects startup.

What OS are you on? I have kubuntu +kxstudio but haven't updated in a while, I'll try that.

Regards,
Robert


RE: Jack problems? - spamatica - 07-18-2016

Hey, it seems to do the same for me after an update. What the.. stay tuned.


RE: Jack problems? - spamatica - 07-18-2016

Some quick trial and errors reveals that MusE still works with the packaged jackd1.
More over I built jackd2 from git and used that and that too works.
So unless I made some testing mistake, it seems they did some change to the packaged jackd2 that effects us severely.
I'll forward the problem to the mailinglist.


RE: Jack problems? - oswaldm - 07-18-2016

Ok, cool. If jackd2 from git works, then I'll try that.

lg,
Michael


RE: Jack problems? - carlv - 07-18-2016

Howdy,

Just wanted to chime in to report the same problem.

Running on Ubuntu 16.04 on this end.

Thanks
Carl


RE: Jack problems? - pauln - 08-09-2016

Hi,

Another "me too" problem here.

Muse 2.2.1 doesn't start.


I'm using regular Ubuntu 16.04 with 4.4.0-34-lowlatency kernel with KXStudios repositories set up according to this page: http://kxstudio.linuxaudio.org/Repositories

Starting Muse with the -d switch gives me this:


Quote:LOCALE en_GB
Denormal protection enabled.
Trying RTC timer...
fatal error: open /dev/rtc failed: Permission denied
hint: check if 'rtc' kernel module is loaded, or used by something else
Trying ALSA timer...
AlsaTimer::initTimer(): best available ALSA timer: system timer
got timer = 79
Aquired timer frequency: 1000
midi thread 19758 _NOT_ running SCHED_FIFO
starting with template /usr/share/muse/templates/default.med
Route::read(): jack port <system:playback_1> not found
  Warning - route invalid. Ignoring route!
Route::read(): jack port <system:playback_2> not found
  Warning - route invalid. Ignoring route!
midi thread 19758 _NOT_ running SCHED_FIFO
uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu
  name2route: <input1> not found
  name2route: <input2> not found
  name2route: <input1> not found
  name2route: <input2> not found

Qtractor works fine, by the way.

Any ideas what could be wrong?

Thanks.
Paul.


RE: Jack problems? - spamatica - 08-12-2016

(08-09-2016, 07:51 PM)pauln Wrote: Hi,

Another "me too" problem here.

Muse 2.2.1 doesn't start.


I'm using regular Ubuntu 16.04 with 4.4.0-34-lowlatency kernel with KXStudios repositories set up according to this page: http://kxstudio.linuxaudio.org/Repositories

Starting Muse with the -d switch gives me this:


Quote:LOCALE en_GB
Denormal protection enabled.
Trying RTC timer...
fatal error: open /dev/rtc failed: Permission denied
hint: check if 'rtc' kernel module is loaded, or used by something else
Trying ALSA timer...
AlsaTimer::initTimer(): best available ALSA timer: system timer
got timer = 79
Aquired timer frequency: 1000
midi thread 19758 _NOT_ running SCHED_FIFO
starting with template /usr/share/muse/templates/default.med
Route::read(): jack port <system:playback_1> not found
  Warning - route invalid. Ignoring route!
Route::read(): jack port <system:playback_2> not found
  Warning - route invalid. Ignoring route!
midi thread 19758 _NOT_ running SCHED_FIFO
uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu
  name2route: <input1> not found
  name2route: <input2> not found
  name2route: <input1> not found
  name2route: <input2> not found

Qtractor works fine, by the way.

Any ideas what could be wrong?

Thanks.
Paul.

Yeah, it seems MusE is the only application that suffers from this so it's something nonstandard we do during initialization. Unfortunately we don't know what yet but will dig more.

/Robert


RE: Jack problems? - oswaldm - 08-12-2016

Any news on this issue?

I tried with jack2 from git but get the same error. Weird. Sigh. Don't want to go to Rosegarden/QTractor, they don't have Jack MIDI and the ALSA-Jack MIDI bridge is not very reliable for some reason...

lg,
Michael


RE: Jack problems? - spamatica - 08-13-2016

No, sorry, we haven't found the problem yet Sad

Though it should work when building jackd2 from git. Did you remove the jackd2 package? I believe this is required. The jack installation isn't very forgiving, I spent a good few hours today and yesterday trying to dig into this and started to question if I had understood anything, as it didn't work with _any_ jack installation.
It turns out that I hadn't removed the jackd2 package and although my own jack installed in /usr/local/ it seems to use the libs from /usr/
The other alternative is to use the packaged jack1 but I suppose you already ruled that out.