[gstreamer-bugs] [Bug 152403] - Integrating externaly developped DVB source element

[bugzilla-daemon at bugzilla.gnome.org]

http://bugzilla.gnome.org/show_bug.cgi?id=152403
GStreamer | gst-plugins | Ver: HEAD CVS





------- Additional Comments From meiker at upb.de  2004-09-13 18:23 -------
On the properties of dvbsrc:

* pol: Is of type gchar. I had a patch for the core to accept g(u)char
properties on elements. However, with the introduction of gstvalue it was
rendered obsolete. The clean solution now is to add g[u]char support to
gstvalue. I'll file a bug.

* pidlist: Is another way to set the pids. It was intended that apps use this
instead of construction a string of pids. I'd agree if someone says it's
redundant , leads to confusion and should be removed.

* tune: From the command line u can't change the channel. For an app I figured
several ways to tune:
   1. Everytime a property is changed. (Everytime u tune, ~1-2sec pass by until 
      the signal is locked, so this is impractical)
   2. A separate pointer property "tune-channel" which is used to hand a struct  
      containing channel properties from app to dvbsrc (Would render all other  
      properties useless)
   3. Set all properties and finally set the special dvbsrc property tune
      (value will be ignored) to tune.

Maybe there is a more coherent way which i haven't thought about.

--------

README, fixed in current version, thx.

--------

gstdvbtv: this is merely an example program. However it should work.
There was something left from my debugging. The issue i was debugging
on is still not resolved. If I build the pipeline which works from the command
line in gstdvbtv something goes horribly wrong with the clocking. I disabled my
left overs from debugging, so if u start gstdvbtv u should see it too, unless it
was fixed in a very recent version of gstreamer.

--------

It's my fault. I tried on consistend naming of functions, and failed....
(fixed now)


I updated both packages on my server. Thx for your comments.

------- You are receiving this mail because: -------
You are the assignee for the bug.
You are the QA contact for the bug.