Yadif(mode=1,...) for double frame rate.
Our website is made possible by displaying online advertisements to our visitors. Consider supporting us by disable your adblocker or try PlayON and record Netflix, HBO, Hulu, etc! :)
+ Reply to Thread
Results 31 to 45 of 45
QTGMC(BlockSize=4) gets rid of the jump in jump_04.avi.
But yadif advantage is that is much faster. Probably faster then QTGMC fastest preset. Not sure.
Edit: for lossless compression, there is of course difference. But question is what is worst. Do perfect deinterlacing with slowest QTGMC preset and then compress to say with CRF 28 or use fast Yadif bob and spatial temporal check and compress with say CRF 22.
Last edited by Bernix; 10th Aug 2018 at 07:16. Reason: EDIT
Last edited by jagabo; 10th Aug 2018 at 07:30.
QTGMC's "ultra fast" preset uses Yadif.
This source isn't worst, but also far from miniDV video quality. The question is if QTGMC is really must have here. Just my opinion.
BernixVideo Avidemux, Mkvtoolnix, Subtitle edit, Vidcoder. Other software that I love :Animation: Opentoonz, Painting: Krita, Video capture: OBS studio, Video player: Potplayer, TV recording: VLC, NLE: KDEnlive
You get this result too?
But it's very slow rendering now.
VD still use only 30% CPU, why not more?
I try that multithreaded version some day, but it crashes every time. So I've to be patient....
How can I fix this jump?
And without deleting?
Note: I want to fix all jumps in interlaced mode first, then save this as a new interlaced (no jump) videofile and then I use QTGMC with this corrected file.
So I can do a interlaced DVD and a 50p without jumps, you know.
If you look at the video field by field you will see three identical fields in a row. the capture inserted an extra frame by making two extra copies of one field. Deleting the frame leaves you with perfectly smooth motion. If this causes audio sync problems insert a frame elsewhere where it won't be noticeable.
Last edited by jagabo; 13th Aug 2018 at 15:20.
Ah ok, now I understand.
I think, that it gets not async, the recorder drop a frame later on. Have to check this later, if is there a drop frame.
Capture cards often drop frames or fields. In order to keep the audio in sync, they will later duplicate either a whole frame or a field in order to make up for what was missed. Unfortunately, the drop is often not immediately adjacent to the duplicate. Therefore in order to fix things, you have to create a script that finds the duplicates (easy to do) but then senses big gaps in motion, due to the drop (hard to do), and inserts a synthesized frame (using motion estimation) at that point.
I created such a script here, and you are welcome to try to make it work for your existing captures. However, the better thing is to find out why your capture card isn't working very well, and fix that.
Automatically fix dups followed (eventually) by drops
AviSource("testfile.avi") AssumeTFF() SeparateFields() StackVertical(SelectEven(), SelectOdd())
Of course, it's also possible for the top field to shift up rather than the bottom. Or maybe both fields (the entire frame) could shift up. Or fields/frames could shift down rather than up. You would need slight variations of the fix to handle those errors. You should be able to figure those out for yourself.
Jump5.avi can be analyzed with:
AviSource("jump5.avi") AssumeTFF() SeparateFields()