Iptv hickups

Discussion in 'General Support' started by doskabouter, February 18, 2019.

  1. doskabouter
    • Premium Supporter

    doskabouter Community Plugin Dev

    Joined:
    September 27, 2009
    Messages:
    2,739
    Likes Received:
    696
    Location:
    Nuenen
    Ratings:
    +1,042 / 1
    Home Country:
    Netherlands Netherlands
    Show System Specs
    Hi all,

    Since a while I'm using iptv to watch tv-content, most of the time it works like a charm except (who would've thought) when it doesn't.

    The thing is, the connection to (or my iptvprovider itself) drops out on me (MPUrlSourceSplitter_Protocol_Http: instance 'Main': CurlDebug(): CURL message: 'Closing connection 2011') and
    Code (Text):
    1.  
    2. 18-02-2019 19:46:20.103 [114c] [{3F93EB93-6AE0-42E4-82A7-E01F26684F3C}] [Verbose] MPUrlSourceSplitter_Protocol_Http: ReceiveData(): discontinuity, completing request, request '17779', start '140895852', size '1046784', found: '74312'
    3. 18-02-2019 19:46:20.123 [16b4] [{AC67E606-D0BA-4857-BAAA-E0FC799ADF81}] [Warning] MPUrlSourceSplitter_Parser_Mpeg2TS: ReceiveDataWorker(): invalid data, removing 4 bytes
    4. 18-02-2019 19:46:20.123 [16b4] [{AC67E606-D0BA-4857-BAAA-E0FC799ADF81}] [Warning] MPUrlSourceSplitter_Parser_Mpeg2TS: ReceiveDataWorker(): discontinuity detected, PID: 17 (0x0011), expected counter: 1, packet counter: 14
    5. 18-02-2019 19:46:20.123 [16b4] [{AC67E606-D0BA-4857-BAAA-E0FC799ADF81}] [Warning] MPUrlSourceSplitter_Parser_Mpeg2TS: ReceiveDataWorker(): discontinuity detected, PID: 0 (0x0000), expected counter: 7, packet counter: 9
    6. 18-02-2019 19:46:20.123 [16b4] [{AC67E606-D0BA-4857-BAAA-E0FC799ADF81}] [Warning] MPUrlSourceSplitter_Parser_Mpeg2TS: ReceiveDataWorker(): discontinuity detected, PID: 4096 (0x1000), expected counter: 7, packet counter: 9
    7. 18-02-2019 19:46:20.123 [16b4] [{AC67E606-D0BA-4857-BAAA-E0FC799ADF81}] [Warning] MPUrlSourceSplitter_Parser_Mpeg2TS: ReceiveDataWorker(): discontinuity detected, PID: 256 (0x0100), expected counter: 12, packet counter: 10
    8. 18-02-2019 19:46:20.143 [16b4] [{AC67E606-D0BA-4857-BAAA-E0FC799ADF81}] [Verbose] MPUrlSourceSplitter_Parser_Mpeg2TS: ReceiveDataWorker(): discontinuity, completing request, request '781', start '140895848', size '1046784', found: '74260', fragment start: 140895848, fragment length: 74260, start searching fragment start: 0
    9. 18-02-2019 19:46:20.143 [ 3a4] [{DE0776D7-5702-4D32-B9E3-C01688D98B4F}] [Verbose] Demuxer: DemuxerRead(): stream 0, request 781, start: 140895848, length: 1046784, pending discontinuity
    10. 18-02-2019 19:46:20.144 [ 3a4] [{DE0776D7-5702-4D32-B9E3-C01688D98B4F}] [Verbose] Demuxer: DemuxerRead(): stream 0, request 782, start: 140970108, length: 1046784, discontinuity reported
    11. 18-02-2019 19:46:20.144 [16b4] [{AC67E606-D0BA-4857-BAAA-E0FC799ADF81}] [Warning] MPUrlSourceSplitter_Parser_Mpeg2TS: ReceiveDataWorker(): invalid data, removing 136 bytes
    12. 18-02-2019 19:46:20.144 [ 3a4] [{DE0776D7-5702-4D32-B9E3-C01688D98B4F}] [Verbose] Demuxer: GetNextPacketInternal(): stream 0, discontinuity received or connection lost
    13. 18-02-2019 19:46:20.144 [16b4] [{AC67E606-D0BA-4857-BAAA-E0FC799ADF81}] [Warning] MPUrlSourceSplitter_Parser_Mpeg2TS: ReceiveDataWorker(): discontinuity detected, PID: 256 (0x0100), expected counter: 15, packet counter: 0
    14. 18-02-2019 19:46:20.144 [16b4] [{AC67E606-D0BA-4857-BAAA-E0FC799ADF81}] [Warning] MPUrlSourceSplitter_Parser_Mpeg2TS: ReceiveDataWorker(): discontinuity detected, PID: 257 (0x0101), expected counter: 6, packet counter: 15
    15. 18-02-2019 19:46:23.143 [16b4] [{AC67E606-D0BA-4857-BAAA-E0FC799ADF81}] [Verbose] MPUrlSourceSplitter_Parser_Mpeg2TS: ReceiveDataWorker(): setting guess total length: 295708960
    16.  
    So it reports a discontinuity upstream (tswriter,log:)
    Code (Text):
    1.  
    2. [2019-02-18 19:36:55,439] [d248890] [610] - CDiskRecorder::Flush() - Throttle to 32336 bytes (max)
    3. [2019-02-18 19:46:20,159] [d248890] [610] - Recorder:Pid 100 Continuity error... a ( prev b ) - bad signal?
    4. [2019-02-18 19:46:20,199] [d248890] [610] - Recorder:Pid 100 Continuity error... 0 ( prev e ) - bad signal?
    5. [2019-02-18 19:46:20,199] [d248890] [610] - Recorder: TIMESHIFT Info : Program clock reference backward jump ( -2995198 ).
    6. [2019-02-18 19:46:20,199] [d248890] [610] - Recorder:Pid 101 Continuity error... f ( prev 5 ) - bad signal?
    7.  
    This results in this case to a jump backwards of 30 seconds, and after that it continues normally.

    Couple of questions:
    - Tv server is 1.18, is it worth it to upgrade and test again, or wasn't there any improvement in that area due to the TVE code freeze issues?
    - Is it possible to change behavior in this case that it doesn't jump back but keeps on playing normally?
    I do realize that when new data is needed to feed to the player and due to network/server issues it is not present, something needs to be done, but I'd rather have a paused image/buffering cursor/other creative solutions than a skip back.

    I can pretty reliably reproduce this, so if someone wants to use me as a guinea-pig, please let me know!


     
Loading...

Users Viewing Thread (Users: 0, Guests: 0)

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice
  • About The Project

    The vision of the MediaPortal project is to create a free open source media centre application, which supports all advanced media centre functions, and is accessible to all Windows users.

    In reaching this goal we are working every day to make sure our software is one of the best.

             

  • Support MediaPortal!

    The team works very hard to make sure the community is running the best HTPC-software. We give away MediaPortal for free but hosting and software is not for us.

    Care to support our work with a few bucks? We'd really appreciate it!