DirectShow video decoders are not required to support frame-accurate seeking; thus DirectShowSource itself is obsolete and depracated for most modern formats such as .ts, m2ts, mp4, other AVC encodings, etc.
If one insists on using DirectShowSource, the script shown is a verbose way of doing it. From this posted script:
Code:
clip=DirectShowSource("Test.m2ts")
clip=AssumeTFF(clip)
return clip
you would get exactly the same results from the following:
Code:
DirectShowSource("Test.m2ts")
AssumeTFF()
Quote:
"the resulting AVI was NOT interlaced: each frame consisted of 2 identical fields combining both of the original interlaced fields."
|
I find that difficult to believe. Not even DirectShowSource will commit
that many errors! msgohan's reply made a very interesting observation in that respect. But we have no sample of the original.
A more accurate and modern way to open .ts files would be to make a .dga index with DGAVCDec and open the file with a more precise, dedicated filter:
Code:
AVCSource("Test.dga")
Or even better, use the FFMS2 plugin package, such as the following for getting a video-only AVI:
Code:
FFVideoSource("Test.m2ts")
AssumeTFF()
or FFmpegSource2 for automatically combining video+audio:
Code:
FFmpegSource2("Test.m2ts")
AssumeTFF()
There is also the LSMASH package:
Code:
### ---for video-only---###
LSMASHVideoSource("Test.m2ts")
AssumeTFF()
Code:
### ---for video+audio---###
aud=LSMASHAudioSource("Test.m2ts")
vid=LSMASHVideoSource("Test.m2ts")
AudioDub(vid,aud)
AssumeTFF()
return last
Meanwhile I have to confess that I'm not enamored of the way Adobe deinterlaces, resizes, or re-interlaces and encodes. The resized videos show chroma displacement errors on downsampling, which most Avisynth resizers and methods avoid. HD-to-SD downscaling usually requires some sort of low-pass filter to avoid aliasing and line twitter, but Adobe users don't seem to employ that kind of prep work. Obviously video must be deinterlaced before resizing, but Adobe isn't the best tool for that, either. There is a better deinterlacer for this sort of thing but Adobe can't use it. The samples show noisy gradients and block noise, chroma flicker, and illegal chroma overshoot that could be avoided.
Other than advising that most members here wouldn't suggest Premiere as the best tool for this project (but of course you can use it if you want), I'm afraid nothing more can be said without a short sample of the unprocessed 1080i original, which was not posted. The "results' samples are appreciated but they can't be corrected. Surely Adobe can smart-render a short edit from the original for posting, or at least make cuts on I-frames to prevent re-encoding of the original m2ts.