paris@parisgraphics.com a écrit :
Hi Patrice,
If you are using pdp, why not just create another pdp_xv window just for previewing? Maybe connected to a [playlist] or your favorite method of browsing? Then when you like what you see, route it to the main output. That's what I have done in the past and it worked quite well.
Best, p
Indeed, I'm planning first for browsing through a list of video files and previewing them into a single monitor windows, because it should be rather simple to implement, and pdp make it even simplier than what I have imaginated first. The finality in fact is about having the possibility of displaying different libraries of video files, with an assigned video processing method for (hmmm don't know how to call it, let me say) each video object. A comparison might be more clear: something like [videogrid] but with animated movies, and if it's possible, a preview of the effect(s) that has been applied to it, and last step (in a not too long future I hope) would be about having a preview that mimics things done with different kind of Gem/Gridflow/pdp patches, I guess that could be done with capturing main window during the saving process.
Obviously this is only for playing little loops.
By this way of displaying video files, VJing improvisations is a lot more efficient than having to browse through lists of video names, somehow, like Cris McCormick has demonstrated lately during a discussion into desiredata mailing list:
http://lists.goto10.org/pipermail/desiredata/2007-July/000056.html
You could start two PDs. Each one controlling it's own Gem window. One would be the main output, the other the "previewer".
Tom
On 7/18/07, Patrice Colet megalegoland@yahoo.fr wrote:
paris@parisgraphics.com a écrit :
Hi Patrice,
If you are using pdp, why not just create another pdp_xv window just for previewing? Maybe connected to a [playlist] or your favorite method of browsing? Then when you like what you see, route it to the main output. That's what I have done in the past and it worked quite well.
Best, p
Indeed, I'm planning first for browsing through a list of video files and previewing them into a single monitor windows, because it should be rather simple to implement, and pdp make it even simplier than what I have imaginated first. The finality in fact is about having the possibility of displaying different libraries of video files, with an assigned video processing method for (hmmm don't know how to call it, let me say) each video object. A comparison might be more clear: something like [videogrid] but with animated movies, and if it's possible, a preview of the effect(s) that has been applied to it, and last step (in a not too long future I hope) would be about having a preview that mimics things done with different kind of Gem/Gridflow/pdp patches, I guess that could be done with capturing main window during the saving process.
Obviously this is only for playing little loops.
By this way of displaying video files, VJing improvisations is a lot more efficient than having to browse through lists of video names, somehow, like Cris McCormick has demonstrated lately during a discussion into desiredata mailing list:
http://lists.goto10.org/pipermail/desiredata/2007-July/000056.html
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Thomas O Fredericks a écrit :
You could start two PDs. Each one controlling it's own Gem window. One would be the main output, the other the "previewer".
Tom
You are right, a previewer window would also be necessary for sighting what's happening on the 'video server', for completing one more function that some good VJing programs would give, that's why it's always interesting to keep client and server separated by different pd instances, even if they are both on the same computer, so every user would enjoy this kind of patch, some would just be frustrated of not being able to use some tools provided by 'unix only' externals, ...
For slightly conclude, it's not really interesting to bring some new libraries, just for building a single previewer window, since many solutions already exist with using only things from the oceans of dependencies we already have.
But still advantageous is to look into some solutions to give better visualizing tools that won't drown the video improvisator with filenames, and codes.
-
paris＠parisgraphics.com -
Patrice Colet -
Thomas O Fredericks