WinTV-CI / Cinergy-USB-CI und ddci2

  • Hi Helmut,

    the test with ACL 2.2 and cor6 patch

    you are the Man!

    CU

    9000h

    Es ist eagl in wlehcer Reiehnfogle die Bchustebaen in Woeretrn vokrmomen. Huapstache der estre und leztte Bchustbae sitmmen.

  • Hi,

    same test with the Matrix Cam Air and cor6 patch.

    CU

    9000h

    Es ist eagl in wlehcer Reiehnfogle die Bchustebaen in Woeretrn vokrmomen. Huapstache der estre und leztte Bchustbae sitmmen.

  • Hi,

    same test with the Diablo Cam and cor6 patch

    CU

    9000h

    Es ist eagl in wlehcer Reiehnfogle die Bchustebaen in Woeretrn vokrmomen. Huapstache der estre und leztte Bchustbae sitmmen.

  • Hi,

    the ACL 2.2

    CU

    9000h

    Es ist eagl in wlehcer Reiehnfogle die Bchustebaen in Woeretrn vokrmomen. Huapstache der estre und leztte Bchustbae sitmmen.

  • Hi,

    the Matrix

    CU

    9000h

    Es ist eagl in wlehcer Reiehnfogle die Bchustebaen in Woeretrn vokrmomen. Huapstache der estre und leztte Bchustbae sitmmen.

  • Hi,

    the Matrix and cor5a

    CU

    9000h

    Es ist eagl in wlehcer Reiehnfogle die Bchustebaen in Woeretrn vokrmomen. Huapstache der estre und leztte Bchustbae sitmmen.

  • Hi,

    the ACL 2.2 and cor5a

    CU

    9000h

    Es ist eagl in wlehcer Reiehnfogle die Bchustebaen in Woeretrn vokrmomen. Huapstache der estre und leztte Bchustbae sitmmen.

  • Is the Matrix CAM in some kind of power-down mode?

    This [ 9550.621568] wintv_usb2ci: parse_cis : CFG_REGS present [0-7] = 0x03 says, that there is a second configuration register available - the CSR (Configuration and Status Register).

    I will look on it tomorrow.


    Helmut

  • Hi,

    the Matrix is a real wired cam with SIDSA + Xilinx in the CI part + a Season like card with extra CPU.

    here are some infos about the internal software

    https://github.com/z1Y2x/mca

    and some internal pics

    http://www.laguarida.us/electr…bra-en-la-matrix-cam-air/


    the xilinx firmware https://www.sat4all.com/forums…indComment&comment=763988


    CU

    9000h

    Es ist eagl in wlehcer Reiehnfogle die Bchustebaen in Woeretrn vokrmomen. Huapstache der estre und leztte Bchustbae sitmmen.

    The post was edited 2 times, last by 9000H ().

  • Hi,

    Yuri666  

    from the USB side it looks good here

    lsusb -t

    /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 5000M

    /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M

    |__ Port 4: Dev 17, If 0, Class=Vendor Specific Class, Driver=wintv_usb2ci, 480M

    |__ Port 5: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M

    ....

    what showes the "speedtest" WinTV-CI / Cinergy-USB-CI und ddci2

    can you try another bus or on different hardware

    can you try with a low latency kernel.

    CU

    9000h

    Es ist eagl in wlehcer Reiehnfogle die Bchustebaen in Woeretrn vokrmomen. Huapstache der estre und leztte Bchustbae sitmmen.

    The post was edited 1 time, last by 9000H ().

  • Hi,

    yes, my speedtest showed equal results.

    But in minisatip if input stream more than 20 Mbps, i have distortions and errors in log:

    Code
    1. [10/02 00:19:54.876 signal]: BW 2056KB/s, Total BW: 36 MB, ns/read 15847, r: 67, w: 1600 fw: 0, tt: 1061 ms
    2. [10/02 00:19:55.842 AD2]: select_and_execute[7]: EOVERFLOW on socket 9 (sid:2) from 0.0.0.0:0 - type dvr errno 75

    EOVERFLOW - means that the data from DVR was not read fast enough. In case minisatip data from AD2 put to WINTV adapter using the function writev()

    WINTV driver report not much load:

    Code
    1. [80333.877045] +++ TS-BITRATE : 15.79 Mbit/s, 328.20 CAM-subs/s, URB-load: 0.83%, TS-miss: 12
    2. [80343.876721] +++ TS-BITRATE : 15.74 Mbit/s, 327.10 CAM-subs/s, URB-load: 0.83%, TS-miss: 12
    3. [80353.874308] +++ TS-BITRATE : 15.71 Mbit/s, 326.60 CAM-subs/s, URB-load: 0.83%, TS-miss: 12
    4. [80363.875110] +++ TS-BITRATE : 15.81 Mbit/s, 328.50 CAM-subs/s, URB-load: 0.83%, TS-miss: 12
    5. [80373.874625] +++ TS-BITRATE : 15.73 Mbit/s, 326.90 CAM-subs/s, URB-load: 0.83%, TS-miss: 12

    Maybe needs to use other write/read method or use low latency kernel - I don't know.

    With real DDCI minisatip have not any problem. Maybe it should be - pcie 1x about four times faster than usb 2.0

    Code
    1.  [10/02 12:22:40.977 signal]: BW 2178KB/s, Total BW: 89 MB, ns/read 1568, r: 31, w: 31 fw: 0, tt: 48 ms

    Can you test much stream load (more than 20 Mbps) to one WINTV adapter at other applications, e.g. VDR?


    BR,

    Yuri

  • Hi,

    no difference

    Code
    1. [11/02 23:26:23.085 signal]: BW 2042KB/s, Total BW: 79 MB, ns/read 5300, r: 199, w: 296 fw: 0, tt: 1054 ms
    2. [11/02 23:26:24.104 signal]: BW 2042KB/s, Total BW: 81 MB, ns/read 5303, r: 199, w: 295 fw: 0, tt: 1055 ms
    3. [11/02 23:26:24.237 AD2]: select_and_execute[7]: EOVERFLOW on socket 9 (sid:2) from 0.0.0.0:0 - type dvr errno 75
    4. [11/02 23:26:25.122 signal]: BW 1971KB/s, Total BW: 83 MB, ns/read 5145, r: 194, w: 285 fw: 0, tt: 998 ms
    5. [11/02 23:26:26.150 signal]: BW 2041KB/s, Total BW: 85 MB, ns/read 5276, r: 200, w: 293 fw: 0, tt: 1055 ms

    BR,

    Yuri

  • Hi Yuri,


    [80333.877045] +++ TS-BITRATE : 15.79 Mbit/s, 328.20 CAM-subs/s, URB-load: 0.83%, TS-miss: 12


    The number of data transfers (CAM-subs) to the CAM is very high (or too high).

    With normal DVB-T2/S2 there are usually only 10 to 20 CAM-submissions per second. So, minisatip delivers many, but only very small data chunks.


    By default the wintvci driver starts submitting URBs to the CAM if there are at least 32 TS-packets in the buffer.

    You can increase this value by changing ISOC_MIN_UF_SUBMIT from 8 to 64 in wintv-ci.c, line 45.

    It should be a multiple of 8, the (theoretical) maximum is the full URB buffer size of 960 - 1.


    Code
    1. #define ISOC_MIN_UF_CHUNK 8 /* transmit only in chunks of 8 micro-frames (1 full frame) */
    2. //#define ISOC_MIN_UF_SUBMIT ISOC_MIN_UF_CHUNK /* the minimum of data to start a URB submission to the CAM */
    3. #define ISOC_MIN_UF_SUBMIT 64 /* the minimum of data to start a URB submission to the CAM */

    Helmut

  • Yury - you have to change this line too.

    Helmut

  • Hi Helmut,


    great job! :) As I understand, minisatip use kernel functions for read/write, and after your changes number submissions reduse several times.

    Code
    1. [136368.283358] +++ TS-BITRATE : 18.78 Mbit/s, 48.78 CAM-subs/s, URB-load: 6.66%, TS-miss: 0
    2. [136378.286315] +++ TS-BITRATE : 18.78 Mbit/s, 48.80 CAM-subs/s, URB-load: 6.66%, TS-miss: 0
    3. [136388.282923] +++ TS-BITRATE : 18.82 Mbit/s, 48.90 CAM-subs/s, URB-load: 6.66%, TS-miss: 0
    4. [136398.295045] +++ TS-BITRATE : 18.76 Mbit/s, 48.74 CAM-subs/s, URB-load: 6.66%, TS-miss: 0
    5. [136408.294683] +++ TS-BITRATE : 18.78 Mbit/s, 48.80 CAM-subs/s, URB-load: 6.66%, TS-miss: 0

    All works fine, minisatip logs clear.

    Code
    1. [12/02 13:34:13.238 signal]: BW 2324KB/s, Total BW: 1115 MB, ns/read 3539, r: 66, w: 335 fw: 0, tt: 233 ms
    2. [12/02 13:34:14.258 signal]: BW 2391KB/s, Total BW: 1117 MB, ns/read 3733, r: 68, w: 344 fw: 0, tt: 253 ms
    3. [12/02 13:34:15.283 signal]: BW 2390KB/s, Total BW: 1119 MB, ns/read 3715, r: 68, w: 343 fw: 0, tt: 252 ms
    4. [12/02 13:34:16.302 signal]: BW 2393KB/s, Total BW: 1122 MB, ns/read 3843, r: 68, w: 344 fw: 0, tt: 261 ms
    5. [12/02 13:34:17.320 signal]: BW 2394KB/s, Total BW: 1124 MB, ns/read 3708, r: 68, w: 344 fw: 0, tt: 252 ms


    BR,

    Yuri