[gstreamer-bugs] [Bug 489107] Autoscan for GstTuner interface

GStreamer (bugzilla.gnome.org) bugzilla-daemon at bugzilla.gnome.org
Fri Nov 2 03:19:59 PDT 2007


If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=489107

  GStreamer | gst-plugins-base | Ver: HEAD CVS




------- Comment #4 from Edgard Lima  2007-11-02 10:19 UTC -------

Ok, so.

1- scanning is up to the application
2- we need to add the following methods to GstTuner
  a- (int) get_max_frequency() - so application knows what the maximum value
for 'set_frequency' (the next step would be loop around)
  b- (int) get_min_frequency() - to know the min value
  c- (step, units) get_frequency_step() - it is the resolution of the tuner
* for all of them there is something similar in v4l2 spec

3- Danilo, instead of have a get_max_signal_strength, I think we could have
pre-defined values (for example, from 0 to 100, or else from 0 to 1000). I mean
just need to be documented in GstTuner interface, and the plugins would have to
convert different strength ranges for it. 
* I think it is like this already for GstTuner (I'm not sure)
* I think it is like this for v4l2 spec (ie there is a defined range)


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=489107.




More information about the Gstreamer-bugs mailing list