| View previous topic :: View next topic |
| Author |
Message |
ev56o
Apprentice
Joined: 26 Jan 2010
Posts: 180
|
 Posted: Thu Apr 04, 2013 9:09 am Post subject: jack, solfege and zynaddsubfx doesn' t work together |
 |
|
When i connect solfege and zynaddsubfx (with midi keyboard) to jack it works for a few of seconds, then in the tab audio zynaddsubfx crash.
| Code: |
m@localhost ~ $ qjackctl &
[1] 1749
m@localhost ~ $ zynaddsubfx &
[2] 1763
m@localhost ~ $
ZynAddSubFX - Copyright (c) 2002-2011 Nasca Octavian Paul and others
Compiled: Mar 25 2013 13:24:15
This program is free software (GNU GPL v.2 or later) and
it comes with ABSOLUTELY NO WARRANTY.
Try 'zynaddsubfx --help' for command-line options.
Sample Rate = 48000
Sound Buffer Size = 256 samples
Internal latency = 5.3 ms
ADsynth Oscil.Size = 1024 samples
Starting Audio: JACK
Jack buffer resized
Audio Started
Starting MIDI: ALSA
MIDI Started
Info, alsa midi port connected
m@localhost ~ $ solfege &
[3] 1770
m@localhost ~ $ 2.34378290176
Jack reports xrun
Jack reports xrun
Jack reports xrun
Jack reports xrun
Jack reports xrun
Jack reports error: cannot read server event (Connection reset by peer)
Jack reports error: jack_client_thread zombified - exiting from JACK
[1] Done qjackctl
[2]- Broken pipe zynaddsubfx
[3]+ Done solfege
|
|
|
| Back to top |
|
 |
aCOSwt
Bodhisattva
Joined: 19 Oct 2007
Posts: 2537
Location: Hilbert space
|
| Posted: Thu Apr 04, 2013 9:37 am Post subject: |
|
|
Hmmm... being said I do not know zynaddsubfx. (I use yoshimi)
What I infer from the trace you publish is that there are good chances that jackd zombifies zynadd for being too slow.
1/ You can retry launching jackd with the -Z option.
This should prevent zynadd to die but will not prevent what jackd believes (appropriately or not) being underruns.
I have had a couple of similar experiences when using the raw alsa devices of an ice1712 and that were related to inappropriate underruns detection. =>
2/ Try launching jackd with the --midi seq option. (also available on qjackctl's option window next to the label : Midi driver.)
_________________
|
|
| Back to top |
|
|
ev56o
Apprentice
Joined: 26 Jan 2010
Posts: 180
|
| Posted: Fri Apr 05, 2013 1:32 pm Post subject: |
|
|
| I tried what you wrote, it doesn' t work. I discovered there is the same problem with more application, lmms and his inner sequencers. I seen other appllication manage the reaction times, maybe we can set somewhere a bigger error margin? |
|
| Back to top |
|
|
aCOSwt
Bodhisattva
Joined: 19 Oct 2007
Posts: 2537
Location: Hilbert space
|
| Posted: Fri Apr 05, 2013 1:42 pm Post subject: |
|
|
| ev56o wrote: | | I seen other appllication manage the reaction times, maybe we can set somewhere a bigger error margin? |
Do you mean increasing buffers ?
Well you can try increasing jack's buffers (via the qjackctl interface) but I doubt it will help if the xruns detected are actually underruns.
Out of curiosity, do you run jackd in realtime mode ?
What are the scheduling mode and priority of zynadd threads ?
What kernel are you running ?
_________________
|
|
| Back to top |
|
|
ev56o
Apprentice
Joined: 26 Jan 2010
Posts: 180
|
| Posted: Mon Apr 08, 2013 9:22 am Post subject: |
|
|
I don' t know about the buffer and scheduling mode
I run jackd in realtime mode, the priority of zyn is 0 and th kernel is Linux localhost 3.7.10-gentoo #1 SMP PREEMPT Sat Mar 23 15:03:35 CET 2013 x86_64 AMD Athlon(tm) 64 Processor 3500+ AuthenticAMD GNU/Linux |
|
| Back to top |
|
|
|
Multimedia
