Page 1 of 2 12 LastLast
Results 1 to 10 of 15
  1. Collapse Details
    How To Make a TS File for Debugging
    #1
    Join Date
    Dec 2010
    Location
    Atlanta, Ga.
    Posts
    8,188
    Post Thanks / Like
    Contribute If you enjoy reading the
    content here, click the below
    image to support our site.
    Click Here To Contribute To Our Site
    Note: Credits go to Athoik for providing the information that is needed to do this task!



    There are times that we need to capture the transport stream in order to study a problem or to do other things. Some think that recording a service using VLC or some other media player will work because a TS file may be generated as the out put file. Understand that this is not the case and is not the correct procedure for making a ts file that is useful for debugging or analyzing problems.

    We can make a useful ts file by carefully entering some telnet commands into a fta receiver that has a few tools loaded into it. Not all enigma2 images will have the tools we need for a ts file, so I suggest using the latest versions of the SatDreamGr image or an OpenPLi image. Really it does not matter what image you use, but the tools that are needed will have to be available for download using telnet.

    Using telnet, we need to download and install these items at minimum.
    (1) dvbsnoop
    (2) dvbapp-test

    We do this using these commands.
    opkg update
    opkg install dvbsnoop
    opkg install dvbapp-tests

    The first step in making a proper ts file is getting the pids. Tune to the transponder you want to record and get the best signal possible.The time of day may also be considered. A lot of times, there will be less pids on a transponder late at night as compared to the middle of the day. So keep this in mind as pids are the key!

    Use dvbsnoop to capture pids. In telnet, Enter the following:
    dvbsnoop -s pidscan
    PID Scanning will start once the command is entered. This may take some time, depending on the transponder.
    Here is an example:
    ---------------------------------------------------------
    root@osninopro:~# dvbsnoop -s pidscan
    dvbsnoop V1.4.55 -- [Only registered and activated users can see links. ]

    ---------------------------------------------------------
    Transponder PID-Scan...
    ---------------------------------------------------------
    PID found: 0 (0x0000) [SECTION: Program Association Table (PAT)]
    PID found: 1 (0x0001) [SECTION: Conditional Access Table (CAT)]
    PID found: 16 (0x0010) [SECTION: Network Information Table (NIT) - actual network]
    PID found: 17 (0x0011) [SECTION: Bouquet Association Table (BAT)]
    PID found: 20 (0x0014) [SECTION: Time Date Table (TDT)]
    PID found: 128 (0x0080) [SECTION: Program Map Table (PMT)]
    PID found: 161 (0x00a1) [SECTION: DVB CA message section (EMM/ECM)]
    PID found: 162 (0x00a2) [unknown]
    PID found: 164 (0x00a4) [SECTION: DVB CA message section (EMM/ECM)]
    PID found: 165 (0x00a5) [SECTION: DVB CA message section (EMM/ECM)]
    PID found: 166 (0x00a6) [SECTION: DVB CA message section (EMM/ECM)]
    PID found: 167 (0x00a7) [unknown]
    PID found: 168 (0x00a8) [unknown]
    PID found: 170 (0x00aa) [SECTION: DVB CA message section (EMM/ECM)]
    PID found: 171 (0x00ab) [SECTION: DVB CA message section (EMM/ECM)]
    PID found: 172 (0x00ac) [SECTION: DVB CA message section (EMM/ECM)]
    PID found: 173 (0x00ad) [SECTION: DVB CA message section (EMM/ECM)]
    PID found: 174 (0x00ae) [unknown]
    PID found: 175 (0x00af) [SECTION: DVB CA message section (EMM/ECM)]
    PID found: 176 (0x00b0) [SECTION: DVB CA message section (EMM/ECM)]
    PID found: 177 (0x00b1) [SECTION: User private]
    PID found: 178 (0x00b2) [SECTION: User private]
    PID found: 256 (0x0100) [unknown]
    PID found: 4098 (0x1002) [PS/PES: ISO/IEC 13818-3 or ISO/IEC 11172-3 audio stream]
    PID found: 4103 (0x1007) [PS/PES: ISO/IEC 13818-3 or ISO/IEC 11172-3 audio stream]
    PID found: 4109 (0x100d) [PS/PES: ISO/IEC 13818-3 or ISO/IEC 11172-3 audio stream]
    PID found: 4111 (0x100f) [PS/PES: ISO/IEC 13818-3 or ISO/IEC 11172-3 audio stream]
    PID found: 4113 (0x1011) [PS/PES: ISO/IEC 13818-3 or ISO/IEC 11172-3 audio stream]
    For transponders with a lot of pids, it may be better to use this command because it will only list the pids:
    dvbsnoop -s pidscan| awk '/PID found/ { print $3 }' | xargs

    The next step will be to record the pids. Some things need to be considered.
    (1) TS recordings can become large in a short period of time.
    (2) Receivers will have different amounts of room in the root file system that can be used for recording.
    At this point, it should be explained that when a receiver is asked to make a file, it will store it in the present directory unless another directory chosen!
    When entering telnet, you are in the root directory which is /home /root. Here is an example:
    root@osninopro:~#
    What directory you use will depend on the hard drives or usb drives that are connected to the receiver.
    For a small ts file, using the root directory will be fine, but I suggest using either usb or hard drive to create a ts file. I suggest this for more than One Reason.

    To set the correct directory for ts file storage, we need to know the path to the usb or hard drive and use the "cd" command to set it. I have an usb drive connected to the receiver, so we will use it as an example. usb drives and hard drives can be located under /media in the receiver. Select the path and change the directory.
    Here is an example for my usb drive:
    root@osninopro:~# cd /media/usb
    root@osninopro:/media/usb#
    We may begin the recording of the TS file after finding the pids and setting the CORRECT directory for recording. This is simple to do and is done using this command:
    test_dvr new_full.ts [PIDS]
    The above command will produce a ts file named "new_full.ts" on the directory we set earlier.
    An actual example taken from theabove dvbsnoop output will look like this:
    test_dvr new_full.ts 0 1 16 17 20 128 160 256 4109 4111 4113
    in telnet You may use "Ctrl c" to break the recording or stop the recording.

    How big the ts file gets is up to you. The size of the file really depends on the information in the pids, and the length of time that is used for recording. A ts file of some radio stations may run for 10 or more minutes and not get above 50 megabyte in size. A transponder that has several videos may get to 50 megabytes in a few minutes. It just depends.

    This thread is Open for discussion of capturing the ts file, and what can be done with it afterwards.
    Reply With Quote
     

  2. Thanks Megatron817, eastof111 thanked for this post
  3. Collapse Details
    #2
    Join Date
    Mar 2018
    Location
    West Central Florida
    Posts
    618
    Post Thanks / Like
    Using the vuzero4k and Openpli 7.0rc could not get dvbapp-tests installed so switch over to Satdreamgr-6 got it installed but never could get any pids to scan. Just kept going back to root@vuzero4k after about 30 seconds of the pidscan.
    Thanks
    Reply With Quote
     

  4. Collapse Details
    #3
    Join Date
    Dec 2010
    Location
    Atlanta, Ga.
    Posts
    8,188
    Post Thanks / Like
    Is the receiver set to a transponder you want to record?
    What is the signal strength for the transponder you are trying to record?
    Reply With Quote
     

  5. Collapse Details
    #4
    Join Date
    Mar 2018
    Location
    West Central Florida
    Posts
    618
    Post Thanks / Like
    I didn't get to the recording part but yes it was set to a transponder with good signal. even tried an atsc channel. I lost audio on the atsc channel while the pidscan was running so it was doing something just went back to root@vuzero4k like it was waiting for the next command but it did not show any pids found like you had posted in your example.
    Reply With Quote
     

  6. Collapse Details
    #5
    Join Date
    Dec 2010
    Location
    Atlanta, Ga.
    Posts
    8,188
    Post Thanks / Like
    Does terminal show Transponder PID-Scan...?
    ---------------------------------------------------------
    Transponder PID-Scan...
    ---------------------------------------------------------
    Reply With Quote
     

  7. Collapse Details
    #6
    Join Date
    Mar 2018
    Location
    West Central Florida
    Posts
    618
    Post Thanks / Like
    yes I get that part just no pids like you show in the example. Just loaded satdreamgr-5 and it is doing the same thing.
    Reply With Quote
     

  8. Thanks el bandido thanked for this post
  9. Collapse Details
    #7
    Join Date
    Mar 2018
    Location
    West Central Florida
    Posts
    618
    Post Thanks / Like
    Got the same results with Openpli 6.2
    Last edited by Megatron817; 12-24-2018 at 12:56 PM.
    Reply With Quote
     

  10. Thanks el bandido thanked for this post
  11. Collapse Details
    #8
    Join Date
    Dec 2010
    Location
    Atlanta, Ga.
    Posts
    8,188
    Post Thanks / Like
    As a test, remove the ATSC usb device, reboot the box and retry. (Do not restart enigma2. Do a reboot.)
    .
    .
    .
    Meine Dreambox One ist ein Stück Scheiße!.
    Reply With Quote
     

  12. Collapse Details
    #9
    Join Date
    Mar 2018
    Location
    West Central Florida
    Posts
    618
    Post Thanks / Like
    Removed HDD and usb full reboot same result went back to satdreamgr-6 same result. vuzero4k must not be compatible or some thing is wrong with mine.
    Reply With Quote
     

  13. Thanks el bandido, eastof111 thanked for this post
  14. Collapse Details
    #10
    Join Date
    Dec 2010
    Location
    Atlanta, Ga.
    Posts
    8,188
    Post Thanks / Like
    Pidscan is not supported on Vu+ Zero 4K.
    Most of the other dvbsnoop commands work on Zero 4K, but not pidscan.
    Reply With Quote
     

  15. Thanks rayydio, Megatron817 thanked for this post
Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •