[RELEASE] MythBox for XBMC - a MythTV Front-end Python Script for XBMC - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: Add-on Support (https://forum.kodi.tv/forumdisplay.php?fid=27) +---- Forum: Program Add-ons (https://forum.kodi.tv/forumdisplay.php?fid=151) +---- Thread: [RELEASE] MythBox for XBMC - a MythTV Front-end Python Script for XBMC (/showthread.php?tid=43115) |
RE: Myth 0.24 fixes and Pre-Eden - droeders - 2012-03-28 (2011-09-18, 16:18)nojstevens Wrote: Hello, Jon, I think I'm having the exact same problem as you with LiveTV and my HD PVR. I'm actually using an IR blaster for channel changing, and it takes about 10 seconds for the change to finish. By the time this finishes, it appears that XBMC has timed out the stream. For the record, playback of existing recordings from my HD PVR work perfectly under XBMC - using either the built-in myth protocol or the MythBox add-on. If I simply change the mythtv backend to used /bin/true as the channel change script, LiveTV works perfectly. Obviously, the channel has to be changed manually, but this might be a good test for you to see if this works. This behaviour has convinced me that I'm running into some type of timeout condition. I posted a thread here (Live TV with Mythtv and Hauppauge HD PVR) asking about mythtv timeouts before I found your post. I'd be interested to hear if this "workaround" behaves the same on your end. RE: [RELEASE] MythBox for XBMC - a MythTV Front-end Python Script for XBMC - marcmerlin - 2012-03-31 Does anyone use ACPI suspend with xmbc running on a mythtv-backend? I currently have mythfrontend setup so that when it exits I get back to mythwelcome and mythbackend then will run a mythsuspend script to do suspend to RAM. The important thing though is that it programs my RTC clock so that it wakes up in time for the next recording schedule. I'm going to guess that if I just use XBMC's suspend feature, it will just suspend and my PC will not wake up for its next recording. How does one do ACPI suspend with xbmc on a PC that is also running a myth backend? Thanks, Marc RE: [RELEASE] MythBox for XBMC - a MythTV Front-end Python Script for XBMC - vskatusa - 2012-04-03 Mythbox 1.1.0 + EDEN Whenever I click on recordings I get a window pop up msg " cannot import name decodelonglong" - When I press the ESC key the popup vanishes...Any fix on this? RE: [RELEASE] MythBox for XBMC - a MythTV Front-end Python Script for XBMC - fiveisalive - 2012-04-03 (2012-04-03, 00:56)vskatusa Wrote: Mythbox 1.1.0 + EDEN I get the same problem. Not sure what the problem/fix is. RE: [RELEASE] MythBox for XBMC - a MythTV Front-end Python Script for XBMC - vskatusa - 2012-04-04 This message never appeared in the XBMC 10.1 + Previous version of mythbox RE: [RELEASE] MythBox for XBMC - a MythTV Front-end Python Script for XBMC - SilkBC - 2012-04-08 I just installed MythBox and when I go into my recordings, not all of them show up. I only see four recording and when I check MythTV itself it shows I have 9. In fact, the recording for one TV show aren't even showing up! Is this a known bug, or have I likely mis-configured something? Let me know what additional info you need. :-) -SilkBC RE: [RELEASE] MythBox for XBMC - a MythTV Front-end Python Script for XBMC - essence25 - 2012-04-14 Does mythbox require an actual MythTV dedicated computer to use the tuner? Not sure how to use this with XBMC Eden and HDHomerun tuner no other computers or devices.. Is this just a remote control for something else? After I create missing database I get: Table 'mythconverg.settings' doesn't exist RE: [RELEASE] MythBox for XBMC - a MythTV Front-end Python Script for XBMC - marcmerlin - 2012-04-14 Yes, you need a working mythtbackend setup to use mythbox. You need to get mythtv working first. RE: [RELEASE] MythBox for XBMC - a MythTV Front-end Python Script for XBMC - nickr - 2012-04-15 Any news of mythbox support for myth 0.25? RE: [RELEASE] MythBox for XBMC - a MythTV Front-end Python Script for XBMC - marcmerlin - 2012-04-22 I tried getting it to talk to myth 0.25, and as expected it did not work. I'm not sure if it's safe to just raisde the protocol number in the code, or not. 17:11:18 T:2841082736 NOTICE: MythBox: loggerIniFile = /home/mythtv/.xbmc/addons/script.mythbox/mythbox_log.ini 17:11:21 T:2841082736 ERROR: settings.py:222 | MainThread | Unsupported protocol: 72 Traceback (most recent call last): File "/home/mythtv/.xbmc/addons/script.mythbox/resources/src/mythbox/settings.py", line 219, in verifyMythTVConnectivity session = Connection(self, translator=self.translator, platform=self.platform, bus=EventBus(), db=db) File "/home/mythtv/.xbmc/addons/script.mythbox/resources/src/mythbox/mythtv/conn.py", line 207, in __init__ self.db_init() File "<string>", line 1, in <lambda> File "/home/mythtv/.xbmc/addons/script.mythbox/resources/src/mythbox/mythtv/db.py", line 87, in inject_db return func(*args, **kwargs) File "/home/mythtv/.xbmc/addons/script.mythbox/resources/src/mythbox/mythtv/conn.py", line 215, in db_init self.cmdSock = self.connect() File "<string>", line 1, in <lambda> File "/home/mythtv/.xbmc/addons/script.mythbox/resources/src/mythbox/mythtv/db.py", line 87, in inject_db return func(*args, **kwargs) File "/home/mythtv/.xbmc/addons/script.mythbox/resources/src/mythbox/mythtv/conn.py", line 242, in connect raise ProtocolException('Unsupported protocol: %s' % protocol.serverVersion) ProtocolException: Unsupported protocol: 72 RE: [RELEASE] MythBox for XBMC - a MythTV Front-end Python Script for XBMC - dteirney - 2012-04-22 If anyone using MythBox is interested in being able to test some code changes that I've made to (in theory) support Myth 0.25 please have a look at: http://forum.xbmc.org/showthread.php?tid=129021 RE: [RELEASE] MythBox for XBMC - a MythTV Front-end Python Script for XBMC - mitch.capper - 2012-04-22 0.25 support should be in the official plugin soon, if you are in a rush though I have a branch at: https://github.com/mitchcapper/mythbox which I will keep up to date with whatever protocol changes I make. RE: [RELEASE] MythBox for XBMC - a MythTV Front-end Python Script for XBMC - bgood - 2012-04-26 Been using Mythbox for a while now and first off I'd just like to say a big thanks, it's an excellent plugin I was wondering if it would be possible to have a small feature added to it, I'd like a watched notification, whether it be a tickbox as used in the rest of xbmc in Movies etc or something else I don't mind but it would be really useful to see which recordings have been watched and which haven't. I used to use Mythtv frontend to view recordings and it has a watched icon available within that so it seems to me the feature is supported by both Mythtv and xbmc so hopefully it wouldn't be too hard to implement, here's hoping anyway. RE: [RELEASE] MythBox for XBMC - a MythTV Front-end Python Script for XBMC - SilverLining - 2012-05-02 (2012-04-22, 04:13)dteirney Wrote: If anyone using MythBox is interested in being able to test some code changes that I've made to (in theory) support Myth 0.25 please have a look at: Great! Initially I installed from zip file, on top of my previous Mythbox (which was giving the protocol 72 error) and continued to get the error. Then I de-installed Mythbox and re-installed from zip file. This time it worked. Many thanks. RE: [RELEASE] MythBox for XBMC - a MythTV Front-end Python Script for XBMC - SilverLining - 2012-05-03 (2012-05-02, 12:59)SilverLining Wrote:(2012-04-22, 04:13)dteirney Wrote: If anyone using MythBox is interested in being able to test some code changes that I've made to (in theory) support Myth 0.25 please have a look at: GROAN! I spoke too soon. All the menus work and the test works but recordings don't play - no error mesage - just nothing happens. Below is the relevant log file extract. It looks like it might be something to do with "unable to load file". I have checked and user01 is a member of the mythtv group so should have access to the recordings folder. Any suggestions? Code: 10:49:04 T:140511004489472 NOTICE: -->Python Interpreter Initialized<-- |