Wrong HD aspect ratio detection (1 Viewer)

Ambass

Retired Team Member
  • Premium Supporter
  • December 24, 2007
    555
    129
    Home Country
    France France
    Aspect ratio detection is not working properly on H264 channels.
    In the following log there is :
    1 ) start TV on M6HD / H264 ( Tsreader shows 4:3, MP found 16:9 ) => correct ratio is 16:9 ( 1440x1080i ) Final aspect is OK.
    2 ) zap to FR3 / MPEG2 ( Tsreader shows 16:9, MP found 16:9 ) => correct ratio is 16:9 ( 720x576i ) Final aspect is OK.
    3 ) zap back to M6HD / H264 ( Tsreader shows 4:3, MP found 4:3 :( ) => correct ratio is 16:9 ( 1440x1080i ) Final aspect is wrong.

    A second XP install on another HDD with same release do not show the problem...I'll attach same logs from 2nd install later.

    Now it's attached.

    MP found 16:9 on zap back to M6 and works... ( Tsreader always fails in H264 AR detection )

    In fact it seems a bit random, I've already seen AR of 1 and 720:480...!
     

    tourettes

    Retired Team Member
  • Premium Supporter
  • January 7, 2005
    17,301
    4,800
    In TsReader uncomment the following

    Code:
    bool CMpegPesParser::ParseVideo(byte* tsPacket,bool isMpeg2)
    
    //hdrParser.DumpAvcHeader(avc);

    That way we see if the parsing itself is faulty, or is there somewhere a bug that the new channel change doesn't trigger the parsing.
     

    Ambass

    Retired Team Member
  • Premium Supporter
  • December 24, 2007
    555
    129
    Home Country
    France France
    I've tried with an old tsreader, it gives a correct AR of 16:9 ( so the new "golomb...." is probably faulty", same on both XP installs) , but it doesn't change anything to the final MP result that found the AR from elsewhere ...
     

    tourettes

    Retired Team Member
  • Premium Supporter
  • January 7, 2005
    17,301
    4,800
    I've tried with an old tsreader, it gives a correct AR of 16:9 ( so the new "golomb...." is probably faulty", same on both XP installs) , but it doesn't change anything to the final MP result that found the AR from elsewhere ...

    Codec could be telling that AR to MP.
     

    Users who are viewing this thread

    Top Bottom