Quote:
Originally Posted by agressiv
I could upload the 700mb AVI from virtualdub, but that mp4 is lossless -- figured it would be good enough. Instead, I've used ffmpeg to output the raw streamcopy to an MKV here. This has no modifications other than trim().
https://mega.nz/#!6ZZw3J7T!3L5HNM5fM...XLfX_xN77qajL0 |
It probably doesn't matter here, but in the future keep in mind this is not a "raw streamcopy", or at least not one that is unprocessed.
Using trim() means you are using avisynth, which means you are subject to whatever decoding pathway you have set up (it's been decoded, and possibly processed). You should cut from the original with something like tsmuxer . Not only will filesize be several times smaller (when you decode it using an avisynth source filter, it becomes uncompressed) , that will ensure no quality loss, or decoding issues , or unforseen processing variables (some source filters might be set to deinterlace or add post processing, especially directshow based) - and you never mentioned how you are loading it in avisynth.
If you cut it with ffmpeg using streamcopy instead of avisynth, then yes that would be acceptable, because it would not have been decoded
But assuming this was representative without any other processing issues, it looks progressive. It's a crossfade - that's what it's supposed to look like. The up/down motion when you separate fields is from the even/odd field offset. That is normal for progressive. There is no clear indication of different moments in time represented each field. Pay attention to the zoom movement in - if it was interlaced content, then you would see zoom increasing every field during that crossfade. You do not here, thus it's progressive
However, some of the other content on the disc - behinds the scenes, etc.. those are interlaced for sure.