From: Andy Spencer <andy753421@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] dataflow programming from shell interpreter
Date: Tue, 19 Jan 2010 22:13:21 +0000 [thread overview]
Message-ID: <20100119221321.GA22431@c.hsd1.tn.comcast.net> (raw)
In-Reply-To: <89568f5cfeef17d6b1a79f12daeea5c6@quintile.net>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
> This is always somthing I have wanted to do for video stream
> processing, writeing a limited proceedural language which can be
> refactored as a dataflow graph for efficent implementation (of video
> processing).
This sounds a lot like how GStreamer operates. An example from the
gst-launch manpage:
gst-launch filesrc location=music.mp3 ! mad ! audioconvert ! vorbisenc ! oggmux ! filesink location=music.ogg
I'm not sure they've done as much work on a procedural language, but
they have a good set of 'plugins', as they call them.
[-- Attachment #2: Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2010-01-19 22:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 10:58 Tim Climber
2010-01-18 12:19 ` Steve Simon
2010-01-18 20:04 ` Tim Newsham
2010-01-19 9:59 ` Aharon Robbins
2010-01-19 15:40 ` Steve Simon
2010-01-20 21:13 ` Eris Discordia
2010-01-20 21:41 ` Patrick Kelly
2010-01-21 8:00 ` roger peppe
2010-01-21 12:45 ` maht
2010-01-21 21:36 ` Skip Tavakkolian
2010-01-22 9:44 ` Eris Discordia
2010-01-19 22:13 ` Andy Spencer [this message]
2010-01-18 16:23 ` Eric Van Hensbergen
2010-01-18 19:23 ` Aharon Robbins
2010-01-19 22:33 ` Andy Spencer
2010-01-27 10:44 ` Sam Watkins
[not found] <c563b2f7-92ac-463a-864c-267721ddb30a@k35g2000yqb.googlegroups.co>
2010-01-18 11:15 ` erik quanstrom
[not found] <58d8d6b4960925aab27312e0968a3e26@quintile.net>
2010-01-18 19:39 ` Eric Van Hensbergen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100119221321.GA22431@c.hsd1.tn.comcast.net \
--to=andy753421@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).