[Martin Belleau]

[Martin Belleau]

Hi Eric,

The biggest things to look for in NTSC/PAL in my experience are:
– jerky motion
– single frame artifacts, in particular for motion compensated conversions. Brand new frames are generated and if the motion is not estimated properly, bad artifacts will appear. Not always visible at full speed playback.
– softness of the output. Happens for output with blended frames, or with motion compensation depending on the implementation.

For the telestream file, the output looks quite soft, in particular where these is some movement. This could be due to compression or other areas of the telestream pipeline, but most likely it’s from the conversion. I would double-check the settings for encoding and maybe try a different codec, as the softness is more than I could expect. I’ll try to upload some screenshots for this.

The Media Encoder file seems to re-use existing frames from the source. So, everything is sharp but looking frame by frame, you see a bigger time jump every 5th frame. Playing back at full speed, the pan and movements are more jerky.

I uploaded a file created by our software, Capella Cambria FTC. You can check it out here:
https://spaces.hightail.com/space/pYNmdNvDen

You’ll see some single frame artifacts but it’s both sharp and motion is fluid.

[Martin Belleau]

Sounds like it’s long GOP encoding since many frames in a row look bad. If it’s I-frame only encoding, a tool could just re-use the previous good frame so you get a freeze frame instead of a bad frame. If you could upload a short sample somewhere I could confirm if it’s long GOP or I-frame encoding.

Have you been able to find anything that helps?