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 May 2020, 02:46 | #401 | Link |
Registered User
Join Date: May 2020
Location: Canada
Posts: 49
|
I've scrubbed through about 18 episodes in the first season creating TFM override files for each, and while that does happen, it is very rare. When it does happen it's usually the first frame of the next scene that is problematic, and QTGMC handles it pretty well. The effect isn't even noticeable upon playback.
|
23rd May 2020, 09:35 | #404 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,829
|
Quote:
What did I write? I edited that post quite a few times to change and add things. Edit: I've looked through the edits (I forgot you could do that) but I still can't see what you're referring to. Last edited by hello_hello; 23rd May 2020 at 10:35. |
|
23rd May 2020, 09:48 | #405 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,829
|
Quote:
DeintClip = Tweak(Bright=200) TFM(Clip2=DeintClip) Most of the screenshots just show it taking specific pixels, but one of them shows it's replacing the whole frame, somewhat inexplicably to my eye, but the screenshot immediately below that one shows that with slightly different settings, it's only taking specific pixels. I think it may relate to setting the MI argument too low, although I haven't tested that, but the screenshots show it must be replacing just the combed pixels, and probably a small area around them, most of the time. |
|
23rd May 2020, 11:27 | #406 | Link |
Registered User
Join Date: Mar 2011
Posts: 4,829
|
It means that normally for telecined content you can step through it and see a pattern of three clean frames and two combed frames repeating, but during the fades from one shot to the next, they've been overlaid without ensuring the pattern isn't interrupted. They're both still telecined with a pattern of 3 clean and 2 combed frames, but the clean and combed frames don't line up for each shot during the fades.
This is the sort of fade I'm referring to. I've made it brighter so it's easier to see. For the first screenshot, the shot that's fading in doesn't show telecine combing while the shot that's fading out does. A few frames later on it's the opposite. Keep in mind though, DVDs were originally intended to be displayed on an interlaced display (CRT), so this sort of thing would display perfectly fine. For a progressive display, and when converting to progressive for encoding, it's a problem. If you simply keep decimating one in five frames for 23.976, one of the shots will probably have "jerky" movement during the fades. One solution is to de-interlace those sections to remove the combing, and to keep them at 29.97fps. That way they'll look smooth, but the end result would be little sections of 29.97fps progressive amongst the 23.976 detelecined progressive frames, and you have to decide how to deal with it. A player performing detelecine and deinterlacing on the DVD would probably treat those fades as video (29.97fps) and de-interlace them, effectively outputting a variable frame rate, which would look quite smooth. Last edited by hello_hello; 23rd May 2020 at 11:43. |
23rd May 2020, 15:24 | #407 | Link | |
Registered User
Join Date: Dec 2002
Location: Region 0
Posts: 1,436
|
Quote:
|
|
23rd May 2020, 15:57 | #408 | Link |
brainless
Join Date: Mar 2003
Location: Germany
Posts: 3,653
|
@hello_hello:
from a theoretical standpoint it sould be perfectly possible to retrieve a non-jerky 24p decimation out of two 3:2 cadences blended together. For sure field matching will be broken. But the decimation of a 50:50 blend of two cadences should be (manually) possible.
__________________
Don't forget the 'c'! Don't PM me for technical support, please. |
23rd May 2020, 19:21 | #409 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,829
|
Quote:
There's been so much debate about how to handle this source that I've obviously became guilty of over-thinking it, so I went back to basics. It appears TFM can sail through all the broken cadences on it own, except one. TFM().TDecimate repeats a frame, and I couldn't convince it not to, so I removed it manually. As it's just the opening sequence, I waited until a fade to black to repeat a frame to make up for it. As it turns out, disabling MicMatching doesn't even make a difference for the opening sequence as I'd come to believe it would. It does however, help with the progressive section I tacked onto the end of the sample for testing, which by the way is the only thing preventing me from wanting to stick my head in a hole somewhere now, because the existence of at least one progressive 29.97fps section still supports an argument for VFR encoding. I'll upload a sample in a little while. There's still one section I'm not happy with at 23.976fps, so I'm working on it now. |
|
23rd May 2020, 23:51 | #410 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,829
|
Here's the new encode of the opening sequence.
Clip "A" does normal field matching for the majority of the CGI and all the film sections. Clip "B" is me being pedantic about making the movement of the stars smoother after the wormhole (behind the text). It's not smooth even if you bob it, so that's probably as good as it gets. The first lot of Trims combine the two clips, deleting one repeated frame during a transition in the CGI, and repeating a frame during a fade to black to compensate. The second lot of Trims are just used for optional filtering on the decimated video. I couldn't find a happy that allowed TFM to de-interlace the text as it fades in/out without unnecessarily de-interlacing half the picture, so I left it, as I think it's the lesser of two evils. Personally, I don't care about it that much. Whether it's encoded as VFR or 23.976, or 59.94, I'm now of the opinion fussing over making sure TFM caught all the combing was heading in the wrong direction. Based on the following test, TFM isn't de-interlacing a single pixel in the whole sample. At least none that I saw. DeintClip = Tweak(Bright=200) TFM(PP=5, MicMatching=0, Clip2=DeintClip) Quote:
Last edited by hello_hello; 24th May 2020 at 10:42. |
|
24th May 2020, 00:05 | #411 | Link | |
Registered User
Join Date: Jan 2015
Posts: 1,056
|
I just realized that, since Joel is putting a GUIDE together and not distributing full video files, there's room for several different AVIsynth scripts and several different target frame rates, with notes on why people might want to select - or not select - each one.
I'd also love to see some examples of what happens when an interlaced frame gets put through AI upscaling. Oh and I just noticed this article: Quote:
__________________
I ask unusual questions but always give proper thanks to those who give correct and useful answers. Last edited by Katie Boundary; 24th May 2020 at 00:54. |
|
24th May 2020, 03:49 | #412 | Link | |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
While I do agree with most of your post I take exception to this:
Quote:
All the things you care about yet you don't believe this is a problem? Humans cannot even see it?
__________________
madVR options explained |
|
24th May 2020, 04:02 | #413 | Link |
Registered User
Join Date: Jan 2015
Posts: 1,056
|
If you're on drugs that have significantly altered your perception of time in such a way that the world around you seems to be moving in slow motion, like Fry in that episode of Futurama where he drinks 100 cups of coffee in a single day, then you might notice it.
__________________
I ask unusual questions but always give proper thanks to those who give correct and useful answers. |
24th May 2020, 04:25 | #414 | Link |
Registered User
Join Date: May 2020
Posts: 77
|
Per request, here are clips of specific scenes from Sacrifice of Angels from a VOB of the DVD. Clip explanations below. Clips are cut to 10 seconds or less per Manono's advice, unless it made no sense to split the scene at that point. Contiguous versions of two longer scenes (FFE = First Fleet Engagement, SFE = Second Fleet Engagement) are available below. I tried to start each clip with a few frames of padding on each side.
In most of the clips below, there are specific places I'm hoping to achieve better antialiasing results. I used QTGMC partly because it fixed some of the problems I'm going to describe below and would like to duplicate this (or improve upon the initial repair). I'm going to describe some specific problem spots I saw in the 23.976 version of this footage because it's all I have for reference and because I was attempting to repair very specific things in certain cases. Apparently, I cannot offer a direct download link via SendSpace unless I have a premium account. A link to 13 of the 14 uploaded clips is here: https://fs01u.sendspace.com/upload?S...TINATION_DIR=5 You do not need to download "FirstFleeetEngagement-Complete" if you download "FirstFleetEngagement-Short1" through "Short3." The complete version of "SecondFleetEngagement" is only available on OneDrive below due to size restrictions. Files are abbreviated as "FFE" and "SFE" on OneDrive after I realized the file names were too long for easy display. The 14th file is "SFE-Complete" and it does contain a few scenes on the Defiant that are not embedded in SFE-1 -- SFE-5. Alternately, if you want individual file downloads, you can use the OneDrive links below: A link to the entire directory is here. https://1drv.ms/u/s!AphTLFRW13WMjk7i...dRO9I?e=3NcPQ3 Individual file links in-line below. Each individual file link will open a OneDrive link. OneDrive does *not* require you to have a login, and you can download by hitting the button in the upper-left-hand corner. FirstDefiantFlyby: https://1drv.ms/v/s!AphTLFRW13WMjlmk...A7rPM?e=UFmhtT There's aliasing on both the Excelsior-class ships (inside the nacelles) and the Defiant's angle of attack in this scene is hard to fix. QTGMC against 23.976 fps did a very good job of resolving a troublesome flicker on the Defiant's left "shoulder" that gave me a lot of trouble, but I never had a great solution to the in-nacelle aliasing. Would like to nuke that from orbit. FirstDominionFleet: https://1drv.ms/v/s!AphTLFRW13WMjlKd...fALn3?e=RgO5tL At the end of this clip there are three Jem'Hadar scarab fighters visible. All three have strong horizontal aliasing across their bottoms. I'd like to eliminate it as part of properly processing the scene. QTGMC using my repair script against a 23.976 MKV does a very good job of eliminating the horizontal lines. SecondDefiantFlyby: https://1drv.ms/v/s!AphTLFRW13WMjleX...0nKcK?e=mzSZ13 This is one where I've had trouble with some scripts causing backwards movement in the small fighters that fly across the screen. The background ships are basically fine no matter what you run against them. First Fleet Engagement (FFE) 1-3 https://1drv.ms/v/s!AphTLFRW13WMjlTG...HFrqU?e=mDKlE4 https://1drv.ms/v/s!AphTLFRW13WMjlHg...l2aGB?e=dfREGR https://1drv.ms/v/s!AphTLFRW13WMjlYt...lENGV?e=yWZGR5 This scene hasn't been problematic, per se, but it's definitely one of the major CGI battle scenes of the episode, so it's included for those reasons. If you want to download the entire contiguous clip, you can do so here (100MB file). https://1drv.ms/v/s!AphTLFRW13WMjlpF...psSD_?e=gmrWr5 Second Fleet Engagement (SFE) 1- 5 https://1drv.ms/v/s!AphTLFRW13WMjljS...ek-we?e=nswJKR https://1drv.ms/v/s!AphTLFRW13WMjlWM...I3x6M?e=DjUO8I https://1drv.ms/v/s!AphTLFRW13WMjlMe...v6E3y?e=mhfNsh https://1drv.ms/v/s!AphTLFRW13WMjlA2...H_ocz?e=YWsefX https://1drv.ms/v/s!AphTLFRW13WMjk8D...98s-w?e=3ehQve The second full fleet engagement. Major things I'm hoping to fix include nacelle-aliasing and the very aliased lines across the bottom of the Miranda-class vessel's ventral saucer. (SFE-1). The other scenes of SFE have been pretty solid, but are included here for completeness' sake. The SFE clips 1-5 omit the Defiant scenes that take place in-between the CGI shots. The full file, available here: SendSpace is limited to 300MB, so if you want the full file, OneDrive is the only place to go. https://1drv.ms/v/s!AphTLFRW13WMjlvP...w7gN7?e=qOAQeq Includes the Defiant interim scenes as well as the CGI scenes. Trivia: According to the VFX team that built the show, this was the most-detailed fleet battle they ever shot. They brought in tactical experts specifically to help them design the fight. SFE is the arguable high-water mark for DS9's entire seven-year run, so if there was one CGI scene to absolutely nail, this one would be it. Sisko-On-Defiant Finally, I've uploaded a clip that I thought might be useful for seeing how DS9 mixes and matches VFR content together. All frame rate references measured using MPC-HC. The frame rate when the DVD is played back begins at 29.97 fps, but starts dropping immediately. By the time the shot switches to Defiant, the frame rate is 23.976 fps again -- but it starts increasing back to 29.97 fps when the Ferengi Nog appears on-screen. The clip stays at 29.97 (at least, MPC-HC reports 29.97 for several minutes thereafter). https://1drv.ms/v/s!AphTLFRW13WMjl_b...TrpuU?e=5ETmw2 I have thought that this could be somehow related to the credits, but there's a later shot on DS9 itself that stays at 29.97 fps well after the credits are finished. I can clip that as well if people want to see it, but this seemed good for now. Last edited by JoelHruska; 24th May 2020 at 05:38. |
24th May 2020, 04:53 | #415 | Link |
Registered User
Join Date: Jan 2015
Posts: 1,056
|
The solution you your aliasing problems is to use a script that reconstructs the original progressive frames and then leaves them the goddamn hell alone.
BTW, I think you say "antialiasing" a lot when you mean "aliasing". Aliasing is bad. Antialiasing is good
__________________
I ask unusual questions but always give proper thanks to those who give correct and useful answers. Last edited by Katie Boundary; 24th May 2020 at 04:58. |
24th May 2020, 05:46 | #417 | Link | |
Registered User
Join Date: May 2020
Posts: 77
|
Quote:
|
|
24th May 2020, 06:15 | #418 | Link |
Registered User
Join Date: Jan 2015
Posts: 1,056
|
Kay, looks good
I've been running more tests and while I still think that both the interpolation and blend variations of my script gives better results than QTGMC in the vast majority of frames, there are still a few interlaced frames where even a straight blending script with no interlacing-detection (treats all frames and pixels as interlaced), no resharpening, and no other fancy stuff... Code:
A=Tfm(field=1,mode=0,slow=2,pp=2,mchroma=false,cthresh=-1,micmatching=0) B=Tfm(field=0,mode=0,slow=2,pp=2,mchroma=false,cthresh=-1,micmatching=0) interleave(A,B) ...whereas QTGMC does: Although this doesn't justify switching over to straight QTGMC, it does make me think that the best script for DS9 specifically might be a variation of my method that incorporates QTGMC. And because "lossless" QTGMC preserves the aberrant field order of the title at the beginning of the opening credits, but "normal" QTGMC smooths it out, this hybrid method would need to incorporate the "lossy" version of QTGMC. So, when you get a chance, try... Code:
A=qtgmc().selecteven() B=qtgmc().selectodd() C=Tfm(field=1,mode=0,slow=2,mchroma=false,cthresh=-1,clip2=A,d2v="601.d2v",flags=1,micmatching=0) D=Tfm(field=0,mode=0,slow=2,mchroma=false,cthresh=-1,clip2=B,d2v="601.d2v",flags=1,micmatching=0) interleave(C,D) "looking like unmitigated shit" is another good one.
__________________
I ask unusual questions but always give proper thanks to those who give correct and useful answers. |
24th May 2020, 09:42 | #419 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,829
|
Quote:
I gather it's lossless but it's encoded as progressive rather than interlaced, I don't know if that makes a difference when it's lossless, in respect to the chroma being upsampled properly. Not to worry though... I only gave two of them a spin. Pure telecine as far as I can see. You probably should take Katie's advice and use a method that reconstructs the original progressive frames and then leaves them the hell alone. Or are you too far down the rabbit hole with the 59.94fps idea? The only reason I went the VFR route is because someone linked to a sample of 29.97fps progressive CGI, and that's the way I'd deal with mixed content, but if it's all telecined except for the odd episode, you can handle those differently when you find them. I gave the CGI the QTGMC treatment, and the film section the MCDegrainSharp treatment, but that was after the frames were reconstructed. If you come across a problem in an episode, cross that bridge when it happens. zapp7 seem to be happy with detelecining most of it. I linked to a CFR sample of the opening CGI section earlier. If it's the biggest problem in most episodes, you'll probably get efficient at creating scripts that'll handle it correctly if you want it to be perfect (the latest encode looks good to me at 23.976fps), but the remainder of each episode might mostly require nothing other than field matching and decimation. samples.zip Edit: I forgot to resize the SFE-1 encode, it's just cropped. Katie, If the script you posted is any indication, you're fussing about combing while using the wrong field order for TFM again. At least for the sample you took the screenshots from. Last edited by hello_hello; 24th May 2020 at 09:57. |
|
24th May 2020, 10:18 | #420 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,829
|
Damn, I just noticed an oddity in the film section towards the end of the Sisko-on-Defiant sample. It's possibly a field order thing that wouldn't have happened working with the original video, but here's the fixed version.
Sisko-on-Defiant take 2.mkv Quote:
|
|
Thread Tools | Search this Thread |
Display Modes | |
|
|