OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Raspberry Pi (https://forum.kodi.tv/forumdisplay.php?fid=166) +---- Thread: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) (/showthread.php?tid=250817) 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
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
|
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - Vimes - 2016-04-04 I have gone back to build 330 and it is perfect, displaying the 3D icon as I would expect.... you can see the 3D symbol on the right. Once I get to a build where it no longer functions would you need me to produce logs, not sure how they could help in this display problem....? RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-04-04 (2016-04-04, 17:48)Vimes Wrote: Once I get to a build where it no longer functions would you need me to produce logs, not sure how they could help in this display problem....? Start with just the build number of the first bad build. Hopefully it will be obvious from the commits that went in that day where the problem came from. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - Vimes - 2016-04-04 (2016-04-04, 17:54)popcornmix Wrote:(2016-04-04, 17:48)Vimes Wrote: Once I get to a build where it no longer functions would you need me to produce logs, not sure how they could help in this display problem....? ok worked my way through the builds one at a time and the problem started with the 3D icon missing on build 402. as you can see the same film is now listed as HD and not 3D.... the same applies to all my other 3D films. Thankfully it is a display issue only as the TV / Kodi still switches to SBS 3D when selected. But I do not know what are 2D or 3D films at the moment. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - niwa2 - 2016-04-04 I got the Same Problem. 3D.MVC shows as HD as well on 0403. Same problem with the confluence skin. Also I just noticed that opening a 3D I so file takes quite long. It takes 15-20s over a nfs share to open. I am not sure if it was always that long, but it does not feel right taking so long. The exact same movie as mkv opens instantaneously. And while testing the 3D flag I noticed that some of my 3D iso files do not play anymore. I have no idea when this started. I guess this could be ffmpeg 3 related In the log I first tried to play a file that now fails and the one that is still working. Debug Log And another thing I noticed with the updated confluence skin: The transparencys now work again (thank you guys for that by the way). But they work a little bit too well. The message boxes that you acknowledge with an OK-Button are fully transparent now. You can only see the text and the button. This should also be in the logs: when the first movie did not play I got a transparent message that at least one file could not be played. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - dekani - 2016-04-04 Thank you for your great work. I'm using Kodi profiles. Since it isn't possible to enable/disable Live TV manually in TV settings, I must disable/enable PVR addons to see Live TV menu option when I'm connected. I have no EPG notifications and LiveTV menu is hidden when I'm connected. (addons are correctly started but first EPG notifications and LiveTV menu only appear when I disable/enable a PVR addon - TVHeadEnd and IPTV Simple client are used - both addons must be disabled/enabled if I want to see all channels) Can be related to a specific setting? I have tried to remove addons, EPG and TV databases with no more success. Re: RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-04-05 (2016-04-04, 16:13)Vimes Wrote: Any ideas as to why films which are correctly tagged as being 3D, and were previous list in the list view with that label, are now showing as HD....? If you switch to Confluence (from the repository) does that show 3D? Edit: it pays to read all unread posts before replying... Confluence has the same issue, apparently. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-04-05 New OpenELEC.tv Krypton build #0404: RPi / RPi2 (Supercedes previous build) Code: # uname -a Based on tip of OpenELEC.tv master (0026734b, changelog) and tip of XBMC master (1e620a01, changelog) with the following modifications:
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-04-05 (2016-04-04, 21:40)niwa2 Wrote: And another thing I noticed with the updated confluence skin: Can you provide a screenshot, or a way to reproduce? The yes/no/cancel dialogs I've seen are all appearing correctly in Confluence 3.0.7 with #0404. Make sure you've updated to Confluence 3.0.7 as 3.0.6 had broken/missing textures. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - Vimes - 2016-04-05 (2016-04-05, 04:20)Milhouse Wrote:(2016-04-04, 16:13)Vimes Wrote: Any ideas as to why films which are correctly tagged as being 3D, and were previous list in the list view with that label, are now showing as HD....? This was also an issue for Android and whilst I am unsure if the fix could be related at all here was the solution.... https://github.com/koying/SPMC/commit/d3b86c1a0be79f2b30a6f343ed4d96f03e8d5937 RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - carl535 - 2016-04-05 As of Sun night (early Mon morning) kodi had not pushed an update to Confluence 3.0.7 It was however in kodi master so I had to manualy update That did fix my transparent small rectangle boxes RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - toppot - 2016-04-05 (2016-03-31, 13:30)toppot Wrote: ... However (besides the lack of adding top level many items, and some other) the main reason I run with Rapier is due to some strange bug in TV mode (with Estuary). Some HD channels take 3-5 seconds to start, some mostly fails.. SD works fine. My TVHeadend is 4.1.xxx running on another server (Debian). With Rapier all channels (actually except 1, but that is just crazy strange - and only if I start in that channel) tune in in ~1 second... At some point in the distant past I changed gpu_mem=256 to 128Mb......... Now that it is back at 256, Live TV works as expected with both Rapier and Estuary skins! - Just to inform, if other had seen strange behavior.. Still funny that somehow Estuary requires a bit extra gnu_mem compared to Rapier - but never mind.. Also: an update and a question. I am now on Libreelec 405. Is that the same as openelec 404 I am confused how come versions are not exactly the same, and how come openelec builds appear to be slightly more frequent than Libreelec (this one is for you Milhouse..) The update: former problems with rare audio stutter seems gone. "adjusting playback to display" has been of for quite some time, but still it seems some small adjustments was made in the first 2 sec. of TV playback (around version 329 through 330... could be fewer or more).. This seems ALL GONE now - thanks This (Libreelec 0405) seems VERY stable for me - only problem still remaining since 3xx (both Openelec and Libreelec) is that somehow it seems that when idling for a long time the RPI2 seems to freeze.. Not sure if it is when I turn on TV (CEC remote), or just from the idling... All in CEC and screensaver is set to NOT sleep (it dims the screen, thats all) - but still this problem. (killing kodi is often possible, but not always). And this is not from 5 min. idling (when screensaver kicks in), but perhaps after 1+ hour... Dont know if it could be related to the "io_is_busy" changes - but now testing this Libre405 to see if it has improved. One thing has improved (since Libre403), and that is now it appears to stay in "underclock" speed 98% of the time when idling (and 90+% when playback), previously it would switch to overclock 30-60% of the time idling... EDIT: Nope - still same problem... after 1,5 hour "something" made it stay in "overclock" territory... It did respond when I turned on the TV (great), but "something" is started after a while... Annoying.. And most surprisingly - a killall -9 kodi.bin did NOT bring the cpu utilization down to where it was before the pause/idle... A reboot did help.... Will try to let bcmstat run to see when if rises..... (and probably I was just a bit impatient after killing kodi.bin... Only gave it 1 minute or something....) RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - mark_dj - 2016-04-05 Running build #1204 but after switching to the Confluence skin there's no way to go back to my different skin (Mimic). It tried to load the skin but ultimately does nothing and now I'm stuck with Confluence. This happens with other skins as well. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-04-05 (2016-04-05, 12:31)mark_dj Wrote: Running build #1204 but after switching to the Confluence skin there's no way to go back to my different skin (Mimic). It tried to load the skin but ultimately does nothing and now I'm stuck with Confluence. This happens with other skins as well. Are you using latest Mimic 4.x? http://forum.kodi.tv/showthread.php?tid=267268 The version in the repo doesn't support Krypton. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - mark_dj - 2016-04-05 (2016-04-05, 12:36)popcornmix Wrote:(2016-04-05, 12:31)mark_dj Wrote: Running build #1204 but after switching to the Confluence skin there's no way to go back to my different skin (Mimic). It tried to load the skin but ultimately does nothing and now I'm stuck with Confluence. This happens with other skins as well. That seemed to have done the trick. Thanks RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-04-05 (2016-04-05, 11:17)toppot Wrote: - Just to inform, if other had seen strange behavior.. Still funny that somehow Estuary requires a bit extra gnu_mem compared to Rapier - but never mind.. Not surprising. The gpu_mem required by GUI is very much skin dependent. The number of textures loaded determines GPU memory use, and Estuary with it's recently added/recommended widgets for TV shows and movies is quite expensive. |