+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: PVR & Live TV Support (https://forum.kodi.tv/forumdisplay.php?fid=167)
+---- Forum: Windows Media Center (WMC) (https://forum.kodi.tv/forumdisplay.php?fid=205)
+---- Thread: WMC as the backend - released (/showthread.php?tid=171216)
Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
RE: WMC as the backend - released - b_pritchard - 2013-11-14
@krustryreturns
Good news, the old version works like a charm! I'm 100% up and running again. I'm thinking something got borked in the latest builds... i'd be happy to test any changes you guys make as you make them! Just lemme know.
Thanks again for all the help.
Cheers!
RE: WMC as the backend - released - goblygoop - 2013-11-14
slightly confused on the builds. The one that's "xbian/openelec"..is that for ALL openelec's (intel, ion, fusion) or only pi openelec's?
RE: WMC as the backend - released - krustyreturns - 2013-11-14
(2013-11-14, 17:05)goblygoop Wrote: slightly confused on the builds. The one that's "xbian/openelec"..is that for ALL openelec's (intel, ion, fusion) or only pi openelec's?
That is only for pi's, I will correct it. Thanks.
(2013-11-14, 15:00)b_pritchard Wrote: @krustryreturns
Good news, the old version works like a charm! I'm 100% up and running again. I'm thinking something got borked in the latest builds... i'd be happy to test any changes you guys make as you make them! Just lemme know.
Thanks again for all the help.
Cheers!
Good. I'll let the guy know who does the apple compile and hopefully get the new version sorted out.
RE: WMC as the backend - released - ktjensen - 2013-11-14
(2013-11-13, 21:02)krustyreturns Wrote:(2013-11-13, 20:48)ktjensen Wrote: You might try the plugin MCEremote to work on the mapping of keys. Just a guess as that tool could help.
Maybe that will solve this 'record' button thing: In testing instant record, hoops just pointed out to me that the 'record' button on an mce remote does not do anything and so far I cannot get a remote mapping that will make it work. I will check into this plugin, thanks for the tip.
be careful with this plugin. it remapped my skip ahead, and skip back, and green launch buttons. Had to do a system restore to get them back.
New question: wonder is the RASPBERRY PI client will work on the OUYA platform.
RE: WMC as the backend - released - krustyreturns - 2013-11-14
(2013-11-14, 18:44)ktjensen Wrote: be careful with this plugin. it remapped my skip ahead, and skip back, and green launch buttons. Had to do a system restore to get them back.
New question: wonder is the RASPBERRY PI client will work on the OUYA platform.
I never tried it. I did enough research to find that to complely run xbmc from a cheap mce remote requires changing the registry. Since I only use this remote for devel it wasn't worth it. I now press the 'record' button by using control-r on the keyboard.
The OUYA is android so I don't except the rpi build to work.
RE: WMC as the backend - released - goblygoop - 2013-11-14
Thanks krusty. I don't know how to get you a +1 reputation. The product works really well
wishing someone will make an ouya client for this awesome backend
RE: WMC as the backend - released - krustyreturns - 2013-11-14
(2013-11-14, 19:58)goblygoop Wrote: Thanks krusty. I don't know how to get you a +1 reputation. The product works really well
wishing someone will make an ouya client for this awesome backend
Click on my name, go to reputation and then rate - you know... since you asked...
There was a user who was working behind the scenes to get the OUYA developers to incorporate it. They expressed some interest, asked some questions, but it seems to have gone quiet - so its not looking good. It would be nice if someone would take a stab at doing an generic android build (if such a thing exists), some have said they would try but I have never heard back from them.
RE: WMC as the backend - released - Jmhthefirst - 2013-11-14
eagerly awaiting and ouya or Android version here too!
RE: WMC as the backend - released - goblygoop - 2013-11-14
(2013-11-14, 20:07)krustyreturns Wrote:(2013-11-14, 19:58)goblygoop Wrote: Thanks krusty. I don't know how to get you a +1 reputation. The product works really well
wishing someone will make an ouya client for this awesome backend
Click on my name, go to reputation and then rate - you know... since you asked...
There was a user who was working behind the scenes to get the OUYA developers to incorporate it. They expressed some interest, asked some questions, but it seems to have gone quiet - so its not looking good. It would be nice if someone would take a stab at doing an generic android build (if such a thing exists), some have said they would try but I have never heard back from them.
Feel like a idiot cause I can't find any buttons to give +1 in your profile. Maybe I have to have 10 posts or something.
WMC as the backend - released - ktjensen - 2013-11-15
Is it best to get MYSQL running and share EPG in your network with multiple clients? Or is that taken care of SERVERWMC itself ?
RE: WMC as the backend - released - scarecrow420 - 2013-11-15
I guess it'd be interesting to hear from someone who did put the LiveTV databases on MySQL. I noticed in the wiki it says you can do this, but havent tried it myself.
My unsubstantiated opinion is that I dont see many benefit to sharing it so I wouldnt say it's "Best". I sort of think that even if they were sharing an EPG database, each client would still send through EPG update requests so it wouldnt cut down on the number of requests to the server, not that the number of requests are concerning anyway - ServerWMC can easily handle sending the EPG data to any client that asks for it. I guess one conceivable benefit would be all clients having the same EPG info at the same time, rather than them all being on their own staggered update timers (assuming they werent all started up at the same time).
Personally I set my clients to not to store EPG data in the database at all, because I am happy to get it every time i start XBMC up (and thus get the most up to date stuff) rather than only every 2 hours or whatever the default is. I have noticed that my EPG often has basic timings for a show that is on later that day, eg 8:30pm - 9:30pm but as it draws closer, the times change to 8:32pm - 9:36pm or whatever. I dont know if this is an Australian thing or what... In Oz our WMC doesnt download EPG data over the internet, it just gets it from the actual OTA channels. Ultimately I want to build something into the server that could have the clients do an EPG refresh whenever such timing changes are detected by the server from the WMC EPG service, but I am finding no time to do any development at the moment...
I do however use MySQL for the media (audio/video files) library but that is because it is useful to have the Watched and InProgress statuses or music ratings/favourites etc sync between XBMC clients and there is alot more metadata about multiple TB's worth of TV show and movies and MP3's, as compared to the reasonably small amount of data that is in the EPG and the quickness that the EPG can be loaded from ServerWMC (as compared to how slow it is for an XBMC client to scrape the information from movie/tv/audio files)
RE: WMC as the backend - released - TechLife - 2013-11-15
What do you want to know about it Scarecrow? I am running mine on MySQL. Mainly because I have everything else there so all of my clients stay in sync like you do. I'm not sure in this case there is much of a difference. As you said, it's not like we're storing much info there. I haven't tried it the other way so I can't really give a good comparison.
RE: WMC as the backend - released - scarecrow420 - 2013-11-15
I just meant that I havent tried having the EPG database in MySQL because I cant really foresee what the benefit would be.
A couple of things you could test I suppose:
When sharing the database does only 1 client request EPG refreshes from the ServerWMC and the others realise that the EPG data is always "current" or do they all just go ahead and request it anyway? You could probably determine this by having multiple clients running and checking the ServerWMC log to see who/when EPG requests come in.
How in sync are they, do they seem to be instant? Eg if you do a manual channel EPG refresh on one client, are those refreshed times or new EPG entries immediately shown on the other clients?
Are recording entries transferred from ServerWMC also in this database? Eg if you setup a recording on one client, when do the other clients see it? They all poll for recordings frequently anyway but perhaps if this is in the XBMC database the other clients know about them sooner than they would otherwise
As mentioned, Im struggling to see the benefit of doing it, eventhough I do have the other XBMC databases shared on MySQL. To me the TV/EPG stuff is OK to be per client, particularly when we have the backend server tying everything together and providing data to the clients anyway. This isnt the case with normal XBMC for video/music etc which I guess is another reason why the database helps for that, as it's a type of common backend between multiple clients
RE: WMC as the backend - released - TechLife - 2013-11-15
Great questions. I'll play it with a bit this weekend and see what I find. Now I'm curious...
RE: WMC as the backend - released - svanhess - 2013-11-15
(2013-11-14, 17:19)krustyreturns Wrote:(2013-11-14, 15:00)b_pritchard Wrote: @krustryreturns
Good news, the old version works like a charm! I'm 100% up and running again. I'm thinking something got borked in the latest builds... i'd be happy to test any changes you guys make as you make them! Just lemme know.
Thanks again for all the help.
Cheers!
Good. I'll let the guy know who does the apple compile and hopefully get the new version sorted out.
Yeah I'm guessing that my upgrade to Mavericks a couple of weeks ago caused this. It looks like we should probably stay away from OS X 10.9 until all the issues are sorted out.
I'm loading up a 10.8 VM and will rebuild the 1013 packages. Thanks b_pritchard for helping test this out!