{"action":"closed","issue":{"url":"https://api.github.com/repos/tsduck/tsduck/issues/160","repository_url":"https://api.github.com/repos/tsduck/tsduck","labels_url":"https://api.github.com/repos/tsduck/tsduck/issues/160/labels{/name}","comments_url":"https://api.github.com/repos/tsduck/tsduck/issues/160/comments","events_url":"https://api.github.com/repos/tsduck/tsduck/issues/160/events","html_url":"https://github.com/tsduck/tsduck/issues/160","id":379022063,"node_id":"MDU6SXNzdWUzNzkwMjIwNjM=","number":160,"title":"EIT Issues","user":{"login":"WinSta0","id":44887511,"node_id":"MDQ6VXNlcjQ0ODg3NTEx","avatar_url":"https://avatars2.githubusercontent.com/u/44887511?v=4","gravatar_id":"","url":"https://api.github.com/users/WinSta0","html_url":"https://github.com/WinSta0","followers_url":"https://api.github.com/users/WinSta0/followers","following_url":"https://api.github.com/users/WinSta0/following{/other_user}","gists_url":"https://api.github.com/users/WinSta0/gists{/gist_id}","starred_url":"https://api.github.com/users/WinSta0/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/WinSta0/subscriptions","organizations_url":"https://api.github.com/users/WinSta0/orgs","repos_url":"https://api.github.com/users/WinSta0/repos","events_url":"https://api.github.com/users/WinSta0/events{/privacy}","received_events_url":"https://api.github.com/users/WinSta0/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":14,"created_at":"2018-11-09T04:49:04Z","updated_at":"2018-12-06T10:51:03Z","closed_at":"2018-12-06T10:51:03Z","author_association":"NONE","body":"Hello everyone,\r\n\r\nI have been learning about DVB-T and its operations from the transport stream to the transmission. So far, I have been able to get; NIT, PAT, PMT, SDT, TDT to all work and display the video and audio to the DVB compliant set top box and TV. However, unfortunately I haven’t quite gotten the EIT to display on the set top box or the TV.\r\n\r\nI have been able to generate an EIT table containing 2 sections: Event 1 and Event 2 (with their text and parental rating descriptor) using the OpenCaster version 3.2.2. The EIT table is then multiplexed with the other tables through OpenCaster to create a DVB-T compatible stream. This works with both receivers (including the EIT).\r\n\r\nWith the TS stream working on both receivers I used TSDuck to dump: NIT, PAT, PMT, SDT, TDT and finally the EIT. Using the command “tstabdump EIT.bin” show me two sections. However, when I convert the bin file to xml then back to bin, I see only one section (instead of two). I have been able to play around the xml file and some of TSDuck’s commands. I been able to get very close (to the original bin file) with two sections displaying but both are Section 0 instead of Section 0 at the top and Section 1 below. I use the command ”tstabdump EIT-ReComp.bin” to verify.\r\n\r\nI would like to know if I’m missing something and what I can do through advice in the TSDuck forums in GitHub to fix the issue. The commands I used to retrieve the EIT:\r\n\r\n“tsp -I file tsdump.ts -P tables --pid 18 --binary-output EIT.bin -O drop”\r\n\r\n“tsp -I file tsdump.ts -P tables --pack-all-sections --all-once --pid 18 --binary-output EIT.bin -O drop”\r\n\r\nThe Commands I used to decompile the bin file to xml:\r\n“tstabcomp -d EIT.bin”\r\n\r\nThe Commands I used to compile the xml file back to bin:\r\n“tstabcomp -c EIT.xml -o EIT_ReComp.bin”\r\n\r\nI have attached 2 text files: 1 “Working EIT.txt” and 2 “Non-Working EIT”.\r\n\r\nI hope this is not too long. Wanted to cover some ground.\r\n\r\nAlexander\r\n[Working EIT.txt](https://github.com/tsduck/tsduck/files/2564630/Working.EIT.txt)\r\n[Non-Working EIT.txt](https://github.com/tsduck/tsduck/files/2564631/Non-Working.EIT.txt)\r\n\r\n"}}
{"actor":{"display_login":"lelegard"}}