Submitted by Athanasios Oikonomou

Link to original bug (#758916)

Description

Currently there there are differences between elements with connection-speed property.

There are three ranges in total, 0 to 2147483 mmssrc/4294967 dashdemux,hlsdemux,mssdemux/18446744073709551.

Is there a reason having connection-speed not as guint64?

Here are all elements with connection-speed property.

dashdemux
connection-speed : Network connection speed in kbps (0 = calculate from downloaded fragments)
flags: readable, writable
Unsigned Integer. Range: 0 - 4294967 Default: 0

decodebin
connection-speed : Network connection speed in kbps (0 = unknown)
flags: readable, writable
Unsigned Integer64. Range: 0 - 18446744073709551 Default: 0

hlsdemux
connection-speed : Network connection speed in kbps (0 = calculate from downloaded fragments)
flags: readable, writable
Unsigned Integer. Range: 0 - 4294967 Default: 0

mmssrc
connection-speed : Network connection speed in kbps (0 = unknown)
flags: readable, writable
Unsigned Integer64. Range: 0 - 2147483 Default: 0

mssdemux
connection-speed : Network connection speed in kbps (0 = calculate from downloaded fragments)
flags: readable, writable
Unsigned Integer. Range: 0 - 4294967 Default: 0

playbin
connection-speed : Network connection speed in kbps (0 = unknown)
flags: readable, writable
Unsigned Integer64. Range: 0 - 18446744073709551 Default: 0

rtspsrc
connection-speed : Network connection speed in kbps (0 = unknown)
flags: readable, writable
Unsigned Integer64. Range: 0 - 18446744073709551 Default: 0

uridecodebin
connection-speed : Network connection speed in kbps (0 = unknown)
flags: readable, writable
Unsigned Integer64. Range: 0 - 18446744073709551 Default: 0