It is possible, but I am not sure what more you would want. In the Convert to Edit Friendly dialog, the Deinterlace option applies the FFmpeg bwdif filter with frame doubling - which is the highest qualify deinterlace filter that is available in the open source community.
Also, OP is asking about the Deinterlacer option in the advanced export panel - which has 4 options. So your comment/question might be off topic.
Answer to the second question:
Video mode is custom:
Width=720
height=576
sample_aspect_num=16
sample_aspect_den=15
display_aspect_num=4
display_aspect_den=3
progressive=0
colorspace=601
frame_rate_num=25000000
frame_rate_den=1000000
Answer to the first question:
Both.
I am curious why you made it custom. Those parameters perfectly match the existing profile for “SD PAL”.
But the output for that profile should be signaled as interlaced if the codec you choose to export supports interlaced…
That is interesting.
What is the Convert To Edit Friendly menu, where can I find it?
Is that meant:
Which option applies the FFmpeg bwdif filter ?
Click on a clip, click on Prperties, at the bottom is the Convert tab. See below for an explanation:
I tested that. Same problems with interlaced output. Video is jerky or shaky in moving scenes. No problems with progressive output.
If I convert the clip with the deinterlace option (Convert to Edit-friendly), I have the same glitches in the resulting progressive mp4 file. What’s wrong with interlaced?
What exactly means “If the source is progressive, each interlaced field will be converted to a progressive frame resulting in double frame rate”?
Do progressive sources have interlaced fields?
I converted the clip with deinterlace and double frame rate (50 fps). Something is wrong with the conversion. Flicker when moving. But if I only select every second frame (selectevery(2, 0) it’s OK.
I do not reproduce this. I am not sure we have determined that interlaced sources are the problem. Maybe there is a different atribute of your clips that cause the glitches. Can you provide screenshots of the glitches?
It is a form of field extension deinterlacing:
No. And that is why the conversion is necessary when going from interlaced to progressive.
What does this mean? How are you selecting frames?
I would understand:
If the source is interlaced, each interlaced field will be converted to a progressive frame resulting in double frame rate.
Or:
If the output format is progressive, each interlaced field will be converted to a progressive frame resulting in double frame rate.
Why should I convert progressive to progressive?
With Avisynth+.
You can’t see it in individual frames, only in a running video. The individual frames are OK, just not the juxtaposition. So it must have something to do with the fields and their compilation / connection / linking. Either wrong order or horizontal line offset (one line).
You discovered a typo in the tool tip. It should say “If the source is interlaced, each interlaced field will be converted to a progressive frame resulting in double frame rate”
I will fix that for the next release.
I do not really know why your clips are not encoding cleanly. I tried my own test using a popular interlaced test clip.
When I export it from Shotcut, the motion is smooth.
Also, I did this experiment with success:
Can you try that experiment with the test clip I linked and then again with your own test clip (except I think your clip is 25fps, so the resulting file would be 50fps)?
I tested that.
With the fireball clip there are probably no problems. But there is no camera movement or zoom involved here. And it’s NTSC.
I still have the same problems with my videos (see video link).
And I also have this kind of effects when I simply export interlaced.
What is wrong?
I do not know. The interlaced clips that I have are working. Maybe the field phase is signaled incorrectly in your clips. If you want to send me a PM with a link to one of your clips, I am willing to take a look at it.
This is the same clip deinterlaced with a different tool, doubling the framerate from 25 fps to 50 fps. You see, here the result is correct. Something is wrong with the Shotcut function in the Convert to Edit Friendly dialog or FFmpeg bwdif filter with frame doubling. Shotcut has problems with interlaced material, but works well with progressive material. These are my findings.
Here is mine example showing Convert with Deinterlace works fine if you give it a clip with correct metadata about the field order. Brian suggested a possible problem with “field phase.” I know this better as “field order,” which is how it appears in Shotcut Properties. This is from a PAL DV clip.
I sent you the original avi file, YUV 4:2:2 as for UYVY but with different component ordering within the u_int32 macropixel, interlaced, top field first.
It looks like the file doesn’t contain any information about interlacing and frame order. You may have to set this in the importing tool.
This is what I did in Shotcut:
Sorry, now I got a better result. Maybe I didn’t pull the slider to “am besten” during my first attempts. But now I could only create an mkv, not an mp4 (why?).
