View Full Version : Sharpening/denoising 720p .mkv, Seesaw/Ff3dfilter/Lsf, any experience?
grkn
28th September 2007, 21:26
Hi, I have a Benq PE7700 720p HD projector and a nice little 70" sony screen to match it. Most settings I've seen on this forum focuses on improving DVD picture, so I'm wondering if anyone has experience with sharpening/denoising HD material.
Finding resize luma sharpening a bit limited, I've experimented with Lsf, FF3DFILTER, SeeSaw and I'm currently using the following (pretty basic) settings:
SetMemoryMax(1024)
AssumeTFF() # If it stutters try AssumeBFF instead of AssumeTFF.
MT("LimitedSharpenFaster(ss_x=1.0, ss_y=1.0, Smode=3, strength=100, overshoot=0)",2)
And denoise 3d chroma 1 time 4 before that, with a 0.2 luma sharpen and lancos 2 resize following. (What's the word on resizing these days btw?).
And advice on settings I could test to improve picture? I'm going to be using a 3 ghz dual core pentium to do the job. (coreavc + ffdshow for h.264 material).
Demi9OD
29th September 2007, 02:20
This is my HD profile, almost exclusively used for h264 in MKV. I run a quadcore though, and don't expect it will run on anything less. If you have a beefy video card (8800gts or better) you could probably manage to do it with fft3dgpu.
MT("FFT3DFILTER(sigma=.8,bw=8,bh=8,bt=3,sharpen=.6).gradfun2db()",6,2)
TheRyuu
29th September 2007, 03:18
@grkn
Are you trying to filter this in real time? or are you encoding this.
Leak
29th September 2007, 11:03
@grkn
Are you trying to filter this in real time? or are you encoding this.
My guess would be realtime, as he explicitely mentions a projector... :)
np: Kid606 - I Wanna Rock (You Just Left The Smallest Rave On Earth) (Who Still Kill Sound?)
grkn
29th September 2007, 17:49
Thanks, real time yes.
Tried your FF3DFILTER settings, got a few fps and a subtly sharper image.
I've found that setting lfs to less than 100 in strenght renders it effectless, and at 100 I get jaggies even if setting avisynth after resize in ffdshow (Sin Sity panning actor names is a good example of where it's evident).
Seesaw is just too slow for HD material on a 2 ghz dualcore (I'm getting a 3 ghz soon, but I'm not sure It'd help).
So, currently I'm left with luma resize sharpen and denoise 3d, not bad, but I would preffer a bit more sharpening.
EDIT: Seems that asharp does a ok job :)
foxyshadis
29th September 2007, 17:55
ss_x/y should be at least 1.1 or 1.15 to prevent obvious jagged edges. Slows it down, but really looks better. I prefer smode 4 with a strength of 200 or so for HD.
I always use seesaw these days, but I don't know what's optimal for HD. Chasing the optimal seesaw inputs turned out to be a fool's game, so I just picked some and left it for everything. :p Seesaw is faster than supersampled LSF, if not at the same resolution.
Demi9OD
29th September 2007, 18:13
May I ask what you picked Foxy?
grkn
30th September 2007, 23:55
Ironically I've stopped using avisynth setteling for denoise 3d, resize-lumasharp and asharp in that order.
Can anyone confirm that lsf only starts having effect with strength 100 (smode=3)?
Didée
1st October 2007, 01:37
Can anyone confirm that lsf only starts having effect with strength 100 (smode=3)?
Definetly not. "Having effect" starts with strength=1. From 15 or 20 on, it gets visible.
Use e.g. LSF(ss_x=1.0,strength=??).subtract(last) to visualize the actual change.
Archimedes
1st October 2007, 16:35
Definetly not. "Having effect" starts with strength=1. From 15 or 20 on, it gets visible.
That's exactly my experience for sharpening digital images (after resizing and so on). I've found out, that a strength value of 20 is a good starting point.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.