Improving decomb?

turbojet · 21st December 2013, 06:35

While decomb is much faster than tivtc for a good simple ivtc. Decimate lacks a way to exclude a part of the video which is important in cases like this. y0/y1 for decimate would be very helpful. Also x0/x1 for telecide and decimate would be helpful.

Another thing is when a only a small part of the frame is moving it chooses the wrong frames to keep. Such as a longshot of a car driving through a barren desert. Tivtc handles these situations fine. I think it has to do with block size, which is not configurable in decomb. Could there be some optimizing and/or a configurable block size added?

21st December 2013, 06:35	#1 \| Link
turbojet Registered User Join Date: May 2008 Posts: 1,840	Improving decomb? While decomb is much faster than tivtc for a good simple ivtc. Decimate lacks a way to exclude a part of the video which is important in cases like this. y0/y1 for decimate would be very helpful. Also x0/x1 for telecide and decimate would be helpful. Another thing is when a only a small part of the frame is moving it chooses the wrong frames to keep. Such as a longshot of a car driving through a barren desert. Tivtc handles these situations fine. I think it has to do with block size, which is not configurable in decomb. Could there be some optimizing and/or a configurable block size added? __________________ PC: FX-8320 GTS250 HTPC: G1610 GTX650 PotPlayer/MPC-BE LAVFilters MadVR-Bicubic75AR/Lanczos4AR/Lanczos4AR LumaSharpen -Strength0.9-Pattern3-Clamp0.1-OffsetBias2.0