GrIPD is an extension to PD that allows one to design custom graphical user interfaces for PD patches. GrIPD is _not_ a replacement for the PD Tcl/Tk GUI, but instead is intended to allow one to create a front end to a PD patch. The concept is to create your PD patch normally and then your GUI using GrIPD (similar to SuperCollider or Reaktor). You can then lauch PD using the -nogui command line argument (although this is certainly not necessary) so only your custom front end will be displayed.
GrIPD is available for Windows and Linux.
Check it out at: http://mambo.peabody.jhu.edu/~jsarlo/gripd/
hi !
how do you make it run ??
on my debian system i have gtk-1.2.10-1 python-1.5.2-16 wxgtk-2.2.6.1 wxgtk-python-2.2.6.1
compilation went fine i always get following error-message when trying to "open"
<snip> GrIPD: Using port 3490 GrIPD: Waiting for a connection... Traceback (innermost last): File "../gripd/gripd.py", line 23, in ? from gripdControls import * File "../gripd/gripdControls.py", line 179, in ? class mToggle(wxToggleButton, wxButton, mButton): NameError: wxToggleButton </snip> obviously there is something missing ? looks like i need wxgtk(-python)-2.3.x instead of 2.2.6 ?? ah, now i've seen the hint on your page so debianized people will have to wait a little bit longer...
mfg.ds.zhrt IOhannes
On Thu, 12 Jul 2001, Joseph A. Sarlo wrote:
GrIPD is an extension to PD that allows one to design custom graphical user interfaces for PD patches. GrIPD is _not_ a replacement for the PD Tcl/Tk GUI, but instead is intended to allow one to create a front end to a PD patch. The concept is to create your PD patch normally and then your GUI using GrIPD (similar to SuperCollider or Reaktor). You can then lauch PD using the -nogui command line argument (although this is certainly not necessary) so only your custom front end will be displayed.
GrIPD is available for Windows and Linux.
Check it out at: http://mambo.peabody.jhu.edu/~jsarlo/gripd/
-- ______________________________ | | Joseph A. Sarlo | | jsarlo@mambo.peabody.jhu.edu |______________________________
I tested GrIPD on my windows98,
Pd-0.31 and Pd-0.32 Patch1 Python 2.1 wxPython 2.3.0
Its GUI componet works and looks great!!! but i got an error in both Pd-0.31 and Pd-0.32.
GrIPD: Bind Error: No error GrIPD: Attempting to re-bind
when i try to connect GrIPD.
Also, Does gripd object always need to receive set_path and set_python_path messages in every patch?
Respect! Uta.
Johannes M Zmoelnig zmoelnig@iem.kug.ac.at wrote:
hi !
how do you make it run ??
on my debian system i have gtk-1.2.10-1 python-1.5.2-16 wxgtk-2.2.6.1 wxgtk-python-2.2.6.1
compilation went fine i always get following error-message when trying to "open"
<snip> GrIPD: Using port 3490 GrIPD: Waiting for a connection... Traceback (innermost last): File "../gripd/gripd.py", line 23, in ? from gripdControls import * File "../gripd/gripdControls.py", line 179, in ? class mToggle(wxToggleButton, wxButton, mButton): NameError: wxToggleButton </snip> obviously there is something missing ? looks like i need wxgtk(-python)-2.3.x instead of 2.2.6 ?? ah, now i've seen the hint on your page so debianized people will have to wait a little bit longer...
mfg.ds.zhrt IOhannes
On Thu, 12 Jul 2001, Joseph A. Sarlo wrote:
GrIPD is an extension to PD that allows one to design custom graphical user interfaces for PD patches. GrIPD is _not_ a replacement for the PD Tcl/Tk GUI, but instead is intended to allow one to create a front end to a PD patch. The concept is to create your PD patch normally and then your GUI using GrIPD (similar to SuperCollider or Reaktor). You can then lauch PD using the -nogui command line argument (although this is certainly not necessary) so only your custom front end will be displayed.
GrIPD is available for Windows and Linux.
Check it out at: http://mambo.peabody.jhu.edu/~jsarlo/gripd/
-- ______________________________ | | Joseph A. Sarlo | | jsarlo@mambo.peabody.jhu.edu |______________________________
Its GUI componet works and looks great!!! but i got an error in both Pd-0.31 and Pd-0.32.
GrIPD: Bind Error: No error GrIPD: Attempting to re-bind
when i try to connect GrIPD.
It sounds like somehow you're attempting to connect twice and the socket is already bound. I just noticed that this is really easy to do, just send "connect" twice, or send "connect" then "open". I'll have to fix this so you can't (that's what v0.0.1 is all about I guess). So if you're doing that, then that's the problem. The usage directions might be a little confusing: "connect" message is only used if you're going to open the GrIPD GUI separately (like on a different machine). If you're using everything local, you don't need to send "connect" at all, just "open <optional filename>".
Also, Does gripd object always need to receive set_path and set_python_path messages in every patch?
If you have all the GrIPD python stuff (*.py files) in "c:\pd\gripd" then you don't need to use "set_path", similarly, if you have python installed to "c:\program files\python" then you don't need "set_python_path". This is only so the GrIPD PD object can find stuff when you use "open". You could always launch gripd.py separately, but I'd recommend wrapping gripd and the set messages in a PD file with a little loadbang magic.
Let me know if this helps or not, I'm really want to iron out the kinks.
"Joseph A. Sarlo" jsarlo@mambo.peabody.jhu.edu wrote:
Its GUI componet works and looks great!!! but i got an error in both Pd-0.31 and Pd-0.32.
GrIPD: Bind Error: No error GrIPD: Attempting to re-bind
when i try to connect GrIPD.
It sounds like somehow you're attempting to connect twice and the socket is already bound. I just noticed that this is really easy to do, just send "connect" twice, or send "connect" then "open". I'll have to fix this so you can't (that's what v0.0.1 is all about I guess). So if you're doing that, then that's the problem. The usage directions might be a little confusing: "connect" message is only used if you're going to open the GrIPD GUI separately (like on a different machine). If you're using everything local, you don't need to send "connect" at all, just "open <optional filename>".
Thank you. I tried just "open Filename", then the GUI showed up, and after few seconds "Connection Timedout" dialog will pop up. It seems the GUI fails to connect to PD, so I changed Options -> configure -> Connection Address from "localhost" to 127.0.0.1 or so, but it still fails to connect.
This happens also under Windows2000.
Python2.1 wxPython 2.3.0 for python 2.1 and i installed python under C:/python21.
Are there a Python's version compatibility ploblem? Any ideas?
Uta.
On Fri, 13 Jul 2001, uta wrote:
Thank you. I tried just "open Filename", then the GUI showed up, and after few seconds "Connection Timedout" dialog will pop up. It seems the GUI fails to connect to PD, so I changed Options -> configure -> Connection Address from "localhost" to 127.0.0.1 or so, but it still fails to connect.
This happens also under Windows2000.
Python2.1 wxPython 2.3.0 for python 2.1 and i installed python under C:/python21.
Are there a Python's version compatibility ploblem? Any ideas?
Hmmm, I suppose the first thing to do is figure out whether it's the PD object that's not accepting or the python GUI that's not connecting. What I would do is create a gripd object in pd with port 23 and telnet to it. Just put "gripd 23" in pd then send it a "connect" message, then open up your telnet client and connect to 127.0.0.1. If it connects, GrIPD will say so in the console. Then send a "disconnect" message to the PD object. Your telnet client should display "!disconnect:0|" and then disconnect if all is good.
To test the python part, I would go get a dummy server. You can get Tambu Dummy Server at: http://www.xploiter.com/tambu/tambudummy.shtml Set the port to 3490 and the protocal to TCP and have it start listening. Then open grip.py and connect (from the file menu). If you add a button control you should see something like "!setRcvr:rbutton0|" in the dummy server if all is good there.
-- ______________________________ | | Joseph A. Sarlo | | jsarlo@mambo.peabody.jhu.edu |______________________________
I just downloaded all the files needed and I have installed them al, however when I run pd and create the patch that opens the 'gui' nothing happens, in the main pd wndow it says
GriPD:Using Port 3490 GriPD:Waiting for a connection...
when I hit the open filename message again it says this, GriPD:Bind Error: No error GriPD:Attempting to re-bind THis message keeps repeating itself over and over again? Any ideas?
Regards, Rory.
Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie
On Fri, 13 Jul 2001, Rory Walsh wrote:
I just downloaded all the files needed and I have installed them al, however when I run pd and create the patch that opens the 'gui' nothing happens, in the main pd wndow it says
GriPD:Using Port 3490 GriPD:Waiting for a connection...
It sounds like gripd.py isn't being launched. Make sure "set_path" and "set_python_path" are correct. If you're sure those are right I would try launching gripd.py manually and then connecting to PD.
when I hit the open filename message again it says this, GriPD:Bind Error: No error GriPD:Attempting to re-bind THis message keeps repeating itself over and over again? Any ideas?
You can stop the repeating by sending the gripd PD object a "disconnect" message. I'll fix this in the next version.
-- ______________________________ | | Joseph A. Sarlo | | jsarlo@mambo.peabody.jhu.edu |______________________________
Is there any way I can create a standalone interface with 'GrIPD' so I can get my GUI pd patch to run on a machine that don't have 'python' installed?
Regards, Rory.
Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie
Not yet, I'm working on this.
I think the wxWindows toggle button object might be new to 2.3, but you should be able to get the source from:
http://www.wxpython.org/download.php#sources
and build it.
| | Joseph A. Sarlo | | jsarlo@mambo.peabody.jhu.edu |______________________________
On Thu, 12 Jul 2001, Johannes M Zmoelnig wrote:
hi !
how do you make it run ??
on my debian system i have gtk-1.2.10-1 python-1.5.2-16 wxgtk-2.2.6.1 wxgtk-python-2.2.6.1
compilation went fine i always get following error-message when trying to "open"
<snip> GrIPD: Using port 3490 GrIPD: Waiting for a connection... Traceback (innermost last): File "../gripd/gripd.py", line 23, in ? from gripdControls import * File "../gripd/gripdControls.py", line 179, in ? class mToggle(wxToggleButton, wxButton, mButton): NameError: wxToggleButton </snip> obviously there is something missing ? looks like i need wxgtk(-python)-2.3.x instead of 2.2.6 ?? ah, now i've seen the hint on your page so debianized people will have to wait a little bit longer...
mfg.ds.zhrt IOhannes
On Thu, 12 Jul 2001, Joseph A. Sarlo wrote:
GrIPD is an extension to PD that allows one to design custom graphical user interfaces for PD patches. GrIPD is _not_ a replacement for the PD Tcl/Tk GUI, but instead is intended to allow one to create a front end to a PD patch. The concept is to create your PD patch normally and then your GUI using GrIPD (similar to SuperCollider or Reaktor). You can then lauch PD using the -nogui command line argument (although this is certainly not necessary) so only your custom front end will be displayed.
GrIPD is available for Windows and Linux.
Check it out at: http://mambo.peabody.jhu.edu/~jsarlo/gripd/
-- ______________________________ | | Joseph A. Sarlo | | jsarlo@mambo.peabody.jhu.edu |______________________________
On Thu, 12 Jul 2001, Joseph A. Sarlo wrote:
I think the wxWindows toggle button object might be new to 2.3, but you should be able to get the source from:
http://www.wxpython.org/download.php#sources
and build it.
thanks, it was easier. i downloaded the binary-rpms wxPython-2.3.1 and wxgtk-2.3.1 from https://sourceforge.net/project/showfiles.php?group_id=10718&release_id=... alienated them to deb-packages and there we go.
great.
mfg.cs.satd IOhannes
This is pretty cool. How do you deal with the real time vrs. garbage collection problems in Python?
(jfm3)
Joseph A. Sarlo wrote:
GrIPD is an extension to PD that allows one to design custom graphical user interfaces for PD patches. GrIPD is _not_ a replacement for the PD Tcl/Tk GUI, but instead is intended to allow one to create a front end to a PD patch. The concept is to create your PD patch normally and then your GUI using GrIPD (similar to SuperCollider or Reaktor). You can then lauch PD using the -nogui command line argument (although this is certainly not necessary) so only your custom front end will be displayed.
GrIPD is available for Windows and Linux.
Check it out at: http://mambo.peabody.jhu.edu/~jsarlo/gripd/
Python's garbage collection is irrelevant in this case, since GrIPD runs as an entirely separate process completely uninvolved with any audio signals. It is theoretically possible the GC may cause (very) momentary glitches in the control signals between PD and GrIPD, but I doubt they could possibly be noticable. Plus, there is very little memory allocation/deallocation (if any) that occurs during the runtime of GriPD.
On Thu, 12 Jul 2001, jfm3 wrote:
This is pretty cool. How do you deal with the real time vrs. garbage collection problems in Python?
(jfm3)
Joseph A. Sarlo wrote:
GrIPD is an extension to PD that allows one to design custom graphical user interfaces for PD patches. GrIPD is _not_ a replacement for the PD Tcl/Tk GUI, but instead is intended to allow one to create a front end to a PD patch. The concept is to create your PD patch normally and then your GUI using GrIPD (similar to SuperCollider or Reaktor). You can then lauch PD using the -nogui command line argument (although this is certainly not necessary) so only your custom front end will be displayed.
GrIPD is available for Windows and Linux.
Check it out at: http://mambo.peabody.jhu.edu/~jsarlo/gripd/
-
jfm3 -
Johannes M Zmoelnig -
Joseph A. Sarlo -
Michael Droettboom -
Rory Walsh -
uta