| vdbucks |
01-28-2012 05:07 AM |
Quote:
Originally Posted by stocktrader23
(Post 18697530)
/usr/local/bin/ffmpeg -i {input_file} -copyts -b 400k -ar 44100 -s {input_width}x{input_height} {output_file};
/usr/local/bin/flvtool2 -U -c -duration:{duration} {output_file}
Looking to improve quality without destroying a server. Any suggestions?
|
Back when we were encoding to flv, we used these settings which worked pretty well with the red5 streaming server:
ffmpeg -i "$filename" -b 1500k -aspect 4:3 -s 720x480 -acodec libmp3lame -ar 44100 -threads 0 "$output"
The threads option tells ffmped how many threads to use (for multicore systems). '-threads 0' let's ffmpeg determine the best number of threds. '-threads 1' uses 1 thread (slower encode time but less resource usage). So on and so forth.
I can also provide you with a shell script that'll run through an encode sequence automatically. If you want it let me know and I'll post it. The current script I have encodes an hd wmv file to sd wmv, sd flv, sd wmv clips and sd mpg clips. Can be modified for your needs though.
But to be honest though, flv is old school and the file size to quality ratio will always suck. The settings above with a standard 30 minute video is about 300mb+
We've since moved to mp4 streaming and haven't looked back. I didn't read the whole thread since it's more or less nothing but idiots bitching at each other, so hopefully you can modify your tube script (if that's what this is for) for mp4 streaming, and better yet I'd highly recommend using rtmp + mp4 (we use wowza + ec2)... save a ton of bandwidth and cut your output files in half with much higher quality.
Hit me up on ICQ if you want more info and whatnot. |
