For several years now, I've been deploying Pd-extended in my teaching environments, and linking to the same installers so that my students could install exactly the same version on their own machines. (I am perfectly aware that Pd-extended has not been maintained for some time.)
I would welcome advice about a strategy to deploy a monolithic "same everywhere" version of PD. Ideally, this would be with a set of libraries that are fixed at a given version and work the same on MacOS and Windows.
I'm leaning toward Purr-data, but as I understand it does not yet have Gem on MacOS. Is that right?
Alternatively, would there be a way for me to install PD-vanilla and Deken install some libraries in such a way that I can deploy a copy with all dependencies in a single folder?
In essence, the constraints have to do with the fact that software installations are managed by our IT team, so I need to give them a specific set of instruction and be reasonably guaranteed that the results will work. Neither students (nor I) can I install software on those machines. It's also important to me to insure that students can bring their work to and from university to home, and that the work in progress that send me opens and works on my machine.
Any good suggestions?
Thanks,
- martin
personally, I would just go with Pd vanilla. Although it's not considered good practice, you can just throw all the libraries into the extra folder and you basically get something very similar to Pd extended. Students just have to unzip it and can run it anywhere. Note that Pd extended automagically added all library folders to the search paths and loaded all libraries on startup, but with Pd vanilla you have to do that either explicitly per patch with [declare] or use a Pd preference file.
I'm usually not advocating this, but for your situation it will probably be the easiest solution.
Christof
Gesendet: Freitag, 24. Mai 2019 um 18:31 Uhr Von: "Martin Dupras" martindupras@gmail.com An: pd-list@lists.iem.at Betreff: [PD] Advice on PD versions for classroom deployment
For several years now, I've been deploying Pd-extended in my teaching environments, and linking to the same installers so that my students could install exactly the same version on their own machines. (I am perfectly aware that Pd-extended has not been maintained for some time.)
I would welcome advice about a strategy to deploy a monolithic "same everywhere" version of PD. Ideally, this would be with a set of libraries that are fixed at a given version and work the same on MacOS and Windows.
I'm leaning toward Purr-data, but as I understand it does not yet have Gem on MacOS. Is that right?
Alternatively, would there be a way for me to install PD-vanilla and Deken install some libraries in such a way that I can deploy a copy with all dependencies in a single folder?
In essence, the constraints have to do with the fact that software installations are managed by our IT team, so I need to give them a specific set of instruction and be reasonably guaranteed that the results will work. Neither students (nor I) can I install software on those machines. It's also important to me to insure that students can bring their work to and from university to home, and that the work in progress that send me opens and works on my machine.
Any good suggestions?
Thanks,
- martin
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
I also suggest you try to check new libraries and other externals that were not part of Pd Extended
- timbreID / convolve~ and many others from william brent
- soundhack
- fftease
- ofelia
- else*
- this one I'm developing myself and I got rid of all dependencies I had,
so I basically just use it. It's still experimental, but you can check it out, I also have a tutorial that relies on it https://github.com/porres/Live-Electronic-Music-Tutorial/releases/tag/v1.0-b...
cheers
Em sex, 24 de mai de 2019 às 14:23, Christof Ressi christof.ressi@gmx.at escreveu:
personally, I would just go with Pd vanilla. Although it's not considered good practice, you can just throw all the libraries into the extra folder and you basically get something very similar to Pd extended. Students just have to unzip it and can run it anywhere. Note that Pd extended automagically added all library folders to the search paths and loaded all libraries on startup, but with Pd vanilla you have to do that either explicitly per patch with [declare] or use a Pd preference file.
I'm usually not advocating this, but for your situation it will probably be the easiest solution.
Christof
Gesendet: Freitag, 24. Mai 2019 um 18:31 Uhr Von: "Martin Dupras" martindupras@gmail.com An: pd-list@lists.iem.at Betreff: [PD] Advice on PD versions for classroom deployment
For several years now, I've been deploying Pd-extended in my teaching environments, and linking to the same installers so that my students could install exactly the same version on their own machines. (I am perfectly aware that Pd-extended has not been maintained for some time.)
I would welcome advice about a strategy to deploy a monolithic "same everywhere" version of PD. Ideally, this would be with a set of libraries that are fixed at a given version and work the same on MacOS and Windows.
I'm leaning toward Purr-data, but as I understand it does not yet have Gem on MacOS. Is that right?
Alternatively, would there be a way for me to install PD-vanilla and Deken install some libraries in such a way that I can deploy a copy with all dependencies in a single folder?
In essence, the constraints have to do with the fact that software installations are managed by our IT team, so I need to give them a specific set of instruction and be reasonably guaranteed that the results will work. Neither students (nor I) can I install software on those machines. It's also important to me to insure that students can bring their work to and from university to home, and that the work in progress that send me opens and works on my machine.
Any good suggestions?
Thanks,
- martin
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
this does deploy PD + many libraries into a standalone version of PD. It is easy to add new ones or modify the .bat/.sh they provide to meet your needs
http://malinette.info/en/#downloads
19/5/24 18:31(e)an, Martin Dupras igorleak idatzi zuen:
For several years now, I've been deploying Pd-extended in my teaching environments, and linking to the same installers so that my students could install exactly the same version on their own machines. (I am perfectly aware that Pd-extended has not been maintained for some time.)
I would welcome advice about a strategy to deploy a monolithic "same everywhere" version of PD. Ideally, this would be with a set of libraries that are fixed at a given version and work the same on MacOS and Windows.
I'm leaning toward Purr-data, but as I understand it does not yet have Gem on MacOS. Is that right?
Alternatively, would there be a way for me to install PD-vanilla and Deken install some libraries in such a way that I can deploy a copy with all dependencies in a single folder?
In essence, the constraints have to do with the fact that software installations are managed by our IT team, so I need to give them a specific set of instruction and be reasonably guaranteed that the results will work. Neither students (nor I) can I install software on those machines. It's also important to me to insure that students can bring their work to and from university to home, and that the work in progress that send me opens and works on my machine.
Any good suggestions?
Thanks,
- martin
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
What I did with the Click Tracker http://j.mp/click-tracker was to add a folder with the necessary externals. The paths in the patch then point to the lib folder.
This puts all the work on my side, but the package is stable. And I can copy it for other projects. But this is a patch to be open and used, not indended for people with programming experience or interest.
Joao
Am 24.05.2019 um 18:31 schrieb Martin Dupras:
For several years now, I've been deploying Pd-extended in my teaching environments, and linking to the same installers so that my students could install exactly the same version on their own machines. (I am perfectly aware that Pd-extended has not been maintained for some time.)
I would welcome advice about a strategy to deploy a monolithic "same everywhere" version of PD. Ideally, this would be with a set of libraries that are fixed at a given version and work the same on MacOS and Windows.
I'm leaning toward Purr-data, but as I understand it does not yet have Gem on MacOS. Is that right?
Alternatively, would there be a way for me to install PD-vanilla and Deken install some libraries in such a way that I can deploy a copy with all dependencies in a single folder?
In essence, the constraints have to do with the fact that software installations are managed by our IT team, so I need to give them a specific set of instruction and be reasonably guaranteed that the results will work. Neither students (nor I) can I install software on those machines. It's also important to me to insure that students can bring their work to and from university to home, and that the work in progress that send me opens and works on my machine.
Any good suggestions?
Thanks,
- martin
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-
Alexandre Torres Porres -
Christof Ressi -
enrike -
João Pais -
Martin Dupras