> My objective is to indentify frames interactively, then use some other program, > lav2yuv, or whatever, to extract interesting frames to Jpeg or PPM images. > I do research in image processing and vision, so I want to interactivly > crop the video and extract a couple of hundred frames at a time. >
You might be interested in my project http://cuisine.bigasterisk.com. I have successfully used it to log 7h of documentary footage and cut an 8m show with 3 tracks of audio. I can't say it's ready for that size project, though, since installation is near-impossible and there are lots of missing features. But, if you want to play DV (raw or avi) only, see the frame you're on, and write notes on frames that will be saved into an XML file, perhaps I've got just the tool. If you wanted to use my stuff, here's an outline of what to do: 1. Have libdv, python (at least 2.1 or 2.2, I think), avifile installed (and probably more). 2. Get my code via cvs. Instructions are on the webpage. 3. In editor/lib, attempt to make. Email me with what goes wrong.. 4. Adjust your paths so editor/lib is in PYTHONPATH and editor/pour is in PATH (latter is optional). 5. Run "butter myvideo.dv" or "butter myvideo.avi" 6. If that's working, you should run "baste myvideo.xx" to make an initial XML file describing the video. Then, butter will let you write notes on the video as you watch. 7. Modify the program 'whip' to do your output. Whip currently makes an html page with thumbnails of your video and the annotations/marks you wrote according to the XML files. I've used it to make indexes of all my clips (one thumbnail per clip in the directory tree, all marks are shown too) or a mark guide for each clip (separate thumbnail for each mark you made). BTW, butter (the playback and annotation tool) has a bunch of keys for skipping different numbers of frames, and it can playback at variable speed. We've used it to transcribe 2 hours of interviews and another project by playing them at about .4 speed and typing during the talking. See http://bigasterisk.com/post/dash/tossscreen1.png for a big screenshot. On the left, hidden, is butter; on the right, mozilla displays the output of whip; and in the middle is the timeline editor 'toss'. Toss is exceptionally hard to run because it uses pygtk2, gnome-python2, libgnomecanvas2, etc. Those were a mistake. The next version will not use them. -Drew ------------------------------------------------------- This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en _______________________________________________ Mjpeg-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mjpeg-users
