To be honest, this is more of an experiment than just trying to ruin a perfectly good looking video. More specifically, what am trying to achieve here is what the encoder of the video I have sent you has achieved...namely, making an interlaced stream appear as though if it were de-interlaced. It's clear there's no de-interlacing or motion interpolation involved, as the MediaInfo clearly states:
And then:Code:Frame rate mode : Variable Frame rate : 59.940 FPS Original frame rate : 29.970 (30000/1001) FPS
It probably has to do with the "Separated Fields" part that not only adds that metadata to the MediaInfo log but also "forces" players like VLC to recognize the frame/field rate as 59.940.Code:Scan type : Interlaced Scan type, store method : Separated fields Scan order : Top Field First
+ Reply to Thread
Results 31 to 42 of 42
Last edited by simon744; 8th Sep 2023 at 17:20.
Yes, as long as your player or device handles those videos, there is nothing to fix. I was particularly interested how to load those videos into Avisynth/Vapoursynth because as everything was as default, it would load wrong. So jagabo explanation was important.
For example MPC-HC was playing it ok or mpv or mpvnet players also (pressing key "D" to activate deinterlace)
Last edited by simon744; 9th Sep 2023 at 13:46.
I have no idea what you want, and guessing others also. You said, you are learning, that is why I said what I said to share what I got.
The sample posted was an example of a desired output video, not input video, correct? _Al_ (and probably many people) assumed it was an input video
What your options are could might be different for each input source. Mediainfo does not indicate what the actual content is, only how it was encoded and/or flagged. So you've really posted not much important information about what you're actually starting with - and many assumptions are being made
Why not to just posted one video at a time and what problem you have with it. Done. You could potentially save weeks of ping-pong gaming.
You can just post 10 second of a video if you cut it losslessly.
There is no such a thing as different frame rate for interlace video, like 29.97i and 59.94i (25i and 50i). There is only one frame rate where label 29.97i or 59.94i could be used.
Interlace video could have only 29.97fps or 25fps.
Fields have temporal resolution 59.94 or 50 if things are right, But fps is 29.97 or 25 only.
That was mentioned in post #2 right away, but not sure if you registered that. You did not respond to most important input in this thread.
Guess I could've simply asked how to re-encode interlaced video as one with separated fields as that pretty much seems to be what I actually need.
Whether or not a source encoded with separated fields, interleaved fields, or MBAFF does not affect "smoothness" - it does not change the actual underlying content
eg. You start with a 25p content source. That is 25 samples taken per second from the camera. If you encode that interlaced as a separated fields, it doesn't add more unique samples. It's still 25 samples /s just encoded in a different manner. Each field is still taken from the same moment in time. You don't magically now have 50 unique moments in time per second. Conversely, true interlaced content aka. "25i content" has 50 samples per second - the motion is smoother to begin with. That's what some of the assumptions were about motion interpolation and generating new inbetween frames. But it's not clear what you have , or what you are starting with
Similarly, if you start with some "25i" source with interleaved fields, regardless of content, and encode it with interlaced separated fields - it does NOT change the content. It's only a different way of storing the same information. The underlying information is not changed.
A common mistake is how people interpret mediainfo - Mediainfo does not analyse the file for actual content - It just reports how a file was encoded, metadata, flagging . It does not give you them most critical information - that information about content.