GNOME Bugzilla – Bug 354883
GParamSpecs of type GUINT give G_MAXUINT as -1
Last modified: 2006-10-06 17:54:55 UTC
Taking a property of the "queue" element as an example: $ gst-inspect-0.10 queue [...] Element Properties: [...] current-level-buffers: Current number of buffers in the queue flags: readable Unsigned Integer. Range: 0 - 4294967295 Default: 0 [...] Trying the same introspection in python: >>> import pygst; pygst.require ("0.10"); import gobject, gst >>> specs = gobject.list_properties (gst.element_factory_make ("queue")) >>> specs[1] <GParamUInt 'current-level-buffers'> >>> specs[1].maximum -1 This is on a 32-bit platform, if that matters. GINTs seem to work ok, for example textoverlay::deltax (min: -2147483648, max: 2147483647).
cutter::run-length is a guint64 whose max value of 18446744073709551615 comes out as -1L. audiotestsrc::timestamp-offset is an example of a gint64 with range -9223372036854775808 to 9223372036854775807. pygst reports min 0L, max -1L.
sounds like a problem in the python bindings
This should probably move to pygobject. I assume gtk+ doesn't really use 64 bit integers in properties, so this bug was undetected all the time.
Looks like a dup of bug #353943.
*** This bug has been marked as a duplicate of 353943 ***