[gst-devel] [ANN] Warsaw Pakt 0.3

[daniel fischer]

"how it would work" is described in the manual ;). i plan to do a short tutorial-style introduction soonish...

for it's uses, well, i try to keep it generic in ways. one can think of a lot of different uses.

personally, i'm using it in context of my studies of "media design" for interactive installations and vjing. the point with vjing here is that i can use my old snuggly laptop to control my much more powerful "performance machine", via wlan from anywhere in the party. the performance box can be placed rather close to the beamer (or whatever display device), saving the all-so-missing long cables.

you could also think of multiple vjs controlling a single pipeline, a single vj controlling pipelines on multiple machines (and parties :), multiple vjs controlling multiple pipelines at the same time, and so on. yet, one of the basic ideas was for the vj to be able to setup a processing graph fitting his/her needs closely, and devising a performance interface in flash. i know a bunch of good flash coders, so in part i did that for those :)

another project i'm loosely involved in is "streaps/radiomatic", where we try to have a audio workshop platform for experimental music. the idea there is to be able to mix in your stream to the platform, and have "the community" decide on the mixer levels. it's currently done with a flash interface and a pd server, and on the long run i'd like to replace it with a pakt-run gst pipeline. (radiostudio.org/streaps)

one more main use would be the easy use of hardware devices (phidgets, sensors, the like) to control a gstreamer pipeline's properties. or, web-access to some installation, or to a video stream's properties.

it's 'just' network-access to gstreamer. the possibilities seem endless to me. APE is a prime example of a client, in that it tries to be a generic (gst-editor-like) pipeline editor. i didn't really expect this kind of stuff to happen that early, but if martin (the ape guy) wants to do this... why should i stop him? :)

i've had various "prototypes" of pakt, one, eg, was a clone of gst-launch that would publish all the pipeline's parameters to an OSC (OpenSoundControl) interface. some friends of mine, MAX/MSP-phreaks, then sent some parameters of their sound patch to my gstreamer video pipeline (using some ad-hoc homegrown plugins) for some artistic performance. it worked great, and pakt will enable the like.

the test server is not in fact down. it's just that APE is not up to the current version, martin will bring it up to speed during the next few weeks. i'm also working on a gtk interface.

also, i hope the tutorial will explain a lot of details on the serialization/deserialization process, and other stuff, when it arrives.

meanwhile, i'll gladly try to answer any questions here or in #gstreamer (as eladin).

-dan

ps: i hope this arrives on the list in time, my mail server seems to have some troubles with lists.sourceforge.net, delaying mails by 3 days...

Thomas Vander Stichele <thomas at apestaart.org> (on Sun, 28 Sep 2003 10:21:48 +0200):

  > I looked over the website.  It looks pretty cool, but what does it do ?
  > :) The server seemed down.
  > 
  > Can you give us a short example of what this would be used for and how
  > it would work ?
  > Thomas
  > 
  > On Thu, 2003-09-25 at 15:20, daniel fischer wrote:
  > > hi gst folks,
  > > 
  > > i'd like to let you know about my projekt "Warsaw Pakt". It uses gstreamer intensively in an attempt to have net-wide control over pipelines and their parameters. It kinda evolved into a relatively generic GObject-access system, but it's main focus is and will be gstreamer.
  > > 
  > > currently, it consists of the "pakt" library that provides the basic functionality, a gst "daemon" (pgstd) that interfaces the pakt semantics to gstreamer (just two classes for elements and pads), and "pash", an access shell. the only supported access method currently is flash-like (null-terminated) XML sockets, OSC will follow soonish.
  > > 
  > > while some features are still missing, i can successfully setup simple gstreamer pipelines, connect their elements, and start/stop them. and, of course, set the element's properties.
  > > 
  > > have more info, including docs on:
  > > 	http://subsignal.org/pakt/
  > > 
  > > keep up the good coding with gstreamer (thanks!).
  > > 
  > > -dan
  > > 
  > > ---
  > > dan at f3c.com
  > > http://f3c.com/dan/
  > > 
  > > 
  > > 
  > > -------------------------------------------------------
  > > This sf.net email is sponsored by:ThinkGeek
  > > Welcome to geek heaven.
  > > http://thinkgeek.com/sf
  > > _______________________________________________
  > > gstreamer-devel mailing list
  > > gstreamer-devel at lists.sourceforge.net
  > > https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
  > 
  > Dave/Dina : future TV today ! - http://davedina.apestaart.org/
  > <-*- thomas (dot) apestaart (dot) org -*->
  > I'll take
  > a quiet life a handshake
  > of carbon monoxide
  > <-*- thomas (at) apestaart (dot) org -*->
  > URGent, best radio on the net - 24/7 ! - http://urgent.rug.ac.be/
  > 
  > 
  > 



-- 

---
dan at f3c.com
http://f3c.com/dan/