Support opentv channel ids

[mspieth]

To enhance channel number support, parse opentv channel ids when scanning for new channels.

I have been running this for a long time.

[mspieth]

opentv channel id patch

[Klaas de Waal]

Thanks for the patch, I do want to use the channel numbers when available.

About OpenTV, for which signals/satellites/countries is this applicable?

For the implementation I want to use the region ID and bouquet ID fields that are now present in the video source. This avoid having to type the numbers again each time a scan is done. Implementation can be done similar to how Freesat and Sky channel numners are now done; selection of the additional pids is done based on the value of the original network ID.

For this I do need the original network ID (or ID's) of the networks which do use this channel numbering format.

Some of the service descriptor IDs are already in use, so for this I do need the PrivateDataSpecifierID values. This is also how it is now done for Freesat/Sky.

It would be useful if I had a capture of 30 seconds of the full transport stream of a representative signal.

[mspieth]

Replying to Klaas de Waal:

About OpenTV, for which signals/satellites/countries is this applicable?

Sky (US/IT/NZ/AU), Dishnet(US) and others I'm not aware of. Anything NDS related would be a guess but not sure about others around the world.

For the implementation I want to use the region ID and bouquet ID fields that are now present in the video source. This avoid having to type the numbers again each time a scan is done. Implementation can be done similar to how Freesat and Sky channel numners are now done; selection of the additional pids is done based on the value of the original network ID.

For this I do need the original network ID (or ID's) of the networks which do use this channel numbering format.

It probably doesn't matter as if these descriptors are available then the channel numbers are probably correct. If multiple logical channel number descriptions are available a choice could be presented to the user in setup, which info should be used.

Some of the service descriptor IDs are already in use, so for this I do need the PrivateDataSpecifierID values. This is also how it is now done for Freesat/Sky.

It would be useful if I had a capture of 30 seconds of the full transport stream of a representative signal.

This may be a problem. It has been a long time since I used this and was only experimental at the time as these services are encrypted normally, though the metadata is not. I will have to fire up my sat or cable card which I have not done in a while. I only used DVBT ATM. This would not be representative of anything but AU for network IDs.

There is a project of mine tvgrabdvbplus which I used other existing projects and fused them with the help of another. There was not freely available info at the time. This project is primarily a guide grabber for sat feeds.

If you don't want to use it due to the restrictions detailed, this is ok too.

[Mark Spieth <mspieth@…>]

In efbc436e3/mythtv:

Error: Processor CommitTicketReference failed

GIT backend not available

[Klaas de Waal <klaas@…>]

In aeafd8108/mythtv:

Error: Processor CommitTicketReference failed

GIT backend not available

[Klaas de Waal]

After testing with a captured Sky NZ stream from the Optus D1 satellite at 160E0 it turns out that channel numbers are already correctly scanned with the code that has been added for Freesat and Sky on the Astra2-28E2 satellite.

As a consequence, most of the OpenTV specific code, including the "Scan OpenTV" channel scanning option, will be removed again.

The code that relates to the additional PIDs that need to be scanned to get the OpenTV guide data will remain, although partially commented out, awaiting a possible future implementation.

[Klaas de Waal <klaas@…>]

In 209ac13295/mythtv:

Error: Processor CommitTicketReference failed

GIT backend not available