DVB plugins warnings and fixmes – a question of protocol

[Russel Winder]

dvbbasebin and dvbsrc in the bad plugins issue some warnings and fixme
messages when using GST_DEBUG=3 that have raised some questions that: a) I do
not know the answer to; b) I do not know if they are issues that need
addressing; or c) are just the way things are and nothing to get concerned
about. Rather than dive in and put in issues on the Freedesktop GitLab
instance, I thought I should ask here first for advice and guidance.

The context is using a playbin with a dvb: protocol URL, so that the pipeline
is self organising.

On connecting to a channel, the data for which is read from
~/.config/gstreamer-1.0/dvb-channels.conf, using DVB-T I get messages like:

0:00:08.865429323 13437 0x7f915c7138f0 WARN              dvbbasebin parsechannels.c:394:parse_and_configure_from_v5_conf_file:<source> Failed to map property 'NETWORK_ID'
0:00:08.865478116 13437 0x7f915c7138f0 WARN              dvbbasebin parsechannels.c:394:parse_and_configure_from_v5_conf_file:<source> Failed to map property 'TRANSPORT_ID'
0:00:08.865496877 13437 0x7f915c7138f0 WARN              dvbbasebin parsechannels.c:394:parse_and_configure_from_v5_conf_file:<source> Failed to map property 'VIDEO_PID'
0:00:08.865513864 13437 0x7f915c7138f0 WARN              dvbbasebin parsechannels.c:394:parse_and_configure_from_v5_conf_file:<source> Failed to map property 'AUDIO_PID'
0:00:08.865532943 13437 0x7f915c7138f0 WARN              dvbbasebin parsechannels.c:394:parse_and_configure_from_v5_conf_file:<source> Failed to map property 'PID_0b'
0:00:08.865550489 13437 0x7f915c7138f0 WARN              dvbbasebin parsechannels.c:394:parse_and_configure_from_v5_conf_file:<source> Failed to map property 'PID_06'
0:00:08.865568444 13437 0x7f915c7138f0 WARN              dvbbasebin parsechannels.c:394:parse_and_configure_from_v5_conf_file:<source> Failed to map property 'PID_05'

a person in ATSC land reported:

0:00:09.349178668 31776 0x7f18ba13acd0 WARN              dvbbasebin parsechannels.c:394:parse_and_configure_from_v5_conf_file:<source> Failed to map property 'VCHANNEL'
0:00:09.349221591 31776 0x7f18ba13acd0 WARN              dvbbasebin parsechannels.c:394:parse_and_configure_from_v5_conf_file:<source> Failed to map property 'VIDEO_PID'
0:00:09.349232275 31776 0x7f18ba13acd0 WARN              dvbbasebin parsechannels.c:394:parse_and_configure_from_v5_conf_file:<source> Failed to map property 'AUDIO_PID'

it seems strange that crucial information about a tuning is being ingord and
yet things work. Either something weird is happening or the warnings are
actually somewhat spurious.

The there is the slew of:

0:00:08.887920646 13437 0x7f915c7138f0 WARN                  dvbsrc gstdvbsrc.c:2226:gst_dvbsrc_output_frontend_stats:<dvbsrc0> There were errors getting frontend status information: 'Unknown error 524'

after tuning is successful these are still reported which is very strange. If
524 is an error should it be an error rather than a warning?

Then in DVB-T land, I get:

0:00:09.140760842 13437 0x7f91578af280 FIXME                default gstutils.c:3981:gst_pad_create_stream_id_internal:<dvbsrc0:src> Creating random stream-id, consider implementing a deterministic way of creating a stream-id
0:00:09.228170117 13437 0x7f915c92b590 FIXME             mpegtsbase mpegtsbase.c:416:mpegts_base_add_program: Refcounting. Setting twice a PID (0x0010) as known PSI

In ATSC land:

0:00:09.635194879 31776 0x7f18ba13acd0 FIXME                 dvbsrc gstdvbsrc.c:2097:gst_dvbsrc_is_valid_trans_mode: No transmission-mode sanity checks implemented for this delivery system
0:00:09.635240150 31776 0x7f18ba13acd0 FIXME                 dvbsrc gstdvbsrc.c:2161:gst_dvbsrc_is_valid_bandwidth: No bandwidth sanity checks implemented for this delivery system
0:00:09.762229952 31776 0x7f18ba13acd0 WARN                  dvbsrc gstdvbsrc.c:2226:gst_dvbsrc_output_frontend_stats:<dvbsrc0> There were errors getting frontend status information: 'Invalid argument'
0:00:10.130042694 31776 0x7f18b29fd940 FIXME                default gstutils.c:3981:gst_pad_create_stream_id_internal:<dvbsrc0:src> Creating random stream-id, consider implementing a deterministic way of creating a stream-id

These can't be errors, so do they actually need fixing?

Whilst I'd prefer not to do any more C programming ever, if these things are
deemed in need of work, and Alessandro Decina and Reynaldo H. Verdejo Pinochet
were around for mentoring, I'd take a go at progressing things. After putting
in a bug report.

-- 
Russel.
===========================================
Dr Russel Winder      t: +44 20 7585 2200
41 Buckmaster Road    m: +44 7770 465 077
London SW11 1EN, UK   w: www.russel.org.uk

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20190111/584af045/attachment.sig>