Howdy all,
I was showing a friend the new pd gui plugins and he suggested one that causes the patch wires to vibrate/wiggle based on the amount of messages being sent. How hard would it be to code such a plugin?
Yeah, it'd be kind of useless but totally fun! Are there any plugins floating around in a similar vein?
Dan Wilcox danomatika.com robotcowboy.com
Le 2011-12-02 à 03:44:00, Dan Wilcox a écrit :
I was showing a friend the new pd gui plugins and he suggested one that causes the patch wires to vibrate/wiggle based on the amount of messages being sent. How hard would it be to code such a plugin?
You need modifications in the centre of the interpreter of pd to first have a trace of all the messages. This will necessarily need recompiling pd.
For plain users who want this already compiled, they'd need some kind of way to pick the correct executable at startup : choose either the regular «fast» interpreter (well, at least faster than the other) or the interpreter that constantly reports to a special kind of plugin (checking whether any such plugins are active still slows down the interpreter).
The 2nd interpreter allows for a plugin that counts the number of messages or total size of messages, or a plugin that prints all messages to a file, or print backtraces for every error message, and perhaps a lot of other things (though probably not a stepping-debugger, for example... you can't be pausing pd while still clicking around).
BTW, Pd has already two interpreters... I'm talking about two possible variants of the message-interpreter, because you are talking about messages, but there is also a signal-interpreter, which would have to be modified if you also wanted runtime stats on that.
There may be other ways of doing similar things using tricks like making invisible patchcords to hidden objects that aren't even in the patch, but to me it doesn't sound any easier than modifying the centre of the message-interpreter (m_class.c and stuff).
What does the patchcord inspector do, to get its data ? I didn't look at it.
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
----- Original Message -----
From: Mathieu Bouchard matju@artengine.ca To: Dan Wilcox danomatika@gmail.com Cc: pd-list List pd-list@iem.at; Luke Loeffler lukerl@gmail.com Sent: Friday, December 2, 2011 10:17 AM Subject: Re: [PD] Any useless/fun gui plugins around?
Le 2011-12-02 à 03:44:00, Dan Wilcox a écrit :
I was showing a friend the new pd gui plugins and he suggested one that
causes the patch wires to vibrate/wiggle based on the amount of messages being sent. How hard would it be to code such a plugin?
You need modifications in the centre of the interpreter of pd to first have a trace of all the messages. This will necessarily need recompiling pd.
What about a gop abstraction with a hsl showing? Just pass the message through and trigger a bang to animate the vsl back and forth, have it decay at some rate. Replace the hsl with a data structure curve with three coordinates, and you've got yourself a "pluckable" patch wire.
-Jonathan
For plain users who want this already compiled, they'd need some kind of way to pick the correct executable at startup : choose either the regular «fast» interpreter (well, at least faster than the other) or the interpreter that constantly reports to a special kind of plugin (checking whether any such plugins are active still slows down the interpreter).
The 2nd interpreter allows for a plugin that counts the number of messages or total size of messages, or a plugin that prints all messages to a file, or print backtraces for every error message, and perhaps a lot of other things (though probably not a stepping-debugger, for example... you can't be pausing pd while still clicking around).
BTW, Pd has already two interpreters... I'm talking about two possible variants of the message-interpreter, because you are talking about messages, but there is also a signal-interpreter, which would have to be modified if you also wanted runtime stats on that.
There may be other ways of doing similar things using tricks like making invisible patchcords to hidden objects that aren't even in the patch, but to me it doesn't sound any easier than modifying the centre of the message-interpreter (m_class.c and stuff).
What does the patchcord inspector do, to get its data ? I didn't look at it.
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
You could do this in a patch with iemguts/receivecanvas to get the messages sent to the canvas, then generate a Tcl command to move the window using [hcs/window_name] to get the Tcl ID and send this command to [hcs/sys_gui].
.hc
On Dec 2, 2011, at 3:44 AM, Dan Wilcox wrote:
Howdy all,
I was showing a friend the new pd gui plugins and he suggested one that causes the patch wires to vibrate/wiggle based on the amount of messages being sent. How hard would it be to code such a plugin?
Yeah, it'd be kind of useless but totally fun! Are there any plugins floating around in a similar vein?
Dan Wilcox danomatika.com robotcowboy.com
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Terrorism is not an enemy. It cannot be defeated. It's a tactic. It's about as sensible to say we declare war on night attacks and expect we're going to win that war. We're not going to win the war on terrorism. - retired U.S. Army general, William Odom
From: Dan Wilcox danomatika@gmail.com To: pd-list List pd-list@iem.at Cc: Luke Loeffler lukerl@gmail.com Sent: Friday, December 2, 2011 3:44 AM Subject: [PD] Any useless/fun gui plugins around?
Howdy all,
I was showing a friend the new pd gui plugins and he suggested one that causes the patch wires to vibrate/wiggle based on the amount of messages being sent. How hard would it be to code such a plugin?
Yeah, it'd be kind of useless but totally fun! Are there any plugins floating around in a similar vein?
I did something like that with data structures to get an array where the y is the index and the x is the
value at that index-- basically a "Put" menu array turned 90-degrees clockwise. The scalar is in a
gop canvas with an inlet/outlet to connect between objects. When dsp is off (or all signals are zero)
it looks like a normal patch. When dsp is on, all the wires animate to show the signal going through them.
I could even turn animation on/off by clicking.
The problem is that most interesting patches don't keep the signal in the -1 1 range the entire time-- for
example, with FM synthesis either the modulation index animates all over the place, or you just scale it
(in which case x/y labels become necessary, which will clutter the patch).
I think the patch might be posted somewhere on this list.
-Jonathan
Dan Wilcox danomatika.com robotcowboy.com
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
Dan Wilcox -
Hans-Christoph Steiner -
Jonathan Wilkes -
Mathieu Bouchard