Store channel type in database

[Stuart Auchterlonie]

Store channel type (TV/Radio/Data etc) into database when we find that information during channel scanning.

This information can then be leveraged in other areas, such as when setting up a recorder and the type of streams it expects to find.

[stuartm]

Milestone 0.25 deleted

[stuartm]

This seems like an interesting and very simple addition, one for 0.26 maybe?

[Stuart Auchterlonie]

Yes, its a good one for 0.26. Fixing the milestone

[Karl Egly]

I'd love to see us store the SD/HD/UHD/3D part of the service type, too. My plan is to use it in MFDB for a fixup similar to FixHD on EIT.

[Stuart Auchterlonie]

Milestone renamed

[Stuart Auchterlonie]

Moving remaining open tickets to 0.28.2 milestone

[Stuart Auchterlonie]

Moving remaining open tickets to 29.2 milestone

[Klaas de Waal]

This would be useful to setup the buffering parameters for Live TV/Radio. At the moment the Live TV is setup for 8Mbit/s for all channels. This is OK for TV but for radio/audio-only channels a much lower setting would be better.

[Stuart Auchterlonie]

Klaas you are welcome to do this.

Regards Stuart

[Klaas de Waal]

It looks like the best value to use for channel type is the service_type as described in the DVB Bluebook A038, Feb 2019, pages 82 and 83. The way to do this is to extend database table channel with a field service_type and copy the service_type into this field when found during the channel scan.

[Stuart Auchterlonie]

Klass, this just needs a DB schema update to add an appropriate column, and then the code as you mention to store the relevant info

[Klaas de Waal]

Column service_type is added to database table channel in commit 8ae1c0b7958f3693ca4361bc9d116e55958a47ad which bumps the database schema version to 1352.

The code to retrieve and store the data as described in comment:15 is added in commit c7ad89a7eb999982c702eda9347603a9a7a1f532.

[Klaas de Waal <kdewaal@…>]

In 8ae1c0b79/mythtv:

Update database schema to version 1352

Revert type change in update to version 1351, part of
commit 6f876b31e9e1a3dbc4f1ef3a27d58f25daacae07
In update to version 1352:

• change type of region_id and bouquet_id from int to unsigned int
• add service_type to table channel for ticket #8774
• change schema version number to 1352

Refs #8774

[Klaas de Waal <klaas@…>]

In bba208158/mythtv:

Support for channel service_type in services API

Add support for service_type in the C++ code of the services API.
Partial support added for perl, python and php bindings.

Refs #8774

[Klaas de Waal]

The possible values of the service_type are enumerated in file dvbdescriptors.h in class ServiceDescriptorMapping?.

An example on how to use this class:

#include "dvbdescriptors.h"
{
    uint32_t service_type = ServiceDescriptorMapping::kServiceTypeDigitalTelevision;
    ServiceDescriptorMapping st(service_type);
    LOG(VB_GENERAL, LOG_INFO, QString("service_type:%1 '%2' IsDTV:%3")
        .arg(st.ServiceType()).arg(st.toString()).arg(st.IsDTV()));
}

which gives the following output:

service_type:1 ' (TV)' IsDTV:1