All posts by js
Below are all of js's postings, with the most recent are at the bottom of the page.
According to this post
https://www.avforums.com/…2373
Winter Hill is not the only transmitter affected.
Searching for the generic term "uklocal.tv", which is the offending string in the offending CRIDs, brought up:
Local TV Limited - Wikipedia
Presumably those are affected too.
| link to this comment |
signs of hope:
Sony 870 (and all Sony HXD and some Pioneers) DVD Recorders - No Freeview | Page 44 | AVForums
the cause:
https://ibb.co/WHSsVGF
| link to this comment |
Karl: These "slashless CRIDs" are actually valid in this case.
default_authority = madeinliverpool.tv
CRID authority = uklocal.tv
From ETSI TS 102 323
Digital Video Broadcasting (DVB); Carriage and signalling of TV-Anytime information in DVB transport streams
6.3 Default authority and abbreviated CRIDs
6.3.1 Abbreviated CRID rules
In certain situations described in the present document a CRID string may use the following abbreviated forms. These reduce the overhead of a CRID string by leaving out information that can be inferred from the location of the CRID entry.
Firstly, the characters "crid://" may be omitted from the start of the string so that the string starts with the first character of the CRID authority. So the example CRID:
crid://company.com/foobar
may be encoded as:
company.com/foobar
Additionally, within the scope of the definition of a default authority (see clause 6.3.2), the CRID authority part of the string may also be omitted if the CRID's authority matches the current value of default authority. In this case the string starts with the delimiter between CRID authority and data parts of the CRID (i.e. "/"). Therefore, the example CRID:
crid://company.com/foobar
may be encoded as:
/foobar
6.3.2 Scope of a default authority definition
A default authority is defined by the presence of a default authority descriptor. The purpose of the default authority is to allow a CRID reference within the scope of such a definition to leave out the protocol and authority parts of a CRID URI, if the CRID authority part of that CRID reference is the same as the defined default authority.
The scope of a particular value of default authority is defined by the location of the default authority descriptor. A value of default authority defined in a scope overrides any value of default authority already defined for a wider, enclosing scope. See table 15 for definitions of the permitted locations of the default authority descriptor and which scope override which others.
| link to this comment |
I thought it might be worth trying to contact the creators of this problematic EIT data.
Local TV Limited - Wikipedia
An attempt to visit uklocal.tv gave this message:
Your connection is not secure
The owner of uklocal.tv has configured their website improperly. To protect your information from being stolen, Tor Browser has not connected to this website.
uklocal.tv uses an invalid security certificate. The certificate expired on 01 May 2024 11:00. The current time is 04 July 2024 10:44.
There is an option to "Add exception..." which I did.
The page which then came up merely said:
"We are updating our website.
Please bear with us while we work our magic"
- nothing there then.
What they have done overrides the existing default_authority "madeinliverpool.tv" with "uklocal.tv"
There are two ways to fix these CRID strings so they are harmless.
"uklocal.tv" is removed from the start of the CRID string enabling the existing default_authority "madeinliverpool.tv" to be used.
"uklocal.tv" is removed from the start of the CRID string and the default_authority is changed to "uklocal.tv"
In each case the CRID string then starts with "/"
| link to this comment |
Karl:
Yes, fixed by removing "uklocal.tv" from the start of the CRID strings.
The fix:
https://ibb.co/Sy2sGby
This time the CRIDs were valid, but not so on previous occasions.
Sony should have fixed the firmware long ago.
| link to this comment |
Karl: I looked at the firmware file, it's encrypted.
I hadn't noticed before that the UK DTT spec, which is not freely available, and which has been uploaded to wikileaks, was filed there under Sony!
https://wikileaks.org/sony/docs/?q=DTG&filter=3
It's what I used to try to understand the legality of those dodgy CRIDs:
D-Book 7 part A v 1.pdf
It refers to "ETSI TS 102 323" for the basic definition of CRIDs:
The content identifier descriptor (CID), defined in ETSI TS 102 323 [98], is used to associate a CRID with an event and is placed within the event loop of EIT.
https://tech.ebu.ch/docs/metadata/ts_102323v010401p.pdf
| link to this comment |
I had a real hard time locating those wikileaks files.
One gets the impression of wikileaks data being blocked.
A search, using DuckDuckGo, for "D-Book" site: wikileaks.org said "No results found for "D-Book" site: wikileaks.org."
Fortunately, nobody posted direct links here:
BBC Four HD | free and easy for 21 years
nobody knows who nobody is and he's not telling.
| link to this comment |
Friday 28 June 2024 3:20PM
Though no expert in this area, it seems to me that apart from the slashless aspect, there seems to be a lack of understanding by whoever created that EIT data.
By analogy with the following example BBC EIT data, there should be firstly a Series CRID and then different Item CRIDs for each item in the series.
From the same EIT dump:
North West series crids 2024 06 28 030220
TOT.UTC_time = Fri 28 Jun 03:02
service_name = "BBC ONE W Mid"
onid.tsid.sid = 233A.1045.1045
default_authority = fp.bbc.co.uk
{
programme = "Weather for the Week Ahead"
{
crid = /b-4N160, type = 32, series
date, duration, eventID, itemCRID
Fri 28 Jun 00:25, 00:05, 4980, /m/13XOM
Sat 29 Jun 00:55, 00:05, 49B5, /m/13XPU
Sun 30 Jun 02:00, 00:05, 49D3, /m/1436C
Sun 30 Jun 12:10, 00:05, 49DC, /m/1436Q
Mon 01 Jul 03:00, 00:05, 49EF, /m/14374
Tue 02 Jul 02:40, 00:05, 4A04, /m/142RH
Wed 03 Jul 02:05, 00:05, 4A18, /m/142S2
Wed 03 Jul 23:40, 00:05, 4A3A, /m/142VU
}
programme = "Breakfast"
{
crid = /b-3RHJ6, type = 32, series
date, duration, eventID, itemCRID
Fri 28 Jun 05:00, 03:30, 499B, /m/13XPB
Sat 29 Jun 05:00, 04:00, 49BB, /m/1435W
Sun 30 Jun 05:00, 03:00, 49D5, /m/1436G
Mon 01 Jul 05:00, 03:30, 49F1, /m/142R0
Tue 02 Jul 05:00, 03:30, 4A06, /m/142RL
Wed 03 Jul 05:00, 03:30, 4A29, /m/142VD
Thu 04 Jul 05:00, 03:30, 4A1A, /m/142VY
}
...
- just saying