as mentioned in LivesExperience, the LivesSDLPlugin? is good.
controls
one thing i wondered about adding to it would be joystick support: e.g. slider for speed (or blend, or whatever effect amount like ctrl-up/down are already) and x-pos for scrubbing (like ctrl-left/right are now on the keyboard). at least for the position SDL should give this nicely directly, might try it myself when have the time (hopefully soon). the slider etc. might be more difficult, hopefully not, 'cause would be nice.
OpenGL
one thing would be doing an opengl playback plugin. in KyperjokkiWorkPSX with PixelShox we used that quite a lot (in psx the only way to show video is to have it as a texture of some, or any!, opengl object). besides enabling weird projections (and nice basic ones, like a cube where the walls are textured with videos), OpenGL enables e.g. nice zooming, rotating etc. of the images. this might be even trivial to do! (depends how LiVES feeds the frames to the showers, haven't checked yet).
another would be getting input from opengl apps to LiVES, dunno if that could work like getting image from normal X11 apps (actually didn't get to try even that yet). opengl does have some capture mechanisms, but at least in PixelShox none were used (you could do no recording).
comments -- Fri, 31 Dec 2004 18:05:56 +0200 reply
Controls like that can be added through the OMC/OSC interface (see my comments on PythonLives). For openGL, it would be lovely to have LiVES as a texture pipeline. I think something could be done using a playback plugin. Getting pixel data back from openGL without actually rendering to a screen is tricky, otherwise it would be possible to get input from an openGL renderer via a livido generator plugin (like libvis, the livido plugin wrapper - http://cvs.sourceforge.net/viewcvs.py/lives/lives-plugins/livido-plugins/libvis.c?view=markup)
livido/libvis -- Mon, 03 Jan 2005 15:02:20 +0200 reply
ah, thanks for remining about LiViDO & LibVis - we must certainly look at those for our image/video/texture generating apps.
forgot to mention OSC (OpenSoundControl?) in the report/comments, certainly useful, but with the LivesSetup / PytonLives? thing was aiming at something bit different .. will reply in PythonLives