Immensely crappy video, need help improving it

[Chainmax]

I have some short 160x120 clips that were taken with an old digicam and would like to be able to watch them fullscreen or at least in a decent sized window. I was thinking of resizing to 448x336 or 512x384 and used several combinations or resizers (lanczos, IIP and SharpResize) with filters like funkydeblock and addgrain to no avail. I think that if this is possible it will require a long and complicated filterchain which I won't be able to create, so I'd like to know if you guys could give it a shot.

Here's one of the clips (http://www.31012.com/~stuff/MOV01825.MPG)

[rfmmars]

You really have nothing to work with. If you mean Digitcam = Webcam then it like asking a 360x250 upconvert to HDTV. First these webcams had limited brightness range and poor color.

I have doneload your clip and will get back to you if I can make some improvment

richard
www.photorecall.net

[Bogalvator]

I get a 404. And I was looking forward to the challenge as well.....

[Chainmax]

rfmmars: by digicam I mean a photo camera, this one in particular being a Sony CyberShot DSC-P31. And I'm just asking what is the best improvement that can be made to these clips, no matter how long the filterchain is.

Bogalvator: I am getting that error too. I'll see if it can be fixed.


BTW, if it's any help, the improved clips are meant to be encoded to XviD with constant quantizer = 2, didée's sixofnine matrix, B-frames at 1/1/1, QPel and Trellis.

[Chainmax]

The clip is up again.

[sh0dan]

EXTREMELY slow script (<1fps)
AVISource("C:\work\improveme.avi")
converttoyv12()
selectevery(3,0)
mvback=mvanalyse(isb=true, fth=60, pel=2,sx=4, sy=4)
mvforw=mvanalyse(isb=false, fth=60, pel=2, sx=4, sy=4)
mvconvertfps(last, mvback, mvforw, fps=25.0, fbw=2, thSCD2=255, thSCD1=500)
EDIUpsizer(method=7, window=8)
addgrain(10,0,0)
EDIUpsizer(method=7, window=8)
addgrain(10,0,0)
lanczosresize(448,336)
Requires EDIUpsizer 0.91 (http://forum.doom9.org/showthread.php?s=&threadid=72174), MVTools 0.9.4 (http://forum.doom9.org/showthread.php?s=&threadid=76041&perpage=40&pagenumber=2) and AddGrain (http://www.avisynth.org/warpenterprises/). You can leave out the last EDIUpsize/Addgrain.

[Chainmax]

Cool, thanks. I have a very slow box (an 850Mhz T-Bord with 128Mb ram) that is even slower than it should be, but since the clips are very short I'll try this script out. Again, thanks a lot, I really appreciate it :):)

About the last EDIUpsize/Addgrain, they can be removed or they have to be removed (i.é: you made a typo)?

[Chainmax]

Maybe I could use SharpResize instead of lanczos, what do you think?

[Chainmax]

This is sh0dan's suggestion (http://www.31012.com/~stuff/MOV01825-Enh.avi) (it will be completely uploaded in about45 minutes)only with SharpResize instead of Lanczos and encoded to XviD with the following settings:

Single Pass @ q2
Didée's SixOfNine matrix
QPel
B-Frames at 1/1/1
Chroma Optimizer and zone beings with keyframe
MSP 6
VHQ 4
Maximum I-frame Interval 250
Trellis Quantization


The file clocked in at 18.2Mbytes. IMO, on static scenes it looks better than the original when played fullscreen, but as soon as the camera starts to move, all sorts of issues appear. There's still way too much macroblocking too. Maybe something like funkydeblock() either at the end of the script or before the resizing would make this better?

P.S: even though B-frames were set at 1/1/1, I think they got Q3 instead of Q2 like I and P-frames. Can someone confirm that?

[Leak]

Originally posted by Chainmax
P.S: even though B-frames were set at 1/1/1, I think they got Q3 instead of Q2 like I and P-frames. Can someone confirm that?

Sure thing - you have your offset set to 1, so you'll get 2(P-frame quant)*1(ratio)+1(offset)=3.

Set your offset to 0 and you'll get quant 2 B-frames.

np: Kings Of Convenience - Summer On The Westhill (Quiet Is The New Loud)

[Chainmax]

Since I imagined that SharpResize's XSharpen might be enhancing the source's blocking, I removed it and put Lanczos back in. I also took out QPel and added an Unfilter(-30,-30) right after the DirectShowSource line. The video does look better that way and file size goes down to 13,2Mbytes, but the macroblock dancing and swimming when the camera moves is still there. Does anyone want to propose an alternate script?

[Chainmax]

Anyone?

[Chainmax]

mf, could you please give this a go?

[Chainmax]

One more bump to see if this gets some extra attention as I really need to improve these clips...

[eb]

First of all i can't belive that presented clip is original one from the camera.

eb

[Chainmax]

Remember it's a photo camera, not a dedicated video camera. Anyway, what's second?

[Chainmax]

Can someone at least confirm the artifacting that starts to occurs after the first camera pan?

[sh0dan]

Don't bump your threads, unless you have something to say. If people had something to add, they would already have done so.

One more bump, and the thread will be closed.