<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 11/15/2010 11:44 AM, Travis Tabbal wrote:
<blockquote
cite="mid:AANLkTi=g9jra0rfV6+izK7fFt5kSct=OX=k8j4ZZkJcj@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">On Mon, Nov 15, 2010 at 12:35 PM, Brad
Templeton <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:brad%2Bmyth@templetons.com">brad+myth@templetons.com</a>></span>
wrote:<br>
<div> </div>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">That's a bit of work. While
Android is linux based, android apps are
JVM based, only a very few blessed apps (like the web browser etc.)
get to be in C. So it means writing a frontend in a language that
compiles to Java. You aren't going to write your video playback in
java, but I have to presume the GTV platform, which I have not
examined, has APIs to stream videos in the GTV way (including their OSD
stuff etc.)<br>
<br>
</div>
</blockquote>
<div><br>
That's not entirely correct. You can write apps in C on Android, you
need Java for the UI, but they provided an NDK for that. It's basically
JNI. So if you have a clean C library you can easily attach a Java UI
to it with those tools. It does lock you to the hardware, but as they
are mostly ARM right now, that's not so bad. And you could include JNI
libraries for other platforms if you needed to. I'm not sure it's
really worth it, but if GTV takes off, it might be a nice thing to have
around. For myself, GTV doesn't seem to offer anything I can't do with
Myth, that I care about anyway. Some of the streaming stuff is mildly
interesting, but I get issues streaming on my internet connection. I'd
rather do downloads/recordings/rips. <br>
</div>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
mythtv-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>
<a class="moz-txt-link-freetext" href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a>
</pre>
</blockquote>
Thanks for the correction on the C apps.<br>
<br>
I think it is true right now that there is not much more in GTV than
Myth, but I think, unless Google fails at this, that this will change
quite a bit as Android apps are written for the GTV and an app ecology
develops. Rumours are of a lot of TV and STB vendors integrating GTV.<br>
<br>
However, there is still a list of things in GTV that Myth does not do
that make it interesting. To sum them up:<br>
<br>
a) Play of various for-pay streaming services such as Netflix, Amazon
VOD etc.<br>
b) Access to data from some cable/sat STB/DVRs, including listings
data, current stored recordings<br>
c) Ability to control said STB/DVRs both to queue recordings, play
recordings and issue remote control commands over IP<br>
d) Ability to do pass-through of HDMI video streams with modification,
including placing OSD on top of stream, zooming/PIP etc.<br>
e) Integrated search over may sources of video and audio<br>
f) Integrated queue combining recordings and RSS videocast feeds<br>
g) Better integration with web browser, with web pages having ability
to offer feeds, and interact with GTV.<br>
<br>
E, F and G can be added to MythTV. I think so can B and C. D may be
difficult and A would require linux players for these pay services.<br>
<br>
However, my main thought is that this is just the beginning, and to
judge GTV at present would be like judging the initial Android phones
or iPhones before their app stores arrived.<br>
</body>
</html>