Just to be clear, I was not suggesting that MythTV and XMBC become one. I see them as quite different (XMBC doesn't record at all, right?). I just think that as a viewer, XMBC is damn fine.<br><br>I guess the only point I'm trying to make is that I hope the people adding Myth support for XMBC feel comfortable with the API for MythTV and that it is stable enough that they can maintain this functionality.
<br><br>P.S. - It is a damn shame that using XBMC isn't as simple as burning an ISO and sticking it into the XBox. That would be awesome.<br><br>--<br>Mike<br><br><div><span class="gmail_quote">On 12/7/05, <b class="gmail_sendername">
Justin Hornsby</b> <<a href="mailto:justin.hornsby2@ntlworld.com">justin.hornsby2@ntlworld.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Michael Tiller wrote:<br>> To be honest I have a hard time figuring out exactly what XMBC is doing<br>> just by looking at the user interface. It asks for the protocol version<br>> but it also wants the video files to be mountable across an SMB
<br>> connection. As far as I can tell, it isn't streaming anything (in the<br>> mythtv://... sense) but I'm not familiar enough with the internals and<br>> the protocol to really say for sure.<br>><br>> I managed to watch recorded shows but never tried live TV (although it
<br>> did ask where my ring buffer was stored on an SMB filesystem).<br>><br>> Based on my very limited experience with XMBC, it looks very<br>> impressive. It would be great if the two communities worked toward some
<br>> kind of integration. With the XBox 360 out and prices on used XBoxs<br>> falling, I would seriously consider an XBox over a MediaMVP. The MVPs<br>> are OK but their video quality and robustness are a bit of an issue.
<br>><br>> --<br>> Mike<br><br>The XBMC Python scripts for MythTV use MySQL to interrogate the database<br>about recording names, channel IDs etc (so you see a pretty name for<br>your recorded shows rather than just the bare filename). The protocol
<br>information (AFAIK) is only used to determine that it's really a Mythtv<br>backend it's connecting to, and that it's there. As it relies on an SMB<br>share to access the files, you can safely assume it's not talking to the
<br>backend the same way a genuine mythtv frontend would ;-)<br><br>The rest of what the scripts do is basically talking to the XBMC API<br>(what there is of it) and telling it what files to play.<br><br>As for XBMC & Mythtv becoming integrated, even to a small extent - I
<br>think maybe hell will freeze over first, seen as XBMC needs to be<br>compiled using 'borrowed' Microsoft development tools. That said, work<br>has been going on for a considerable amount of time, on a _true_ open<br>
source development kit. How work on that will continue to progress now<br>attention has shifted towards the Xbox360, is anybody's guess.<br><br>Regards,<br>Justin<br>_______________________________________________<br>mythtv-users mailing list
<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></blockquote></div>
<br>