seems to run fine on "macOS Sierra - 10.12.6"
miller: does it also run on "Mac OS X Lion - 10.7"? (or even "OS X Snow Leopard - 10.6"?)
gffxyd IOhannes
Nope - Wish 8.6.12 seems to depend on newer Mac features than are on OSX 10.7.
But I'm OK with continuing to compile for 10.7 on my old machine and make it available to people like me :)
Probably stick with Tk 8.6.10 or 11 for that build then.
Meanwhile, the jack mystery is still unsolved as far as I know (the brew version somehow doesn't like newest jackd?)
As explained in previous emails, I don't use jack from Homebrew for my builds. I use the distribution from jack.org http://jack.org/ which is equivalent to the old JackOSX distribution:
https://jackaudio.org/downloads/ https://jackaudio.org/downloads/
You just need to download and run the installer on the build machine, which could also be automated via a script. People needing to use jack installed via Homebrew should build Pd themselves as the those libs doesn't seem to enable weak linking like the ones in the installer AFAICT.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
As explained in previous emails, I don't use jack from Homebrew for my builds. I use the distribution from jack.org <https://urldefense.proofpoint.com/v2/url?u=http-3A__jack.org_&d=DwIFAg&a... > which is equivalent to the old JackOSX distribution:
https://urldefense.proofpoint.com/v2/url?u=https-3A__jackaudio.org_downloads... <https://urldefense.proofpoint.com/v2/url?u=https-3A__jackaudio.org_downloads... >
You just need to download and run the installer on the build machine, which could also be automated via a script. People needing to use jack installed via Homebrew should build Pd themselves as the those libs doesn't seem to enable weak linking like the ones in the installer AFAICT.
Dan Wilcox
Right ho - Iohannes - I'm hoping this is something you can fix in the CI builds (since I plan to distribute that as the up-to-date compiled version for MacOS)
cheers M
On 12/13/21 03:42, Miller Puckette via Pd-list wrote:
As explained in previous emails, I don't use jack from Homebrew for my builds. I use the distribution from jack.org <https://urldefense.proofpoint.com/v2/url?u=http-3A__jack.org_&d=DwIFAg&a... > which is equivalent to the old JackOSX distribution:
https://urldefense.proofpoint.com/v2/url?u=https-3A__jackaudio.org_downloads... <https://urldefense.proofpoint.com/v2/url?u=https-3A__jackaudio.org_downloads... >
You just need to download and run the installer on the build machine, which could also be automated via a script. People needing to use jack installed via Homebrew should build Pd themselves as the those libs doesn't seem to enable weak linking like the ones in the installer AFAICT.
Dan Wilcox
Right ho - Iohannes - I'm hoping this is something you can fix in the CI builds
yes of course.
i'd still like to understand the problem first though.
my setup is: macOS X Sierra (10.7) in a VM
if i install the dmg file from my CI-scripts (now that they use a non-broken Tcl/Tk) Pd opens up just fine. going to the media menu, i see two options for the audio backend:
- standard (portaudio)
- jack
selecting "jack" i get an error on the Pd-console, saying:
Can't open Jack (it seems not to be installed)
this is expected, as i haven't installed jack.
i then download JACK-1.9.19 from https://jackaudio.org/downloads/, extract it, and run the jack2.pkg found withing. this should install JACK.
i *restart* Pd and select "jack" again, and now i get an error
JACK: couldn't connect to server, is JACK running?
again, tihs is expected, as i haven't started JACK.
so i open up qJackCtl (also found in the download from jackaudio.org), and start the JACK server (i use the *dummy* audio backend, as the VM has no soundcard).
back in Pd, i again select "jack" as the backend, and - tada - no more warnings *and* Pd shows up in the qjackctl graph.
the binary i'm using is this one (Tcl/Tk is universal; but Pd itself is only amd64; this is built with JACK from homebrew): https://git.iem.at/pd/pure-data/-/jobs/33751/artifacts/download
william: could you tell me where our paths deviate?
gfmdsa IOhannes
Hi, here are the steps I've carried out in my test:
I'm using macOS Big Sur 11.6.1 on an Intel 64bit machine. I've already got JACK 1.9.19 installed from https://jackaudio.org/downloads/. I went with the Intel 64bit installer as opposed to the universal installer. My version of Pd 0.52-0 test3 is the one "compiled for Macintosh OS 10 or later" from Miller's page.
When I open Pd-0.52-0test3.app and choose "jack" as the audio backend, I get an error in the Pd console saying "JACK: couldn't connect to server, is JACK running?"
I then quit Pd entirely and start QjackCtl (also obtained from the https://jackaudio.org/downloads/ install package). I can successfully start the JACK server through QjackCtl and engage with other apps like Ardour. When I start Pd again and choose "jack" as the audio backend, I still receive the "JACK: couldn't connect to server, is JACK running?" error and "pure_data" does not show up in the JACK connection graph.
If I then start Dan's most recent build of test3 (Pd-0.52-0test3-x86_64-jack.app) from this email thread, choosing "jack" from the Media menu results in no error and "pure_data" shows up in the JACK connection graph.
Thanks and let me know if I can test other attempts to fix this. I'll keep an eye on this thread.
On Mon, Dec 13, 2021 at 4:29 AM IOhannes m zmölnig zmoelnig@iem.at wrote:
On 12/13/21 03:42, Miller Puckette via Pd-list wrote:
As explained in previous emails, I don't use jack from Homebrew for my
builds. I use the distribution from jack.org < https://urldefense.proofpoint.com/v2/url?u=http-3A__jack.org_&d=DwIFAg&a...
which is equivalent to the old JackOSX distribution:
https://urldefense.proofpoint.com/v2/url?u=https-3A__jackaudio.org_downloads... < https://urldefense.proofpoint.com/v2/url?u=https-3A__jackaudio.org_downloads...
You just need to download and run the installer on the build machine,
which could also be automated via a script. People needing to use jack installed via Homebrew should build Pd themselves as the those libs doesn't seem to enable weak linking like the ones in the installer AFAICT.
Dan Wilcox
Right ho - Iohannes - I'm hoping this is something you can fix in the CI builds
yes of course.
i'd still like to understand the problem first though.
my setup is: macOS X Sierra (10.7) in a VM
if i install the dmg file from my CI-scripts (now that they use a non-broken Tcl/Tk) Pd opens up just fine. going to the media menu, i see two options for the audio backend:
- standard (portaudio)
- jack
selecting "jack" i get an error on the Pd-console, saying:
Can't open Jack (it seems not to be installed)
this is expected, as i haven't installed jack.
i then download JACK-1.9.19 from https://jackaudio.org/downloads/, extract it, and run the jack2.pkg found withing. this should install JACK.
i *restart* Pd and select "jack" again, and now i get an error
JACK: couldn't connect to server, is JACK running?
again, tihs is expected, as i haven't started JACK.
so i open up qJackCtl (also found in the download from jackaudio.org), and start the JACK server (i use the *dummy* audio backend, as the VM has no soundcard).
back in Pd, i again select "jack" as the backend, and - tada - no more warnings *and* Pd shows up in the qjackctl graph.
the binary i'm using is this one (Tcl/Tk is universal; but Pd itself is only amd64; this is built with JACK from homebrew): https://git.iem.at/pd/pure-data/-/jobs/33751/artifacts/download
william: could you tell me where our paths deviate?
gfmdsa IOhannes
On 12/13/21 14:56, William Brent wrote:
If I then start Dan's most recent build of test3 (Pd-0.52-0test3-x86_64-jack.app) from this email thread, choosing "jack" from the Media menu results in no error and "pure_data" shows up in the JACK connection graph.
thanks for the info.
i'm having a bit trouble finding the relevant infos in this growing thread (getting old, i guess), so i've started a ticket on github to collect all this information.
https://github.com/pure-data/pure-data/issues/1512
it would be supercool if you could add your info as well. (there's no need to test with JackOSX like I did - i only did this because Jack-1.9.19 was not really working on ElCapitan)
Thanks and let me know if I can test other attempts to fix this. I'll keep an eye on this thread.
could you also try the "iem-ci" build that is linked in the ticket? (it links to a disk image, that should be signed and notarized) that would be great.
gfmadsr IOhannes
No problem - just posted a comment with all of my info there. Unfortunately, no luck with the iem-ci build on my system either...
On Mon, Dec 13, 2021 at 10:03 AM IOhannes m zmoelnig zmoelnig@iem.at wrote:
On 12/13/21 14:56, William Brent wrote:
If I then start Dan's most recent build of test3 (Pd-0.52-0test3-x86_64-jack.app) from this email thread, choosing "jack" from the Media menu results in no error and "pure_data" shows up in the JACK connection graph.
thanks for the info.
i'm having a bit trouble finding the relevant infos in this growing thread (getting old, i guess), so i've started a ticket on github to collect all this information.
https://github.com/pure-data/pure-data/issues/1512
it would be supercool if you could add your info as well. (there's no need to test with JackOSX like I did - i only did this because Jack-1.9.19 was not really working on ElCapitan)
Thanks and let me know if I can test other attempts to fix this. I'll
keep
an eye on this thread.
could you also try the "iem-ci" build that is linked in the ticket? (it links to a disk image, that should be signed and notarized) that would be great.
gfmadsr IOhannes _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 12/13/21 21:20, William Brent wrote:
No problem - just posted a comment with all of my info there. Unfortunately, no luck with the iem-ci build on my system either...
thanks.
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 (as dan always suggested).
hopefully this will get the protocol version right.
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?
gfmdsf IOhannes
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 (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 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
Iohannes, I tested jack on Big Sur (11.6.1) but looks like no audio is coming out. [image: Screenshot 2021-12-14 at 13.46.31.png]
Output device must be the same as input, I cannot change it in Pd. Portaudio works fine but Jack is without sound. Best, Popesz
On Tue, Dec 14, 2021 at 10:37 AM IOhannes m zmoelnig zmoelnig@iem.at 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...
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 (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 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 _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 12/14/21 13:49, Csaba Láng wrote:
Iohannes, I tested jack on Big Sur (11.6.1) but looks like no audio is coming out. [image: Screenshot 2021-12-14 at 13.46.31.png]
Output device must be the same as input, I cannot change it in Pd. Portaudio works fine but Jack is without sound.
- make sure that you have connected Pd to your soundcard in qJackCtl
(using the Graph resp Connect button)
2. turn on "callbacks" in Pd's audio settings (it seems that this is
required on macOS)
thanks for testing.
gfmasdr IOhannes
- turn on "callbacks" in Pd's audio settings (it seems that this is
required on macOS)
Are you sure? In my understanding, the "callback scheduler" is generally legacy and usually you would always use the "polling scheduler". (Both the Jack backend and the portaudio backend support both modes.)
Christof
On 14.12.2021 14:10, IOhannes m zmoelnig wrote:
On 12/14/21 13:49, Csaba Láng wrote:
Iohannes, I tested jack on Big Sur (11.6.1) but looks like no audio is coming out. [image: Screenshot 2021-12-14 at 13.46.31.png]
Output device must be the same as input, I cannot change it in Pd. Portaudio works fine but Jack is without sound.
- make sure that you have connected Pd to your soundcard in qJackCtl
(using the
GraphrespConnectbutton) 2. turn on "callbacks" in Pd's audio settings (it seems that this is required on macOS)thanks for testing.
gfmasdr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On Tue, 2021-12-14 at 14:45 +0100, Christof Ressi wrote:
- turn on "callbacks" in Pd's audio settings (it seems that this
is required on macOS)
Are you sure? In my understanding, the "callback scheduler" is generally legacy and usually you would always use the "polling scheduler". (Both the Jack backend and the portaudio backend support both modes.)
Here's my experience with my on own (recent) Pd build on macOS Catalina and with JACK from jackaudio.org:
Pd works fine with JACK. It works with 'callbacks' unchecked (default) and with 'callbacks' checked. However, for me using 'callbacks' is not at all legacy and it would hurt our team project if it would be removed. From what I measured, the latency added by Pd with 'callbacks' unchecked is roughly the number specified in 'delay(ms)'. With 'callbacks' checked, Pd behaves like many other JACK clients and doesn't add any latency on top of the buffersize induced latency of JACK. So, if low latency is a concern, it seems using 'callbacks' is the the way to go. OTOH, I managed to kill ardour and jack while being connected to Pd with 'callbacks' checked while the CPU was almost maxed out. I think it makes sense to have 'callbacks' unchecked by default for higher resilience, but I find 'callbacks' a rather valuable option.
That said, I never really understood what 'callbacks' means. To me it looks like "polling scheduler" means that Pd maintains its own separate (from JACK) ringbuffer whose size is given by 'delay(ms)', while 'callbacks' means no additional ringbuffer.
@IOhannes: re your request of Pd-JACK-macOS experiences: Probably more interesting are the results with the proposed Pd builds that are candidates for distribution than with my self-compiled Pd. I'll try to test those soon.
Roman
That said, I never really understood what 'callbacks' means.
It means that the Pd scheduler runs directly in the audio callback. This is what most audio applications do. However, Pd does many things that are not realtime-safe, which can be a problem.
To me it looks like "polling scheduler" means that Pd maintains its own separate (from JACK) ringbuffer whose size is given by 'delay(ms)', while 'callbacks' means no additional ringbuffer.
With the polling scheduler, the Pd scheduler runs in a seperate thread and uses a lockfree ringbuffer to communicate with the audio callback. In this case, the latter does nothing but exchanging input/output samples. The disadvantage is some extra latency. The advantage is better control over latency (not restricted to the values allowed by the hardware driver) and more tolerance towards non-realtime-safe operations.
However, for me using 'callbacks' is not at all legacy and it would hurt our team project if it would be removed. From what I measured, the latency added by Pd with 'callbacks' unchecked is roughly the number specified in 'delay(ms)'. With 'callbacks' checked, Pd behaves like many other JACK clients and doesn't add any latency on top of the buffersize induced latency of JACK.
Ah, I see the issue. When using the polling scheduler, you would typically use the lowest possible hardware buffer size (ideally 64 samples) and use "delay" to control the latency. In theory, the polling scheduler only adds one block of 64 samples of extra latency (compared to the callback scheduler). In practice, the extra latency is at least the hardware buffer size because for every hardware buffer the Pd scheduler is ticked several times in a row, so the ring buffer must be large enough not to overflow.
If the Jack server uses a larger hardware buffer size, the extra latency of the polling scheduler becomes more pronounced.
Christof
On 14.12.2021 15:18, Roman Haefeli wrote:
On Tue, 2021-12-14 at 14:45 +0100, Christof Ressi wrote:
- turn on "callbacks" in Pd's audio settings (it seems that this
is required on macOS)
Are you sure? In my understanding, the "callback scheduler" is generally legacy and usually you would always use the "polling scheduler". (Both the Jack backend and the portaudio backend support both modes.)
Here's my experience with my on own (recent) Pd build on macOS Catalina and with JACK from jackaudio.org:
Pd works fine with JACK. It works with 'callbacks' unchecked (default) and with 'callbacks' checked. However, for me using 'callbacks' is not at all legacy and it would hurt our team project if it would be removed. From what I measured, the latency added by Pd with 'callbacks' unchecked is roughly the number specified in 'delay(ms)'. With 'callbacks' checked, Pd behaves like many other JACK clients and doesn't add any latency on top of the buffersize induced latency of JACK. So, if low latency is a concern, it seems using 'callbacks' is the the way to go. OTOH, I managed to kill ardour and jack while being connected to Pd with 'callbacks' checked while the CPU was almost maxed out. I think it makes sense to have 'callbacks' unchecked by default for higher resilience, but I find 'callbacks' a rather valuable option.
That said, I never really understood what 'callbacks' means. To me it looks like "polling scheduler" means that Pd maintains its own separate (from JACK) ringbuffer whose size is given by 'delay(ms)', while 'callbacks' means no additional ringbuffer.
@IOhannes: re your request of Pd-JACK-macOS experiences: Probably more interesting are the results with the proposed Pd builds that are candidates for distribution than with my self-compiled Pd. I'll try to test those soon.
Roman
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Forgot to say: the callback scheduler will not be removed. If it works for you, by all means keep using it!
On 14.12.2021 15:53, Christof Ressi wrote:
That said, I never really understood what 'callbacks' means.
It means that the Pd scheduler runs directly in the audio callback. This is what most audio applications do. However, Pd does many things that are not realtime-safe, which can be a problem.
To me it looks like "polling scheduler" means that Pd maintains its own separate (from JACK) ringbuffer whose size is given by 'delay(ms)', while 'callbacks' means no additional ringbuffer.
With the polling scheduler, the Pd scheduler runs in a seperate thread and uses a lockfree ringbuffer to communicate with the audio callback. In this case, the latter does nothing but exchanging input/output samples. The disadvantage is some extra latency. The advantage is better control over latency (not restricted to the values allowed by the hardware driver) and more tolerance towards non-realtime-safe operations.
However, for me using 'callbacks' is not at all legacy and it would hurt our team project if it would be removed. From what I measured, the latency added by Pd with 'callbacks' unchecked is roughly the number specified in 'delay(ms)'. With 'callbacks' checked, Pd behaves like many other JACK clients and doesn't add any latency on top of the buffersize induced latency of JACK.
Ah, I see the issue. When using the polling scheduler, you would typically use the lowest possible hardware buffer size (ideally 64 samples) and use "delay" to control the latency. In theory, the polling scheduler only adds one block of 64 samples of extra latency (compared to the callback scheduler). In practice, the extra latency is at least the hardware buffer size because for every hardware buffer the Pd scheduler is ticked several times in a row, so the ring buffer must be large enough not to overflow.
If the Jack server uses a larger hardware buffer size, the extra latency of the polling scheduler becomes more pronounced.
Christof
On 14.12.2021 15:18, Roman Haefeli wrote:
On Tue, 2021-12-14 at 14:45 +0100, Christof Ressi wrote:
- turn on "callbacks" in Pd's audio settings (it seems that this
is required on macOS)
Are you sure? In my understanding, the "callback scheduler" is generally legacy and usually you would always use the "polling scheduler". (Both the Jack backend and the portaudio backend support both modes.)
Here's my experience with my on own (recent) Pd build on macOS Catalina and with JACK from jackaudio.org:
Pd works fine with JACK. It works with 'callbacks' unchecked (default) and with 'callbacks' checked. However, for me using 'callbacks' is not at all legacy and it would hurt our team project if it would be removed. From what I measured, the latency added by Pd with 'callbacks' unchecked is roughly the number specified in 'delay(ms)'. With 'callbacks' checked, Pd behaves like many other JACK clients and doesn't add any latency on top of the buffersize induced latency of JACK. So, if low latency is a concern, it seems using 'callbacks' is the the way to go. OTOH, I managed to kill ardour and jack while being connected to Pd with 'callbacks' checked while the CPU was almost maxed out. I think it makes sense to have 'callbacks' unchecked by default for higher resilience, but I find 'callbacks' a rather valuable option.
That said, I never really understood what 'callbacks' means. To me it looks like "polling scheduler" means that Pd maintains its own separate (from JACK) ringbuffer whose size is given by 'delay(ms)', while 'callbacks' means no additional ringbuffer.
@IOhannes: re your request of Pd-JACK-macOS experiences: Probably more interesting are the results with the proposed Pd builds that are candidates for distribution than with my self-compiled Pd. I'll try to test those soon.
Roman
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On Tue, 2021-12-14 at 16:04 +0100, Christof Ressi wrote:
Forgot to say: the callback scheduler will not be removed. If it works for you, by all means keep using it!
Sorry for the alarmist tone, then. 'legacy' sounded to me like 'to be removed in the future'.
Roman
On Tue, 2021-12-14 at 15:53 +0100, Christof Ressi wrote:
That said, I never really understood what 'callbacks' means.
It means that the Pd scheduler runs directly in the audio callback
Thanks for your detailed explanation. It all makes sense now, especially why it is not advised to perform non-realtime-safe operations while running callback mode.
Roman
On 12/14/21 14:45, Christof Ressi wrote:
- turn on "callbacks" in Pd's audio settings (it seems that this is
required on macOS)
Are you sure?
i'm not sure at all.
however, i'm testing mostly with the "dummy" backend (rather than a "real" soundcard-based backend like "coreaudio"), and in my tests i need to enable "callbacks" to have Pd do anything. my test usually is just looping back the output of Pd to it's input (so i dont really need a soundcard, but i still know whether Pd can send data to JACK and receive data from JACK)
dfksard IOhannes
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 zmoelnig@iem.at 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...
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 (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 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 _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
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 william.brent@gmail.com 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 zmoelnig@iem.at 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...
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 (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 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 _______________________________________________ Pd-list@lists.iem.at 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 _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
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 william.brent@gmail.com 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 <zmoelnig@iem.at> 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 _______________________________________________ Pd-list@lists.iem.at 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> _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management ->https://lists.puredata.info/listinfo/pd-list
For me, IOhannes' latest build ( https://git.iem.at/pd/pure-data/-/jobs/33818/artifacts/file/Pd-0.52-0test3-2...) and Dan's recent build ( http://docs.danomatika.com/pdbuilds/0.52/Pd-0.52-0test3-x86_64-jack.zip) work on Big Sur 11.6.1 *without* callbacks enabled. I've done a lot of work with Pd/JACK and have never enabled callbacks.
On Tue, Dec 14, 2021 at 9:01 AM Christof Ressi info@christofressi.com wrote:
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 william.brent@gmail.com 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 zmoelnig@iem.at 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...
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 (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 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 _______________________________________________ Pd-list@lists.iem.at 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 _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
_______________________________________________Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Excellent.. I think it's time for test4 :)
M
On Tue, Dec 14, 2021 at 09:22:51AM -0500, William Brent wrote:
For me, IOhannes' latest build ( https://urldefense.proofpoint.com/v2/url?u=https-3A__git.iem.at_pd_pure-2Dda... ) and Dan's recent build ( https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.danomatika.com_pdbu... ) work on Big Sur 11.6.1 *without* callbacks enabled. I've done a lot of work with Pd/JACK and have never enabled callbacks.
On Tue, Dec 14, 2021 at 9:01 AM Christof Ressi info@christofressi.com wrote:
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 william.brent@gmail.com 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 zmoelnig@iem.at wrote:
On 12/13/21 22:06, IOhannes m zmölnig wrote:
once it finished building, the dmg will be available on
< https://urldefense.proofpoint.com/v2/url?u=https-3A__git.iem.at_pd_pure-2Dda... >
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 (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 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 _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.puredata.info_lis...
-- William Brent
“Great minds flock together” Conflations: conversational idiom for the 21st century
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.conflations.com&... _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.puredata.info_lis...
_______________________________________________Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.puredata.info_lis...
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.puredata.info_lis...
-- William Brent
“Great minds flock together” Conflations: conversational idiom for the 21st century
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.conflations.com&...
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.puredata.info_lis...
Em ter., 14 de dez. de 2021 às 19:18, Miller Puckette via Pd-list < pd-list@lists.iem.at> escreveu:
Excellent.. I think it's time for test4 :)
Guess we're almost there. I had brought up some gatom issues and went ahead and tried to fix symbol boxes not being able to generate symbolic floats as before. Seems I nailed it, please revise https://github.com/pure-data/pure-data/pull/1515
Also, I did realize how we're accepting any character in number boxes, while before we filtered them, so I also filtered undesired characters back!
cheers
-
Alexandre Torres Porres -
Christof Ressi -
Csaba Láng -
Dan Wilcox -
IOhannes m zmoelnig -
IOhannes m zmölnig
-
Miller Puckette -
Roman Haefeli -
William Brent