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 - Mafarricos - 2014-07-20 Already tested transmission, everything is working fine! RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Mafarricos - 2014-07-20 Trying to open some YouTube videos using yatse. And with this latest version I'm getting this type of errors: http://xbmclogs.com/show.php?id=250741 Another log more complete: http://xbmclogs.com/show.php?id=250752 Is release related? Also trying to output audio to analog and HDMI. I have HDMI as source and activated the dual output, but I don't get audio output on analog, more people with this problem? Re: RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Milhouse - 2014-07-21 (2014-07-20, 20:55)Mafarricos Wrote: Is release related? I don't really use Yatse any more, I tried opening a few Youtube videos with a recent release and the Youtube add-on without any problem. The errors appear to be http rather than https, can you try a pre-libressl release and see if the problem is still there? RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Mafarricos - 2014-07-21 Milhouse in previous releases I always used the Yatse to send youtube videos and never had problems. I will do a downgrade to previous release, and check if was a update on yatse or so. For the tests that I made opening from youtube addon or from other addons it seems that youtube videos allways open. I will also try on another pi, so see if it was a upgrade release problem. RE: OpenELEC Testbuilds for RaspberryPi Part 3 - AlderaaN - 2014-07-22 (2014-07-20, 20:55)Mafarricos Wrote: Trying to open some YouTube videos using yatse. And with this latest version I'm getting this type of errors: (2014-07-21, 02:42)Milhouse Wrote: I don't really use Yatse any more, I tried opening a few Youtube videos with a recent release and the Youtube add-on without any problem. The errors appear to be http rather than https, can you try a pre-libressl release and see if the problem is still there?Hello people. I think the issue was resolved with the latest patches to the YouTube Video Plugin, though I'm not running an OpenELEC Beta (v4.0.7 Official, at the moment). Here are two possible solutions for you: 1. Simple, 1-file replacement. 2. More in-depth, addresses several issues (mentioned here), including the one from solution #1: https://github.com/learningit/plugin.video.youtube/ (or simply click here to download the .zip master from the aforementioned site). @Milhouse: Mind I ask which remote control solution are you currently using for your OpenELEC setup? Regards, Re: RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Milhouse - 2014-07-22 (2014-07-22, 00:57)AlderaaN Wrote: @Milhouse: Mind I ask which remote control solution are you currently using for your OpenELEC setup? VRC-1100 for my Pi. With my OpenELEC/x86 I use a Harmony One programmed with VRC-1100 codes. RE: OpenELEC Testbuilds for RaspberryPi Part 3 - AlderaaN - 2014-07-22 (2014-07-22, 03:14)Milhouse Wrote:Cool.(2014-07-22, 00:57)AlderaaN Wrote: @Milhouse: Mind I ask which remote control solution are you currently using for your OpenELEC setup? Thank you for the information! AW: OpenELEC Testbuilds for RaspberryPi Part 3 - Heiko123 - 2014-07-22 Ohhh with one of the latest builds, I can't play all h264 files. It is now the same problem how in raspbmc! Is it possible to change the codec? Re: RE: AW: OpenELEC Testbuilds for RaspberryPi Part 3 - Milhouse - 2014-07-22 (2014-07-22, 17:55)Heiko123 Wrote: Ohhh with one of the latest builds, I can't play all h264 files. Which build works/doesn't work? What file - need mediainfo, a sample file or debug log (wiki). Try increasing GPU mem (128 on a 256MB Pi, 256 on a 512MB Pi) and see if that helps. RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Heiko123 - 2014-07-22 Hello, thanks. I will test it and I have send a PM to you within a sample file. EDIT: Hola, I change the GPU mem to 256MB and ... all files are playing. Thanks for you tip. RE: OpenELEC Testbuilds for RaspberryPi Part 3 - glenn 1990 - 2014-07-22 @popcornmix Is there some kind of a hardware/firmware limitation according deinterlacing on SD content? Deinterlacing doesn't seems to work with official and these builds, deinterlace is set on auto or fore on. My sat provider has several SD h264 encoded channels, this is pretty exceptional I think as other providers all seems to use mpeg2 in combo with SD channels. At the first sight, HD channels with H264 seems fine, a bit odd as it should be more work for the GPU. You can download a short sample here: https://dl.dropboxusercontent.com/u/18133665/Keeping%20Up%20with%20the%20Kardashians.2014-07-22.mkv Pictures where you can see the interlace effects: RE: OpenELEC Testbuilds for RaspberryPi Part 3 - popcornmix - 2014-07-22 (2014-07-22, 20:39)glenn 1990 Wrote: Is there some kind of a hardware/firmware limitation according deinterlacing on SD content? Not a hardware limitation. There are two deinterlace algorithms - a complex one for SD and a simpler one for HD. I have seen another (SD) interlaced sample that behaves better with the simpler deinterlacer. I suspect that your file will look better with the simpler deinterlacer. The short term solution is to provide a way of choosing the deinterlace algorithm (either through GUI or config.txt). The longer term solution is to understand what's going wrong and fix it. There will be something unexpected in the encoding that means we are not identifying the fields correctly. RE: OpenELEC Testbuilds for RaspberryPi Part 3 - glenn 1990 - 2014-07-23 (2014-07-22, 23:51)popcornmix Wrote:(2014-07-22, 20:39)glenn 1990 Wrote: Is there some kind of a hardware/firmware limitation according deinterlacing on SD content? Thanks for your response. Yea, a option in config.txt would be a nice thing. I saw you did some work to offload deinterlacing to the TV, wich would prabably work ok then? Simple deinterlacer is basic software BOB I assume, right? RE: OpenELEC Testbuilds for RaspberryPi Part 3 - popcornmix - 2014-07-23 (2014-07-23, 20:01)glenn 1990 Wrote: Yea, a option in config.txt would be a nice thing. Command line omxplayer now supports "native" deinterlace. It only works where video resolution matches TV resolution, framerate matches and the interlace is "simple" (i.e. field order doesn't change during the stream). It's effectively free, processing wise, and the TV can probably do a better job at deinterlacing. I'd like to add this to these xbmc test builds at some point, just to see whether it works for many people. The current HD/simple deinterlacer is software BOB. RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Milhouse - 2014-07-24 New OpenELEC Helix build: #0724 (Supercedes previous build) Code: # uname -a Based on tip of OpenELEC master (c6c7a82, changelog) and tip of XBMC master (a8fc99e, changelog) with the following modifications:
New firmware with on-screen warning for over-temperature and, on Model B+, under-voltage warning (see discussion thread). OpenELEC: Migration from OpenSSL to LibreSSL is now complete. Addons should now be updated in the Official and Unofficial repositories. OpenELEC: Loading SYSTEM into RAM is no longer supported as it didn't seem to provide much if any benefit.
|