Jack svn issues

View: New views
3 Messages — Rating Filter:   Alert me  

Jack svn issues

by Jouni Rinne :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi all!

First, I'd like to thank you for this excellent application and the hard work
you developers are doing!

I've watched jack (and, of course, used it :) ) to transform from 0.103 and
earlier (usable) to 0.109 (almost unusable) to current 0.112 (usable again).

I'm at this moment using jack-0.112.0 from svn, revision 2690, on Gentoo. While
most of the wrinkles seems to be ironed out, there are still some issues I have
with it:



1) Traverso-0.42.0 segfaults with this jack version (Just FYI; I have already
reported this on traverso forums.)



2) Qsynth-0.3.3 seems to have severe trouble with multiple engines. If it is
started with two engines, autoconnection enabled, Qsynth does not get any
connection to jackd, but exits with an error. If started with two engines and
autoconnection *disabled*, sometimes the same thing happens, sometimes not. I'm
sorry, I haven't been able to figure out why this behaviour is not consistent...

(Rui, if you are reading this: could you please in the next Qsynth version
change the default setting of Audio > Auto Connect JACK Outputs to false, when
creating new engines? So I don't have to remember to uncheck it every time.)

Also, when playing around with the engines, creating, deleting and restarting
them, it's a hit & miss whether the audio connection is accepted by jackd or
not. Usually I have to restart both jackd and Qsynth to have thing working again.

Sometimes, when everything seemingly works & connects all right, the sound
output becomes horribly distorted. I always have to restart jackd to correct that.

Here are some example logs, first qjackctl.log:

15:26:12.613 Logging started --- to heinä 17 15:26:12 2008 ---
15:26:14.611 JACK is starting...
15:26:14.612 /usr/bin/jackd -R -P89 -dalsa -dhw:1 -r44100 -p64 -n2 -s -Xseq
15:26:14.653 JACK was started with PID=14158.
no message buffer overruns
jackd 0.112.0
Copyright 2001-2005 Paul Davis and others.
jackd 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
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:1|hw:1|64|2|44100|0|0|nomon|swmeter|soft-mode|32bit
control device hw:1
configuring for 44100Hz, period = 64 frames (1.5 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit little-endian
ALSA: use 2 periods for playback
port created: in-14-0-Midi-Through-Port-0
port created: out-14-0-Midi-Through-Port-0
port created: in-16-0-EMU10K1-MPU-401--UART-
port created: out-16-0-EMU10K1-MPU-401--UART-
port created: out-17-0-Emu10k1-Port-0
port created: out-17-1-Emu10k1-Port-1
port created: out-17-2-Emu10k1-Port-2
port created: out-17-3-Emu10k1-Port-3
port created: in-20-0-M-Audio-Audiophile-24-96-MIDI
port created: out-20-0-M-Audio-Audiophile-24-96-MIDI
port created: in-24-0-VirMIDI-2-0
port created: out-24-0-VirMIDI-2-0
port created: in-25-0-VirMIDI-2-1
port created: out-25-0-VirMIDI-2-1
port created: in-26-0-VirMIDI-2-2
port created: out-26-0-VirMIDI-2-2
port created: in-27-0-VirMIDI-2-3
port created: out-27-0-VirMIDI-2-3
port created: in-36-0-USB-Device-0x7104-0x2202-MIDI-1
port created: out-36-0-USB-Device-0x7104-0x2202-MIDI-1
port created: in-36-1-USB-Device-0x7104-0x2202-MIDI-2
port created: out-36-1-USB-Device-0x7104-0x2202-MIDI-2
port created: out-128-0-qamix
15:26:16.675 Statistics reset.
15:26:16.747 Client activated.
15:26:16.748 Post-startup script...
15:26:16.749 /home/madmax/bin/qjackctlafterstart
lash_init: Not attempting to start daemon server automatically
15:26:20.205 Post-startup script terminated successfully.
15:26:20.215 JACK connection change.
15:26:44.631 JACK connection graph change.
15:26:44.770 JACK connection change.
15:26:44.772 JACK connection graph change.
subgraph starting at glashctl timed out (subgraph_wait_fd=35, status = 0, state
= Running, pollret = 0 revents = 0x0)
subgraph starting at glashctl timed out (subgraph_wait_fd=35, status = 0, state
= Running, pollret = 0 revents = 0x0)
subgraph starting at glashctl timed out (subgraph_wait_fd=35, status = 0, state
= Running, pollret = 0 revents = 0x0)
subgraph starting at glashctl timed out (subgraph_wait_fd=35, status = 0, state
= Running, pollret = 0 revents = 0x0)
subgraph starting at glashctl timed out (subgraph_wait_fd=35, status = 0, state
= Running, pollret = 0 revents = 0x0)
subgraph starting at glashctl timed out (subgraph_wait_fd=35, status = 0, state
= Running, pollret = 0 revents = 0x0)
15:26:44.974 JACK connection change.
15:27:24.924 Client deactivated.
15:27:24.928 JACK is stopping...
jack main caught signal 15
JACK error: zombified - calling shutdown handler
jack_mgr_shutdown_cb: JACK server shut us down; telling server to quit
jack_client_thread zombified - exiting from JACK
jack_mgr_destroy: could not deactivate jack client
subgraph starting at LASH_Server lost client
bad status (-2) for client LASH_Server handling event (type = 7)
Connected to JACK server with client name 'LASH_Server'
Opened ALSA sequencer with client ID 134
Listening for connections
Cleaning up
Finished
bad status (1) for client glashctl handling event (type = 7)
port deleted: in-16-0-EMU10K1-MPU-401--UART-
port deleted: in-36-0-USB-Device-0x7104-0x2202-MIDI-1
port deleted: in-20-0-M-Audio-Audiophile-24-96-MIDI
port deleted: in-36-1-USB-Device-0x7104-0x2202-MIDI-2
port deleted: in-24-0-VirMIDI-2-0
port deleted: in-25-0-VirMIDI-2-1
port deleted: in-26-0-VirMIDI-2-2
port deleted: in-27-0-VirMIDI-2-3
port deleted: in-14-0-Midi-Through-Port-0
port deleted: out-128-0-qamix
port deleted: out-16-0-EMU10K1-MPU-401--UART-
port deleted: out-17-0-Emu10k1-Port-0
port deleted: out-17-1-Emu10k1-Port-1
port deleted: out-17-2-Emu10k1-Port-2
port deleted: out-36-0-USB-Device-0x7104-0x2202-MIDI-1
port deleted: out-20-0-M-Audio-Audiophile-24-96-MIDI
port deleted: out-17-3-Emu10k1-Port-3
port deleted: out-36-1-USB-Device-0x7104-0x2202-MIDI-2
port deleted: out-24-0-VirMIDI-2-0
port deleted: out-25-0-VirMIDI-2-1
port deleted: out-26-0-VirMIDI-2-2
port deleted: out-27-0-VirMIDI-2-3
port deleted: out-14-0-Midi-Through-Port-0
15:27:27.402 JACK was stopped successfully.
15:27:27.403 Post-shutdown script...
15:27:27.403 /home/madmax/bin/qjackctlaftershutdown
jackd: ei lopetettuja prosesseja
15:27:27.839 Post-shutdown script terminated with exit status=256.
15:27:35.009 Logging stopped --- to heinä 17 15:27:35 2008 ---

and then qsynth.log

15:26:39.677 Logging started --- to heinä 17 15:26:39 2008 ---
15:26:40.070 Qsynth1: Creating synthesizer engine...
15:26:41.098 Qsynth1: Loading soundfont: "/mnt/data/soundfonts/FluidR3_GM.sf2"
(bank offset 0)...
15:26:44.609 Qsynth1: Creating audio driver (jack)...
15:26:44.666 Qsynth1: Creating MIDI router (alsa_seq)...
15:26:44.668 Qsynth1: Creating MIDI driver (alsa_seq)...
15:26:44.694 Qsynth1: Creating MIDI player...
15:26:44.695 Qsynth1: fluid_synth_program_reset()
15:26:44.698 Qsynth1: Synthesizer engine started.
15:26:44.699 Qsynth2: Creating synthesizer engine...
15:26:44.733 Qsynth2: Loading soundfont: "/mnt/data/soundfonts/BladeRunner.sf2"
(bank offset 0)...
15:26:44.756 Qsynth2: Creating audio driver (jack)...
15:26:44.821 Qsynth2: Creating MIDI router (alsa_seq)...
15:26:44.821 Qsynth2: Creating MIDI driver (alsa_seq)...
15:26:44.845 Qsynth2: Creating MIDI player...
15:26:44.846 Qsynth2: fluid_synth_program_reset()
15:26:44.846 Qsynth2: fluid_synth_set_reverb_on(1)
15:26:44.847 Qsynth2: fluid_synth_set_chorus_on(1)
15:26:44.847 Qsynth2: fluid_synth_set_gain(1)
15:26:44.848 Qsynth2: fluid_synth_set_reverb(0.2,0,0.5,0.9)
15:26:44.848 Qsynth2: fluid_synth_set_chorus(3,2,0.3,8,0)
15:26:44.865 Qsynth2: Synthesizer engine started.
15:26:44.866 Qsynth1: fluid_synth_set_gain(1)
15:26:44.866 Qsynth1: fluid_synth_set_reverb(0.9,0.12,0.5,0.9)
15:26:44.867 Qsynth1: fluid_synth_set_chorus(64,2,0.3,8,0)
fluidsynth: warning: Could not connect to any physical jack ports; fluidsynth is
unconnected
fluidsynth: warning: Could not connect to any physical jack ports; fluidsynth is
unconnected
zombified - calling shutdown handler
fluidsynth: error: Help! Lost the connection to the JACK server
cannot complete execution of the processing graph (Resurssi ei tilapäisesti ole
käytettävissä)
zombified - calling shutdown handler
fluidsynth: error: Help! Lost the connection to the JACK server

15:27:21.888 Qsynth1: Stopping MIDI player...
15:27:21.888 Qsynth1: Waiting for MIDI player to terminate...
15:27:21.889 Qsynth1: Destroying MIDI player...
15:27:21.889 Qsynth1: Destroying MIDI driver...
15:27:21.890 Qsynth1: Destroying MIDI router...
15:27:21.891 Qsynth1: Destroying audio driver...
15:27:21.891 Qsynth1: Unloading soundfont: "/mnt/data/soundfonts/FluidR3_GM.sf2"
(SFID=1)...
15:27:21.934 Qsynth1: Destroying synthesizer engine...
15:27:21.948 Qsynth1: Synthesizer engine terminated.
15:27:22.153 Qsynth2: Stopping MIDI player...
15:27:22.155 Qsynth2: Waiting for MIDI player to terminate...
15:27:22.156 Qsynth2: Destroying MIDI player...
15:27:22.160 Qsynth2: Destroying MIDI driver...
15:27:22.162 Qsynth2: Destroying MIDI router...
15:27:22.163 Qsynth2: Destroying audio driver...
15:27:22.165 Qsynth2: Unloading soundfont:
"/mnt/data/soundfonts/BladeRunner.sf2" (SFID=1)...
15:27:22.168 Qsynth2: Destroying synthesizer engine...
15:27:22.171 Qsynth2: Synthesizer engine terminated.
15:27:22.373 Logging stopped --- to heinä 17 15:27:22 2008 ---



3) Some VST/VSTi plugins which worked fine with earlier versions of jack,
doesn't work anymore. The problem seems to be related to problem 2). I've tried
both fst-1.8 and dssi-vst-0.7, here's some example output:

dssi-vst (the MrRay73 VSTi GUI didn't start at all):

RemoteVSTClient: all cache files are up-to-date, not running scanner
DSSIVSTPlugin::instantiate(MrRay73.dll)
DSSIVSTPluginInstance::DSSIVSTPluginInstance(MrRay73.dll)
Returning file identifiers: 9OMZh7elTrIxVXjU8XIBwozo
RemoteVSTClient: executing /usr/lib/dssi/dssi-vst/dssi-vst-server
MrRay73.dll,9OMZh7elTrIxVXjU8XIBwozo
DSSI VST plugin server v0.986
Copyright (c) 2004-2008 Chris Cannam
Loading "MrRay73.dll"...
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
fixme:mixer:ALSA_MixerInit No master control found on M Audio Audiophile 24/96,
disabling mixer
fixme:mixer:ALSA_MixerInit No master control found on VirMIDI, disabling mixer
fixme:mixer:ALSA_MixerInit No master control found on Brooktree Bt878, disabling
mixer
fixme:mixer:ALSA_MixerInit No master control found on USB Device 0x7104:0x2202,
disabling mixer
fixme:mixer:ALSA_MixerInit No master control found on Camera, disabling mixer
dssi-vst-server[1]: found in /home/madmax/vst/MrRay73.dll
done
Testing VST compatibility...
dssi-vst-server[1]: VST 2.4 entrypoint "VSTPluginMain" not found in DLL
"MrRay73.dll", looking for "main"
dssi-vst-server[1]: VST entrypoint "main" found
dssi-vst-server[1]: plugin instantiated
dssi-vst-server[1]: plugin is a VST
dssi-vst-server[1]: plugin has a GUI
dssi-vst-server[1]: plugin supports processReplacing
dssi-vst-server[1]: opening plugin
dssi-vst-server[1]: plugin is VST 2.0 or newer
dssi-vst-server[1]: plugin is a synth
dssi-vst-server[1]: plugin name is "MrRay73 1.0"
dssi-vst-server[1]: vendor string is "Guido Scognamiglio"
Initialising Windows subsystem...
dssi-vst-server[1]: registered Windows application class "dssi_vst"
dssi-vst-server[1]: created main window
done
dssi-vst-server[1]: created audio thread
terminate called after throwing an instance of 'std::bad_alloc'
   what():  std::bad_alloc
ERROR: Remote VST plugin communication failure in audio thread
Remote VST plugin audio thread: returning
/home/madmax/bin/dssivst: line 14: 11236 Keskeytetty             jack-dssi-host
dssi-vst.so:$DLL
Remote VST plugin watchdog thread: returning
dssi-vst-server[1]: cleaning up
dssi-vst-server[1]: closed audio thread
dssi-vst-server[1]: freed dll
dssi-vst-server[1]: exiting

fst (MrRay73 GUI started and seemingly worked all right, and the midi connection
was shown in QJackCtl > Connect > ALSA tab, but no connection was available in
Audio tab > no sound):

yo... lets see...
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
fixme:mixer:ALSA_MixerInit No master control found on M Audio Audiophile 24/96,
disabling mixer
fixme:mixer:ALSA_MixerInit No master control found on VirMIDI, disabling mixer
fixme:mixer:ALSA_MixerInit No master control found on Brooktree Bt878, disabling
mixer
fixme:mixer:ALSA_MixerInit No master control found on USB Device 0x7104:0x2202,
disabling mixer
fixme:mixer:ALSA_MixerInit No master control found on Camera, disabling mixer
lash_init: Not attempting to start daemon server automatically
jack_client_thread zombified - exiting from JACK

and finally the qjackctl.log from the same time as the above:

14:49:22.767 Logging started --- to heinä 17 14:49:22 2008 ---
14:49:28.463 JACK is starting...
14:49:28.463 /usr/bin/jackd -R -P89 -dalsa -dhw:1 -r44100 -p64 -n2 -s -Xseq
no message buffer overruns
jackd 0.112.0
Copyright 2001-2005 Paul Davis and others.
jackd 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
JACK compiled with System V SHM support.
14:49:28.520 JACK was started with PID=11094.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:1|hw:1|64|2|44100|0|0|nomon|swmeter|soft-mode|32bit
control device hw:1
configuring for 44100Hz, period = 64 frames (1.5 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit little-endian
ALSA: use 2 periods for playback
port created: in-14-0-Midi-Through-Port-0
port created: out-14-0-Midi-Through-Port-0
port created: in-16-0-EMU10K1-MPU-401--UART-
port created: out-16-0-EMU10K1-MPU-401--UART-
port created: out-17-0-Emu10k1-Port-0
port created: out-17-1-Emu10k1-Port-1
port created: out-17-2-Emu10k1-Port-2
port created: out-17-3-Emu10k1-Port-3
port created: in-20-0-M-Audio-Audiophile-24-96-MIDI
port created: out-20-0-M-Audio-Audiophile-24-96-MIDI
port created: in-24-0-VirMIDI-2-0
port created: out-24-0-VirMIDI-2-0
port created: in-25-0-VirMIDI-2-1
port created: out-25-0-VirMIDI-2-1
port created: in-26-0-VirMIDI-2-2
port created: out-26-0-VirMIDI-2-2
port created: in-27-0-VirMIDI-2-3
port created: out-27-0-VirMIDI-2-3
port created: in-36-0-USB-Device-0x7104-0x2202-MIDI-1
port created: out-36-0-USB-Device-0x7104-0x2202-MIDI-1
port created: in-36-1-USB-Device-0x7104-0x2202-MIDI-2
port created: out-36-1-USB-Device-0x7104-0x2202-MIDI-2
port created: out-128-0-qamix
14:49:30.568 Statistics reset.
14:49:30.641 Client activated.
14:49:30.642 Post-startup script...
14:49:30.643 /home/madmax/bin/qjackctlafterstart
lash_init: Not attempting to start daemon server automatically
14:49:34.097 Post-startup script terminated successfully.
14:49:34.101 JACK connection change.
14:50:47.106 JACK connection graph change.
14:50:47.429 JACK connection graph change.
14:50:47.465 JACK connection change.
14:51:07.840 JACK connection graph change.
14:51:07.967 JACK connection change.
14:51:41.094 JACK connection graph change.
Got unhandled LASH event from the server
Got unhandled LASH event from the server
14:51:43.094 JACK connection graph change.
14:51:43.137 JACK connection change.
Got unhandled LASH event from the server
14:51:43.429 JACK connection graph change.
subgraph starting at LASH_Server timed out (subgraph_wait_fd=35, status = 0,
state = Running, pollret = 0 revents = 0x0)
14:51:43.728 JACK connection change.
14:51:43.730 JACK connection graph change.
Got unhandled LASH event from the server
14:52:10.459 ALSA connection change.
Got unhandled LASH event from the server
14:52:32.353 Client deactivated.
14:52:32.356 JACK is stopping...
jack main caught signal 15
jack_client_thread zombified - exiting from JACK
JACK error: zombified - calling shutdown handler
jack_mgr_shutdown_cb: JACK server shut us down; telling server to quit
jack_mgr_destroy: could not deactivate jack client
Connected to JACK server with client name 'LASH_Server'
Opened ALSA sequencer with client ID 134
Listening for connections
Created project project-1 in directory /home/madmax/audio-projects/project-1
Added client 8bb23830-b319-492f-88f7-c20083bf9a95 of class MrRay73 to project
project-1
Client 8bb23830-b319-492f-88f7-c20083bf9a95 set its name to 'MrRay73'
Client MrRay73 removed from project project-1
Project project-1 removed
Cleaning up
Finished
bad status (1) for client glashctl handling event (type = 7)
port deleted: in-16-0-EMU10K1-MPU-401--UART-
port deleted: in-36-0-USB-Device-0x7104-0x2202-MIDI-1
port deleted: in-20-0-M-Audio-Audiophile-24-96-MIDI
port deleted: in-36-1-USB-Device-0x7104-0x2202-MIDI-2
port deleted: in-24-0-VirMIDI-2-0
port deleted: in-25-0-VirMIDI-2-1
port deleted: in-26-0-VirMIDI-2-2
port deleted: in-27-0-VirMIDI-2-3
port deleted: in-14-0-Midi-Through-Port-0
port deleted: out-128-0-qamix
port deleted: out-16-0-EMU10K1-MPU-401--UART-
port deleted: out-17-0-Emu10k1-Port-0
port deleted: out-17-1-Emu10k1-Port-1
port deleted: out-17-2-Emu10k1-Port-2
port deleted: out-36-0-USB-Device-0x7104-0x2202-MIDI-1
port deleted: out-20-0-M-Audio-Audiophile-24-96-MIDI
port deleted: out-17-3-Emu10k1-Port-3
port deleted: out-36-1-USB-Device-0x7104-0x2202-MIDI-2
port deleted: out-24-0-VirMIDI-2-0
port deleted: out-25-0-VirMIDI-2-1
port deleted: out-26-0-VirMIDI-2-2
port deleted: out-27-0-VirMIDI-2-3
port deleted: out-14-0-Midi-Through-Port-0
14:52:34.779 JACK was stopped successfully.
14:52:34.780 Post-shutdown script...
14:52:34.780 /home/madmax/bin/qjackctlaftershutdown
jackd: ei lopetettuja prosesseja
14:52:35.230 Post-shutdown script terminated with exit status=256.



Was any of the above useful information? I'm more than willing to debug things
further.

I really hope that you're able to fix these bugs before releasing the
jack-audio-connection-kit-1.0

Jouni Rinne

--
| me@home ~$whoami            ^ ^  | "Trust me, I know what I'm doing!" |
| Jouni 'Mad Max' Rinne      ('x') | - Sledge Hammer                    |
| me@home ~$man woman       C " "  | -------[ph34r t3h p3Ngu1n]-------- |
| Segmentation fault (core dumped) | ::   Last.fm user ID: l33tmmx   :: |
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

Re: Jack svn issues

by Rui Nuno Capela :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

hi Jouni,

On Fri, July 18, 2008 07:16, Jouni Rinne wrote:

>
> 2) Qsynth-0.3.3 seems to have severe trouble with multiple engines. If it
> is started with two engines, autoconnection enabled, Qsynth does not get
> any connection to jackd, but exits with an error. If started with two
> engines and autoconnection *disabled*, sometimes the same thing happens,
> sometimes not. I'm sorry, I haven't been able to figure out why this
> behaviour is not consistent...
>
> (Rui, if you are reading this: could you please in the next Qsynth
> version change the default setting of Audio > Auto Connect JACK Outputs
> to false, when creating new engines? So I don't have to remember to
> uncheck it every time.)
>

i'm somewhat reluctant to change the default, qsynth's jack auto-connect
option is set as is as it ever was since its inception and that is quite
some time (5 years now:)

re. your issues with jackd 0.112, i'll suggest you try change your setup
from scratch and test what else is causing the trouble. start with a bare
minimal and then retest step by step until things start to break apart.

for example: start with a plain minimal jackd command line, without midi
support (eg. -Xnone), and don't start lashd or anything else as i think
you're probably doing in some qjackctl start-up script. then try having
each one of those parts back in, one by one, just in case you don't face
the same trouble on each trial.

and, of course, give us back your findings

cheers
--
rncbc aka Rui Nuno Capela
rncbc@...



_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

Re: Jack svn issues

by Jouni Rinne :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Rui Nuno Capela kirjoitti:

> hi Jouni,
>
> On Fri, July 18, 2008 07:16, Jouni Rinne wrote:
>> 2) Qsynth-0.3.3 seems to have severe trouble with multiple engines. If it
>> is started with two engines, autoconnection enabled, Qsynth does not get
>> any connection to jackd, but exits with an error. If started with two
>> engines and autoconnection *disabled*, sometimes the same thing happens,
>> sometimes not. I'm sorry, I haven't been able to figure out why this
>> behaviour is not consistent...
>>
>> (Rui, if you are reading this: could you please in the next Qsynth
>> version change the default setting of Audio > Auto Connect JACK Outputs
>> to false, when creating new engines? So I don't have to remember to
>> uncheck it every time.)
>>
>
> i'm somewhat reluctant to change the default, qsynth's jack auto-connect
> option is set as is as it ever was since its inception and that is quite
> some time (5 years now:)
>

OK, I understand that :)

> re. your issues with jackd 0.112, i'll suggest you try change your setup
> from scratch and test what else is causing the trouble. start with a bare
> minimal and then retest step by step until things start to break apart.
>
> for example: start with a plain minimal jackd command line, without midi
> support (eg. -Xnone), and don't start lashd or anything else as i think
> you're probably doing in some qjackctl start-up script. then try having
> each one of those parts back in, one by one, just in case you don't face
> the same trouble on each trial.
>
> and, of course, give us back your findings
>
> cheers

Sorry for the lengthy delay... Well, it seems that the changes between jack
revisions 2690 and 2753 have smoothed things down, I'm now unable to reproduce
any of the problems I had with Qsynth (with jackd 0.112.1, revision 2753).
Either that, or I have ghosts in my machine :)

JR

--
| me@home ~$whoami            ^ ^  | "Trust me, I know what I'm doing!" |
| Jouni 'Mad Max' Rinne      ('x') | - Sledge Hammer                    |
| me@home ~$man woman       C " "  | -------[ph34r t3h p3Ngu1n]-------- |
| Segmentation fault (core dumped) | ::   Last.fm user ID: l33tmmx   :: |
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
LightInTheBox - Buy quality products at wholesale price