Program to pull frames from video – 2093 days old

[BlackHawk]

I would like a program to pull individual frames from video and save them as .png, .jpg, etc. The format is .mov from Quicktime.

[Grogan]

You probably have mplayer? It can capture frames from the command line. This works, I tested it (though it captured two frames, one of the png files was just a black screen *shrug*). It names the pngs 00000001.png etc.

mplayer filename.mov -frames 1 -vo png -nosound -ss 20

The trick is to know the time of the frame you want to capture (20 seconds in this example). Play the movie and watch the time counter.

[Grogan]

Actually that doesn't quite work as I thought. If you specify frames 1 it only grabs the first frame. Try something like:

mplayer filename.mov -frames 10 -vo png -nosound -ss 20

and you'll get the first frame, plus the next 10 after -ss (20 seconds) position

Play with that to get what you want

[BlackHawk]

Will give it a try. Thanks.

I don't mind farking around with the command line but My Wifey would more appreciate a nice gui.

So, I found LiVES which works great on PCLinuxOS. Just click on the frame you want and it saves as .jpg using (go figger) mplayer as a back end.

Found a package for it at Slacky.eu. Iff'n I can resolve the dependency bs I'll be cool to go with a lot of features Mrs. Hawk would like.

[Grogan]

mplayer is extraordinarily useful. I use it to convert .wma audio files to wav too (I hate WMA) and then pipe the output to lame to encode as mp3.

Good that you found a front end for it. In slack, compile it yourself and then you'll be sure of having the dependencies (it won't compile without the mandatory ones, and some of them may be optional and the configure script will just skip over them). If it's a binary, you will have to get all the dependencies it's linked against whether you want that functionality or not. (In general)

[BlackHawk]

mplayer is extraordinarily useful. I use it to convert .wma audio files to wav too (I hate WMA) and then pipe the output to lame to encode as mp3.

Good that you found a front end for it. In slack, compile it yourself and then you'll be sure of having the dependencies (it won't compile without the mandatory ones, and some of them may be optional and the configure script will just skip over them). If it's a binary, you will have to get all the dependencies it's linked against whether you want that functionality or not. (In general)

Would a binary be the Slackware package? So, however they compiled it will determine my dependency list?

[Grogan]

Yes, that's what I meant. A "slackware package" would be precompiled binaries.

Also, again speaking in general, yes how a package is compiled (e.g. what libraries are present on the system at compile time and/or what options they've enabled) will determine some of the dependencies required.