Debug.log

[Tony]

Hi bards,

 

Please explain to me what it means to write ParseSI in the debug log and what is repeating write ParseSI Bad CRC, lasting a several tens of minutes (simply please)...

 

[Derrick]

SI contains important tables for the allocation of programs (PAT) and the corresponding stream_ pids (PMT). These tables are protected by crc. Bad crc means the application is receiving garbage..

[Tony]

Thanks Derrick, so I understand it. .. This means, for example, that the DVBV constantly repeatedly attempts to load the SI table, but for a failure in the income, or because the table is transmitted only occasionally, with trouble-free reception of the remainder? Or is it the usual accompanied DVB reception? ParseSi Bad CRC I recorded on my both computers, DVB-C and DVB-T (from my cable provider).

Solution, of course, to specialists, but the problem is ...

[Derrick]

..the SI tables are part of the normal transport stream. Means the stream is broken.

[Tony]

OK Derrick, it seems so. At first I thought that these disorders can be associated with a communications of the program and the tbsCIapi library or CAM. It indicated that another test with a record FTA station. In contrast, this conclusion is contrary to the fact that similar ParseSI disorders also occur on another computer with a DVB-T dual-tuner (with the Recording Service). The next two tests, by contrast, seems to confirm that this is the fault of the occasional stream, regardless of whether the station is FTA or srambled…

 

The problem apparently is not related to the problematic card yet TBS6680, many thanks for the clarification of the problem ...

Edited August 8, 2013 by Tony

[Tjod]

It can be related to a CAM. To test that you should remove the CAM from the CI. Sometimes FTA channels are affected by a CAM.

But it can be as well a reception problem. Or something else.

You can take a look at View > Filters > DVB Source > Discontinuities
While watching TV.
http://www.DVBViewer.com/griga/DVBSource%20E/DVBSource.html

Or TransEdit > Analyzer > Missing

[Tony]

During this afternoon I conducted more tests from various multiplexes, the debug log files showed absolutely no ParseSI Bad CRC.

If I sometimes View > Filters > DVB Source > Discontinuities, I never notice the discontinuity. Similarly, TransEdit > Analyzer > Missing not shows any packet loss (of course, there are examples).

Before, I did not follow this issue, but probably its occurrence depends on the time of day and in many other circumstances, as, for example, any network maintenance or on the source of the signal (the cable from the TV studios, satelite reception, etc.)

 

I just needed a kick in the right direction...

Edited August 8, 2013 by Tony