-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear all,
at the SOb project (http://www.soundobject.org) we're writing some really cool physical model objects which we are soon going to package and propose to the pure-data externals repository (they are GNU/GPL).
However, we now have a problem that we want to solve soon: we need standalone versions of some demo applications (possibly running griPD etc.) we did. It would be nice to have a sort of MaxPlay type of thing (how about PdPlay?). I have some ideas on how to do it and it could be trivial, and therefore it is very probable that someone has already done it somewhere. If no one has done it, I'll hack up one solution and report back to the list as soon as it is done (it is going to be GNU/GPL anyway :).
Thank you in advance for all the help you will want to give.
nicb
+--------------------------------------------------------------------+ |Nicola Bernardini | |E-mail: nicb@centrotemporeale.it | |GPG Fingerprint = 6AE6 AF21 E160 D9B3 396E EBAC 906C CFAE 4D65 D910| |Neither MS-Word nor MS-PowerPoint attachments please: | |http://www.fsf.org/philosophy/no-word-attachments.html | +--------------------------------------------------------------------+
Hi Nicola,
I bet if you just run "-nogui" and use griPD for the GUI that will work. Am I right that you just want to prevent people editing the patch?
cheers Miller
On Tue, Oct 01, 2002 at 09:55:08PM +0200, Nicola Bernardini wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear all,
at the SOb project (http://www.soundobject.org) we're writing some really cool physical model objects which we are soon going to package and propose to the pure-data externals repository (they are GNU/GPL).
However, we now have a problem that we want to solve soon: we need standalone versions of some demo applications (possibly running griPD etc.) we did. It would be nice to have a sort of MaxPlay type of thing (how about PdPlay?). I have some ideas on how to do it and it could be trivial, and therefore it is very probable that someone has already done it somewhere. If no one has done it, I'll hack up one solution and report back to the list as soon as it is done (it is going to be GNU/GPL anyway :).
Thank you in advance for all the help you will want to give.
nicb
+--------------------------------------------------------------------+ |Nicola Bernardini | |E-mail: nicb@centrotemporeale.it | |GPG Fingerprint = 6AE6 AF21 E160 D9B3 396E EBAC 906C CFAE 4D65 D910| |Neither MS-Word nor MS-PowerPoint attachments please: | |http://www.fsf.org/philosophy/no-word-attachments.html | +--------------------------------------------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: Made with pgp4pine 1.75-6
iD8DBQE9mf2qkGzPrk1l2RARAqi/AJ92NXY9HoDWlMbRcu59RkUQNH8E7gCeLU07 +ocbGJWYRzzrrdQO/cG0BcM= =TT6i -----END PGP SIGNATURE-----
PD-dev mailing list PD-dev@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Thank you Miller for your quick reply!
Il 01/10/02 alle 16:47, Miller Puckette scrisse:
I bet if you just run "-nogui" and use griPD for the GUI that will work. Am I right that you just want to prevent people editing the patch?
well - the -nogui option + griPD is a possible 'initial' option. No the problem is not so much patch editing (the users these demo are intended for would not know how to do it).
The thing we need is something to build an application completely selfcontained (= linked statically :() so that people do not have to download install etc. pd. I know it's an ugly thing to do to your wonderful environment :) however that's the problem we currently have to solve. Indeed the patch itself, along with griPD interfaces etc., should be embedded in the executable. This way, pd could become a way to prototype applications and to arrive up to production-grade.
I will try to give a stab at it and report to the list as soon as I am arrived somewhere.
Thanks again
nicb
+--------------------------------------------------------------------+ |Nicola Bernardini | |E-mail: nicb@centrotemporeale.it | |GPG Fingerprint = 6AE6 AF21 E160 D9B3 396E EBAC 906C CFAE 4D65 D910| |Neither MS-Word nor MS-PowerPoint attachments please: | |http://www.fsf.org/philosophy/no-word-attachments.html | +--------------------------------------------------------------------+
Miller, Here at the university of Limerick, our students are seriously into pd. So is staff ;-) One project that I've suggested for Final Years (in Computer Science) is a meta-compiler for pd. This might seem a bit farfetched, but one of my favourite programming languages is Forth.... Here, at UL, most of our work is on Interaction Design, and for real-time synthesis of auditory interfaces, pd is the best prototyping tool. However, when designing the interaction, the overhead with ALL pd stuff is often too slow (we're talking less than 10 ms latency stuff). I recently finished a hack, creating soft-buttons using audio only, but I had to butcher pd to reduce the latency to acceptable levels (to be published in IEEE Multimedia).
Thanks for Max. Thanks for pd. Keep hacking. /Mikael
On 01/10/2002 23:47, "Miller Puckette" mpuckett@man104-1.ucsd.edu wrote:
Hi Nicola,
I bet if you just run "-nogui" and use griPD for the GUI that will work. Am I right that you just want to prevent people editing the patch?
cheers Miller
On Tue, Oct 01, 2002 at 09:55:08PM +0200, Nicola Bernardini wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear all,
at the SOb project (http://www.soundobject.org) we're writing some really cool physical model objects which we are soon going to package and propose to the pure-data externals repository (they are GNU/GPL).
However, we now have a problem that we want to solve soon: we need standalone versions of some demo applications (possibly running griPD etc.) we did. It would be nice to have a sort of MaxPlay type of thing (how about PdPlay?). I have some ideas on how to do it and it could be trivial, and therefore it is very probable that someone has already done it somewhere. If no one has done it, I'll hack up one solution and report back to the list as soon as it is done (it is going to be GNU/GPL anyway :).
Thank you in advance for all the help you will want to give.
nicb
+--------------------------------------------------------------------+ |Nicola Bernardini | |E-mail: nicb@centrotemporeale.it | |GPG Fingerprint = 6AE6 AF21 E160 D9B3 396E EBAC 906C CFAE 4D65 D910| |Neither MS-Word nor MS-PowerPoint attachments please: | |http://www.fsf.org/philosophy/no-word-attachments.html | +--------------------------------------------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: Made with pgp4pine 1.75-6
iD8DBQE9mf2qkGzPrk1l2RARAqi/AJ92NXY9HoDWlMbRcu59RkUQNH8E7gCeLU07 +ocbGJWYRzzrrdQO/cG0BcM= =TT6i -----END PGP SIGNATURE-----
PD-dev mailing list PD-dev@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-dev
Hi all,
The faster the better. If you can get Pd to turn it around in less than 5 msec you're usng it well, in my opinion.
I often use a foot pedal that's actually an audio switch, since the sudio inputs and outputs seem to get into and out of Pd the fastest of anything.
cheers Miller
On Thu, Oct 07, 2004 at 12:27:09AM +0100, Mikael Fernstrm wrote:
Miller, Here at the university of Limerick, our students are seriously into pd. So is staff ;-) One project that I've suggested for Final Years (in Computer Science) is a meta-compiler for pd. This might seem a bit farfetched, but one of my favourite programming languages is Forth.... Here, at UL, most of our work is on Interaction Design, and for real-time synthesis of auditory interfaces, pd is the best prototyping tool. However, when designing the interaction, the overhead with ALL pd stuff is often too slow (we're talking less than 10 ms latency stuff). I recently finished a hack, creating soft-buttons using audio only, but I had to butcher pd to reduce the latency to acceptable levels (to be published in IEEE Multimedia).
Thanks for Max. Thanks for pd. Keep hacking. /Mikael
On 01/10/2002 23:47, "Miller Puckette" mpuckett@man104-1.ucsd.edu wrote:
Hi Nicola,
I bet if you just run "-nogui" and use griPD for the GUI that will work. Am I right that you just want to prevent people editing the patch?
cheers Miller
On Tue, Oct 01, 2002 at 09:55:08PM +0200, Nicola Bernardini wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear all,
at the SOb project (http://www.soundobject.org) we're writing some really cool physical model objects which we are soon going to package and propose to the pure-data externals repository (they are GNU/GPL).
However, we now have a problem that we want to solve soon: we need standalone versions of some demo applications (possibly running griPD etc.) we did. It would be nice to have a sort of MaxPlay type of thing (how about PdPlay?). I have some ideas on how to do it and it could be trivial, and therefore it is very probable that someone has already done it somewhere. If no one has done it, I'll hack up one solution and report back to the list as soon as it is done (it is going to be GNU/GPL anyway :).
Thank you in advance for all the help you will want to give.
nicb
+--------------------------------------------------------------------+ |Nicola Bernardini | |E-mail: nicb@centrotemporeale.it | |GPG Fingerprint = 6AE6 AF21 E160 D9B3 396E EBAC 906C CFAE 4D65 D910| |Neither MS-Word nor MS-PowerPoint attachments please: | |http://www.fsf.org/philosophy/no-word-attachments.html | +--------------------------------------------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: Made with pgp4pine 1.75-6
iD8DBQE9mf2qkGzPrk1l2RARAqi/AJ92NXY9HoDWlMbRcu59RkUQNH8E7gCeLU07 +ocbGJWYRzzrrdQO/cG0BcM= =TT6i -----END PGP SIGNATURE-----
PD-dev mailing list PD-dev@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-dev
This is actually where I'm hoping to take GrIPD. It can be done manually now. Just use the PD '-nogui' command line (don't forget to put a netreceive object in your patch, something I need to look into) and use a loadbang connected to an 'open_locked <filepath>' message to the gripd object (the _locked will disable any GrIPD gui editing). Keep in mind that the filepath for 'open' and 'open_locked' are relative to the PD executable file. To close when the GrIPD gui closes, just use the outlet of the gripd object with the ';pd quit' message. You can then just bundle everything together (your patches, PD, and GrIPD) into a single distribution and have it launch with some script. The only problem might be other command line args such as selecting the audio and MIDI devices, etc. I've been thinking of creating some kind of distribution compiler that would do all this automagically. I'm also considering making some 'setup' app for PD (probably with wxPython) that the end user (the user getting your distro) would run once to generate the command line args. I think this would be a nice thing for people wanting to create seemingly stand alone apps with PD or for installation/demo/educational types of situations. There's also the possibility of working up a stripped down version of PD without any editing features at all, to further prevent editing of PD patches by expeditious users, but I personally don't think this is such a good idea.
Joe jsarlo@ucsd.edu
at the SOb project (http://www.soundobject.org) we're writing some really cool physical model objects which we are soon going to package and propose to the pure-data externals repository (they are GNU/GPL).
However, we now have a problem that we want to solve soon: we need standalone versions of some demo applications (possibly running griPD
etc.)
we did. It would be nice to have a sort of MaxPlay type of thing (how about PdPlay?). I have some ideas on how to do it and it could be trivial, and therefore it is very probable that someone has already done it somewhere. If no one has done it, I'll hack up one solution and report back to the list as soon as it is done (it is going to be GNU/GPL anyway :).
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Il 01/10/02 alle 22:28, Joseph A. Sarlo scrisse:
This is actually where I'm hoping to take GrIPD. It can be done manually now. Just use the PD '-nogui' command line (don't forget to put a netreceive object in your patch, something I need to look into) and use a loadbang connected to an 'open_locked <filepath>' message to the gripd object (the _locked will disable any GrIPD gui editing). Keep in mind that the filepath for 'open' and 'open_locked' are relative to the PD executable file. To close when the GrIPD gui closes, just use the outlet of the gripd object with the ';pd quit' message. You can then just bundle everything together (your patches, PD, and GrIPD) into a single distribution and have it launch with some script. The only problem might be other command line args such as selecting the audio and MIDI devices, etc. I've been thinking of creating some kind of distribution compiler that would do all this automagically. I'm also considering making some 'setup' app for PD (probably with wxPython) that the end user (the user getting your distro) would run once to generate the command line args. I think this would be a nice thing for people wanting to create seemingly stand alone apps with PD or for installation/demo/educational types of situations. There's also the possibility of working up a stripped down version of PD without any editing features at all, to further prevent editing of PD patches by expeditious users, but I personally don't think this is such a good idea.
Thank you Joe for your quick reply (and also for griPD obviously!:)
My current problem is not so much patch editing but rather the idea that users that would like to see some application of some sort would *have* to have the whole shabang installed into their machine. Thank you for all the suggestions, I'll do some hacking and see if I'll explain myself better with that.
However, your suggestions were *extremely* useful. Thank you.
nicb
+--------------------------------------------------------------------+ |Nicola Bernardini | |E-mail: nicb@centrotemporeale.it | |GPG Fingerprint = 6AE6 AF21 E160 D9B3 396E EBAC 906C CFAE 4D65 D910| |Neither MS-Word nor MS-PowerPoint attachments please: | |http://www.fsf.org/philosophy/no-word-attachments.html | +--------------------------------------------------------------------+
you could package your own distro of PD and your patches with a fancy installed and a nice shortcut/link/alias to open PD with the proper options and your patch. Another possibility.
somwhat related, there is something called tclkit which is a self-contained single exe tcl/tk distro. Maybe something like that for PD? Would make the above a bit easier... (does it have to be multiplatform?)
Ben
On Wed, 2 Oct 2002, Nicola Bernardini wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Il 01/10/02 alle 22:28, Joseph A. Sarlo scrisse:
This is actually where I'm hoping to take GrIPD. It can be done manually now. Just use the PD '-nogui' command line (don't forget to put a netreceive object in your patch, something I need to look into) and use a loadbang connected to an 'open_locked <filepath>' message to the gripd object (the _locked will disable any GrIPD gui editing). Keep in mind that the filepath for 'open' and 'open_locked' are relative to the PD executable file. To close when the GrIPD gui closes, just use the outlet of the gripd object with the ';pd quit' message. You can then just bundle everything together (your patches, PD, and GrIPD) into a single distribution and have it launch with some script. The only problem might be other command line args such as selecting the audio and MIDI devices, etc. I've been thinking of creating some kind of distribution compiler that would do all this automagically. I'm also considering making some 'setup' app for PD (probably with wxPython) that the end user (the user getting your distro) would run once to generate the command line args. I think this would be a nice thing for people wanting to create seemingly stand alone apps with PD or for installation/demo/educational types of situations. There's also the possibility of working up a stripped down version of PD without any editing features at all, to further prevent editing of PD patches by expeditious users, but I personally don't think this is such a good idea.
Thank you Joe for your quick reply (and also for griPD obviously!:)
My current problem is not so much patch editing but rather the idea that users that would like to see some application of some sort would *have* to have the whole shabang installed into their machine. Thank you for all the suggestions, I'll do some hacking and see if I'll explain myself better with that.
However, your suggestions were *extremely* useful. Thank you.
nicb
+--------------------------------------------------------------------+ |Nicola Bernardini | |E-mail: nicb@centrotemporeale.it | |GPG Fingerprint = 6AE6 AF21 E160 D9B3 396E EBAC 906C CFAE 4D65 D910| |Neither MS-Word nor MS-PowerPoint attachments please: | |http://www.fsf.org/philosophy/no-word-attachments.html | +--------------------------------------------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: Made with pgp4pine 1.75-6
iD8DBQE9mrC1kGzPrk1l2RARAg50AJ42ybzTtgPE+sgc4Azn6mRfCXIuwwCg1O3n n9P0nXT4Y9wMdwprKRnWKb0= =8ZLB -----END PGP SIGNATURE-----
PD-dev mailing list PD-dev@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-dev
B. Bogart ---------