|
if you want to still use ffmpeg, here are a few tips:
1) always use the latest SVN version of ffmpeg, do not get a standard release, the app changes 5 times a day.
2) use 2 passes to encode, not just 1
3) never use -qscale, its not going to work right, I tried it for weeks.
4) for high res great quality video, I tend to use these settings:
pass 1: -f flv -vcodec flv -keyint_min 250 -r 25 -ar 44100 -ab 96 -b 3000k -s 1024x820 -g 150 -pass 1 -y
pass 2: -f flv -vcodec flv -mbd 2 -flags +mv0+trell+cbp -keyint_min 250 -r 25 -ar 44100 -ab 96 -b 3000k -s 1024x820 -g 150 -pass 2
The -s of course depends on your original video, thats just a sample size, keep the ratio obviously.
For the player size you suggested, I would use a size of around 540x432 and at that size, these other settings:
-ar 22050 -ab 32 -b 700k
At that quality, stretching the video to the player size you mentioned is going to be totally fine.
keyframes every 250 frames is also completely enough, with -r 25 that means one keyframe every 10 seconds. This is whats going to keep the size of your file down the most. ffmpeg will also lower the bitrate automatically if it achives a qscale of 2.0 with a lower one. Thats what 2 passes is good for.
The keyframe rate does mean of course that framegrabs are only possible every 10 seconds from the flv. So if that is not enough framegrabs for you, build frames for the original wmv instead.
It also means that in a skipable player, they can skip 10 seconds at a time, which usually is fine though in my oppinion.
Your question if running the flv through for example flvtool2 after converting is needed... answer is no, its not NEEDED, but you would be stupid not to. Not using it will ruin the player experience for the user that he got so accustomed to. I at least would never do that.
__________________
"Think about it a little more and you'll agree with me, because you're smart and I'm right."
- Charlie Munger
|