#53 Unable to record with Jack

open
nobody
None
5
2014-04-27
2010-04-08
jkroll
No

Hi,

Recording fails when Jack sound input is selected. After pressing the Record button, an error message pops up. I'm attaching a screenshot of my Jack settings and the error message.

Discussion

  • jkroll
    jkroll
    2010-04-08

    Screenshot of error message after recording and settings window.

     
  • Gilzad
    Gilzad
    2010-04-21

    Hello,

    I can confirm that.

    The error messages you'd get in the gtk-frontend can be random, when using jack fails.
    It might report "failed shared memory segment" or "window size specs out of bounds" or "invalid param attributes" and sometimes it will even work.

    I could get it running by calling it with the same command again immediately:

    gilzad@gilzad:~$ recordmydesktop --use-jack renoise:output_01_left
    Window size specification out of bounds!(current resolution:1920x1200)
    gilzad@gilzad:~$ recordmydesktop --use-jack renoise:output_01_left
    Window size specification out of bounds!(current resolution:1920x1200)
    gilzad@gilzad:~$ recordmydesktop --use-jack renoise:output_01_left
    Initial recording window is set to:
    X:-27992 Y:0 Width:29912 Height:1200
    Adjusted recording window is set to:
    X:-27988 Y:0 Width:29904 Height:1200
    Your window manager appears to be Metacity

    Initializing...
    jack_client_new: deprecated
    Failed to obtain Shared Memory segment!
    Capturing!
    gilzad@gilzad:~$ recordmydesktop --use-jack renoise:output_01_left
    Initial recording window is set to:
    X:680 Y:0 Width:1240 Height:1200
    Adjusted recording window is set to:
    X:672 Y:0 Width:1248 Height:1200
    Your window manager appears to be Metacity

    Initializing...
    jack_client_new: deprecated
    Capturing!
    ^C
    *********************************************

    Cached 2 MB, from 222 MB that were received.
    Average cache compression ratio: 99.0 %

    *********************************************
    Saved 39 frames in a total of 39 requests
    Shutting down.....
    STATE:ENCODING
    Encoding started!
    This may take several minutes.
    Pressing Ctrl-C will cancel the procedure (resuming will not be possible, but
    any portion of the video, which is already encoded won't be deleted).
    Please wait...
    Output file: out.ogv
    [102%]
    Encoding finished!
    Wait a moment please...

    Done.
    Written 215365 bytes
    (215089 of which were video data and 276 audio data)

    Cleanning up cache...
    Done!!!
    Goodbye!
    gilzad@gilzad:~$

    ..during that time I did not change any settings on the jack side and re-called RMD like a brute-force-attack.

    One other time I got:

    gilzad@gilzad:~$ recordmydesktop --channels=2 --use-jack renoise:output_01_left renoise:output_01_right
    Initial recording window is set to:
    X:-3344 Y:0 Width:5264 Height:1200
    Adjusted recording window is set to:
    X:-3344 Y:0 Width:5264 Height:1200
    Your window manager appears to be Metacity

    Initializing...
    jack_client_new: deprecated
    X Error: BadMatch (invalid parameter attributes)

    Beside that I'm having a hard time connecting RMD to two ports (stereo) via jack (if at all).
    According to the help example this should work:

    recordmydesktop --channels=2 --use-jack renoise:output_01_left renoise:output_01_right

    But if I get RMD to start, then it'll only connect its input1 to the first passed output. Furthermore in qjackctl I can see that RMD only registers one input "input1" to jack. So there's no chance for me to manually connect a second port to it.

    An excerpt of my jack_lsp:

    gilzad@gilzad:~$ jack_lsp
    [...] /* just keeping the list small here */
    renoise:output_01_left
    renoise:output_01_right

    I've done the tests with RMD 0.3.8.1 on Debian Squeeze, kernel 2.6.31.12-rt20.

    Thanks,

    Gilzad

     

  • Anonymous
    2010-08-20

    Hi!

    A fix for this issue has been provided by Torben Hohn. I've sent it via mail to the upstream author and also attached it to a Debian bug report:

    http://bugs.debian.org/588260

    HTH

     
    Last edit: Anonymous 2014-04-03
  • Rafael Vega
    Rafael Vega
    2014-04-27

    Hi. Is this project being maintained? I see a bug report here with a working patch about 4 years old.
    Anyway, the bug is still there in Debian 7.