Bug #1219
Scanning of services on cable networks like Ziggo in The Netherlands is broken.
0%
Description
Scanning of services on cable networks like Ziggo in The Netherlands is broken.
Though the correct amount of services are detected, they don't get a 'service name'.
And the type of service is set to 'other' on all services, where it should say Radio. SDTV and so on.
A service looks like this:
{
"service_id": 232,
"pmt": 5415,
"stype": 0,
"scrambled": 0,
"channel": 112,
"dvb_eit_enable": 1,
"pcr": 4220,
"disabled": 0,
"stream": {
"pid": 4220,
"type": "MPEG2VIDEO",
"position": 0
},
"stream": {
"pid": 4221,
"type": "MPEG2AUDIO",
"position": 1
},
"stream": {
"pid": 4222,
"type": "AC3",
"position": 2
},
"stream": {
"pid": 5007,
"type": "CA",
"position": 262144,
"caidlist": [
{
"caid": 1540
}
]
}
}
while it should look like this: (same service)
{
"service_id": 232,
"pmt": 5415,
"stype": 1,
"scrambled": 1,
"channel": 112,
"provider": "Ziggo",
"servicename": "HBO 2",
"dvb_eit_enable": 1,
"pcr": 4220,
"disabled": 0,
"stream": {
"pid": 4220,
"type": "MPEG2VIDEO",
"position": 0
},
"stream": {
"pid": 4221,
"type": "MPEG2AUDIO",
"position": 1
},
"stream": {
"pid": 4222,
"type": "AC3",
"position": 2
},
"stream": {
"pid": 5007,
"type": "CA",
"position": 262144,
"caidlist": [
{
"caid": 1540
}
]
}
}
History
Updated by bas t about 12 years ago
This is related to one ore more commits of 11 september.
Using a checkout of 10 september, the issue does not exist.
Updated by Adam Sutton about 12 years ago
Hmmm, I've obviously cocked something up the new combined SDT parser. I'll try and take a look.
May need a bit of help testing it. Will see.
Adam
Updated by bas t about 12 years ago
Adam Sutton wrote:
Hmmm, I've obviously cocked something up the new combined SDT parser. I'll try and take a look.
May need a bit of help testing it. Will see.
Adam
ThatÅ› OK. After all it IS master.
I'll be glad to help testing, and shooting holes in your commits for that matter
Updated by Adam Sutton about 12 years ago
- Status changed from New to Fixed
- % Done changed from 0 to 100
Applied in changeset commit:b5263ac111d5723c974ae4afe7aa3f6e5393f110.
Updated by Adam Sutton about 12 years ago
- Status changed from Fixed to New
- % Done changed from 100 to 0
OK, interesting, think I've found the problem and its a bug I had previously fixed. My guess is I corrected it in one of my repos (I have one on laptop and one on my tvh server) and then forgot to push it back and overwrote with a forced pull.
Commit on its way.
Adam
Updated by Adam Sutton about 12 years ago
- Status changed from New to Fixed
Status incorrectly changed due to crossover of my posts.