@jak.willis @johnebaker

Thanks both. I learned a bit about MEP's deinterlacing too. Not that I understand why those settings eg Interpolate intermediate images work! 🙂 . The written description/explanation of each setting certainly doesn't help.

QTGMC is a process for deinterlacing video and is arguably the best process in the business. Unfortunately though, it is an absolute nightmare to set up as it is made up of many different programs that sort of meld together somehow. If you're sitting down and unstressed, have a read though this. The guide I used to set it up is here. It's part of the AVISynth, an incredibly powerful video manipulation/editing world where results can be absolutely stunning if you know what you are doing. To me, it's all black magic and I just use examples that others have posted or suggested. Additionally, it is very resource-intensive and for Jak's video, my system was encoding at 10% video speed (not that I have a "normal" system any more).

Unfortunately, the deinterlacing of MPEG 2 with QTGMC is complicated further by the need to separate the audio and video, deinterlace the video, then put them back together again.

If I haven't scared you off, there is a program called Hybrid which has largely automated the QTGMC process but won't produce an MPEG file, only a lossless AVI or MP4, with no real "editing". I sometimes use it to de-interlace a file, then export it as an AVI, then import that into MEP for actual editing. Hybrid has lots of options and is a bit daunting at first but is quite clever. The developer, Selur, is quite active on his Hybrid forum and will respond quickly.

After working on Jak's file, I was quite impressed with MEPs' quality compared to the QTGMC output; it's not as good, but pretty close. Video is one of those "it's all in the eye of the beholder" things and I think MEP does a good job for us "normal" users.

For the exercise, I also did an MEP export with everything "standard" ie SD movie settings, including 25fps. I didn't change any of the Video object properties ie left the interlacing settings "as is". The only change I made was export at 50fps instead of the standard 25fps. The result was as good as the others.

So the secret appears to be to export at 50fps if the motion is violent.

@jak.willis @johnebaker

Thanks both. I learned a bit about MEP's deinterlacing too. Not that I understand why those settings eg Interpolate intermediate images work! 🙂 . The written description/explanation of each setting certainly doesn't help.

QTGMC is a process for deinterlacing video and is arguably the best process in the business. Unfortunately though, it is an absolute nightmare to set up as it is made up of many different programs that sort of meld together somehow. If you're sitting down and unstressed, have a read though this. The guide I used to set it up is here. It's part of the AVISynth, an incredibly powerful video manipulation/editing world where results can be absolutely stunning if you know what you are doing. To me, it's all black magic and I just use examples that others have posted or suggested. Additionally, it is very resource-intensive and for Jak's video, my system was encoding at 10% video speed (not that I have a "normal" system any more).

Unfortunately, the deinterlacing of MPEG 2 with QTGMC is complicated further by the need to separate the audio and video, deinterlace the video, then put them back together again.

If I haven't scared you off, there is a program called Hybrid which has largely automated the QTGMC process but won't produce an MPEG file, only a lossless AVI or MP4, with no real "editing". I sometimes use it to de-interlace a file, then export it as an AVI, then import that into MEP for actual editing. Hybrid has lots of options and is a bit daunting at first but is quite clever. The developer, Selur, is quite active on his Hybrid forum and will respond quickly.

After working on Jak's file, I was quite impressed with MEPs' quality compared to the QTGMC output; it's not as good, but pretty close. Video is one of those "it's all in the eye of the beholder" things and I think MEP does a good job for us "normal" users.

For the exercise, I also did an MEP export with everything "standard" ie SD movie settings, including 25fps. I didn't change any of the Video object properties ie left the interlacing settings "as is". The only change I made was export at 50fps instead of the standard 25fps. The result was as good as the others.

So the secret appears to be to export at 50fps if the motion is violent.

 

Very well done! Thank you so much again. So what is it about H.264 that it can’t cope with rapid motion without increasing from 25 to 50fps? If MPEG-2 can cope with it then I wonder why MPEG-4 can’t?

@jak.willis

So what is it about H.264 that it can’t cope with rapid motion without increasing from 25 to 50fps?

Probably because you're only getting 25 frames every second with H264 (remember H264 is normally a progressive video codec), whereas MPEG 2 is an interlaced codec with 50 fields per second. Even though each field only has half the info, the eyes probably see the motion as smoother.

As I mentioned before, that motion is pretty wild and is probably on the extreme end of rough. Even then, it did take a close look on a big TV to notice it, so the encoders were doing a reasonable job at 25fps.

@jak.willis

So what is it about H.264 that it can’t cope with rapid motion without increasing from 25 to 50fps?

Probably because you're only getting 25 frames every second with H264 (remember H264 is normally a progressive video codec), whereas MPEG 2 is an interlaced codec with 50 fields per second. Even though each field only has half the info, the eyes probably see the motion as smoother.

As I mentioned before, that motion is pretty wild and is probably on the extreme end of rough. Even then, it did take a close look on a big TV to notice it, so the encoders were doing a reasonable job at 25fps.

Ah, yes, I see what you mean. So if we were to do the same thing but using the MainConcept encoder this time, do you think we’d get the same results? Both yourself & John have mentioned about H.264 being a Progressive codec, but in MainConcept you do get the option of using interlaced. So I just wondered whether it would make any difference.

@jak.willis

Hi

. . . . in MainConcept you do get the option of using interlaced. So I just wondered whether it would make any difference . . . .

At 25 fps there would be no difference at 50 fps possibly a slight improvement.

John EB

@jak.willis

Hi

. . . . in MainConcept you do get the option of using interlaced. So I just wondered whether it would make any difference . . . .

At 25 fps there would be no difference at 50 fps possibly a slight improvement.

John EB

Hi,

So if we did the same thing with exporting at 50fps, the motion issue would still be corrected regardless of whether or not it’s interlaced or progressive?

@jak.willis

Hi Jak

. . . . the motion issue would still be corrected regardless of whether or not it’s interlaced or progressive? . . . .

That is a presumption which would require testing.

I was referring specifically to what you asked

. . . . in MainConcept you do get the option of using interlaced. So I just wondered whether it would make any difference. . . .

John EB