To Pd-announce:
Pd 0.51-0test2 is up. It should fix the code signing problem in test1 ofr Macintoshes. No difference from test1 on other OSes.
http://msp.ucsd.edu/software.htm
cheers Miller
Pd-announce mailing list Pd-announce@lists.iem.at https://lists.puredata.info/listinfo/pd-announce
Em sex., 29 de mai. de 2020 às 23:22, Miller Puckette via Pd-announce < pd-announce@lists.iem.at> escreveu:
To Pd-announce:
Pd 0.51-0test2 is up. It should fix the code signing problem in test1 ofr Macintoshes.
More precisely, Macs on Catalina.
For me, it still asks to throw pd into the trash the 1st time I try to open it, but I guess that's life now, and I still find it takes longes to load externals and patches.
cheers
One thing is, you can throw Pd in the trash anytime you want - it'll still be easy to get another copy :)
Anyhow, I'm curious about the slow load times you're seeing - am I right that this is on Catalina? If loads on older Mac OSes are slower for some reason, maybe I can test that on my 10.6 or 10.7 machines :)
Miller
On Sat, May 30, 2020 at 01:03:39AM -0300, Alexandre Torres Porres wrote:
Em sex., 29 de mai. de 2020 ??s 23:22, Miller Puckette via Pd-announce < pd-announce@lists.iem.at> escreveu:
To Pd-announce:
Pd 0.51-0test2 is up. It should fix the code signing problem in test1 ofr Macintoshes.
More precisely, Macs on Catalina.
For me, it still asks to throw pd into the trash the 1st time I try to open it, but I guess that's life now, and I still find it takes longes to load externals and patches.
cheers
Em sáb., 30 de mai. de 2020 às 13:42, Miller Puckette msp@ucsd.edu escreveu:
One thing is, you can throw Pd in the trash anytime you want - it'll still be easy to get another copy :)
hahahah
Anyhow, I'm curious about the slow load times you're seeing - am I right that this is on Catalina?
yup, same computer, but on Mojave (the previous one) I don't see this.
For me, on almost-latest macOS (10.15.4, although 10.15.5 just came out), test2 will not load externals at all.
I get the "… couldn’t create” message in the Pd Window, but whereas previously I could quit Pd, go to System Preferences > Security & Privacy and there would be a little message telling me the last piece of software that was blocked (and allowing me to unblock it), that message no longer appears.
To make matters worse, when I go back to 0.50-2, none of my externals will load there, either, now that I’ve run test2.
Yikes! Kevin
On May 29, 2020, at 4:01 PM, Miller Puckette via Pd-announce pd-announce@lists.iem.at wrote:
To Pd-announce:
Pd 0.51-0test2 is up. It should fix the code signing problem in test1 ofr Macintoshes. No difference from test1 on other OSes.
http://msp.ucsd.edu/software.htm
cheers Miller
Pd-announce mailing list Pd-announce@lists.iem.at https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-announce... _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-list__;!...
Hi all, thanks very much for this work.
I'm testing on Catalina 10.15.5. I installed Pd-0.51-0test2 when I had System Integrity Protection and Gatekeeper disabled. I got an initial warning asking if I wanted to open the software, and a request for microphone access the first time I turned on DSP. Also got a dialog confirming that I wanted to allow network comm when loading a patch with [netsend]/[netreceive]. After that, I've had no issues, and all of the externals I've tried so far are working with no increased load time that I can notice. I've used ofelia, tof, hcs, timbreID, and a DSP extern of mine for a current project - all working fine.
Since that initial run I re-enabled SIP and Gatekeeper to see if that would affect performance. After reboot, it brought up the above warning/confirmation dialogs again, but then no problems and still no increased loading times here.
PS: I happen to have a project that involves lots of TCP messaging between remote networked players and we're meeting twice weekly these days, so I can look for any issues related to network performance. And I'm happy to test/confirm any specific details of this release - I have the blessing/curse of 3 separate machines running Ubuntu 18.04.4 LTS, Mac OS Catalina, and Windows 10.
On Sat, May 30, 2020 at 4:07 AM Kevin Haywood via Pd-list < pd-list@lists.iem.at> wrote:
For me, on almost-latest macOS (10.15.4, although 10.15.5 just came out), test2 will not load externals at all.
I get the "… couldn’t create” message in the Pd Window, but whereas previously I could quit Pd, go to System Preferences > Security & Privacy and there would be a little message telling me the last piece of software that was blocked (and allowing me to unblock it), that message no longer appears.
To make matters worse, when I go back to 0.50-2, none of my externals will load there, either, now that I’ve run test2.
Yikes! Kevin
On May 29, 2020, at 4:01 PM, Miller Puckette via Pd-announce <
pd-announce@lists.iem.at> wrote:
To Pd-announce:
Pd 0.51-0test2 is up. It should fix the code signing problem in test1
ofr
Macintoshes. No difference from test1 on other OSes.
http://msp.ucsd.edu/software.htm
cheers Miller
Pd-announce mailing list Pd-announce@lists.iem.at
https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-announce...
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management ->
https://urldefense.com/v3/__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
This is deeply worrisome... it seems like your OS has somehow decided to ban the externs themselves (irrespective of Pd).
Is it feasible for you to either make or download an extern you haven't used before and see if an older Pd can at least load that one? And anyway, are these your own externs (that you compiled) that don't load, or downloaded externs, or both?
thanks M
On Sat, May 30, 2020 at 12:24:36AM -0700, Kevin Haywood wrote:
For me, on almost-latest macOS (10.15.4, although 10.15.5 just came out), test2 will not load externals at all.
I get the "??? couldn???t create??? message in the Pd Window, but whereas previously I could quit Pd, go to System Preferences > Security & Privacy and there would be a little message telling me the last piece of software that was blocked (and allowing me to unblock it), that message no longer appears.
To make matters worse, when I go back to 0.50-2, none of my externals will load there, either, now that I???ve run test2.
Yikes! Kevin
On May 29, 2020, at 4:01 PM, Miller Puckette via Pd-announce pd-announce@lists.iem.at wrote:
To Pd-announce:
Pd 0.51-0test2 is up. It should fix the code signing problem in test1 ofr Macintoshes. No difference from test1 on other OSes.
http://msp.ucsd.edu/software.htm
cheers Miller
Pd-announce mailing list Pd-announce@lists.iem.at https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-announce... _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-list__;!...
Ok, current testing results:
Created and built a new external in Xcode. The external loads and runs as expected in 0.51-0test2, without throwing any kind of warning.
The externals that weren’t loading yesterday with 0.51-0test2 suddenly work again, in both that version and in 0.50-2. These are externals that I had created myself, as well as some that a friend had created and compiled.
However, I next used Deken to install zexyv2.3.0(Linux-amd64-32)(Windows-amd64-32)(Windows-i386-32).dek, and Zexy’s compiled externals such as demux and demultiplex can’t be created in either 0.51-0test2 or in 0.50-2. No mention appears in System Preferences > Security and Privacy.
However, I next used Deken to install cyclonev0.4(Darwin-i386-32).dek, and compiled externals from there run as expected.
Not sure what’s happening : ) Kevin
On May 30, 2020, at 9:35 AM, Miller Puckette msp@ucsd.edu wrote:
This is deeply worrisome... it seems like your OS has somehow decided to ban the externs themselves (irrespective of Pd).
Is it feasible for you to either make or download an extern you haven't used before and see if an older Pd can at least load that one? And anyway, are these your own externs (that you compiled) that don't load, or downloaded externs, or both?
thanks M
On Sat, May 30, 2020 at 12:24:36AM -0700, Kevin Haywood wrote:
For me, on almost-latest macOS (10.15.4, although 10.15.5 just came out), test2 will not load externals at all.
I get the "??? couldn???t create??? message in the Pd Window, but whereas previously I could quit Pd, go to System Preferences > Security & Privacy and there would be a little message telling me the last piece of software that was blocked (and allowing me to unblock it), that message no longer appears.
To make matters worse, when I go back to 0.50-2, none of my externals will load there, either, now that I???ve run test2.
Yikes! Kevin
On May 29, 2020, at 4:01 PM, Miller Puckette via Pd-announce pd-announce@lists.iem.at wrote:
To Pd-announce:
Pd 0.51-0test2 is up. It should fix the code signing problem in test1 ofr Macintoshes. No difference from test1 on other OSes.
http://msp.ucsd.edu/software.htm
cheers Miller
Pd-announce mailing list Pd-announce@lists.iem.at https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-announce... _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-list__;!...
Zexy’s compiled externals such as demux and demultiplex can’t be created in either 0.51-0test2 or in 0.50-2
Did you actually load zexy, i.e. [declare -lib zexy]?
Christof
On 30.05.2020 20:08, Kevin Haywood via Pd-list wrote:
Ok, current testing results:
Created and built a new external in Xcode. The external loads and runs as expected in 0.51-0test2, without throwing any kind of warning.
The externals that weren’t loading yesterday with 0.51-0test2 suddenly work again, in both that version and in 0.50-2. These are externals that I had created myself, as well as some that a friend had created and compiled.
However, I next used Deken to install zexyv2.3.0(Linux-amd64-32)(Windows-amd64-32)(Windows-i386-32).dek, and Zexy’s compiled externals such as demux and demultiplex can’t be created in either 0.51-0test2 or in 0.50-2. No mention appears in System Preferences > Security and Privacy.
However, I next used Deken to install cyclonev0.4(Darwin-i386-32).dek, and compiled externals from there run as expected.
Not sure what’s happening : ) Kevin
On May 30, 2020, at 9:35 AM, Miller Puckette msp@ucsd.edu wrote:
This is deeply worrisome... it seems like your OS has somehow decided to ban the externs themselves (irrespective of Pd).
Is it feasible for you to either make or download an extern you haven't used before and see if an older Pd can at least load that one? And anyway, are these your own externs (that you compiled) that don't load, or downloaded externs, or both?
thanks M
On Sat, May 30, 2020 at 12:24:36AM -0700, Kevin Haywood wrote:
For me, on almost-latest macOS (10.15.4, although 10.15.5 just came out), test2 will not load externals at all.
I get the "??? couldn???t create??? message in the Pd Window, but whereas previously I could quit Pd, go to System Preferences > Security & Privacy and there would be a little message telling me the last piece of software that was blocked (and allowing me to unblock it), that message no longer appears.
To make matters worse, when I go back to 0.50-2, none of my externals will load there, either, now that I???ve run test2.
Yikes! Kevin
On May 29, 2020, at 4:01 PM, Miller Puckette via Pd-announce pd-announce@lists.iem.at wrote:
To Pd-announce:
Pd 0.51-0test2 is up. It should fix the code signing problem in test1 ofr Macintoshes. No difference from test1 on other OSes.
http://msp.ucsd.edu/software.htm
cheers Miller
Pd-announce mailing list Pd-announce@lists.iem.at https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-announce... _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.com/v3/__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
Sorry, I didn’t see this message!
No, I used Deken to install zexy, then opened a zexy help file. I assumed that that would work, and apparently it doesn’t, but that seems to be a specification issue colliding with an unfounded assumption. Creating [declare -lib zexy] before trying to load a zexy external does indeed cause zexy to work, so thank you. I apologize that I didn’t know this requirement, but I almost never use externals, except occasionally my own.
So, the issue now seems to be that my own externals, and those of a friend who compiled his on macos in 2018 (and which I was using earlier this week in Pd 0.50-2), would neither load nor initiate an OS security prompt of any sort in Pd 0.51-0test2. For some still-inexplicable reason, my externals started working again in both of these versions of Pd after building and loading a newly-created external. macOS Catalina 10.15.4.
Thanks again for your help!
On May 30, 2020, at 11:12 AM, Christof Ressi info@christofressi.com wrote:
Zexy’s compiled externals such as demux and demultiplex can’t be created in either 0.51-0test2 or in 0.50-2
Did you actually load zexy, i.e. [declare -lib zexy]?
Christof
On 30.05.2020 20:08, Kevin Haywood via Pd-list wrote:
Ok, current testing results:
Created and built a new external in Xcode. The external loads and runs as expected in 0.51-0test2, without throwing any kind of warning.
The externals that weren’t loading yesterday with 0.51-0test2 suddenly work again, in both that version and in 0.50-2. These are externals that I had created myself, as well as some that a friend had created and compiled.
However, I next used Deken to install zexyv2.3.0(Linux-amd64-32)(Windows-amd64-32)(Windows-i386-32).dek, and Zexy’s compiled externals such as demux and demultiplex can’t be created in either 0.51-0test2 or in 0.50-2. No mention appears in System Preferences > Security and Privacy.
However, I next used Deken to install cyclonev0.4(Darwin-i386-32).dek, and compiled externals from there run as expected.
Not sure what’s happening : ) Kevin
On May 30, 2020, at 9:35 AM, Miller Puckette msp@ucsd.edu wrote:
This is deeply worrisome... it seems like your OS has somehow decided to ban the externs themselves (irrespective of Pd).
Is it feasible for you to either make or download an extern you haven't used before and see if an older Pd can at least load that one? And anyway, are these your own externs (that you compiled) that don't load, or downloaded externs, or both?
thanks M
On Sat, May 30, 2020 at 12:24:36AM -0700, Kevin Haywood wrote:
For me, on almost-latest macOS (10.15.4, although 10.15.5 just came out), test2 will not load externals at all.
I get the "??? couldn???t create??? message in the Pd Window, but whereas previously I could quit Pd, go to System Preferences > Security & Privacy and there would be a little message telling me the last piece of software that was blocked (and allowing me to unblock it), that message no longer appears.
To make matters worse, when I go back to 0.50-2, none of my externals will load there, either, now that I???ve run test2.
Yikes! Kevin
On May 29, 2020, at 4:01 PM, Miller Puckette via Pd-announce pd-announce@lists.iem.at wrote:
To Pd-announce:
Pd 0.51-0test2 is up. It should fix the code signing problem in test1 ofr Macintoshes. No difference from test1 on other OSes.
http://msp.ucsd.edu/software.htm
cheers Miller
Pd-announce mailing list Pd-announce@lists.iem.at https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-announce... _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-list__;!...
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-list__;!...
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-list__;!...
Em sáb., 30 de mai. de 2020 às 17:22, Kevin Haywood via Pd-list < pd-list@lists.iem.at> escreveu:
Sorry, I didn’t see this message!
No, I used Deken to install zexy, then opened a zexy help file. I assumed that that would work, and apparently it doesn’t, but that seems to be a specification issue colliding with an unfounded assumption. Creating [declare -lib zexy] before trying to load a zexy external does indeed cause zexy to work, so thank you. I apologize that I didn’t know this requirement, but I almost never use externals, except occasionally my own.
just so you know, you should aslo do that same procedure with cyclone ([declare -lib cyclone] or include it via startup)
So, the issue now seems to be that my own externals, and those of a friend who compiled his on macos in 2018 (and which I was using earlier this week in Pd 0.50-2), would neither load nor initiate an OS security prompt of any sort in Pd 0.51-0test2.
I guess this is because your externals / that of your friend had already been blacklisted by the GateKeeper by trying to open them with an unnotarized Pd (and not setting the necessary security exceptions)
For some still-inexplicable reason, my externals started working again in both of these versions of Pd after building and loading a newly-created external. macOS Catalina 10.15.4.
Newly built externals are not blacklisted.
Christof
On 30.05.2020 22:19, Kevin Haywood wrote:
Sorry, I didn’t see this message!
No, I used Deken to install zexy, then opened a zexy help file. I assumed that that would work, and apparently it doesn’t, but that seems to be a specification issue colliding with an unfounded assumption. Creating [declare -lib zexy] before trying to load a zexy external does indeed cause zexy to work, so thank you. I apologize that I didn’t know this requirement, but I almost never use externals, except occasionally my own.
So, the issue now seems to be that my own externals, and those of a friend who compiled his on macos in 2018 (and which I was using earlier this week in Pd 0.50-2), would neither load nor initiate an OS security prompt of any sort in Pd 0.51-0test2. For some still-inexplicable reason, my externals started working again in both of these versions of Pd after building and loading a newly-created external. macOS Catalina 10.15.4.
Thanks again for your help!
On May 30, 2020, at 11:12 AM, Christof Ressi info@christofressi.com wrote:
Zexy’s compiled externals such as demux and demultiplex can’t be created in either 0.51-0test2 or in 0.50-2
Did you actually load zexy, i.e. [declare -lib zexy]?
Christof
On 30.05.2020 20:08, Kevin Haywood via Pd-list wrote:
Ok, current testing results:
Created and built a new external in Xcode. The external loads and runs as expected in 0.51-0test2, without throwing any kind of warning.
The externals that weren’t loading yesterday with 0.51-0test2 suddenly work again, in both that version and in 0.50-2. These are externals that I had created myself, as well as some that a friend had created and compiled.
However, I next used Deken to install zexyv2.3.0(Linux-amd64-32)(Windows-amd64-32)(Windows-i386-32).dek, and Zexy’s compiled externals such as demux and demultiplex can’t be created in either 0.51-0test2 or in 0.50-2. No mention appears in System Preferences > Security and Privacy.
However, I next used Deken to install cyclonev0.4(Darwin-i386-32).dek, and compiled externals from there run as expected.
Not sure what’s happening : ) Kevin
On May 30, 2020, at 9:35 AM, Miller Puckette msp@ucsd.edu wrote:
This is deeply worrisome... it seems like your OS has somehow decided to ban the externs themselves (irrespective of Pd).
Is it feasible for you to either make or download an extern you haven't used before and see if an older Pd can at least load that one? And anyway, are these your own externs (that you compiled) that don't load, or downloaded externs, or both?
thanks M
On Sat, May 30, 2020 at 12:24:36AM -0700, Kevin Haywood wrote:
For me, on almost-latest macOS (10.15.4, although 10.15.5 just came out), test2 will not load externals at all.
I get the "??? couldn???t create??? message in the Pd Window, but whereas previously I could quit Pd, go to System Preferences > Security & Privacy and there would be a little message telling me the last piece of software that was blocked (and allowing me to unblock it), that message no longer appears.
To make matters worse, when I go back to 0.50-2, none of my externals will load there, either, now that I???ve run test2.
Yikes! Kevin
On May 29, 2020, at 4:01 PM, Miller Puckette via Pd-announce pd-announce@lists.iem.at wrote:
To Pd-announce:
Pd 0.51-0test2 is up. It should fix the code signing problem in test1 ofr Macintoshes. No difference from test1 on other OSes.
http://msp.ucsd.edu/software.htm
cheers Miller
Pd-announce mailing list Pd-announce@lists.iem.at https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-announce... _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-list__;!...
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-list__;!...
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-list__;!...
On May 30, 2020, at 1:46 PM, Christof Ressi info@christofressi.com wrote:
For some still-inexplicable reason, my externals started working again in both of these versions of Pd after building and loading a newly-created external. macOS Catalina 10.15.4.
Newly built externals are not blacklisted.
I trust you on that, but loading a newly-created external seems to have resulted in my previously-blacklisted externals also loading with no problem.
In the case of my externals, I would guess that perhaps this might be because the new and old all used the same signing certificate? But that wouldn't explain my friend’s externals which he compiled.
So perhaps there’s something else going on which I’ve missed, because no one else has confirmed this yet : \
Kevin
Oh, I thought you've only spoken about the external you've freshly compiled... I have no idea. And I have to say that I'm not a macOS expert (just had to occasionally fight with macOS Catalina in the last few weeks), so don't trust me on anything I say about macOS :-)
Christof
On 30.05.2020 23:36, Kevin Haywood wrote:
On May 30, 2020, at 1:46 PM, Christof Ressi <info@christofressi.com mailto:info@christofressi.com> wrote:
For some still-inexplicable reason, my externals started working again in both of these versions of Pd after building and loading a newly-created external. macOS Catalina 10.15.4.
Newly built externals are not blacklisted.
I trust you on that, but loading a newly-created external seems to have resulted in my previously-blacklisted externals also loading with no problem.
In the case of my externals, I would guess that perhaps this might be because the new and old all used the same signing certificate? But that wouldn't explain my friend’s externals which he compiled.
So perhaps there’s something else going on which I’ve missed, because no one else has confirmed this yet : \
Kevin
-
Alexandre Torres Porres -
Christof Ressi -
Kevin Haywood -
Miller Puckette -
Miller Puckette via Pd-announce -
William Brent