On Fri, Jan 09, 2004 at 01:15:38PM -0400, Rob Shortt wrote: > Its funny you should mention this because after you committed the fxd > generation stuff to recordserver I initially had the thought that the > individual plugins may be doing too much (redundant) work themselves and > that it was good you committed those changes to recordserver.py.
Well, luckily, the FXD can (and probably should) be generated whenever since the length is calculated by mmpython, and sometimes you want to watch something while it's recording. The thumbnail, on the other hand, requires that some recording has taken place; at least five minutes. > Only after reading this email have I realized that we can leverage the > event handling in recordserver that I added recently. We could create a > RECORD_END (or something) event (perhaps with some descriptive args) and > post it from the recording plugin. The main portion of recordserver > would instantly pick it up and handle it however it wishes. Do you want to add the event? Also, would you be opposed to me moving some of the many, many 'print' statements in recordserver into debug? My logs are typically full of a lot of information which isn't needed in daily use. Aubin ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
