Just out of curiosity...

I don't really know much about UPnP but is it possible (or does it even make sense) to extend MythBackend to be a MediaRenderer.  Yes, I mean MythBackend not MythFrontend.  What I'm talking about here is the ability for the Myth backend to capture content being streamed by a MediaServer.

This may seem odd, but let me explain where I'm coming from here.  I noticed, for example, that Bill Maher is now featured in a "show" on Amazon.com called "Amazon Fishbowl" (dumb name).  Anyway, if Amazon opened this up via the UPnP protocol (does that even make sense, like I said, I'm ignorant UPnP in general) could I set up myth to record it?

I guess what I'm wondering is, could UPnP be the protocol that, DRM issues aside, unifies all the possible content sources out there (Google Video, Amazon.com, IPTV) so they are all addressable for the purposes of recording from a DVR?

Just a question.

--
Mike

On 1/18/06, David Blain <[EMAIL PROTECTED]> wrote:

>
> > 7) Open issues:
> >
> > One thing that I don't have time to implement that is
> needed for off
> > the shelf devices to work is an implementation of a
> standard transport stream.
> > I was thinking RTSP/RTP.
> >
>
> Doesn't UPnP just define HTTP GET as the current method for
> this?  From what I've seen after doing some network sniffing,
> our D-Link UPnP Media Renderer does HTTP GETs when grabbing files.
>
> ~Lou

The method used to access the resources (videos, ...) is based on which
<res> elements are listed in the CDS response and which of those the client
knows how to access.

The least common denominator is usually http, however, if we implement
RTP/RTSP I think the support for streaming would be a richer experience
(assuming a server controlled stream) that would allow the use of commercial
cut points and other advanced features.  (I still need to research the
details to make sure I understand the features of the protocol).

HTTP is what I am planning as the first protocol, to make sure everything is
working correctly.  I listed RTP as an open issue in my previous e-mail,
since it's something I know I will not have time to address for some time to
come.

David B.


_______________________________________________
mythtv-dev mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

_______________________________________________
mythtv-dev mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

Reply via email to