Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#5764 closed defect (fixed)

EIT fix introduced in [16054] and [16055] are not needed any more

Reported by: j.suarez.agapito@… Owned by: Janne Grunau
Priority: minor Milestone: 0.21.1
Component: eit Version: 0.21-fixes
Severity: low Keywords: eit encoding
Cc: Ticket locked: no

Description

Hello to everybody:

Some time ago I had reported some issues with the EIT data aired by some Spanish TV broadcasters (namely those with transportid's 10, 12, 13 and 6200), which got solved by changesets [16054] and [16055]. The patch has worked perfectly until 1 month ago, more or less (strange characters appear again). In order to troubleshoot the issue, I tried reverting the changes introduced by those changesets. I have been running 0.21-fixes with those changes reverted for more than 3 weeks and now the EIT data from those broadcasters looks OK. It seems that those broadcasters (or whoever is responsible for those transportid's) changed the encoding and now there is no enconding trouble anymore. There is no more need to specify encoding since they are using the default.

I would thank you if those changesets were reverted.

Best regards, José

P.S. Thanks for all the active development in trunk (and not forgetting 0.21-fixes at the same time). Keep up the good work. I'm really looking forward to enjoying 0.22!

Attachments (4)

10.log (32.8 KB) - added by anonymous 11 years ago.
12.log (56.4 KB) - added by anonymous 11 years ago.
13.log (21.1 KB) - added by anonymous 11 years ago.
6200.log (28.7 KB) - added by anonymous 11 years ago.

Download all attachments as: .zip

Change History (10)

comment:1 Changed 11 years ago by Janne Grunau

Owner: changed from Stuart Auchterlonie to Janne Grunau
Status: newaccepted

the strange characters appear all over the texts? Strange, I doubt that they switched to ISO6937.

Can you please attach the output of "dvbsnoop -n 5 0x12" while your first DVB adapter is tuned to one of the multiplexes with broken text?

Changed 11 years ago by anonymous

Attachment: 10.log added

Changed 11 years ago by anonymous

Attachment: 12.log added

Changed 11 years ago by anonymous

Attachment: 13.log added

Changed 11 years ago by anonymous

Attachment: 6200.log added

comment:2 Changed 11 years ago by j.suarez.agapito@…

I have just attached the logs of dvbsnoop -n 5 0x12 of the transportid's in which the affected channels are. The logs are named just like the transportid's. By the way, the output of dvbsnoop was obtained while running mythbackend with the EITfixes reverted (mythtv was compiled this morning at aprox. 13:00 GMT+2, but with those EITfixes lines removed from eithelper.cpp).

As whether the strange characters appear on the EIT guide, they don't appear when the EITfixes are reverted, and the "good" special characters (such as ñ and the ones described in ticket #3549) do appear correctly. Before reverting the changeset the strange characters appeared where the "good" special characters should appear.

Thanks for the time trying to get this solved. Should you need any further info, please feel free to ask.

Best regards, José

comment:3 Changed 11 years ago by Janne Grunau

I'll revert the changesets since there is now the correct encoding specified.

Are you running latest fixes? I'm asking since the correct encoding should have been used.

comment:4 Changed 11 years ago by Janne Grunau

Resolution: fixed
Status: acceptedclosed

(In [18544]) remove now unneeded EIT encoding for some spanish DVB-T multiplexes. Fixes #5764

comment:5 Changed 11 years ago by Janne Grunau

(In [18545]) backports [18544] from trunk

Removed no longer needed EIT encoding override for spanish DVB-T multiplexes. Refs #5764

comment:6 Changed 11 years ago by j.suarez.agapito@…

Yes, I was running latest 0-21-fixes svn (as of yesterday, 4 October 2008, at 13:00 GMT+2) with those lines you have just removed in [18544] and [18545] commented (with two slashes: , so the effect is the same as if they didn't exist). So now the eithelper.cpp code in 0-21-fixes and trunk are the same I was running yesterday, and EIT showed perfect.

Thanks for the fast fix!

Regards

Note: See TracTickets for help on using tickets.