sacherjj wrote:Yes you can but it decimates every other frame, 60i becomes 30p not 60p.
To do a quality deinterlacing I would strongly recommend to use a tool that does motion compensation based deinterlacing and that does not decimate every other frame.
You are correct the DR deinterlace is not really an option.
If I have to do it outside, then Avisynth is by far the best way.
A typical 25i PAL Avisynth script, that I would use would be something like:
Process before editing:
Clip=("D:\Input clip.mp4")
V1=LWLibavVideoSource(Clip)
A1=LWLibavAudioSource(Clip)
V2=V1.tdeint(mode=1)
AudioDub(V2,A1)
AssumeFPS(50)
Process after editing:
Clip=("D:\ Output clip.mp4")
V1=LWLibavVideoSource(Clip)
A1=LWLibavAudioSource(Clip)
AudioDub(V1,A1)
AssumeFrameBased()
SeparateFields()
SelectEvery(4,0,3)
Weave()
AssumeTFF()
AssumeFPS(25)
What a time consuming process that really only achieves the intended and technically correct output for TV.
Without proper interlacing moving text looks terrible and is so much harder to read, therefore less effective This is especially the case at 25fps.
It makes DR certainly seems a poor excuse for an up-market editing program which is marketed for all production!!!
To think that the developers of DR have not considered the huge TV industry as being important.
I think that industry deserves a lot better consideration from the developers.
I know they have a lot on their plate at the moment but this should have been one of the first issues to be addressed a long time ago.
They certainly should drop the interlacing option altogether if they don't intend fixing it, that way the TV industry does not broadcast material that is half right.
You may wonder why I am so harsh, but I am over so much software being developed that has all the bells a whistles, but fails on the basics.