Encoding tennis matches with x264, encoding small fast moving balls

[rottweily]

Hello,

I'm the owner of a website with x264 encodes of tennis matches.
http://rottweily.freehostia.com/

Most of them are DVD rips, some of them are recodes of matches that were too big.
The goal is to have HQ matches that are still reasonable in size.
So I've set the following limitations on bitrates:
Video: 512kbps
Audio: 64kbps

Subject to change:
Video: H264 with x264
x264.exe --pass 1 --threads 2 --bitrate 512 --stats x264.log --progress --no-psnr --no-ssim --b-pyramid --bframes 3 --ref 5 --partitions all --direct auto --weightb --me umh --merange 16 --subme 7 --b-rdo --mixed-refs --bime --8x8dct --trellis 2
x264.exe --pass 2 --threads 2 --bitrate 512 --stats x264.log --progress --no-psnr --no-ssim --b-pyramid --bframes 3 --ref 5 --partitions all --direct auto --weightb --me umh --merange 16 --subme 7 --b-rdo --mixed-refs --bime --8x8dct --trellis 2


Audio: AAC with neroaac
neroAacEnc_SSE2.exe -br 64000 -2pass

Avisynth script:
TDeint(order=1)
AutoCrop(mode=0,wMultOf=2,hMultOf=2,leftAdd=2,rightAdd=2,topAdd=2,bottomAdd=2)
LanczosResize(640,480)
Undot()

Joining Stuff:
mkvmerge.exe --engage old_aac_codecid



Main question is, can I do any better keeping the bitrates?
Can I change specific parameters that change the quality of small fast moving balls?

[quake74]

To improve the lines on the field (I use it with soccer, and it works very well) you could use EEDI2. The combination suggested by MeGUI is usually


edeintted = last.SeparateFields().SelectEven().EEDI2(field=-1)
TDeint(full=false,edeint=edeintted)


See http://heptium.sh.cvut.cz/~integra/deint/ for examples. Obviously, mvbob, mcbob and the like are much better, but they are al least 2x slower.

[DarkZell666]

I can't see what's wrong with the ball, especially considering the bitrate you used.

Appart from using crf mode, changing the --direct auto to something else, and adding something like fft3dfilter() to your script, you pretty much maxed out everything.

If you're asking about the ball "echo" while it's moving, I suspect that that was already on the DVD, but if not, changing the deinterlacing method as suggested by quake74 is your last resort for this specific problem.

[rottweily]

I can't see what's wrong with the ball, especially considering the bitrate you used.

In most cases nothing is wrong. But because seeing the ball clearly is the most important thing, any quality increase without size increase is good.


Appart from using crf mode, changing the --direct auto to something else, and adding something like fft3dfilter() to your script, you pretty much maxed out everything.

Thanks.


If you're asking about the ball "echo" while it's moving, I suspect that that was already on the DVD, but if not, changing the deinterlacing method as suggested by quake74 is your last resort for this specific problem.
Ok.