hello again ( <yawn > )
another note about unauthorized - i know it's boring ::
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.
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