OpenELEC Testbuilds for RaspberryPi Part 3 (Kodi 14.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 Part 3 (Kodi 14.0) (/showthread.php?tid=192380) 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
|
RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Milhouse - 2014-10-16 (2014-10-16, 01:10)pootler Wrote: Unfortunately no luck with the hauppauge remote Thanks. Not really sure what else to suggest right now. RE: OpenELEC Testbuilds for RaspberryPi Part 3 - doveman2 - 2014-10-16 What was the last Gotham build, as it seems that xTV-SAF skin doesn't work with Helix, especially the on-screen keyboard? Also seems that PopcornTV and Steam addons don't work, although they're not listed as incompatible. PopcornFlix does work though. RE: OpenELEC Testbuilds for RaspberryPi Part 3 - menakite - 2014-10-16 (2014-10-15, 22:37)popcornmix Wrote: I have a guess what it may be. Can you try setting "sync playback to display"This was already enabled Quote:and A/V sync to resample. Any different?while this was set to "Adjust PLL". It didn't have any effect. Quote:Also can you try (in config.txt)This instead seems to have cured it. Changed A/V sync back to adjust PLL and still it seems to have worked - thanks! It's hard to say for sure that something random is not happening though. I'll report back in a couple days. I'm curious now - based on the name, I'd say that it limits the HDMI clock changes, and I assume that 50 is smaller than the default. Was the default value increased in recent firmwares? Also, why does this only affect a certain frame rate? RE: OpenELEC Testbuilds for RaspberryPi Part 3 - PeaceMkr - 2014-10-16 since switching to newclock4 i have audiodropouts. When i disable omx-acceleration they are gone but then i have problems with TV-Playback with VNSI (stuttering, blocky pictures). Ive checked the nightly from openelec and milhouse and both have those problems. Any hint or is this behavior known? RE: OpenELEC Testbuilds for RaspberryPi Part 3 - popcornmix - 2014-10-16 (2014-10-16, 05:22)menakite Wrote: I'm curious now - based on the name, I'd say that it limits the HDMI clock changes, and I assume that 50 is smaller than the default. Was the default value increased in recent firmwares? Also, why does this only affect a certain frame rate? Default is 175 (ppm). It has not changed for a long long time. Framerate is not significant, but how well the video timestamps and audio timestamps match the data is significant. Run with mmal, sync video to display and set A/V sync to resample and watch the codec info. The "rr" parameter shows how much audio needs to be resampled to keep the audio and video clocks synced. While omxplayer uses a different algorithm, it still has to do a similar compensation. It alllows up to 0.1% adjustment in HDMI pixel clock, but limits each change step to that specified by hdmi_clock_change_limit. hdmi_clock_change_limit=50 equates to allowing 0.005% hdmi clock adjustment per step. I suspect that either your 25Hz videos are encoded in such a way that the timestamps require significant adjustment (can be verified with "rr" number varying from 1.00 or oscillating), or your receiver is more fussy in that mode. Note: The default settings work fine for 99% of TVs/receivers - there are just some models that are unusually fussy - what receiver are you using? RE: OpenELEC Testbuilds for RaspberryPi Part 3 - pootler - 2014-10-16 (2014-10-16, 01:16)Milhouse Wrote:(2014-10-16, 01:10)pootler Wrote: Unfortunately no luck with the hauppauge remote Thanks for trying- I'll roll back to official build for a while. pootler RE: OpenELEC Testbuilds for RaspberryPi Part 3 - allan87 - 2014-10-16 Hi Popcornmix. Have you had a chance to think about the commercial skip issue at this post? RE: OpenELEC Testbuilds for RaspberryPi Part 3 - menakite - 2014-10-16 (2014-10-16, 13:00)popcornmix Wrote: Default is 175 (ppm). It has not changed for a long long time.Thanks for the detailed explanation. I have tested the video I extracted the sample from and I can see that it varies (not so frequently) from 0.98 to 1.05 during the first 5 minutes. Quote:Note: The default settings work fine for 99% of TVs/receivers - there are just some models that are unusually fussy - what receiver are you using?It's a recent LG TV (32LB650). I'm perplexed though - I was getting the same behavior with old videos I'm sure I've watched at least one time (i.e. Avatar, my sister recently watched it again for the third time). Am I supposed to find the maximum value between 50 and 175, or it doesn't have any effect (performance/artifacts/...)? (Note: I'm not sure about local laws, so I'll delete the sample later day.) RE: OpenELEC Testbuilds for RaspberryPi Part 3 - doveman2 - 2014-10-16 Can I roll-back to Gotham stable by just extracting (and renaming as needed) the files from the zip (including the bootloader files) to the FAT partition of the SD card, or will running Helix have updated any files on the ext4 partition that will no longer be backwards-compatible with Gotham? RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Milhouse - 2014-10-16 (2014-10-16, 17:47)doveman2 Wrote: Can I roll-back to Gotham stable by just extracting (and renaming as needed) the files from the zip (including the bootloader files) to the FAT partition of the SD card, or will running Helix have updated any files on the ext4 partition that will no longer be backwards-compatible with Gotham? You can roll back to Gotham from Helix using just the Gotham tar. You should also be able to upgrade to Helix from a recent Gotham stable using just the Helix tar as tar upgrade support is in OpenELEC 4.2. As far as files on the /storage partition are concerned you should be OK although your guisettings.xml might cause problems so you should probably delete that after upgrading/downgrading. RE: OpenELEC Testbuilds for RaspberryPi Part 3 - menakite - 2014-10-16 (2014-10-16, 05:22)menakite Wrote:Got it again :-(Quote:Also can you try (in config.txt)This instead seems to have cured it. Changed A/V sync back to adjust PLL and still it seems to have worked - thanks! RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Milhouse - 2014-10-16 New OpenELEC Helix build: #1016 (Supercedes previous build) Code: # uname -a Based on tip of OpenELEC master (4556014c, changelog) and tip of XBMC master (cd5807a5, changelog) with the following modifications:
RE: OpenELEC Testbuilds for RaspberryPi Part 3 - popcornmix - 2014-10-17 (2014-10-16, 20:40)menakite Wrote: Got it again :-( Try with a lower number - e.g. 10 or 20? RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Milhouse - 2014-10-17 @pootler - any luck with the new kernel? RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Milhouse - 2014-10-17 New OpenELEC Helix build: #1017 (Supercedes previous build) Code: # uname -a Based on tip of OpenELEC master (4556014c, changelog) and tip of XBMC master (21a4abb1, changelog) with the following modifications:
|