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) - doldi - 2016-02-20 no - because is not so fast like the old build 1001, often restarts and freezing cursor. DD and DTS play after some time (have wrote them yesterday) ...it's a pity after your hard work since 1001, that this problem is not resolved (hope you understand me - it is hard for me with my terrible english to explain this for you) btw - yesterday i have played an 20GB mkv file from usb HD - all audio works fine with 1001. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - da-anda - 2016-02-20 AC3 and DTS PT from PI2:HDMI -> TV:SPIF -> AVR works like a charm with OMX and MMAL. I didn't even know my TV can forward DTS, as fritsch and I didn't manage to get that working via Android. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - doldi - 2016-02-20 hmm, what am I doing wrong? - don't get any multichannel over optical spdif on Yamaha receiver - only pcm notifications. I wont to listen direkt sound over seven loudspeakers not on verry little tv-tin- rubber johnny. :-) well, i think need now a new receiver? :-) RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - dkscan - 2016-02-20 (2016-02-20, 13:48)popcornmix Wrote: Good to hear. Any other user who had working passthrough with omxplayer enabled, but no pssthrough with omxplayer disabled, then please test the latest build.Replaced the .elf and .dat files on my RPI2 running OSMC and passthrough with MMAL now works with my Sony tv and Sonos Playbar. Good job :-) RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - da-anda - 2016-02-20 @doldi - what's your setup? Have you tried with setting the number of speakers to 2.0 with PT enabled? Also, if you want your TV to passthrough via SPDIF, it's quite possible that you have to enable this in your TV. My LG has "PCM" and "Auto" as options for it's optical out and ofc only "Auto" will support PT. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - doldi - 2016-02-20 @ da-anda ;-) thanks ok, lets go to my setup. RPi2 is connected to a Ligawo HDMI Switch ( TV have only 2 HDMI's and no s/pdif-out)). Yamaha receiver is connected over optical s/pdif to this switch. But i won't switch KODI to 2 channels and aktivate AC3 transformation, because so i have no DTS5.1 with my equipment combination. Yes, if i want to hear AAC5.1 this is the only way to listen DD5.1, I am aware. hmmm ;-) RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - da-anda - 2016-02-20 @doldi - your assumption is wrong. At least for anything SPDIF and PT related you HAVE TO set the channels to 2.0 - SPDIF can only handle 2 channels and the 5.1 information is encoded in these two channels. So AC3 transcoding will still work and you can enjoy 5.1AAC and 5.1FLAC as 5.1AC3 streams even if speakers are set to 2.0. I know this is a bit confusing, but that is the correct configuration. edit: so in short: - set speakers to 2.0 - enable passthrough - enable AC3 PT - enable AC3 transcoding - enable DTS PT once done, everything SPDIF can handle should work and you'll also get any other 5.1 format converted to AC3 5.1 RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - doldi - 2016-02-20 Thanks da-anda, i will test it first on old 1001 build and report later. Now i am looking "Lucy" mky with my old configuration ;-) RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - doldi - 2016-02-20 (2016-02-20, 21:52)da-anda Wrote: @doldi - your assumption is wrong. At least for anything SPDIF and PT related you HAVE TO set the channels to 2.0 - SPDIF can only handle 2 channels and the 5.1 information is encoded in these two channels. So AC3 transcoding will still work and you can enjoy 5.1AAC and 5.1FLAC as 5.1AC3 streams even if speakers are set to 2.0. I know this is a bit confusing, but that is the correct configuration. Well - your right da-anda. With this setting lip sync is much better than 5.1 configuration. On 20GB mkv after 10 min was sensed 1 second! Now is build #0219 with this setting usable for me. btw: Skip back left under the progressbar is always shown (aktivated) and "blinking", if i move the cursor on screen in this build? RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-02-21 New OpenELEC Krypton build #0220: RPi / RPi2 (Supercedes previous build) Code: # uname -a Based on tip of OpenELEC master (d61e8ce7, changelog) and tip of XBMC master (146e7155, changelog) with the following modifications:
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - stourwalk - 2016-02-21 Just installed #0220 and when I try and scan my music library Kodi crashes repeatedly every single time after the first album is scanned. This was a clean install with no existing music db. http://sprunge.us/GSBA is the Crashlog The kodi.old.log doesn't seem to give much hint, so hopefully the stack trace in the crashlog is of more use The album it scans is the only one I have for that artist, so it's impossible to tell which one it's trying to scan next that might be the cause (and there are some 1300 artists to choose from ) RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-02-21 Is it crashing always with the same album? It looks like it is crashing after or while scraping smb://STOURWALK/music/2 Unlimited/No Limit/album.nfo. There's nothing obvious in #0220 that looks like it would cause this, can you try earlier builds and try to determine when the crashing started? RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - rudrood - 2016-02-21 For some reason the visualisations for radio aren't working. The visualisation is on the screen but not reacting to the music/sounds. When playing an mp3 they work oke. Tested both TVHeadend and VU enigma radio. They do work with OpenElec 6.0.1. For the rest: thanks for all your work! RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - nb2a - 2016-02-21 Is anyone using the HD Home run PVR with any success on the latest build? RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - stourwalk - 2016-02-21 (2016-02-21, 16:02)Milhouse Wrote: Is it crashing always with the same album? It looks like it is crashing after or while scraping smb://STOURWALK/music/2 Unlimited/No Limit/album.nfo. There's nothing obvious in #0220 that looks like it would cause this, can you try earlier builds and try to determine when the crashing started? A little more investigation done (although not yet trying to bisect previous builds) and a little more background. The music in question live on my unraid NAS and was previously controlled by a x86 based openelec build (most likely Isengard based). The NAS has been shipped from the UK to the US and is now hooked up to my rPi, so I'm rescanning all the files again. All of my artists and albums have 'artist.nfo' and 'album.nfo' files in place. The crash consistent occurs whenever the Universal Artist/Album Scraper gets involved. If I remover the album.nfo then it crashes on the Artist, if I then remove the artist.nfo then it'll scan in that Artist/Album just fine. All the crashlogs seem to SEGFAULT in the same place.. Code: Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'. And indeed the method place seems to indicate a NFO related issue So the simple solution is to delete all my existing NFO files, but that just masks what might be a problem rather than cures it. Given that it therefore might not be rPi specific either who is the best person to talk to? |