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. |
23rd January 2021, 23:30 | #41 | Link | |||
Registered User
Join Date: Mar 2017
Location: Germany
Posts: 234
|
Quote:
Quote:
Quote:
|
|||
24th January 2021, 19:11 | #42 | Link |
Registered User
Join Date: Apr 2013
Posts: 346
|
Tried TDecimate(mode=2) and result is the same as mode=7.
The video has two sections: one section is clearly 1 dup in 5 and the other section is clearly 1 dup in 10. If I use Decimate(cycle=10,cycler=1), then about 90% of the video plays smoothly. If I use Decimate(cycle=5,cycler=1), then about 10% of the video plays smoothly. These two patterns repeat in varying segments throughout the video. I probably could find each transition point and apply the appropriate decimation, but the time commitment would be significant. As a hobbyist, I don't have the investment in various professional tools, such as you do for your studio work, so I'm pretty much limited to Avisynth. |
24th January 2021, 20:50 | #43 | Link |
Registered User
Join Date: Mar 2017
Location: Germany
Posts: 234
|
TDecimate(mode=2) requires no cycle, but a framerate. This could f. e. be something like 24.385. But you are of course right: If the pattern" changes that often, it's a waste of time.
As I said: Avisynth and the fabulous people here provide a motion-flow-framerateconverter that is sometimes even better than professional tools. |
25th January 2021, 03:03 | #44 | Link |
Registered User
Join Date: Apr 2013
Posts: 346
|
Yes, I'm afraid it is a waste of time chasing those two patterns around. fortunately, QTGMC, while not ideal, gives the smooth playback.
When you say: "motion-flow-framerateconverter", are you referring to some specific functions that haven't been raised here, or is this a generalization for some of the tools that have already been explored in this thread? I agree about the knowledge and creativity by so many members on this forum. I bring my problems here and generally get solutions that I never envisioned or expected. |
25th January 2021, 09:28 | #45 | Link |
Registered User
Join Date: May 2006
Posts: 3,997
|
It's about synthesizing of new frames from existing frames by motion interpolation in order to match a desired new constant frame rate.
There exist Avisynth filters for this purpose. See for example here: https://forum.doom9.org/showthread.php?t=174793 https://www.svp-team.com/wiki/Manual:SVPflow Last edited by Sharc; 25th January 2021 at 09:30. |
25th January 2021, 13:49 | #46 | Link |
Registered User
Join Date: Mar 2017
Location: Germany
Posts: 234
|
To make it clear: This was just my answer to your statement:
"As a hobbyist, I don't have the investment in various professional tools, such as you do for your studio work, so I'm pretty much limited to Avisynth." You will not need motion-flow-converting here at all. This was just meant for hybrid sources that were mentioned before, and there only for the portions in native 29.97fps. |
27th January 2021, 14:58 | #47 | Link | ||
Registered User
Join Date: Apr 2013
Posts: 346
|
Quote:
Using cycle=10 (it affects more of the video than cycle=5), the play was nearly identical to QTGMC. So much so, that I've decided to employ InterFrame (supposedly better than FrameRateConverter) so that I can eliminate the moire effect, which cannot be done when QTGMC is used. So, I can now handle these mixtures of odd duplicates, eliminate the moire effect, extend/correct the playing time, establish a more conforming fps (23.976), and sync the audio because of all the help in this thread by so many of you. For those interested in seeing the full script: Quote:
Last edited by Danette; 27th January 2021 at 15:21. |
||
28th January 2021, 06:32 | #50 | Link |
Registered User
Join Date: Feb 2002
Location: California
Posts: 2,691
|
Just so the OP understands, both FrameRateConverter and InterFrame use the code and/or the algorithms from MVTools2. FrameRateConverter attempts to reduce artifacts via masking. InterFrame doesn't really add anything to the quality of the motion estimation and instead was created to provide real-time, GPU-assisted motion estimation so you can change 24p to 60p and get the "soap opera effect" while watching movies, without having to encode offline. InterFrame was optimized for that one task and is quite limited and doesn't attempt to do all the other things that you can do with MVTools2 (like noise reduction).
So, while I certainly agree that the quality produced by FrameRateConverter is better than Interframe, I am not at all certain that it produces better quality than simply using MVTools2 itself. I participated quite a bit in the thread which led to the development of FrameRateConverter, and much of my work with MVTools2 was used as a sort of benchmark against which FrameRateConverter was measured. It definitely did produce good results in some cases, but also failed to produce any improvement in others, and occasionally produced worse output. So, bottom line, I don't know if you'll see much improvement by changing, but by all means, if you have the time, try it out. |
28th January 2021, 23:09 | #51 | Link |
Registered User
Join Date: Apr 2013
Posts: 346
|
I did try it and cannot detect a difference, but I do accept that FrameRateConverter is the better approach, so I'll use that on those difficult videos that also exhibit moire-effect problems. If there is no moire-effect issue on these difficult videos, I'll use QTGMC, which does give slightly better smoothness of play.
Last edited by Danette; 28th January 2021 at 23:11. |
Thread Tools | Search this Thread |
Display Modes | |
|
|