[PD] video output from PD

[Dan Wilcox]

I would pick up an old rackmount ethernet switch and use static ips. I imagine wireless would work, but you're asking for trouble if you don't get an industrial wifi router.

As for software, I'd echo using OpenFrameworks. The current version (0.8.0) now supports the RPI and there is an OMX video player class which can run with hardware acceleration. It would be simple to code a single, custom video player app that listens over OSC to start, stop, set frame position, etc. Said app would read from an xml file to know which video to load, so you don't have to hardcode anything.

You will not be able to do this with PD alone on the RPI since, as mentioned before, GEM currently has no OPENGL ES support on the RPI.

Email me if you guys need help/have a budget, although my timeframe is a little cramped right now.

On Dec 1, 2013, at 6:00 AM, pd-list-request at iem.at wrote:

> From: peiman khosravi <peimankhosravi at gmail.com>
> Subject: Re: [PD] video output from PD
> Date: December 1, 2013 at 5:25:53 AM EST
> To: Charles Goyard <cg at fsck.fr>
> Cc: PD List <pd-list at iem.at>
> 
> 
> Hello, 
> 
> Thanks for the answers. I've been looking around and it doesn't look like that omxplayer accepts OSC messages. Does it?
> 
> Also how are the Pis connected to a network? Through ethernet? In this case I would need a router with 20 outputs right?
> 
> To explain a bit more about the project. It's a live band, with precomposed videos playing back (with stop/start variations) across a bunch of analogue TVs placed on stage, all in sync with the sound. We don't know yet to what extent the result will be predetermined or generative but as long as there is the possibility of controlling the overall visual rhythm... The live sound from each instrument is also being transformed through lots of DSP in pd. So it's a complex setup and it needs to be reliable as we'll be taking the show on the road at some point. 
> 
> Many Thanks

--------
Dan Wilcox
@danomatika
danomatika.com
robotcowboy.com





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20131201/f670b514/attachment-0001.htm>