Open GoogleCodeExporter opened 8 years ago
It's not possible for apps that use the HME protocol(like streambaby) to append
to the NPL. Netflix is a special case that TiVo, Inc. has shoehorned in (btw,
Netflix in the NPL available to all the S3, HD and above Tivos, not just the
Premiere). pyTivo uses a different protocol, HMO, to announce shared videos to
the Tivo. It simply presents a formatted list of content it is is sharing to
the Tivo, and the Tivo unit handles the display and transfer functions.
Streambaby actually draws all of the graphics and text, as well as managing the
video display and playback controls. There are no publicly documented methods
(or even known hacks) to add HME apps, other kinds of content to the NPL, other
than HMO shares(pytivo, tivo desktop, and other tivos on the network are
examples of HMO shares).
It's within the remote realm of possibility for streambaby to implement the HMO
protcol, but then the end result would be a clone of the functionality pyTivo
already offers. Streaming wouldn't be possible, nor would the extended
functionalities streambaby offers like subtitling, extra metadata, and remote
file deletion. Unfortunately, you'd gain nothing over what pyTivo can already
provide.
Not saying it's a bad idea, but without help from TiVo, Inc. there's not much
the devs can do to change this.
Original comment by gonzotek
on 30 Sep 2010 at 6:34
Is it possible to look at the Netflix app, and what the Tivo is doing to put it
in the Now playing, and "Spoof" it so the Tivo thinks Streambaby is a second
netflix app, or something like that? Even if it required a hack on the Tivo
itself, it seems like it'd be useful.
Original comment by DSpaz...@gmail.com
on 30 Sep 2010 at 8:28
It might be, and this is really over my skill level, but my understanding is
that traffic between the tivo and services like Netflix and other 'official'
hme apps is encrypted. Some of the current streambaby functionality was
actually reverse engineered thanks to man-in-the-middle attacks on the
encryption: watching the traffic in either direction between the youtube app
and the servers enabled people to see what had to be done to get the tivo to
accept a video stream. The encryption and lack of support is also the reason
the 1.1GB buffer has never been overcome, no one outside of TiVo knows how to
request a larger buffer or how to discard the tail end of the buffer for more
content at the head end (or even if it's possible). If I can find the forum or
wiki posts I think I'm remembering I'll post them here in a comment for
reference.
Original comment by gonzotek
on 30 Sep 2010 at 11:33
Original issue reported on code.google.com by
DSpaz...@gmail.com
on 30 Sep 2010 at 4:21