Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
9th July 2006, 23:13 | #41 | Link | |
King of the Jungle
Join Date: Mar 2003
Location: Shoreditch, London
Posts: 429
|
Quote:
@ Didee I tried increasing ml but I didn't see any difference at all! Very strange. |
|
10th July 2006, 06:33 | #42 | Link | |
Registered User
Join Date: Oct 2003
Posts: 209
|
Quote:
Now for the news you don't want to hear: For a DVD I'm doing with source material in PAL with a LOT of full motion smooth movements (think dance videos), I am using MVFlowFPS2 for everything and I put that on track B; I then do a conversion using ConvertFPS(59.94, zone=80) and put that on track A. Anywhere MVFlowFPS2 makes a mistake, I cut that frame out and use the frame from the ConvertFPS conversion. Tedious, but it's pretty much a flawless conversion when I'm done. |
|
10th July 2006, 06:38 | #43 | Link | |
Registered User
Join Date: Oct 2003
Posts: 209
|
Quote:
Here is a particularly fast panning head using MVTools' MVFlowFPS2: ...and here is the same interpolation as done by MotionProtectedFPS: As you can see, the MotionProtectedFPS example has more distortion, as well as chroma flying all over the place :-) This isn't a massive slam on MotionProtectedFPS, just an example of why I use MVFlowFPS2. If I'm doing a quickie for viewing an MPEG-1 on television or something, MotionProtectedFPS's speed is fantastic. If I'm transcoding footage for a DVD for commercial sale, I use MVTools for the most quality. Just my $0.02. Last edited by Trixter; 10th July 2006 at 07:30. |
|
10th July 2006, 07:57 | #44 | Link | |
Registered User
Join Date: Dec 2004
Location: Terneuzen, Zeeland, the Netherlands, Europe, Earth, Milky Way,Universe
Posts: 689
|
Quote:
I confirm the depan, method is perfect for clear pans... But not for moving objects and/or zoom scenes. Stuttering! I have the best results with mvflowfps() followed by depan for stabilising. Motionprotectedfps() gives very good results too, and it is much faster. Actualy, both are giving me near perfect results in 90% of the cases... The artefacts are almost invisible on TV. Very fast moving people/objects, original recorded at low speeds like 15FPS are giving me the most problems. Maybe I am going to use convertfps() for these scenes instead. *EDIT* MvFlowFPS2 works a lot better for this. Fred.
__________________
About 8mm film: http://www.super-8.be Film Transfer Tutorial and example clips: https://www.youtube.com/watch?v=W4QBsWXKuV8 More Example clips: http://www.vimeo.com/user678523/videos/sort:newest Last edited by videoFred; 14th July 2006 at 14:55. |
|
10th July 2006, 15:16 | #45 | Link | ||
Huh?
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
|
Quote:
Quote:
Code:
vf=last.mvanalyse(isb=false,blksize=4,pel=2,search=3,truemotion=true) vb=last.mvanalyse(isb=true,blksize=4,pel=2,search=3,truemotion=true) MVFlowFPS(last,vb,vf,num=30000,den=1001)
__________________
Read Decomb's readmes and tutorials, the IVTC tutorial and the capture guide in order to learn about combing and how to deal with it. |
||
10th July 2006, 21:42 | #46 | Link | ||
King of the Jungle
Join Date: Mar 2003
Location: Shoreditch, London
Posts: 429
|
Quote:
Quote:
|
||
10th July 2006, 21:49 | #47 | Link | |
Registered User
Join Date: Oct 2003
Posts: 209
|
Quote:
I see that you shrunk blocksize from 8 to 4... from the docs, larger blocks are less sensitive to noise, are faster, but also less accurate. A blocksize of 4 might exacerbate the noise already present in your source. I see you increased the search algorithm to exhaustive... with small blocks, you're going to be waiting a very long time :-) MVFlowFPS2 uses two different motion analyses: A regular one and another one with the entire frame shifted half the block size diagonally. It then averages the results of both so that there are less estimation errors. So MVFlowFPS2 is always going to provide better motion estimation than just MVFlowFPS. I would only use small block sizes like 4 if your source is less than 480 lines (like 320x240 640x360). If you're working with 720x480 or source, 8 is sufficient. Finally, doing some quick math off the top of my head, MVFlowFPS2 with the default (subdividing) search algo and 8x8 blocksize should run faster than MVFlowFPS with an exhaustive search and 4x4 blocksize. I shudder to think how long 4x4, exhaustive, FPS2 would take ;-) |
|
11th July 2006, 16:51 | #48 | Link | |
Huh?
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
|
Quote:
By the way, once I have the MVFlowFPS/2 and ChangeFPS encodes, is there a faster way to replace individual frames or frame ranges of the former with the corresponding ones from the latter than cutting and pasting (i.é: can I do it directly from Avisynth)?
__________________
Read Decomb's readmes and tutorials, the IVTC tutorial and the capture guide in order to learn about combing and how to deal with it. Last edited by Chainmax; 11th July 2006 at 17:00. |
|
11th July 2006, 18:30 | #50 | Link | |
Registered User
Join Date: Oct 2003
Posts: 209
|
Quote:
As for an AVISYNTH only solution, I would imagine you can use trim() but I've never done it... I would love to hear from the seasoned scriptwriters how something like this would be done. |
|
11th July 2006, 18:31 | #51 | Link | |
Registered User
Join Date: Oct 2003
Posts: 209
|
Quote:
|
|
12th July 2006, 21:37 | #52 | Link | |
Huh?
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
|
Quote:
I really wish MVTools could be altered so that a new MVFlowFPS parameter would be created. This new parameter would be linked to the artifacting (no idea how) and if in a given frame it exceeds or falls below a user-defined threshold then the frame in question would be replaced by an interpolation of the previous and next frame. How feasible would that be?
__________________
Read Decomb's readmes and tutorials, the IVTC tutorial and the capture guide in order to learn about combing and how to deal with it. |
|
13th July 2006, 11:25 | #53 | Link | |
Movie buff & shine
Join Date: Jan 2004
Location: Logan, the only hole above ground.
Posts: 257
|
Quote:
I might be wrong on that last point, so feel free to correct me if I am.
__________________
I'm a boxer who can Bob () & Weave (). I like to Overlay () punches and Blur () his vision to ShowFiveVersions (). My KO punch will always Pulldown ().TimeStretch () and all he will hear is Tone (). |
|
13th July 2006, 15:52 | #54 | Link |
Registered User
Join Date: Sep 2004
Location: Near LA, California, USA
Posts: 1,545
|
I wish there was a way to adaptively use multiple block sizes kinda like what X264 does.
__________________
Pirate: Now how would you like to die? Would you like to have your head chopped off or be burned at the stake? Curly: Burned at the stake! Moe: Why? Curly: A hot steak is always better than a cold chop. |
13th July 2006, 15:57 | #55 | Link |
Movie buff & shine
Join Date: Jan 2004
Location: Logan, the only hole above ground.
Posts: 257
|
Perhaps an algorithm could be written where it initially tests 16x16 blocks. If the amount of detail (determined by some algorithm that searches for texture) in a block exceeds one threshold, it reduces that block to 4 blocks of 8x8. If it exceeds a higher threshold, it could reduce it to 16 blocks of 4x4.
Would that be possible? Actually, should this go to the MVTools thread?
__________________
I'm a boxer who can Bob () & Weave (). I like to Overlay () punches and Blur () his vision to ShowFiveVersions (). My KO punch will always Pulldown ().TimeStretch () and all he will hear is Tone (). |
14th July 2006, 03:57 | #56 | Link | ||
Registered User
Join Date: Oct 2003
Posts: 209
|
Quote:
Yes, with the third option you can see a frame blend across 80 lines into the new image... but when you're watching on a television that scans top to bottom 60 times a second, 99% of the population won't notice it. It hurts horizontal panning/crawls, but little else. And remember, most people aren't going to be pausing to stare at a bad image that is 1/60th of a second long :-) Since my DVD is mastered specifically for television, the zone=80 method is what I'm using. In motion, it's less jerky than without zone=80. Freeze-framed, it has those "inbetween" frames. So you have to pick what you like best. Quote:
That being said, it might be possible to "fall through" to a ChangeFPS/ConvertFPS frame if the certainty of the mocomp vector analysis falls below a certain threshhold, but I have no idea how to script that. Scharfis might have already done something like that somewhere in mvbob() but I'm not brave enough to comment every line to find out. |
||
14th July 2006, 08:32 | #58 | Link |
Movie buff & shine
Join Date: Jan 2004
Location: Logan, the only hole above ground.
Posts: 257
|
Your welcome, Trixter... always glad to help where I can.
But do you reckon the possibility of variable block size analysis would be feasible for application? They do it for motion compensation in video compression... Would it work with MVFlowFPS?
__________________
I'm a boxer who can Bob () & Weave (). I like to Overlay () punches and Blur () his vision to ShowFiveVersions (). My KO punch will always Pulldown ().TimeStretch () and all he will hear is Tone (). |
14th July 2006, 09:49 | #59 | Link |
Angel of Night
Join Date: Nov 2004
Location: Tangled in the silks
Posts: 9,559
|
x264 has some of the most advanced ME algorithms available in the open source world, if they could be cut-and-pasted into mvtools I'm sure it would improve output (and cut speed), though it'd take quite a bit of work to port their interfaces. It's certainly possible. On the other hand, x264 gets to rely on texture bits to make up for any deficiencies, and it's designed for qpel (although it doesn't necessarily have to use it).
It'd certainly be a cool summer project by someone interested. |
14th July 2006, 09:51 | #60 | Link |
Movie buff & shine
Join Date: Jan 2004
Location: Logan, the only hole above ground.
Posts: 257
|
Should this recommendation be forwarded over to the MVTools thread?
__________________
I'm a boxer who can Bob () & Weave (). I like to Overlay () punches and Blur () his vision to ShowFiveVersions (). My KO punch will always Pulldown ().TimeStretch () and all he will hear is Tone (). |
|
|