I have a simple question, is there an easy way to list used abstractions of a patch?
I oftenly pass on patches to fellow musicians and finding used abstractions per patch can be sticky business - i’d like to not send all abstractions i ever made instead :) Thanx for any hints!
jayrope
www.jayrope.com www.aircushionfinish.com www.ello.co/jayrope
This is always a pain, sorry - I often want to do this too. I do it this way: set "verbose" flag, load the patch, copy all the messages into a file, then "grep succeeded <file>", then sort. The linux/Mac sort program has a "-u" flag (unique) that suppresses repeats.
But Pd ought to offer a simpler way to do this :)
cheers Miller
On Thu, Jul 27, 2017 at 07:13:57PM +0200, jlistshit wrote:
I have a simple question, is there an easy way to list used abstractions of a patch?
I oftenly pass on patches to fellow musicians and finding used abstractions per patch can be sticky business - i’d like to not send all abstractions i ever made instead :) Thanx for any hints!
jayrope
www.jayrope.com www.aircushionfinish.com www.ello.co/jayrope
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
But Pd ought to offer a simpler way to do this :)
+1
but wasn't there a gui plugin that did this...? maybe i don't remember... or was that purrdata/l2ork
On Thu, Jul 27, 2017 at 1:33 PM, Miller Puckette msp@ucsd.edu wrote:
This is always a pain, sorry - I often want to do this too. I do it this way: set "verbose" flag, load the patch, copy all the messages into a file, then "grep succeeded <file>", then sort. The linux/Mac sort program has a "-u" flag (unique) that suppresses repeats.
But Pd ought to offer a simpler way to do this :)
cheers Miller
On Thu, Jul 27, 2017 at 07:13:57PM +0200, jlistshit wrote:
I have a simple question, is there an easy way to list used abstractions
of a patch?
I oftenly pass on patches to fellow musicians and finding used
abstractions per patch can be sticky business - i’d like to not send all abstractions i ever made instead :)
Thanx for any hints!
jayrope
www.jayrope.com www.aircushionfinish.com www.ello.co/jayrope
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
Thank you Miller, that’s at least a better way than going through all by hand and try to list what one finds… that process usually results in missing things here.
Should i file a feature request? +1
I think everyone would be happy to see this, and it would make PD more accessible for non-programmers, too.
Thank you for all you do.
jayrope
www.jayrope.com www.aircushionfinish.com www.ello.co/jayrope
On Jul 27, 2017, at 19:33, Miller Puckette msp@ucsd.edu wrote:
This is always a pain, sorry - I often want to do this too. I do it this way: set "verbose" flag, load the patch, copy all the messages into a file, then "grep succeeded <file>", then sort. The linux/Mac sort program has a "-u" flag (unique) that suppresses repeats.
But Pd ought to offer a simpler way to do this :)
cheers Miller
On Thu, Jul 27, 2017 at 07:13:57PM +0200, jlistshit wrote:
I have a simple question, is there an easy way to list used abstractions of a patch?
I oftenly pass on patches to fellow musicians and finding used abstractions per patch can be sticky business - i’d like to not send all abstractions i ever made instead :) Thanx for any hints!
jayrope
www.jayrope.com www.aircushionfinish.com www.ello.co/jayrope
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
I agree this is indeed very useful. I would even dare to raise the stakes, if you allow:
Maybe since there is deken, which adds externals to pd, it would be nice to have a similar tool that packs and exports a "distribution" of pd for performance, with all required libs/abs/prefs the patch requires. (Perhaps even for multiple platforms, but this is asking too much). In mac it would be close to a sort of make app adapted to the patch.
Could this be possible? I'd be interested in contributing to this if so and i still need a huge lot to learn
I've seen pd distributions in many highly experienced users, and so I also ask if this is the only solution (packing a distribution) when it comes to the "last steps" before publishing a patch/piece that has a lot of extra stuff that might break if not mantained/adapted, etc.
Cheers,
fd
fdch.github.io/tv
On Jul 27, 2017, at 2:40 PM, jlistshit jlistshit@kliklak.net wrote:
Thank you Miller, that’s at least a better way than going through all by hand and try to list what one finds… that process usually results in missing things here.
Should i file a feature request? +1
I think everyone would be happy to see this, and it would make PD more accessible for non-programmers, too.
Thank you for all you do.
jayrope
www.jayrope.com www.aircushionfinish.com www.ello.co/jayrope
On Jul 27, 2017, at 19:33, Miller Puckette msp@ucsd.edu wrote:
This is always a pain, sorry - I often want to do this too. I do it this way: set "verbose" flag, load the patch, copy all the messages into a file, then "grep succeeded <file>", then sort. The linux/Mac sort program has a "-u" flag (unique) that suppresses repeats.
But Pd ought to offer a simpler way to do this :)
cheers Miller
On Thu, Jul 27, 2017 at 07:13:57PM +0200, jlistshit wrote: I have a simple question, is there an easy way to list used abstractions of a patch?
I oftenly pass on patches to fellow musicians and finding used abstractions per patch can be sticky business - i’d like to not send all abstractions i ever made instead :) Thanx for any hints!
jayrope
www.jayrope.com www.aircushionfinish.com www.ello.co/jayrope
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
Well I don't know about how extended worked, since I really never used it. I only mean to 'export' into a pd distrib that is only intended to use with a particular patch that only has the requirements of that patch
if you could do that, then you could just autogenerate pd-extended, no?
Le 27/07/2017 à 22:17, Fede Camara Halac a écrit :
I agree this is indeed very useful. I would even dare to raise the stakes, if you allow:
Maybe since there is deken, which adds externals to pd, it would be nice to have a similar tool that packs and exports a "distribution" of pd for performance, with all required libs/abs/prefs the patch requires. (Perhaps even for multiple platforms, but this is asking too much). In mac it would be close to a sort of make app adapted to the patch.
pd is already multiplatform, I think this would work if it is possible to add a binary extension to PureData that would use functions in pd headers for managing the distribution.
Could this be possible? I'd be interested in contributing to this if so and i still need a huge lot to learn
I've seen pd distributions in many highly experienced users, and so I also ask if this is the only solution (packing a distribution) when it comes to the "last steps" before publishing a patch/piece that has a lot of extra stuff that might break if not mantained/adapted, etc.
Cheers,
fd
fdch.github.io/tv
On Jul 27, 2017, at 2:40 PM, jlistshit jlistshit@kliklak.net wrote:
Thank you Miller, that’s at least a better way than going through all by hand and try to list what one finds… that process usually results in missing things here.
Should i file a feature request? +1
I think everyone would be happy to see this, and it would make PD more accessible for non-programmers, too.
Thank you for all you do.
jayrope
www.jayrope.com www.aircushionfinish.com www.ello.co/jayrope
On Jul 27, 2017, at 19:33, Miller Puckette msp@ucsd.edu wrote:
This is always a pain, sorry - I often want to do this too. I do it this way: set "verbose" flag, load the patch, copy all the messages into a file, then "grep succeeded <file>", then sort. The linux/Mac sort program has a "-u" flag (unique) that suppresses repeats.
But Pd ought to offer a simpler way to do this :)
cheers Miller
On Thu, Jul 27, 2017 at 07:13:57PM +0200, jlistshit wrote: I have a simple question, is there an easy way to list used abstractions of a patch?
I oftenly pass on patches to fellow musicians and finding used abstractions per patch can be sticky business - i’d like to not send all abstractions i ever made instead :) Thanx for any hints!
jayrope
www.jayrope.com www.aircushionfinish.com www.ello.co/jayrope
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
Of course a pd patch is in itself platform independent, which is what allows one to bring patches to diff platforms.
For externals, my guess is that you can ask deken to fetch the corresponding binary for the target platform and use that in the exported bundle.
I dont understand, though, how from pd in one platform you would build pd for another. Or, perhaps you dont need to build and you need only to fetch the corresponding build from Miller's builds and put the libs in the "extra" (as suggested in the deken path github discussion)
Are Miller's builds dekenizable for that matter?
fdch.github.io/tv
On Jul 27, 2017, at 5:57 PM, patrice colet colet.patrice@free.Fr wrote:
functions in pd headers
I was more thinking about a tool that would determine platforms were the distribution would work by fetching database containing an historic of all pd functions, internals, externals, and abstractions.
Then the distribution provider would know if it works on other platforms, and why it wouldn't work, eventually advising the use of some objects and methods over some other to be compatible everywhere, .
Of course deken could be used at the other end for providing the missing objects.
Building pd wouldn't resolve many cases were some functions aren't compatible between different platforms.
Le 28/07/2017 à 00:41, Fede Camara Halac a écrit :
Of course a pd patch is in itself platform independent, which is what allows one to bring patches to diff platforms.
For externals, my guess is that you can ask deken to fetch the corresponding binary for the target platform and use that in the exported bundle.
I dont understand, though, how from pd in one platform you would build pd for another. Or, perhaps you dont need to build and you need only to fetch the corresponding build from Miller's builds and put the libs in the "extra" (as suggested in the deken path github discussion)
Are Miller's builds dekenizable for that matter?
fdch.github.io/tv
On Jul 27, 2017, at 5:57 PM, patrice colet colet.patrice@free.Fr wrote:
functions in pd headers
2017-07-27 14:13 GMT-03:00 jlistshit jlistshit@kliklak.net:
I have a simple question, is there an easy way to list used abstractions of a patch?
I oftenly pass on patches to fellow musicians and finding used abstractions per patch can be sticky business - i’d like to not send all abstractions i ever made instead :)
my way:
If you have tons of abstractions you've made in life that you use a lot, maybe organize them as "libraries" and provide them as a dependency for your patches.
If you have a specialized abstraction that's only for a project/patch, keep it in the same folder and send it all together.
cheers
-
Alexandre Torres Porres -
Fede Camara Halac -
Federico Camara Halac
-
jlistshit -
Matt Davey -
me.grimm -
Miller Puckette -
patrice colet