Hi, there's a quick pre-test release of a new "unauthorized" version I'm working on. It's up in deken. Someone on the Pd forum was looking for [playlist] for apple silicon and I had to upload to deken so he can test it (it's just a nightmare now with apple and malware). All objects but the streaming ones seem to be working... I also still need to figure out linking dynamic libs for those but I'm aware they already have issues, so my main concern is to provide the others for now, specially the GUIs! I might solve the streaming deals in new objects in ELSE.
Please test and let me know. I gotta be off for a couple of days for gigs upstate in the meantime. When I'm back I'll clean the dust off my old intel mac that can still run Pd-Extended and try the unauthorized library in there to see how it behaves. I'll also try the other deken upload we have for Vanilla and mac intel. I gotta see if it all really works and what's the trouble. Many tests ahead. I'll check it all out and get back for at least a final apple upload with some more technical remarks.
By the way, I also did reorganize things and also cleaned up the documentation a bit, included the [output~] abstraction from extra and tried to mitigate some of the mess. I would like to work more on that for the final version.
I can guarantee a working apple upload, but I guess I need help for other systems. This version uses pd-lib-builder, so others can fork and try and build themselves and test quite easily for other operating OSes. Kudos to Pd for being awesome as it's incredible we can build such an old code so easily. I just needed mostly to change '*error(*' to '*pd_error(*' so things could build.
Here's the repository by the way https://github.com/porres/pd-unauthorized
Now, if you're not aware, I'm taking some time off the pd-list, so I'm not reading or responding. People can still reach me though via email (or join the new unauthorized repository if interested in collaborating with it and discussing it).
I think some things could go without saying, but under the light of recent events, here is a bit of a disclaimer: I consider Pd to be a community of free and independent contributors. I don't speak or act on behalf of the Pd Community, nor the Pd-list (which I'm currently not participating in). That is to say I'm the only one responsible for my actions and if someone (like, say, the original author of this library) is not happy and reading this, please leave the pd-list and the pd community alone because of my actions and take anything up directly with me, ok? Come to the repository, whatever
- that is to suggest you to leave the premises and meet me in the parking
lot if desired ;) but bring it on and let's see what you really got (unless all that was needed was the stage to troll and make a scene).
Others can reach me too, of course, but I don't really want to discuss the recent events, we can all leave it behind. My last action about this situation is that I'm uploading this library to deken and maintaining it, and there's nothing else to it besides technical discussions about keeping this code available, accessible and working as best as possible.
Sorry again for causing trouble at the bar.
Be back soon.
cheers
Pd-announce mailing list -- pd-announce@lists.iem.at To unsubscribe send an email to pd-announce-leave@lists.iem.at
oops, a little change of plans
recalculating route...
Em qua., 27 de nov. de 2024 às 16:07, Alexandre Torres Porres < porres@gmail.com> escreveu:
Hi, there's a quick pre-test release of a new "unauthorized" version I'm working on. It's up in deken. Someone on the Pd forum was looking for [playlist] for apple silicon and I had to upload to deken so he can test it (it's just a nightmare now with apple and malware). All objects but the streaming ones seem to be working... I also still need to figure out linking dynamic libs for those but I'm aware they already have issues, so my main concern is to provide the others for now, specially the GUIs! I might solve the streaming deals in new objects in ELSE.
Please test and let me know. I gotta be off for a couple of days for gigs upstate in the meantime. When I'm back I'll clean the dust off my old intel mac that can still run Pd-Extended and try the unauthorized library in there to see how it behaves. I'll also try the other deken upload we have for Vanilla and mac intel. I gotta see if it all really works and what's the trouble. Many tests ahead. I'll check it all out and get back for at least a final apple upload with some more technical remarks.
By the way, I also did reorganize things and also cleaned up the documentation a bit, included the [output~] abstraction from extra and tried to mitigate some of the mess. I would like to work more on that for the final version.
I can guarantee a working apple upload, but I guess I need help for other systems. This version uses pd-lib-builder, so others can fork and try and build themselves and test quite easily for other operating OSes. Kudos to Pd for being awesome as it's incredible we can build such an old code so easily. I just needed mostly to change '*error(*' to '*pd_error(*' so things could build.
Here's the repository by the way https://github.com/porres/pd-unauthorized
Now, if you're not aware, I'm taking some time off the pd-list, so I'm not reading or responding. People can still reach me though via email (or join the new unauthorized repository if interested in collaborating with it and discussing it).
I think some things could go without saying, but under the light of recent events, here is a bit of a disclaimer: I consider Pd to be a community of free and independent contributors. I don't speak or act on behalf of the Pd Community, nor the Pd-list (which I'm currently not participating in). That is to say I'm the only one responsible for my actions and if someone (like, say, the original author of this library) is not happy and reading this, please leave the pd-list and the pd community alone because of my actions and take anything up directly with me, ok? Come to the repository, whatever
- that is to suggest you to leave the premises and meet me in the parking
lot if desired ;) but bring it on and let's see what you really got (unless all that was needed was the stage to troll and make a scene).
Others can reach me too, of course, but I don't really want to discuss the recent events, we can all leave it behind. My last action about this situation is that I'm uploading this library to deken and maintaining it, and there's nothing else to it besides technical discussions about keeping this code available, accessible and working as best as possible.
Sorry again for causing trouble at the bar.
Be back soon.
cheers
Pd-announce mailing list -- pd-announce@lists.iem.at To unsubscribe send an email to pd-announce-leave@lists.iem.at
hello, Alexander,
i'm glad you have gigs and take some distance with the computer, this will surely help you to calm down...
i am on holidays too in the mountains, and i wanted that the peace of he mountain would invade my mind for a few days, missed.
but, as you seem to wait for it, i will only say a few words about unauthorized and _only_ about unauthorized because we mixed up many subjects here and it's no good for clarity :
[ people who are not interested in the subject, please, drop this email and don't write to me that you don't care about my work, this is useless ]
so :
- /what is unauthorized ?/
unauthorized is an accumulation of some graphical helper objects, streaming objects, control objects and simple audio effects that I needed in 2000 to make music with pd ; as i am more a graphical inspired game-like person, they were useful to ME and only ME to make sound out of PD. it was also handy for people who are not programmers and even children to start with PD.
- why is it called unauthorized ?
it is called like that not for my personal paranoia, but because, as externals, they are doing things that are considered dangerous and almost illegal mainly :
* heavy graphical updates that can endanger pd overall stability.
* heavy use of threads, that have the reputation to be dangerous too.
- what is to be improved [ if time available ] ?
well, what was said before can be a huge flaw for objects dealing with sound like sonogram~ or cooled~, because there is absolutely no control or checking of network flow between pd-engine and the GUI, and if you load big soundfiles, you can always manage to provoke a *****buffer overflow ***** and subsequent crash.
so, communication with the GUI should be managed and monitored to avoid crashes, and i even see that in recent versions of Vanilla, this buffer has been reduced because things running in a PD of 2010 ( mine ) are not working anymore.
- about the status of the library and its future?
i have no problem that it is now handled and maintained by another dev here under the GPL, i can question why external authors cannot use the license they wish to choose, like an hippocratic license, for example :
https://ethicalsource.dev/blog/hl3-announcement/ ??
but this is not the subject of this mail and tartiflette is getting cold.
i don't understnad well though that it got from a 'total iece of sh**' to a 'wonderful library', it's neither one ot the other : no rocket science, no complicated theory, just something that was ( and still is ) useful for me.
about rants, i can regret that i posted your private message here, but you know about the #MeToo epoch now, everything is made public, especilally when we find it abusive.
so long, chevil@giss.tv
hello again ( <yawn > )
another note about unauthorized - i know it's boring ::
- instructions to get my version are wrong, it's no more CVS but git :
git clone http://giss.tv/~git/git.cgi/unauthorized.git
and i publish only sources that are tested only on Linux, it's the only system i have here.
- i checked all objects and fixed STK instruments for modern linux (
22.04 ); for other systems i don't know..
i know the lib is not so trim and documented as ELSE, but it was my first lib.
adeu, chevil@giss.tv
ydegoyon @gmail.com wrote:
hello, Alexander,
i'm glad you have gigs and take some distance with the computer, this will surely help you to calm down...
i am on holidays too in the mountains, and i wanted that the peace of he mountain would invade my mind for a few days, missed.
but, as you seem to wait for it, i will only say a few words about unauthorized and _only_ about unauthorized because we mixed up many subjects here and it's no good for clarity :
[ people who are not interested in the subject, please, drop this email and don't write to me that you don't care about my work, this is useless ]
so :
- /what is unauthorized ?/
unauthorized is an accumulation of some graphical helper objects, streaming objects, control objects and simple audio effects that I needed in 2000 to make music with pd ; as i am more a graphical inspired game-like person, they were useful to ME and only ME to make sound out of PD. it was also handy for people who are not programmers and even children to start with PD.
- why is it called unauthorized ?
it is called like that not for my personal paranoia, but because, as externals, they are doing things that are considered dangerous and almost illegal mainly :
* heavy graphical updates that can endanger pd overall stability.
* heavy use of threads, that have the reputation to be dangerous too.
- what is to be improved [ if time available ] ?
well, what was said before can be a huge flaw for objects dealing with sound like sonogram~ or cooled~, because there is absolutely no control or checking of network flow between pd-engine and the GUI, and if you load big soundfiles, you can always manage to provoke a *****buffer overflow ***** and subsequent crash.
so, communication with the GUI should be managed and monitored to avoid crashes, and i even see that in recent versions of Vanilla, this buffer has been reduced because things running in a PD of 2010 ( mine ) are not working anymore.
- about the status of the library and its future?
i have no problem that it is now handled and maintained by another dev here under the GPL, i can question why external authors cannot use the license they wish to choose, like an hippocratic license, for example :
https://ethicalsource.dev/blog/hl3-announcement/ ??
but this is not the subject of this mail and tartiflette is getting cold.
i don't understnad well though that it got from a 'total iece of sh**' to a 'wonderful library', it's neither one ot the other : no rocket science, no complicated theory, just something that was ( and still is ) useful for me.
about rants, i can regret that i posted your private message here, but you know about the #MeToo epoch now, everything is made public, especilally when we find it abusive.
so long, chevil@giss.tv
-
Alexandre Torres Porres -
ydegoyon ＠gmail.com