Hello,

Just upgraded a machine to the latest Fedora, shipping with JACK-1.9.14,
and now caed won't connect to JACK.

    $ caed -d
    QSettings::sync: filename is null/empty
    Cannot connect to server socket err = Aucun fichier ou dossier de ce
    type
    Cannot connect to server request channel
    jack server is not running or cannot be started
    JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
    skipping unlock
    JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
    skipping unlock
    unable to communication with JACK server
    caed: unable to communicate with JACK server
    JACK general failure
    caed: JACK general failure
    no connection to JACK server
    caed: no connection to JACK server
    caed: Found TwoLAME encoder library, MPEG L2 encoding supported
    caed: Found MAD decoder library, MPEG L2 decoding supported
    caed: using realtime scheduling, priority=8
    caed: cae started
    caed: cae saveState(), set restart hint to Never


I painfully downgraded JACK to version 1.9.12 (which I knew was working)
and now I get normal caed operation:

    $ caed -d
    QSettings::sync: filename is null/empty
    caed: connected to JACK server
    caed: Found TwoLAME encoder library, MPEG L2 encoding supported
    caed: Found MAD decoder library, MPEG L2 decoding supported
    caed: using realtime scheduling, priority=54
    caed: cae started
    caed: cae saveState(), set restart hint to Never


Is it something that rings a bell? I know it's 2.19.3 related, and maybe
the latest 3.X already has fixes for this, but if so, is there something
I could patch for 2.19.3 here?

Thanks!

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Reply via email to