Menu

#22 problems when starting rezound /w jack-support

open
None
5
2016-03-11
2005-06-16
Shamarel
No

I have some problems with rezound when using rezound
--audio-method=jack

First Case

If jack is started with option -R (realtime)
jackd -R -d alsa -d hw:0

rezound does not come up, please see debug below:

(gdb) run
Starting program: /usr/bin/rezound --audio-method=jack
[New Thread 16384 (LWP 5779)]
using path '/usr/share/rezound' for share data directory
[New Thread 32769 (LWP 5780)]
[New Thread 16386 (LWP 5781)]
If rezound dies unexpectedly while seeking with the
keyboard, auto-repeat may be disabled.. if this happens
run 'rezound --fix-auto-repeat'

Program received signal SIGUSR2, User defined signal 2.
[Switching to Thread 16386 (LWP 5781)]
0x40a77768 in sigsuspend () from /lib/libc.so.6

Second Case

If jack is started with
jackd -d alsa -d hw:0
(without realtime option)

rezound starts, but when playing a stereo wave file,
both -the right and the left channel- come out of the
left speaker, the right one is dead.

Are there some more debug options? Do I have to modify
the configuration of rezound somewhere? Please advice.

I am using
alsa-driver 1.0.9b
jack 0.100.0

If you need more information please let me know.

Thank you,
Stefan

Discussion

  • Shamarel

    Shamarel - 2005-06-17
    • assigned_to: nobody --> ddurham
     
  • errantloons

    errantloons - 2005-10-09

    Logged In: YES
    user_id=1359064

    Hi there,

    Just a fellow user here looking up info on an unrelated
    problem I've been having, but I may have some useful info
    for you.

    First Case/using jack in realtime mode--
    Invoking jack with -R requires higher permissions than is
    usually assigned to normal user accounts. On my machine I
    run jack as root, although I've heard there is a workaround
    that lets you get realtime support on other user accounts.
    In any case, your jack clients have to be running the same
    way that jack is--if you run jack as root, you need to run
    rezound as root, or if you've got a workaround on jack, try
    the same trick on rezound.

    Second Case/using jack without realtime option--
    Check your ~/.rezound/registry.dat file. I'm guessing
    you'll see near the top:

    JACKOutputPortName1="alsa_pcm:playback_1";
    JACKOutputPortName2="alsa_pcm:playback_1";

    try changing to:

    JACKOutputPortName1="alsa_pcm:playback_1";
    JACKOutputPortName2="alsa_pcm:playback_2";

    Good luck,

    EL

     
  • Olivier HUMBERT

    Olivier HUMBERT - 2016-03-11

    I suggest this thread to be closed since it's pretty old (2005) and doesn't look to apply to a current setup (aka: "it works for me" (tm) ).

     

Log in to post a comment.