HDHomeRun
Dustin Oprea
myselfasunder at gmail.com
Tue Nov 13 23:26:01 PST 2012
I've been trying to read the RTP feed from my HDHR tuner with zero success.
Does anyone have experience with this?
GStreamer:
gst-launch --gst-debug=udpsrc:5 udpsrc port=5000
caps="application/x-rtp,media=(string)video,format=(fourcc)I420,
width=(int)720,
height=(int)480,encoding-name=(string)RAW,sampling=(string)YUV,pixel-aspect-ratio=(fraction)8/9,
framerate=(fraction)30000/1001, interlaced=(boolean)true" ! gstrtpbin !
rtpvrawdepay ! filesink location=/tmp/output
* I got the capabilities via autodetection somehow, at some point.
HDHR:
hdhomerun_config 1310DA25 set /tuner2/target udp://192.168.5.102:5000
When I try to send via RTP (rtp://192.1685.102:5000, instead of using UDP,
as above), I get a UDP error every time, no matter what the capabilities,
whenever it sinks to gstrtpbin:
ERROR: from element /GstPipeline:pipeline0/GstUDPSrc:udpsrc0: Internal data
flow error.
I'm assuming this means that capabilities don't match between linked pads.
When I use the UDP scheme (originally, above), I don't get any errors, but
no data moves through the pipeline.
--gst-debug on various elements at various levels didn't give me anything
useful.
VLC works perfectly, whether I'm sending to rtp://xxx.xxx.xxx.xxx:nnnn and
receiving on rtp://:nnnn, or sending to udp://xxx.xxx.xxx.xxx:nnnn and
receiving on udp://:nnnn.
Any thoughts?
Also, is GST not able to automatically identify capabilities of the RTP
stream? I don't know how I tripped over it (in order to get the
capabilities, above), but it doesn't seem very intuitive. It seems like
that if VLC (super-versatile) could do it, GStreamer (also super-versatile)
could do it.
Thanks.
Dustin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20121114/b7f4b31c/attachment.html>
More information about the gstreamer-devel
mailing list