2014-12-09, 19:06
(2014-12-09, 03:02)Dogchow Wrote: Ah good info, that explains the screen flash as renderer reconfigures itself on the change of format. A random check of some DVB-T2 recordings using that ffprobe command does show the mixed progressive/interlaced content.
Seems some programmes are switching format frequently even between different camera shots in the same drama scene, which I find a little odd, and can lead to frequent screen flashes. Either that or maybe the encoders used aren't perfect and sometimes flagging frames incorrectly? Of course now I'm sensitive to the flashes I can't unsee them and they're annoying me now on every change!
Hollyoaks (without the deaf signer) seems to be a heavy user of the switching between camera shots, it would be interesting if anyone else can record the DVB-T2 broadcast at 6.30pm Tue on CH4HD and look for the format changes in scenes just to confirm they're there and not something tvh is introducing for me - anyone a DVB-T2 user? You don't have to be a hollyoaks watcher, I'm not either, but it's now my test broadcast
It also explains why when I tried xbmc on my android box a while back, it was unwatchable during the proper HD programme but would play perfectly when the commercials were on.
Interesting. Hollyoaks is shot 25p - but any dissolves or wipe/fade to black transitions will be 50i (as is required by all UK broadcasters for 25p shot content) as will all rolling/crawling credits. With no overlaid 50i sign-language interpreter, I'd expect the encoder to be 25p for most of the time, but shot changes could also trigger a drop to 50i (as it is the safer of the two encoder profiles) until the encoder has decided the next shot is also 25p?
I guess it is a problem for Kodi to 'know' that an MPEG2 transport stream with H264 video that is constantly switching between 25p and 50i GOP-by-GOP should be treated as 50i constantly (or any transitions between 25p and 50i deinterlaced to 50p should be transparent?)
As a matter of interest 1080i 4:2:2 interlaced stuff isn't detected as interlaced by XBMC (or wasn't last time I checked) and you have to force de-interlacing to be on to get it de-interlaced as well. (There were also rendering issues with 4:2:2 interlaced 50i content which caused saturated content to look 25p even when de-interlaced)
