Thanks Thanks:  0
Ergebnis 1 bis 6 von 6
  1. #1
    Anfänger
    Registriert seit
    16.12.2015
    Beiträge
    5
    Total Downloaded
    147,3 KB
    Total Downloaded
    147,3 KB
    ReceiverDankeAktivitäten

    Bug in MPEG TS that stops IPTV apps from streaming and playing recorded file on STV

    Hello,

    I found the following issue using the latest kernel and openatv 5.3 image on my edision osmini stb.
    In short the problems concerns a bug in MPEG TS generated from descrambled channels that blocks streaming from the stb via IPTV apps and playing recorded .ts files on Smart TVs.
    siptv and ss-iptv apps are used for streaming.

    I used the following image to stream and play recorded files from FTA and descrambled channels on Samsung 4k Tizen TV: openatv-5.1-osmini-20151020_usb. I haven't had any issues with it.

    The box was upgraded to openatv-5.3-osmini-20160922_usb with 4.7.0 kernel, and the latest updates applied including 4.8.0 kernel.

    The streaming and playing recorded .ts files from descrambled channels to the TV is not possible anymore!
    I have no problems with FTA channels, everything works normally.

    The TV returns errror: Not supported for streams and the file format is not supported for recorded files.


    The WMP, MPC and VLC players play/stream the content normally from both openatv 5.1 and openatv 5.3 from a descrambled channel!

    BUT there is one "big difference" in TS generated from the both images:

    When you use MediaInfo app or another to analyze a descrambled channel's recorded file from OpenATV 5.3 image, it shows that Video/Audio streams are encrypted which is NOT true.

    The video/audio streams from a recorded file on OpenATV 5.1 are shown as unencrypted with their stream parameters.

    The dvbsnoop app was used to analyze a recorded .ts file for both of the images. Just to note the the same result was received when the content's stream is saved to a file.
    The results are the following:

    Openatv 5.3
    .................................................. ...........

    Sync-Byte 0x47: 71 (0x47)
    Transport_error_indicator: 0 (0x00) [= packet ok]
    Payload_unit_start_indicator: 1 (0x01) [= Packet data starts]
    transport_priority: 0 (0x00)
    PID: 6191 (0x182f) [= NIT, PMT or Elementary PID, etc.]
    transport_scrambling_control: 2 (0x02) [= TS packet scrambled with Even Key]
    adaptation_field_control: 1 (0x01) [= no adaptation_field, payload only]
    continuity_counter: 6 (0x06) [= (sequence ok)]
    Payload: (len: 184)
    Data-Bytes:

    .................................................. ............

    Openatv 5.1
    .................................................. ............

    Sync-Byte 0x47: 71 (0x47)
    Transport_error_indicator: 0 (0x00) [= packet ok]
    Payload_unit_start_indicator: 1 (0x01) [= Packet data starts]
    transport_priority: 0 (0x00)
    PID: 6191 (0x182f) [= NIT, PMT or Elementary PID, etc.]
    transport_scrambling_control: 0 (0x00) [= No scrambling of TS packet payload]
    adaptation_field_control: 1 (0x01) [= no adaptation_field, payload only]
    continuity_counter: 15 (0x0f) [= (sequence ok)]
    Payload: (len: 184)
    ==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2 or ISO/IEC 11172-2 video stream]
    Data-Bytes:
    .................................................. .............

    The obvious difference is that we have:

    transport_scrambling_control: 0 (0x00) [= No scrambling of TS packet payload] on Openatv 5.1 which is correct.

    the transport_scrambling_control: 2 (0x02) [= TS packet scrambled with Even Key] on Openatv 5.3 which is NOT correct as the channel has already been descrambled and the plain payload is put in packets.

    OpenPLi-4.0-beta-osmini-20161009_usb was also tested on the STB. The results were the same.

    Seems that the Smart TV "strictly adhere" to DVB standards

    Thanks in advance for any workarounds if someone knows how to "overcome" this bug because the streaming to Smart TVs is totally blocked.

    Maybe the bug has appeared from: osmini proprietary drivers/libraries and/or the new kernel ?

    •   Alt Advertising

       

  2. #2
    Avatar von Captain
    Registriert seit
    03.04.2013
    Beiträge
    11.903
    Total Downloaded
    162,35 MB
    Total Downloaded
    162,35 MB
    ReceiverDankeAktivitäten
    we report this to the driver team , thx for the info


    openATV we are open Source

    Boykott GPL violator

  3. #3
    Anfänger
    Registriert seit
    16.12.2015
    Beiträge
    5
    Themenstarter
    Total Downloaded
    147,3 KB
    Total Downloaded
    147,3 KB
    ReceiverDankeAktivitäten
    Zitat Zitat von Captain Beitrag anzeigen
    we report this to the driver team , thx for the info
    10x!, hope that the fix will come soon....

  4. #4
    Avatar von Captain
    Registriert seit
    03.04.2013
    Beiträge
    11.903
    Total Downloaded
    162,35 MB
    Total Downloaded
    162,35 MB
    ReceiverDankeAktivitäten
    So please check for us

    this is only for test your issue not for normal use , other user only you have this issue too dont use this driver in normal image !


    you find test drivers for atv 5.3 with kernel 4.7.and 4.8
    replace the drivers in folder

    \lib\modules\4.7.0\extra or
    \lib\modules\4.8.0\extra

    reboot

    and report
    Angehängte Dateien Angehängte Dateien


    openATV we are open Source

    Boykott GPL violator

  5. #5
    Anfänger
    Registriert seit
    16.12.2015
    Beiträge
    5
    Themenstarter
    Total Downloaded
    147,3 KB
    Total Downloaded
    147,3 KB
    ReceiverDankeAktivitäten
    Zitat Zitat von Captain Beitrag anzeigen
    So please check for us

    this is only for test your issue not for normal use , other user only you have this issue too dont use this driver in normal image !


    you find test drivers for atv 5.3 with kernel 4.7.and 4.8
    replace the drivers in folder

    \lib\modules\4.7.0\extra or
    \lib\modules\4.8.0\extra

    reboot

    and report
    The today's last updates and the above new drivers have been applied to the STB running atv 5.3 with kernel 4.8.0.
    Now everything is OK. The above issue has been fixed.

    I will prepare and check a atv 5.3 with kernel 4.7.0 image tomorrow and report the result.

  6. #6
    Anfänger
    Registriert seit
    16.12.2015
    Beiträge
    5
    Themenstarter
    Total Downloaded
    147,3 KB
    Total Downloaded
    147,3 KB
    ReceiverDankeAktivitäten
    Zitat Zitat von ig73 Beitrag anzeigen
    The today's last updates and the above new drivers have been applied to the STB running atv 5.3 with kernel 4.8.0.
    Now everything is OK. The above issue has been fixed.

    I will prepare and check a atv 5.3 with kernel 4.7.0 image tomorrow and report the result.


    Recording a scrambled channel is now OK on Atv5.3 + 4.7.0 kernel(openatv-5.3-osmini-20160923_usb) using the provided drivers and atv openatv-5.3-osmini-20161015_usb (saw that drivers already included).
    The MPEG TS file does not contain anymore packets marked as scrambled.




    There is still one more bug left in MPEGS TS when start streaming descrambled channel via the STB's HTTP server.
    There are packets marked as scrambled in the beginnig of the TS and at a some moment the status flag gets cleared for the following packets.


    This leads to difficult starting of descrambled channels on Smart TV's IPTV apps. "not supported" and different errors are sent from the TV to the app.
    It is needed to try 3-5 times to start the streaming if you have a luck.
    I've always been wondering so far what is going on, sometimes it works and sometimes not ....., and was thinking that the IPTV app has some problems.


    NOTE: When the STB is switched on a scrambled channel and Smart TV's IPTV app starts streaming from the same channel, the probability to get a scrambled packet is minimal!!!
    Sometimes that's the only way(workaround) to start descrambled channel via the IPTV app on the TV.
    I just checked only this scenario in my previous post hoping that everything has been fixed.....


    The bug is also present in ATV5.1(openatv-5.1-osmini-20151020_usb + 4.2.3 kernel) and in the above ATV 5.3 images.
    I just checked it with Openpli image OpenPLi-4.0-beta-osmini-20161015_usb using the above drivers and the bug also exists there.


    In short the bug can be reproduced in any of the following ways:


    - switch on the STB to watch a scrambled channel service1, then start streaming another scrambled channel service2 on the same transponder
    making a call to via Browser's address bar to this channel http://<ip>:8001/<service2>, save to a file
    or curl -v http://<ip>:8001/<service2> > file.ts(prefer this way).
    The streaming's recording has to continue no more than a minute.


    - standby the STB, check in Webif that's shown nothing playing and make one of the described steps and start streaming any scrambled channel.


    Then in both cases there are packets in the beginning of the stream marked as scrambled.
    I didn't check whether they are really scrambled or not.


    Here is the dvbsnoop's result for a descrambled channel TS sent via HTTP streaming recorded using: curl -v 'http://<ip>:8001/<service2>' > file.ts
    It can be seen that there are 187 packets marked as scrambled, sometimes the count is between 1000-3000 packets in the beginning of TS.


    ------------------------------------------------------------
    TS-Packet: 00000001 PID: (Unkown PID), Length: 188 (0x00bc)
    from file: file.ts
    ------------------------------------------------------------


    Sync-Byte 0x47: 71 (0x47)
    Transport_error_indicator: 0 (0x00) [= packet ok]
    Payload_unit_start_indicator: 0 (0x00) [= Packet data continues]
    transport_priority: 0 (0x00)
    PID: 6191 (0x182f) [= NIT, PMT or Elementary PID, etc.]
    transport_scrambling_control: 2 (0x02) [= TS packet scrambled with Even Key]
    adaptation_field_control: 1 (0x01) [= no adaptation_field, payload only]
    continuity_counter: 12 (0x0c) [= (sequence ok)]
    Payload: (len: 184)
    Data-Bytes:
    ================================================== ========
    .................................................. .................................................. .................................................. .................................................. ....................
    ------------------------------------------------------------
    TS-Packet: 00000187 PID: (Unkown PID), Length: 188 (0x00bc)
    from file: file.ts
    ------------------------------------------------------------


    Sync-Byte 0x47: 71 (0x47)
    Transport_error_indicator: 0 (0x00) [= packet ok]
    Payload_unit_start_indicator: 0 (0x00) [= Packet data continues]
    transport_priority: 0 (0x00)
    PID: 6191 (0x182f) [= NIT, PMT or Elementary PID, etc.]
    transport_scrambling_control: 2 (0x02) [= TS packet scrambled with Even Key]
    adaptation_field_control: 1 (0x01) [= no adaptation_field, payload only]
    continuity_counter: 13 (0x0d) [= (sequence ok)]
    Payload: (len: 184)
    Data-Bytes:
    ================================================== ========

    TS sub-decoding (1 packet(s) stored for PID 0x0012):
    ================================================== ===
    Packet cannot be sub-decoded: packet scrambled or packet error

    ------------------------------------------------------------
    TS-Packet: 00000188 PID: (Unkown PID), Length: 188 (0x00bc)
    from file: file.ts
    ------------------------------------------------------------


    Sync-Byte 0x47: 71 (0x47)
    Transport_error_indicator: 0 (0x00) [= packet ok]
    Payload_unit_start_indicator: 0 (0x00) [= Packet data continues]
    transport_priority: 0 (0x00)
    PID: 6191 (0x182f) [= NIT, PMT or Elementary PID, etc.]
    transport_scrambling_control: 0 (0x00) [= No scrambling of TS packet payload]
    adaptation_field_control: 1 (0x01) [= no adaptation_field, payload only]
    continuity_counter: 14 (0x0e) [= (sequence ok)]
    Payload: (len: 184)
    Data-Bytes:
    ================================================== ========
    .................................................. .................................................. .................................................. .................................................. ..................

    ------------------------------------------------------------
    TS-Packet: 00000226 PID: (Unkown PID), Length: 188 (0x00bc)
    from file: file.ts
    ------------------------------------------------------------


    Sync-Byte 0x47: 71 (0x47)
    Transport_error_indicator: 0 (0x00) [= packet ok]
    Payload_unit_start_indicator: 1 (0x01) [= Packet data starts]
    transport_priority: 0 (0x00)
    PID: 6191 (0x182f) [= NIT, PMT or Elementary PID, etc.]
    transport_scrambling_control: 0 (0x00) [= No scrambling of TS packet payload]
    adaptation_field_control: 1 (0x01) [= no adaptation_field, payload only]
    continuity_counter: 1 (0x01) [= (sequence ok)]
    Payload: (len: 184)
    ==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2 or ISO/IEC 11172-2 video stream]
    Data-Bytes:
    ================================================== ========

    ------------------------------------------------------------
    TS-Packet: 00000227 PID: (Unkown PID), Length: 188 (0x00bc)
    from file: file.ts
    ------------------------------------------------------------


    Sync-Byte 0x47: 71 (0x47)
    Transport_error_indicator: 0 (0x00) [= packet ok]
    Payload_unit_start_indicator: 0 (0x00) [= Packet data continues]
    transport_priority: 0 (0x00)
    PID: 6191 (0x182f) [= NIT, PMT or Elementary PID, etc.]
    transport_scrambling_control: 0 (0x00) [= No scrambling of TS packet payload]
    adaptation_field_control: 1 (0x01) [= no adaptation_field, payload only]
    continuity_counter: 2 (0x02) [= (sequence ok)]
    Payload: (len: 184)
    Data-Bytes:

    .................................................. .................................................. .................................................. .................................................. ....................................

    Does the issue come again from the osmini drivers and/or Http server code in combination ?


    It will be great to share any other unknown workarounds so far until a fix is available.
    I can check a new fix again if provided by your driver team.


    10x in advance for your response and help!


Stichworte

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •  
Diese Website benutzt Cookies
Wir benutzen Cookies um Sitzungsinformationen zu speichern. Dies erleichtert es uns z.B. Dich an Deine Login zu erinnern, Einstellungen der Webseite zu speichern, Inhalte und Werbung zu personalisieren, Social Media Funktionen anzubieten und unser Datenaufkommen zu analysieren. Wir teilen diese Informationen ebenfalls mit unseren Social Media-, Werbe- und Analysepartnern.
     
Alle Zeitangaben in WEZ +1. Es ist jetzt 18:02 Uhr.
Powered by vBulletin® Version 4.2.5 (Deutsch)
Copyright ©2018 Adduco Digital e.K. und vBulletin Solutions, Inc. Alle Rechte vorbehalten.
Resources saved on this page: MySQL 11,11%
Parts of this site powered by vBulletin Mods & Addons from DragonByte Technologies Ltd. (Details)
vBulletin Skin By: PurevB.com