-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"packet BAD CRC32 PID : 18" Errors on not high used Transponder #277
Comments
I think the stone old was just not computing CRC ....
I see this issue is closed, did you found the source of the problem ?
Brice
…On Tue, Oct 12, 2021 at 5:45 PM SourceDoctor ***@***.***> wrote:
Closed #277 <#277>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#277 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACRID7T6U3FM4C3GDXJ6W3UGRJ3NANCNFSM5F2XQZ5Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
i didn't find cause of the issue. |
btw, i could use "BAD CRC32 PID" recognization via API :-) |
I don't remember exactly but I think there is a bad packet counter in the
API that should correspond to that
On the driver side I had CRC32 issue if the lna was not activated in the
module parameters for some cards. Maybe this could give you a direction to
look for !
…On Tue, Oct 12, 2021 at 9:01 PM SourceDoctor ***@***.***> wrote:
btw, i could use "BAD CRC32 PID" recognization via API :-)
do you have some plans to implement it somewhere for error detection?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#277 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACRID2OYBLWKN3MA6LNXHDUGSAZHANCNFSM5F2XQZ5Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
thanks for the hint. I have the same issue on all cards of the same type and i don't think they all have been damaged at the same time. |
@braice Other DVB applications don't have this issue Issue causing example is: Transponder at moment only contains CNN with 4,4Mbit/s which means above 90% Null Pids on Transpnder Maybe some misscalculation with Null Pids?
|
@braice |
Hello
I gave it some thoughts and you might be on the right track about
miscalculation
The reason is that only one PID seem affected by the CRC32 issue, while
with reception issues it is spread across the whole stream
As you have your test setup up and running could you show me what CRC32
mumudvb computes (should be in the verbose logs) and what is expected and
computed from other software.
Maybe even a small TS dump might prove useful
Best
Brice
…On Fri, Oct 15, 2021 at 11:59 AM SourceDoctor ***@***.***> wrote:
@braice <https://github.com/braice>
there is definitly a problem.
I retried it on a small home Antenna Multiswitch Environment with CNN
Transponder and have the same problem
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#277 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACRIDZI5LNTRSYPRJKZCDDUG73Q3ANCNFSM5F2XQZ5Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
i logged some stuff with this command: Output can be downloaded here: If you need further data, tell me :-) |
@braice is this log enough, or do you need more information? |
Hello
After being tunnel vision on the CRC32 calculation I think I finally found
it !
It's triggering on a stuffing table which is not processed by MuMuDVB and
does not have a CRC32 in it
Can you please try to modify ts_check_raw_crc32 in ts.c and add the if
below ?
It should just ignore the CRC32 calculation for this table
Brice
int ts_check_raw_crc32(unsigned char *data)
{
int i,len;
uint32_t crc32;
tbl_h_t *tbl_struct;
tbl_struct=(tbl_h_t *)data;
// Stuffing table does not have CRC
if(tbl_h_t-> table_id == 0x72)
return 0;
…On Wed, Oct 20, 2021 at 10:33 PM SourceDoctor ***@***.***> wrote:
@braice <https://github.com/braice> is this log enough, or do you need
more information?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#277 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACRID22FTSABJYB54A3CTDUH4RSJANCNFSM5F2XQZ5Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
tried this one
Nethertheless i think this if clause is not wrong on this place :-) |
And you still have
Struct data table_id 0x72 section_syntax_indicator 0x01 section_length
0xb4 transport_stream_id 0xffff version_number 0x1f current_next_indicator
0x01 last_section_number 0xff
just before ?
…On Mon, Oct 25, 2021 at 5:35 PM SourceDoctor ***@***.***> wrote:
tried this one
(show differences in if clause), but still
""
Deb0: TS: packet BAD CRC32 PID : 18
int ts_check_raw_crc32(unsigned char *data)
{
int i,len;
uint32_t crc32;
tbl_h_t *tbl_struct;
tbl_struct=(tbl_h_t *)data;
// Stuffing table does not have CRC
if(tbl_struct->table_id == 0x72)
return 0;
...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#277 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACRIDYRAQGRPHX3AW6QEALUIV2LZANCNFSM5F2XQZ5Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Found it !
Should be a return 1 not a return 0 in the new piece of code
// Stuffing table does not have CRC
if(tbl_h_t->table_id == 0x72)
return 1;
…On Sat, Oct 30, 2021 at 8:36 PM Brice Dubost ***@***.***> wrote:
And you still have
Struct data table_id 0x72 section_syntax_indicator 0x01 section_length
0xb4 transport_stream_id 0xffff version_number 0x1f current_next_indicator
0x01 last_section_number 0xff
just before ?
On Mon, Oct 25, 2021 at 5:35 PM SourceDoctor ***@***.***>
wrote:
> tried this one
> (show differences in if clause), but still
> ""
> Deb0: TS: packet BAD CRC32 PID : 18
>
> int ts_check_raw_crc32(unsigned char *data)
> {
> int i,len;
> uint32_t crc32;
> tbl_h_t *tbl_struct;
> tbl_struct=(tbl_h_t *)data;
> // Stuffing table does not have CRC
> if(tbl_struct->table_id == 0x72)
> return 0;
> ...
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#277 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AACRIDYRAQGRPHX3AW6QEALUIV2LZANCNFSM5F2XQZ5Q>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
>
|
@braice
|
@braice
i receive continously CRC Errors with MuMuDVB on tuned Transponder which contains CNN (the only Service delivered on the whole transponder).
But a TV on same Multiswitch has no problems with receiving CNN.
also capturing with tsduck the transponder to a file and streaming CNN from it has no Errors.
i tried it with several Multiswitches, 2 different antennas and 3 different Tuner Cards
all the same result
I use current head on a Debian Buster
Log Output
configuration looks like this:
even "rewrite_eit=0" does not solve the problem.
Maybe an error in Null-Pid calculation?
The text was updated successfully, but these errors were encountered: