Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Muse3 unresponsive after "restart audio" - [looping waiting for sequencer thread to start] #522

Closed
rghvdberg opened this issue Jul 25, 2016 · 2 comments

Comments

@rghvdberg
Copy link

System: Linux Mint 17.3 with kxstudio repos
Muse3 compiled from git

$ muse3 -v
Config File </home/rob/.config/MusE/MusE.cfg>
muse3: Linux Music Editor; Version 3.0.0pre1, (git: master - 84cee40 - 2016-06-27 12:15:48 +0200)

After starting Muse3 I get this warning
jack shutdown _054

After clicking restart, Muse3 doesn't react to mouse or keyboard any more and has to be 'force killed'

Latest output of "muse3 -D"

MusE:initJackAudio: jack_get_version() returned zeros. Setting version major to 1.
initJackAudio(): registering error and info callbacks...
JACK ERROR: Jack server was closed but clients are still allocated, cleanup...
JACK ERROR: Cleanup client ref = 3
JACK ERROR: Server is not running
initJackAudio(): client MusE opened.
initJackAudio(): registering client...
reconnecting output Out 1
name=Out 1

MusE::seqStart: getting audio driver MusEGlobal::realTimePriority:5
Thread <Prefetch, id 0x7fc5aa7fc700> has SCHED_OTHER priority 0
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
Thread <Midi, id 0x7fc5aaffd700> has SCHED_FIFO priority 4
looping waiting for sequencer thread to start

Jack Log

Mon Jul 25 08:42:51 2016: Starting jack server...
Mon Jul 25 08:42:51 2016: JACK server starting in realtime mode with priority 10
Mon Jul 25 08:42:51 2016: self-connect-mode is "Don't restrict self connect requests"
Mon Jul 25 08:42:51 2016: Acquired audio card Audio0
Mon Jul 25 08:42:51 2016: creating alsa driver ... hw:0|hw:0|512|2|44100|0|0|nomon|swmeter|-|32bit
Mon Jul 25 08:42:51 2016: Using ALSA driver HDA-Intel running on card 0 - HDA Intel PCH at 0xf7310000 irq 49
Mon Jul 25 08:42:51 2016: configuring for 44100Hz, period = 512 frames (11.6 ms), buffer = 2 periods
Mon Jul 25 08:42:51 2016: ALSA: final selected sample format for capture: 32bit integer little-endian
Mon Jul 25 08:42:51 2016: ALSA: use 2 periods for capture
Mon Jul 25 08:42:51 2016: ALSA: final selected sample format for playback: 32bit integer little-endian
Mon Jul 25 08:42:51 2016: ALSA: use 2 periods for playback
Mon Jul 25 08:42:51 2016: graph reorder: new port 'system:capture_1'
Mon Jul 25 08:42:51 2016: New client 'system' with PID 0
Mon Jul 25 08:42:51 2016: graph reorder: new port 'system:capture_2'
Mon Jul 25 08:42:51 2016: graph reorder: new port 'system:playback_1'
Mon Jul 25 08:42:51 2016: graph reorder: new port 'system:playback_2'
Mon Jul 25 08:42:52 2016: New client 'MusE' with PID 24941
Mon Jul 25 08:42:52 2016: New client 'qjackctl' with PID 24917
Mon Jul 25 08:45:54 2016: Client 'MusE' with PID 24941 is out
Mon Jul 25 08:50:31 2016: New client 'MusE' with PID 25522
Mon Jul 25 08:50:55 2016: Client 'MusE' with PID 25522 is out
Mon Jul 25 08:50:55 2016: New client 'MusE' with PID 25522
Mon Jul 25 08:50:56 2016: port 'MusE:Out 1-0' created
Mon Jul 25 08:50:56 2016: port 'MusE:Out 1-1' created
Mon Jul 25 08:50:56 2016: Connecting 'MusE:Out 1-0' to 'system:playback_1'
Mon Jul 25 08:50:56 2016: Connecting 'MusE:Out 1-1' to 'system:playback_2'
Mon Jul 25 08:53:53 2016: Disconnecting 'MusE:Out 1-0' from 'system:playback_1'
Mon Jul 25 08:53:53 2016: Disconnecting 'MusE:Out 1-1' from 'system:playback_2'
Mon Jul 25 08:53:53 2016: ERROR: Failed to find port 'MusE:Out 1-0' to destroy
Mon Jul 25 08:53:53 2016: ERROR: Failed to find port 'MusE:Out 1-1' to destroy
Mon Jul 25 08:53:53 2016: Client 'MusE' with PID 25522 is out
@rghvdberg rghvdberg changed the title Muse3 unresponsive after "restart audio" - Muse3 unresponsive after "restart audio" - [looping waiting for sequencer thread to start] Jul 25, 2016
@GraysonPeddie
Copy link

GraysonPeddie commented Aug 4, 2016

This also happens in MusE 2.2, 1:2.2.1-2kxstudio2v5

Thu Aug  4 11:56:21 2016: New client 'MusE' with PID 25035
Thu Aug  4 11:56:22 2016: Client 'MusE' with PID 25035 is out
Thu Aug  4 11:56:29 2016: New client 'MusE' with PID 25077
Thu Aug  4 11:56:30 2016: New client 'JackAss-NativeVST' with PID 25077
Thu Aug  4 11:56:30 2016: port 'JackAss-NativeVST:midi-out_01' created
Thu Aug  4 11:56:30 2016: Client 'JackAss-NativeVST' with PID 25077 is out
Thu Aug  4 11:56:31 2016: New client 'JackAssFX-NativeVST' with PID 25077
Thu Aug  4 11:56:31 2016: port 'JackAssFX-NativeVST:midi-out_01' created
Thu Aug  4 11:56:31 2016: Client 'JackAssFX-NativeVST' with PID 25077 is out
Thu Aug  4 11:56:36 2016: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Thu Aug  4 11:56:36 2016: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Thu Aug  4 11:56:50 2016: Client 'MusE' with PID 25077 is out

@kybos
Copy link
Contributor

kybos commented Jun 13, 2020

Obsolete release.
Please reopen if problem still exists.

@kybos kybos closed this as completed Jun 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants