this must be a bug then... I don't see why Jack should only work with "callbacks" enabled.

On 14.12.2021 14:51, Csaba Láng wrote:
I confirm Jack works on Big Sur with using callback in the audio settings.

Thanks for the hint.

On Tue, Dec 14, 2021 at 2:16 PM William Brent <[email protected]> wrote:

    Good news - this new build is indeed working for me with JACK
    1.9.19 on Big Sur 11.6.1 (Intel 64bit hardware). I'll update my
    comment on the ticket to document it. Thanks IOhannes!

    On Tue, Dec 14, 2021 at 4:37 AM IOhannes m zmoelnig
    <[email protected]> wrote:


        On 12/13/21 22:06, IOhannes m zmölnig wrote:
         >
         >
         > once it finished building, the dmg will be available on
        
<https://git.iem.at/pd/pure-data/-/jobs/33818/artifacts/file/Pd-0.52-0test3-2-g6ca9539f.dmg>


         >
         > could you please be so kind and test with that version as well?

        my first tests show that this version indeed works (at least
        on Catalina).
        could someone on Big Sur or Monterey confirm this?


        gfsdr
        IOhannes


        PS: here's a bit more in-depth tech babble, for those
        interested what (I
        think) is going on:

        >
        > this info in the issue was incredibly helpful:
        >  > JACK protocol mismatch 8
        >
        > afaict it tries to tell us that Pd and jackd speak different
        (and
        > obviously incompatible) protocols.
        >
        > i'm currently trying to create a new binary on our CI that
        finally uses
        > the pre-built binaries from jackaudio.org
        <http://jackaudio.org> (as dan always suggested).
        >
        > hopefully this will get the protocol version right.

        i now think that this was a red hering.

        the problem really seems to be that depending on whether Pd is
        linked
        against  JACK from homebrew or jackaudio.org
        <http://jackaudio.org> it will look for the
        library in /usr/local/opt/jack/lib/ resp. /usr/local/lib/.
        for reasons i do not fully understand yet, a homebrew-jacked
        Pd (that
        looks for libjack.so.0.1.0 in /usr/local/opt/jack/lib/) will
        refuse to
        load the library if it is found in /usr/local/lib/ (even
        though this is
        a standard search path for libraries).
        copying/symlinking the libjack.so to the searched for
        directory, makes
        binaries work.

        $ mkdir /usr/local/opt/jack/lib/
        $ ln -s /usr/local/lib/libjack.0.1.0.dylib
        /usr/local/opt/jack/lib/


        of course this is not really practical
        _______________________________________________
        [email protected] mailing list
        UNSUBSCRIBE and account-management ->
        https://lists.puredata.info/listinfo/pd-list



-- William Brent

    “Great minds flock together”
    Conflations: conversational idiom for the 21st century

    www.conflations.com <http://www.conflations.com>
    _______________________________________________
    [email protected] mailing list
    UNSUBSCRIBE and account-management ->
    https://lists.puredata.info/listinfo/pd-list


_______________________________________________
[email protected]  mailing list
UNSUBSCRIBE and account-management 
->https://lists.puredata.info/listinfo/pd-list
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Reply via email to