I think it was an old powerdvd directshow filter I was messing with during testing. I can't remember at the moment. Most media players will ignore it. As far as using all kinds of different splitters and directshow filters on windows that is probably more suspect. I think one time at a friend's place when we were reviewing some of the AMV archive we were trying to figure out wtf the interlaced videos weren't de-interlacing on the fly and then found out someone had setup an override and it was using a hardware codec for this tv card he had instead of the usual MPEG-2 filters used by MPC.Scintilla wrote:I didn't even know this could be an issue. I'd always been under the impression that software players didn't even bother applying the 3:2 pulldown, because PCs have no problem playing stuff back at 23.976 progressive -- I always thought the flag was just there for standalone DVD players and MPEG playback cards that were outputting to a display that required 29.97 interlaced.
Which player is rendering it at 29.97 interlaced? I'm curious now.
To answer the real why: We don't primarily treat anything like it's in the NTSC world anymore (hence the switch to requiring progressive 2 years ago and making it a recommendation 3 years ago) but I still need to be prepared and have a fallback plan (DVD). So I tend to prefer to just not have the flag set so later when I do things with the archive down the road beyond even this year I don't have to worry about "will this software app or avisynth setup" treat this as interlaced or progressive. Usually when I need to prep a conversion I always use an intermediate like huffyuv exported from an avisynth setup. Sometimes I've had files choke on that though and have had to rely on other programs which have limitations or behaviors I don't like or am not as familiar with.
