Hello,
Is there a way to show gui of a pd instance that was launched with -nogui option ?
Cheers
On 8/28/25 14:14, Yogi data wrote:
Hello,
Is there a way to show gui of a pd instance that was launched with -nogui option ?
send a "vis" message to Pd¹. the vis message takes the base path to your Pd(-GUI) installation.
since this can be different for each system, you can use something like this to dynamically get the right path:
[symbol ../tcl/pd-gui.tcl(
|
[file which]
|
[symbol $1/../..(
|
[file normalize]
|
[vis $1(
|
[s pd]
if you provide no argument (e.g. [; pd vis(), the GUI will be closed.
(i think the interface is a bit ugly, and we should be able to simply do [; pd vis 1(, resp [; pd vis 0(; but that's just syntactic sugar)
gfmasdr IOhannes
¹ you have to provide your own means to send that message to Pd, once it is running headless. Pd provides plenty of ways to do that.
Something is unclear to me.
I'm on linux, with command line, my path to pd-gui is /usr/local/lib/pd/tcl/pd-gui.tcl
So the message is " vis /usr/local/lib/pd/tcl/pd-gui.tcl "
In order to send this to pd, Should I use 'pdsend' and create a netreceive in my patch ? ( this worked fine)
Or find the port "pd" already opened ?
From: IOhannes m zmoelnig via Pd-list pd-list@lists.iem.at Sent: 28 August 2025 14:40 To: pd-list@lists.iem.at pd-list@lists.iem.at Subject: [PD] Re: Opening gui of running -nogui pure data instance
On 8/28/25 14:14, Yogi data wrote:
Hello,
Is there a way to show gui of a pd instance that was launched with -nogui option ?
send a "vis" message to Pd¹. the vis message takes the base path to your Pd(-GUI) installation.
since this can be different for each system, you can use something like this to dynamically get the right path:
[symbol ../tcl/pd-gui.tcl(
|
[file which]
|
[symbol $1/../..(
|
[file normalize]
|
[vis $1(
|
[s pd]
if you provide no argument (e.g. [; pd vis(), the GUI will be closed.
(i think the interface is a bit ugly, and we should be able to simply do [; pd vis 1(, resp [; pd vis 0(; but that's just syntactic sugar)
gfmasdr IOhannes
¹ you have to provide your own means to send that message to Pd, once it is running headless. Pd provides plenty of ways to do that.
On 28/08/2025 17:10, Yogi data wrote:
Something is unclear to me.
I'm on linux, with command line, my path to pd-gui is /usr/local/lib/pd/tcl/pd-gui.tcl
So the message is " vis /usr/local/lib/pd/tcl/pd-gui.tcl "
no. it's "vis /usr/local/lib/pd/".
this is what my patch should have produced.
In order to send this to pd, Should I use 'pdsend' and create a netreceive in my patch ? ( this worked fine)
yes, that's one way. another is to listen on the serial port for a given event. or, whatever.
but [netreceive] is a good start :-)
Or find the port "pd" already opened ?
there's none.
gfmsadr IOhannes
PS: sorry for my off-list mail; i didn't see your reply to the mailing list at first.
Cheers, yes your patch was returning the right path. It did work.
Before asking I was looking into the message in pd console : 'pd-gui' connecting to 'pd' on localhost 41969 & I thought there was a way to use this port for opening the gui.
( sorry for off-list mail ! I noticed this too late ) ________________________________ From: IOhannes m zm?lnig via Pd-list pd-list@lists.iem.at Sent: 28 August 2025 16:26 To: pd-list@lists.iem.at pd-list@lists.iem.at Subject: [PD] Re: Opening gui of running -nogui pure data instance
On 28/08/2025 17:10, Yogi data wrote:
Something is unclear to me.
I'm on linux, with command line, my path to pd-gui is /usr/local/lib/pd/tcl/pd-gui.tcl
So the message is " vis /usr/local/lib/pd/tcl/pd-gui.tcl "
no. it's "vis /usr/local/lib/pd/".
this is what my patch should have produced.
In order to send this to pd, Should I use 'pdsend' and create a netreceive in my patch ? ( this worked fine)
yes, that's one way. another is to listen on the serial port for a given event. or, whatever.
but [netreceive] is a good start :-)
Or find the port "pd" already opened ?
there's none.
gfmsadr IOhannes
PS: sorry for my off-list mail; i didn't see your reply to the mailing list at first.