[PD] That's a surprising new look

Patrice Colet pat at mamalala.org
Thu Oct 11 13:11:24 CEST 2007


Max Neupert a écrit :
> Am 10.10.2007 um 12:24 schrieb Jack:
>> I prefer PD with a small GUI, it's better for CPU and GPU.
>> Jack
> i wonder why people do things in pd like
> $ reducing the number of sliders, toggles and bangs to a minimum, or
> $ running two instances of pd for the gui, or writing their gui  
> themselves in python, or
> $ using -nogui
> when its so efficient for CPU and GPU ... or was your comment ironic?
> m.

Personaly, both of those situations makes patches good looking and 

  Reducing the number of iem GUI is primordial, not only for gaining cpu 
process, but for gaining visibility, one interface patch could control 
several sets of similar abstractions, similar by the fact they use the 
same kinds of paremeter settings.
  Using two instance of pd is interesting, because it would be possible 
to use pd in a cluster like environment, with several computers, or even 
with one sigle computer, e.g. for Gem patches, one pd instance for the 
'client interface', and the other for the 'rendering server'.
  -nogui could be used for one of the two instances...
And extension interfaces made with tkinter, php-gtk, tcl-tk or anything 
else, could add features to the interface as well as replacing it.
  I wanted to make a project like this since some time ago, and it's 
called 'Mediale' now, here is how it looked like last year:


  The principle is about having a standard sized interface for each kind 
of pd patch, that could be created interactively following the project 
done with the application.

  The illustrated exemple from the upside link shows four different 
kinds of patches, the first one is for playing audio files like a 
sampler, the second one is for recording sounds, the third one is for 
controlling VST instruments, and the fourth is for controlling Gem objects.

  Each different interfaces are created/destructed dynamically and would 
share the same interface patch for controlling the sound output, talking 
with a main sequencer, talking with another network computer ..., they 
would share also the same libraries, and library interfaces (color 
picker, sound libraries, image libraries, etc...).

  And one another interface abstraction would control the 

  This is not really another kind of netpd, because this is not really 
for sharing a creation through network, or this is not a sequencer only, 
but this could integrate netpd patches, also this could live into 
pd-extended box in the long term.

  I wanted to add my two cents about this because I think the project is 
worth a try even if I don't really have time actually to complete a 
fully working version, and maybe some other people on the list has 
already made a project like that.

  Thanks for attention.

More information about the Pd-list mailing list