OpenELEC Testbuilds for RaspberryPi (Kodi 16.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 16.0) (/showthread.php?tid=231092) 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
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
|
AW: RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Heiko123 - 2015-08-16 (2015-08-16, 07:13)Leopold Wrote:(2015-08-16, 01:47)Milhouse Wrote: Latest debug-enabled build #0815x: RPi / RPi2.In the Dev Update add-on I've added the debug builds as a new source. It is only enabled if the FAT partition is >= 384MB. Oo, what is now the differences between? The Fat partition >384MB only? But didn't everyone have sdcards > 500MB. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Leopold - 2015-08-16 (2015-08-16, 09:49)Heiko123 Wrote:(2015-08-16, 07:13)Leopold Wrote:(2015-08-16, 01:47)Milhouse Wrote: Latest debug-enabled build #0815x: RPi / RPi2.In the Dev Update add-on I've added the debug builds as a new source. It is only enabled if the FAT partition is >= 384MB. This refers to the first partition on the card which has a FAT file system, labelled 'System' and mounted at /flash. The rest of the space on the card is used for the ext4 'Storage' partition mounted at /storage. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - gandharva - 2015-08-16 (2015-08-14, 20:22)popcornmix Wrote:I made the changes and it also seems to work. No hangs. Can I safely remove all the config parameters now?(2015-08-14, 20:20)gandharva Wrote: No But again, there was a crash during video playback. No crashlog... I think this one is not related to the hangs/lockups I initially reported. Maybe I need to install a debug build... RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-08-16 (2015-08-16, 13:39)gandharva Wrote: I made the changes and it also seems to work. No hangs. Can I safely remove all the config parameters now? Okay, remove all config.txt parameters and try again. Last night's build did include an overclock related fix that may help. If you have a crash (where kodi disappears and relaunches) then catching that with a debug build would be useful. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - afremont - 2015-08-16 (2015-08-16, 03:18)Milhouse Wrote:(2015-08-16, 02:56)afremont Wrote: I've been having some little audio dropouts when watching live TV. I use a Mythbuntu back end, HDHomerun tuner and RPi2 for the front end. I'm currently running the latest build 0815 from this thread. I've included a log made after rebooting everything and was wondering if someone could look at it and tell me if there is anything wrong with my configuration that might be causing the audio drops every few seconds. I have no idea where to look. Maybe I need to adjust my clocking or memory split? Adjust PLL, but I tried the Resample Audio and had the same results. I'm not sure what deinterlace method I'm using. Where is that setting? I went through all the "Expert" settings I think and didn't see that anywhere. I will say that pausing for a couple of seconds definitely seemed to end the issue. It seems like it goes away on its own after watching for a few minutes. I'm guessing that playback is just a smidgen slower than the live and eventually buffers enough to stop dropping out. I'll post a debug log if you want. I just thought maybe I was doing something obviously wrong. My "flash" partition is 386856 1k blocks long, is that big enough? Yeah, I see those error messages. I suspect that there is something wrong with the guide data that is retrieved by EIT from over the air, I doubt it's schedules direct to blame. I had a similar issue with the channel callsigns. I use an HDHomerun and some of the channel information that it returned when scanning for channels had some oddball characters at the end of the string. They caused the whole getting of the guide information to blow up with a similar message. I manually fixed all of those and it started loading the guide ok from the addon. There must be something similar going on somewhere else in the information. There seems to be NULLs in the string. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - zaphod24 - 2015-08-16 Welcome back! Nice to see you moved from WMC to MythTV. I also use MythTV with an HD Homerun Prime. I found the following settings in advancesettings.xml helped make sure the cache was filled a bit more when playing live TV: <pvr> <minvideocachelevel>25</minvideocachelevel> <minaudiocachelevel>25</minaudiocachelevel> <cacheindvdplayer>true</cacheindvdplayer> </pvr> I also use the following overclocking settings which work quite well playing back 1080i60: dtoverlay=sdhost,overclock_50=84 gpu_mem_1024=320 arm_freq=1050 core_freq=525 gpu_freq=350 over_voltage=4 With the latest firmware, turbo mode is started automatically during playback and the PI goes back to normal when playback ends. Re: RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-08-16 (2015-08-16, 14:07)afremont Wrote: I'm not sure what deinterlace method I'm using. Where is that setting? Bring up the OSD: http://kodi.wiki/view/Video_playback#On_screen_display_.28OSD.29 Deinterlace is in the Video section. (2015-08-16, 14:07)afremont Wrote: I'll post a debug log if you want. I just thought maybe I was doing something obviously wrong. My "flash" partition is 386856 1k blocks long, is that big enough? You're confusing a debug-enabled build (useful when experiencing crashes as a more detailed crashlog is produced, but requires a larger FAT partition) with a debug log (wiki) that can be produced from a standard build. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - afremont - 2015-08-16 Okay, so you just want me to enable debugging then. Sorry about that. I'll do that, but first I'm going to try zaphod24's settings, but I'm going to put them in advancedsettings.xml instead of advancesettings.xml. I also have this leftover in my config.txt from a long time ago. I'll try removing it as well since it might be causing a problem instead of preventing one now. hvs_priority=0xf3fc If that fixes it, I'll post back to let you know, otherwise I'll post a debug log. EDIT: Oh yeah, I had the interlacing set to AUTO. I always forget about those special settings in the OSD. What is the preferred method now? RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-08-16 (2015-08-16, 21:32)afremont Wrote: EDIT: Oh yeah, I had the interlacing set to AUTO. I always forget about those special settings in the OSD. What is the preferred method now? If you want to help test, "Auto" wth "MMAL-Advanced", but this has a few issues which are being worked through right now. AW: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Heiko123 - 2015-08-16 Hello, after the last upgrade, i heve the freezes everytime. If I skip recordings then I get a freeze, but with stop I get to the list. Then I deactiveted the omxplayer, and all jumps worked fine. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - MrNice - 2015-08-16 (2015-08-06, 12:39)MrNice Wrote:Still the same with build #0815(2015-07-28, 19:35)MrNice Wrote:A bit different with build #0805;(2015-07-27, 19:58)MrNice Wrote: I did some tests, all with the same process, no setup change: Have you the same? Do you know why? RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-08-16 New OpenELEC Jarvis build #0816: RPi / RPi2 (Supercedes previous build) Code: # uname -a Based on tip of OpenELEC master (cac5a18a, changelog) and tip of XBMC master (2500b739, changelog) with the following modifications:
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - afremont - 2015-08-17 So far, it looks like by using Zaphod24's cache settings in advancedsettings.xml, I have gotten rid of my dropouts. I also disabled OMX player and MMAL by itself seems to be playing LiveTV okay. I used to have serious issues with that, perhaps the caching fixed it. I do notice that it takes a second or two for audio to start coming out when I start playing a channel or after unpausing a channel. I can live with that I guess. The deinterlacing is still set to AUTO right now, don't want to change too many things at once in case problems occur. The audio sync looks good so far and the video isn't racing and pausing and racing and pausing like it used to when I tried disabling OMXPlayer. I guess this means I'm finally having success using DVDPlayer? I haven't tried the overclocking stuff yet, but most of what I watch is SD anyway. Any idea of how to get the guide to not take so long to come up? I have about 100 channels of program info so I suspect that's the problem. Takes about 3 seconds to appear whether I have Live TV playing or not. OOPs, spoke too soon. I had a few seconds of audio dropout in the middle of watching something. The AVR box display went blank which means that it either stopped getting data over the HDMI or it thought the format changed. That's the same thing that happens when I first start watching Live TV and it takes a couple of seconds for audio to start coming out. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - illiac4 - 2015-08-17 According to cache settings in pvr to troubleshoot dropouts (video just stops and log claims that the there is no stream). Which player is cached with those settings? OMX or. MMAL? I would like to cache OMX player or. also MMAL and i am interested if this line <cacheindvdplayer>true</cacheindvdplayer> affects both or. none or. can the cache size be separated and defined for both? <pvr> <minvideocachelevel>25</minvideocachelevel> <minaudiocachelevel>25</minaudiocachelevel> <cacheindvdplayer>true</cacheindvdplayer> </pvr> And another question. When using deinterlacer with omx player and mmal player, what is the difference when mmal deinterlacer is used with omx player and not mmal player? RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - gandharva - 2015-08-17 (2015-08-16, 13:44)popcornmix Wrote:Thank you! No more hangs without the config changes so far. Currently running #0815.(2015-08-16, 13:39)gandharva Wrote: I made the changes and it also seems to work. No hangs. Can I safely remove all the config parameters now? @Milhouse Can you please add a short description howto resize the partition for debug image usage? Preferrable in Post 1 of this thread. Thanks! |