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. |
16th February 2011, 13:07 | #321 | Link |
Registered User
Join Date: Apr 2002
Location: Germany
Posts: 5,391
|
Regarding "what interlacing types can be processed" and "can I use for it IVTC" ...
What needs to be understood is: the consequences of the temporal blur used before the motionsearch. This temporal blur is ... a) ... ultimately necessary, it's THE key feature. Without it, Q/TGMC would not be what it is. b) ... only well suited for "true" interlaced input, where each field represents a unique point in time. This is NOT the case for progressive input, nor for telecined input, nor for fieldblended input. The problem with input that isn't of the "true" interlacing type is that the distribution of "temporal motion states" is not evenly distributed. In effect, the preprocessed searchclip will exhibit a certain kind of left-right-"wobble", which in turn will fool the motionsearch. (And if the motionsearch is bad, then everything is bad.) Summed up: The method generally is made up only for "true" or "video-type" interlacing. With all other interlacing types, there be dragons. It might work out, or it might fail. Clinic example: a grey square (with some letters & a vertical line) moving at constant speed. Only in the case of "true" interlacing all frames look "the same". With the other types, the frames are changing their shape in a way that MVTools can not reasonably deal with. (For clarity, this example is without the "rep0" feature. Using rep0 will lessen the problem to some extend, but it will not eliminate it.)
__________________
- We´re at the beginning of the end of mankind´s childhood - My little flickr gallery. (Yes indeed, I do have hobbies other than digital video!) Last edited by Didée; 16th February 2011 at 13:11. |
16th February 2011, 16:49 | #322 | Link |
Registered User
Join Date: Sep 2006
Posts: 55
|
Ok, well 3.10 did succeed in holding things together and I managed to get a full crf 20 encode with SM=2, Sh=.3 settings. Then I looked and thought, boy, these are awfully sharp, rather...noisy sharp in fact. Then I go on-line and read about version 3.11. Grrr. Vit, ever heard of Murphy's law in Russia?
So back to square A. Maybe not in vain, as I had a few surprises. http://rapidshare.com/files/44826318...us_fingers.avi http://rapidshare.com/files/44826318...us_plastic.avi http://rapidshare.com/files/44826318...sing_frame.avi Clips A & B are still captures that as you'll see are bit quite a bit more animated than your average noise. In a way kind of comical. Clip C missing frame syndrome (er I should have named it 'extra frame' is found in 3 places in the video). In fact, I say 'missing' because in a frame-by-frame search in Premiere, Pinnacle Studio and Virtualdub it simply cannot be found. Only Avidemux spotted it and of course when I chopped them out and direct stream saved the file they came right back (the ol' keyframe limitation). Also, neither my interlaced dvd copy nor an earlier 25p encode manifest it either. It's a purely full-rate 50p issue. I mean in three weeks of editing never saw it. As the French say, a true 'piege a con'. That said, all three had one trait in common, the sequences had been pre-rendered in reverse motion. Any thoughts or workaround? Another 12 hour encode for three lousy frames seem a bit much. So before discovering your 'bug' I'd thought to do a follow-up 25p encode with the default sharpness=0.20 to correct my supposed error, but I'm not sure now. Is there that much of a difference .3 vs .2 or would your goof be the over-riding factor for that hardened image I got? Is DirectShowSource really such a drag? In the past with mpeg4-asp I alternated with avisource indifferently. No probs. Only here virtualdub wouldn't let me open as such, even if I believe I've got the DVCPro DV decoder by Sony. HenryHo recommended Cenocida as a solution. Why not, though I can't see how that would effect such things as smearing. Oh well, onwards. |
16th February 2011, 18:12 | #323 | Link |
Registered User
Join Date: Jul 2010
Posts: 448
|
Yup, QTGMC likes "real" predictable motion with true interlacing. I never work with anime or unpleasant hybrid sources (I looked at YATTA once... I had to go lie down) so QTGMC is never tested on such material. I occasionally work with game footage - the same issues can apply where the motion is jumpy or artificial. Source match will not help in these cases, it will probably make things worse as it does double or triple the temporal work
As an adjunct to Didee's comments though - progressive input will work in QTGMC if you use the InputType setting. The problem Didee illustrated is what happens if you don't set InputType and treat progressive material as though it were interlaced - the algorithm will (inappropriately) try to separate fields and interpolate the result. With InputType=1, those steps are skipped, leaving a correct result more like the interlaced case. With InputType=2,3 the source is reweaved into a true interlaced stream, also correct for TGMC processing (loses half the "fields" in the process though). However, despite these adjustments it's only appropriate to use progressive QTGMC if you're trying to remove some kind of shimmering post-deinterlacing artefacts. Q/TGMC is designed to interpolate and remove bob-shimmer. Progressive doesn't need interpolation, so if you don't have bob-like-shimmer then there's no reason left to use QTGMC - likely you just want a temporal smooth of some kind. ____ sadie: The bug in v3.05 and v3.10 created a noisier, sharper result, probably greater than the difference between 0.2 and 0.3 sharpness. The bug was worse if TR2 was higher (=slower presets). Regarding source filters, I know no of no rationale for when they decide not to work, nor any workaround other than try every possible filter. Or pre-render to lossless in any package that can successfully deal with the vid. Rendering via lossless would have helped you - it's then easy (if rather manual) to reprocess the few problem section, splice the result in another script then encode to x264. |
16th February 2011, 19:08 | #324 | Link |
Registered User
Join Date: Sep 2006
Posts: 55
|
Yeah, I gotcha. Finally, to do this stuff with this level of sophistication I'm really going to have to get out of the mindset that pre-processing and encoding are a one-stop all inclusive operation. They really should be treated as two entirely separate stages in the workflow.
|
17th February 2011, 21:50 | #326 | Link |
Registered User
Join Date: Feb 2009
Location: USA
Posts: 676
|
Is specifying progressive input appropriate enough to get the smoothing/resharpening effects without getting other funky artifacts on IVTC'd material?
I suppose that what I should have asked earlier back when I jumped into this thread. It is really helpful on sources that are slightly blurry, and also have some aliasing present. I haven't really been able to duplicate the result I get from QTGMC with other traditional sharpening filters. |
18th February 2011, 05:31 | #328 | Link |
Registered User
Join Date: Jul 2010
Posts: 448
|
Yes, you can use QTGMC to deinterlace 1080i to a 1080p MKV. As it can be a demanding script you're recommended to use a more modest preset depending on the power of your system (it will still look good at HD). Using multi-threaded Avisynth will help the speed (see the OP for instructions), but you should start low with the number of threads
|
18th February 2011, 07:04 | #329 | Link |
Registered User
Join Date: May 2010
Posts: 123
|
I'm using QTGMC to deinterlace 2 videos, one is MPEG-TS and the other is H264-TS then joining them into one. But when the encoding goes for about 6% I keep getting a disturbing crash along with an error, which tells "x264.exe has stopped working...fault module name: avisynth.dll"
What can I do to get rid of it? Thanks. |
18th February 2011, 11:05 | #330 | Link | ||
Registered User
Join Date: Jan 2011
Posts: 16
|
Quote:
I don't understand the best script setting for deinterlace 1080i to 1080p. Maybe... Quote:
Which GUI can i use? I tried MEGUI but give me error at line 2 ( QTGMC( Preset="Slow", Sourc....) All needed DLLs are downloaded and stored in AVISYNTH folder. Thanks in advance for Help. |
||
18th February 2011, 12:21 | #331 | Link | |
Registered User
Join Date: Dec 2007
Location: Germany
Posts: 632
|
Quote:
Put them into the /AviSynth/plugins folder. Also, you can gain a lot of speed if you switch to a multithreaded AviSynth and add SetMTmode right before QTGMC. |
|
18th February 2011, 12:42 | #332 | Link | |
Registered User
Join Date: Jan 2011
Posts: 16
|
Yes,pardon I mean Avisynt/plugin folder.
Do U mean like this? Quote:
I read the instructions carefully but I think I need an AVS script sample to better understand conversion from 1080i 29,970 fps to 1080p fps 23,976 and allow the same resolution and video bitrate. TS file is "true interlaced" not Telecined. Tk's |
|
18th February 2011, 16:03 | #333 | Link |
Registered User
Join Date: Jul 2010
Posts: 448
|
There is info on basic usage and multi-threaded usage near the top of the first post of this thread and near the top of the script itself. There are example scripts in there. Please read that information first. If you still don't understand then you need to learn about AviSynth.
I would advise against source-match/lossless on 1080i material. It will make a difference, but a very small difference at that resolution. In any case, on your system the encoding speed will be very slow with those settings. You need a top end system and a lot of MT encoding experience to do that. I suggest you start with Preset="Fast", EdiThreads=1 and work up from there. You can do a test encode by adding a trim on the end of your script (e.g. "trim(0,999)" for 1000 frames). I would recommend MeGUI instead of VirtualDub, it seems to cope better with the most demanding scripts. If you have the disk space, then a good approach is to check the "Add pre-rendering job" button, which will do the QTGMC to a lossless avi first, then x264/mkv the result in a second pass. You will need at least 200Gb for an hour of 1080p footage though. If you have to do the QTGMC and encoding in one pass then you may need to reduce the number of threads. QTGMC will give you a 59.94fps output by default. If you add "SelectEven()" at the end of your script you will get 29.97fps. There are methods to convert to 24p but (a) I never do that so I'm not going to advise and (b) you need to have a good reason to do it because the results might not be so good. ____ dragon_warrior: Sounds like the usual avisynth-doesn't-like-mt crash to me. Try adding a SetMemoryMax (see the multithreading section in the first post). Try different versions of MT avisynth (linked on the AviSynth wiki). Make sure your plugins are up to date. Reduce the number of threads or preset. Set EdiThreads to 1. Try a different machine. Last edited by -Vit-; 18th February 2011 at 16:11. |
18th February 2011, 16:17 | #334 | Link | |
Registered User
Join Date: May 2010
Posts: 123
|
Quote:
Anyway, my choice for TS is ffms. I'm also encoding 1080i materials to 720p. Unfortunately, TS container is not really friendly with ffms so you need to remux your TS to MKV before putting it into your script. Last but not least, don't forget to state the fps, which is "fpsnum=30000, fpsden=1001" (30000/1001 ~ 29.97) Hope this help |
|
19th February 2011, 00:48 | #335 | Link | |||
Registered User
Join Date: Jan 2011
Posts: 16
|
Tk's Vit.
Quote:
It's not a real problem except for some things. One of these, for example, can't add SRT Forced track. I know I can use PGS or m2ts+srt m2ts's same name but i like x264,Mkv and SRT . I find them are more flexibles for my project. Quote:
About FFMS U mean like this? Quote:
Last edited by fusebyte; 19th February 2011 at 04:09. |
|||
19th February 2011, 06:52 | #336 | Link | |||
Registered User
Join Date: May 2010
Posts: 123
|
Quote:
Quote:
Quote:
Otherwise, if your source is telecined, then IVTC is the right option. It's to remove 1 frame every 5 frames. Let's do a little calculation, 29.97 - 29.97*1/5 = 23.976, and that's the FPS you get after IVTC'd. Do analyse your source properly before deciding what to use ------------- @-Vit-: It seems ffms 2.15 mt is the cause, I try switching back to the former version and surprisongly it works for me. Thanks Last edited by dragon_warrior; 19th February 2011 at 07:02. |
|||
19th February 2011, 12:37 | #337 | Link | ||
Registered User
Join Date: Jan 2011
Posts: 16
|
Quote:
Why video remuxed with MkvMerge or another GUI plays so bad? It's very very slowed.I can't touch video track anyway after DSMUX coonversion, if I do it,video will always have playback problem. If I could work on the file after being processed by DSMUX not have more problems. Do U know a solution? Quote:
Can read if prog. or Interl.,say me if YUV 4.2.0 or other, as U know. But I ask U about interlaced file best way to analize right frame sequence, if 3:2 or i.e. ibrid 2i-4p-3i-4p or other sequence and how set output parameters. (i.e = if 3:2 telecined remove pulldown using telecide, if "true interlaced" only change container, if some sequence ibrid like example ??? ) thanks in advance. Last edited by fusebyte; 19th February 2011 at 14:51. |
||
19th February 2011, 12:56 | #338 | Link | |
Registered User
Join Date: Apr 2009
Posts: 478
|
Quote:
|
|
19th February 2011, 13:43 | #339 | Link |
Registered User
Join Date: Apr 2002
Location: Germany
Posts: 5,391
|
MediaInfo is accurate. As is DGIndex. Such Tools report how the stream was encoded, not what the actual content is like. It is quite common that progressive content is encoded in interlaced mode.
__________________
- We´re at the beginning of the end of mankind´s childhood - My little flickr gallery. (Yes indeed, I do have hobbies other than digital video!) |
Thread Tools | Search this Thread |
Display Modes | |
|
|