Results 1 to 9 of 9

Thread: Qsynth connection to Jack

  1. #1
    Join Date
    Feb 2011
    Location
    Brazil
    Beans
    23
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Qsynth connection to Jack

    Hi all,

    After a previous Jack startup issue having been solved, I'm now trying to make Fluidsynth (Qsynth) work. The Qsynth MIDI Driver is being set to alsa_seq and the Audio Driver to jack, however Jack Control reports something when I start Qsynth. What could be possibly happening?


    22:33:20.856 Patchbay deactivated.
    22:33:20.904 Statistics reset.
    Cannot connect to server socket err = Arquivo ou diretório não encontrado
    Cannot connect to server socket
    jack server is not running or cannot be started
    22:33:20.919 ALSA connection graph change.
    22:33:21.114 ALSA connection change.
    22:33:22.018 Startup script...
    22:33:22.018 artsshell -q terminate
    Cannot connect to server socket err = Arquivo ou diretório não encontrado
    Cannot connect to server socket
    jack server is not running or cannot be started
    sh: artsshell: not found
    22:33:22.419 Startup script terminated with exit status=32512.
    22:33:22.419 JACK is starting...
    22:33:22.419 /usr/bin/jackd -dalsa -dhw:0 -r48000 -p1024 -n2 -P
    22:33:22.421 JACK was started with PID=2743.
    no message buffer overruns
    no message buffer overruns
    jackdmp 1.9.6
    Copyright 2001-2005 Paul Davis and others.
    Copyright 2004-2010 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
    JACK server starting in realtime mode with priority 10
    audio_reservation_init
    Acquire audio card Audio0
    creating alsa driver ... hw:0|-|1024|2|48000|0|0|nomon|swmeter|-|32bit
    Using ALSA driver HDA-Intel running on card 0 - HDA Intel at 0xfe978000 irq 44
    configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
    ALSA: final selected sample format for playback: 32bit integer little-endian
    ALSA: use 2 periods for playback
    22:33:24.563 Server configuration saved to "/home/piovezan/.jackdrc".
    22:33:24.564 Statistics reset.
    22:33:24.585 Client activated.
    22:33:24.586 JACK connection change.
    22:33:24.611 JACK connection graph change.
    22:33:31.751 JACK connection graph change.
    22:33:31.780 ALSA connection graph change.
    22:33:31.815 JACK connection change.
    22:33:31.816 ALSA connection change.
    22:33:31.817 JACK connection graph change.
    22:33:31.823 XRUN callback (1).
    JackEngine::XRun: client = qsynth was not run: state = 2
    JackAudioDriver::ProcessAsync Process error
    JackPosixMutex::Unlock res = 1


    Please let me know if further info is needed.

    Thanks!

  2. #2
    Join Date
    Feb 2011
    Location
    Brazil
    Beans
    23
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Qsynth connection to Jack

    Well, strangely enough the issue is gone in my system. I tried various things, including removing pulseaudio-module-jack and physically reconnecting the MIDI cable, either of which seems to have done the trick.

  3. #3
    Join Date
    Jan 2009
    Location
    The Netherlands
    Beans
    Hidden!
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Qsynth connection to Jack

    Well, Qsynth can be quite a bit unstable. Try the FluidSynth DSSI plugin, works a lot more stable. You can run it standalone: jack-dssi-host fluidsynth-dssi.so

    Best,

    Jeremy

  4. #4
    Join Date
    Feb 2011
    Location
    Brazil
    Beans
    23
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Qsynth connection to Jack

    That's cool, thanks. However the GUI won't show up, any idea why? This is the log. Google found me some possibilities but I don't think any of them is my case.


    jack-dssi-host: Warning: DSSI path not set
    jack-dssi-host: Defaulting to "/usr/local/lib/dssi:/usr/lib/dssi:/home/piovezan/.dssi"

    Cannot connect to server socket err = No such file or directory
    Cannot connect to server socket
    jackdmp 1.9.6
    Copyright 2001-2005 Paul Davis and others.
    Copyright 2004-2010 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
    no message buffer overruns
    no message buffer overruns
    JACK server starting in realtime mode with priority 10
    audio_reservation_init
    Acquire audio card Audio0
    creating alsa driver ... hw:0|-|512|2|48000|0|0|nomon|swmeter|-|32bit
    Using ALSA driver HDA-Intel running on card 0 - HDA Intel at 0xfe978000 irq 44
    configuring for 48000Hz, period = 512 frames (10.7 ms), buffer = 2 periods
    ALSA: final selected sample format for playback: 32bit integer little-endian
    ALSA: use 2 periods for playback

    jack-dssi-host: OSC URL is:
    osc.udp://ubuntu:18912/dssi/fluidsynth-dssi/FluidSynth-DSSI/chan00

    host: Ready
    fsd-gui starting (pid 2368)...
    JackEngine::XRun: client = FluidSynth DSSI plugin was not run: state = 2
    JackAudioDriver::ProcessAsync Process error
    JackActivationCount::Signal value = 0 ref = 2
    JackActivationCount::Signal value = 0 ref = 2
    Last edited by piovezan; February 3rd, 2011 at 02:30 AM.

  5. #5
    Join Date
    Jan 2009
    Location
    The Netherlands
    Beans
    Hidden!
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Qsynth connection to Jack

    Quote Originally Posted by piovezan View Post
    Code:
    JackEngine::XRun: client = FluidSynth DSSI plugin was not run: state = 2
    The GUI probably didn't start because of an xrun. And I now see Qsynth had the exact same issue. Try running JACK with the -S option (so set Server path to /usr/bin/jackd -S in the QjackCtl setup window).

  6. #6
    Join Date
    Feb 2011
    Location
    Brazil
    Beans
    23
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Qsynth connection to Jack

    I'm confused about this -S option. According to HowToJACKConfiguration it makes JACK run in synchronous mode, which causes less xruns. According to the jackd manual page (man jackd) it is an ALSA driver-specific option which is equivalent to --shorts and tries to configure card for 16-bit samples first, only trying 32-bits if unsuccessful (default is to prefer 32-bit samples). Still according to the manual there is a -s option (lowercase) which means soft mode and ignores xruns reported by the ALSA driver (not the same thing as synchronous mode, from what I've read somewhere). Is the manual outdated?

    By the way the GUI still won't show up Qsynth on the other hand seems quite stable in my system.
    Last edited by piovezan; February 4th, 2011 at 04:36 PM.

  7. #7
    Join Date
    Jun 2008
    Location
    Gipuzkoa, Spain
    Beans
    732
    Distro
    Ubuntu Studio 10.04 Lucid Lynx

    Re: Qsynth connection to Jack

    According to the jackd manual page, -S (force 16 bits) is an option for the alsa backend. However, as a general option and only for jackd2, it is equivalent to --sync (synchronous mode).

    The same happens with other letters. For example, -P means priority as a general option, but means "playback only" for the alsa backend.

    Admittedly, it is a bit confusing that the default behaviour of jackd2 is asynchronous mode, while jackd1 is only synchronous. Moreover because sync mode seems to perform better in jackd2.
    Last edited by Pablo_F; February 4th, 2011 at 05:37 PM.

  8. #8
    Join Date
    Jan 2009
    Location
    The Netherlands
    Beans
    Hidden!
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Qsynth connection to Jack

    Quote Originally Posted by piovezan View Post
    Is the manual outdated?
    No. -S is both an option for jackd directly (Synchronous) and for the alsa backend. You can even set them both:
    Code:
    jackd -S -dalsa -S
    Quote Originally Posted by piovezan View Post
    By the way the GUI still won't show up Qsynth on the other hand seems quite stable in my system.
    That's weird, but if Qsynth works just use that one

  9. #9
    Join Date
    Feb 2011
    Location
    Brazil
    Beans
    23
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Qsynth connection to Jack

    Quote Originally Posted by AutoStatic View Post
    No. -S is both an option for jackd directly (Synchronous) and for the alsa backend. You can even set them both:
    Code:
    jackd -S -dalsa -S
    So actually the man page *IS* outdated in a sense, right? I mean, I can't find an entry for -S in the general option list, only in the alsa option list, at least for jackd2 v1.9.6. Perhaps I've got the wrong manual installed after moving to and from jackd1? Or perhaps the synchronous option has been left undocumented intentionally by the developers (for 'beta testing' or something)? Anyway thank you both AutoStatic and Pablo_F for clarifying how it works, it was a very clear explanation.

    Quote Originally Posted by AutoStatic View Post
    That's weird, but if Qsynth works just use that one
    Yeah guess I'll have to stick to it but I'll keep your FluidSynth DSSI recommendation in mind

    Thanks again!
    Last edited by piovezan; February 4th, 2011 at 08:39 PM.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •