Kodi Community Forum

Full Version: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
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 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495
(2016-12-26, 19:43)nuwonda Wrote: [ -> ]is there another way to wake up kodi from it's dimmed state other than reboot from terminal or unplugging power? this mostly happens after I switch to another input on my av receiver (eg play wii or ps3) and come back to the kodi hdmi after a while, kodi will then be dimmed and won't react to any key from the remote.
I have to press the "Simplink"button on my tv-remote (LG) otherwise CEC wont work.
(2016-12-26, 22:46)Etheric Wrote: [ -> ]I've found that it takes at least 5 key presses from my remote to wake up the pi when in this dimmed state, whereas one key press from a usb keyboard will wake it up.

Capture a debug log (wiki) and check if the 5 key presses are reported (look for OnKey lines)
It may be the TV doesn't forward the first 4 key presses to us.
(2016-12-26, 22:30)popcornmix Wrote: [ -> ]
(2016-12-26, 19:43)nuwonda Wrote: [ -> ]is there another way to wake up kodi from it's dimmed state other than reboot from terminal or unplugging power? this mostly happens after I switch to another input on my av receiver (eg play wii or ps3) and come back to the kodi hdmi after a while, kodi will then be dimmed and won't react to any key from the remote.

Is this a CEC issue?
Can you test if it works with a USB keyboard or phone remote?

Will do next time it happens, I have a phone remote I can use. Will post with results later. Debug log needed too?

edit: I found a crash log from yesterday: https://hastebin.com/pipuxuvunu.swift
maybe it didn't wake up because it was crashed... however the time would not match as the crashlog timestamp is from after the first post there when I rebooted.
I do not have the latest testbuild installed, but please hear me out.

I noticed that the PCM mixer for the HDMI output has an upper volume limit of +4dB (as seen in amixer). Kodi itself is somehow limited to a safe -1.31dB, but add-ons that talk to the mixer directly, will set the volume to +4dB at the 100% level (Spotify Connect Web for instance). This will cause some pretty bad distortion due to clipping.

With my HiFiBerry, I could just store the amixer settings and edit them and my edits would be persistent across reboots, but somehow this won't work for the PCM mixer. I saved it, edited the range and dbmax, set the volume at 0dB, but to no avail. It just boots at -1.31dB and with an upper limit of +4dB. I asked around on the LibreElec forum, but nobody was able to help me.

So this is why I'm asking here. Isn't it better to just limit the mixer to 0dB at the OS level for everyone? The same is done for the HiFiBerry sound card's Digital mixer, which is limited to 0dB, level 207, in software (instead of level 255). I think the use case for +4dB is very limited and Kodi itself is limited to -1.31dB anyway. In most cases it will just cause bad distortion and a lot of users will not understand why that is happening.

Edit: It was not clear that I'm talking about the HDMI sound output.
i try to connect ir receiver via gpio . irrecord works ,dots appear , but after reboot remote not working correctly. irw no output but mode2 -d /dev/lirc0 ir sensor receives signal correctly strange or j make something wrong? there is a file (remote name).lircd.conf not in configfiles but on 7,7gb ext4 partition visible under linux pc
(2016-12-27, 12:57)makruiten Wrote: [ -> ]Edit: It was not clear that I'm talking about the HDMI sound output.

HDMI output doesn't use ALSA (make sure you have the top option "HDMI" selected in system/audio setting), so this issue shouldn't exist for HDMI.
(2016-12-27, 14:38)popcornmix Wrote: [ -> ]
(2016-12-27, 12:57)makruiten Wrote: [ -> ]Edit: It was not clear that I'm talking about the HDMI sound output.

HDMI output doesn't use ALSA (make sure you have the top option "HDMI" selected in system/audio setting), so this issue shouldn't exist for HDMI.

Thanks, this explains why Kodi does not have this problem. Spotify Connect Web does use ALSA and it uses the PCM mixer, which effects the audio volume through HDMI. If I manually change the PCM volume, the audio volume is changed with it, so it's not just some digits in the terminal. I could not find any way to cap the volume to 0dB. With the HiFiBerry soudcard I can change anything I like and it's already capped to 0dB to begin with. My setup is RPi > HDMI > receiver/amp > HDMI > TV.
New LibreELEC.tv Krypton build #1225: RPi / RPi2
(Supercedes previous build)

Code:
# uname -a
Linux rpi512 4.9.0 #1 Sun Dec 25 21:04:00 GMT 2016 armv6l GNU/Linux

# vcgencmd version
Dec 23 2016 16:46:02
Copyright (c) 2012 Broadcom
version 18a9fe64e58d73e303bf09b176fe63ddb7994a0c (clean) (release)

# lsb_release
LibreELEC (Milhouse) - Version: devel-20161225210259-#1225-gdc61a12 [Build #1225]

# Kodi version
(18.0-ALPHA1 Git:17.0-beta7-eed32e7). Platform: Linux ARM 32-bit

Based on tip of LibreELEC.tv master (dc61a122, changelog) and tip of XBMC master (5b7006a9, changelog) with the following modifications: Build Highlights:
  1. Improve German keyboard
  2. Remember last used keyboard layout
Build Details:
  1. XBMC:
    • [docs] Adapt README.osx.md and README.ios.md (PR:11264, 2 commits, 2 files changed)
    • [cmake/depends] Add info about Android SDK/NDK to Toolchain_binaddons… (PR:11257, 1 commit, 1 file changed)
    • WIn32 Partially revert scaling changes (PR:11269, 1 commit, 2 files changed)
    • [PVR] Fix crashes on pvr manager deinit/reinit - part 2 (PR:11225, 3 commits, 12 files changed)
    • [keyboard] improvements to German keyboard layout (PR:11239, 1 commit, 1 file changed)
    • [GUI] remember last used keyboard layout (PR:11242, 1 commit, 4 files changed)
New LibreELEC.tv Krypton build #1226: RPi / RPi2
(Supercedes previous build)

Code:
# uname -a
Linux rpi512 4.9.0 #1 Tue Dec 27 05:12:28 GMT 2016 armv6l GNU/Linux

# vcgencmd version
Dec 23 2016 16:46:02
Copyright (c) 2012 Broadcom
version 18a9fe64e58d73e303bf09b176fe63ddb7994a0c (clean) (release)

# lsb_release
LibreELEC (Milhouse) - Version: devel-20161227051123-#1226-ga5d29bc [Build #1226]

# Kodi version
(18.0-ALPHA1 Git:17.0-beta7-eed32e7). Platform: Linux ARM 32-bit

Based on tip of LibreELEC.tv master (a5d29bcf, changelog) and tip of XBMC master (efbd57a5, changelog) with the following modifications: Build Highlights:
  1. libnfs: NFSv4 and RPC server support
Build Details:
  1. LibreELEC.tv:
    • eventlircd: Fix missing buttons with WP2 remote (PR:1081, 2 commits, 2 files changed)
    • Virtual network package: Fix samba and openvpn build options (PR:1078, 2 commits, 1 file changed)
    • protobuf: set protoc path (PR:1097, 1 commit, 1 file changed)
    • ccache: fix build with CCACHE_DISABLE (PR:1096, 1 commit, 1 file changed)
    • libdvbcsa: AArch64 support (PR:1058, 1 commit, 1 file changed)
  2. XBMC:
    • [cleanup] Replace atomic functions with std::atomic (PR:11251, 3 commits, 28 files changed)
    • Recalculate SyncClock after reconfigure (PR:11273, 1 commit, 1 file changed)
  3. libnfs:
    • For upstream (PR:158, 3 commits, 2 files changed)
    • ZDR_ARRAY: remove the check for element-size * num-objects (468424c4)
    • Create a generic RPC NULL function (6f27daf6)
    • Add a PDU flag for discard after sending. (11f85665)
    • socketsize is of type socklen_t not int (6f8b2f85)
    • Create a new helper function to set the sockaddr for a rpc context (dccffb86)
    • Remove sockaddr argument to rpc_connect_sockaddr_async (9eaa36c4)
    • Add NFSv4 protocol definitions (853474d3)
    • Use a static sockaddr_storage for rpc.udp_dest (7596d0f3)
    • Change type of zdrproc_t to return uint32_t instead of int (f4273cf9)
    • Update portmap.x to use nicer names for procedure arguments and responses (be2c87c2)
    • Add ZDR* and void* as arguments to zr_void so that it can be used as a zdrproc_t (6f860fd8)
    • Initial rpc server support (eb6b3912)
    • Automatically detect if a server context fd is a UDP socket or not (57a9bd85)
    • Make zdr_malloc() visible outside of libnfs-zdr.c (2d348242)
    • EXAMPLE: Add nfs4-cat example (6d397028)
    • Add support for PMAP2 SET operation to the portmapper client (34926e9d)
    • Add PMAP2 UNSET support to the portmapper client (2cffb48c)
    • EXAMPLE: portmapper server (85aca36e)
    • Update README and mention NFSv4 and general RPC server support. (adf158bb)
    • EXAMPLE: nfs4-cat-talloc (0a4f9cd8)
    • WIN32: Add nfs4 to the visual studio project files (85853ae9)
    • WIN32: VS does not like the spurious int i; that rpcgen sometimes generate (d93cc94d)
    • NFS4: Remove the buf variable from the generated c code as it is unused. (b06b37ec)
    • PORTMAP: Remove buf variable where we do not use/need it from the generated files (46d63f13)
    • Fix compiler warning for min/max version being unset (which can not happen) (ca67c18d)
    • WIN32: SO_TYPE is a char on windows not int. (01ca7997)
(2016-12-27, 15:42)makruiten Wrote: [ -> ]
(2016-12-27, 14:38)popcornmix Wrote: [ -> ]
(2016-12-27, 12:57)makruiten Wrote: [ -> ]Edit: It was not clear that I'm talking about the HDMI sound output.

HDMI output doesn't use ALSA (make sure you have the top option "HDMI" selected in system/audio setting), so this issue shouldn't exist for HDMI.

Thanks, this explains why Kodi does not have this problem. Spotify Connect Web does use ALSA and it uses the PCM mixer, which effects the audio volume through HDMI. If I manually change the PCM volume, the audio volume is changed with it, so it's not just some digits in the terminal. I could not find any way to cap the volume to 0dB. With the HiFiBerry soudcard I can change anything I like and it's already capped to 0dB to begin with. My setup is RPi > HDMI > receiver/amp > HDMI > TV.
Or am I looking in the wrong direction? Is the PCM mixer something that is setup by Spotify Connect Web? I installed Spotify Connect Web from the LibreELEC repo and it uses a mixer called PCM to control HDMI volume. I was assuming that the mixer was there before installing Spotify Connect Web.
As an FYI, maybe you are already aware of it, I would like to mention that HDhomerun is not working anymore, it will play a channel with a constant buffering and the logo will stay on the screen while the message box down on the right of the screen will indicate that is trying to load the recording (Do not remember the exact world) but nothing shows up. It was working about 10 versions ago.
Thanks
(2016-12-27, 17:18)alphatech69 Wrote: [ -> ]As an FYI, maybe you are already aware of it, I would like to mention that HDhomerun is not working anymore, it will play a channel with a constant buffering and the logo will stay on the screen while the message box down on the right of the screen will indicate that is trying to load the recording (Do not remember the exact world) but nothing shows up. It was working about 10 versions ago.
Thanks
You will need to pinpoint the build that broke the plugin so the commits of that build can be looked at.

Or at a minimum capture and post a log.
(2016-12-27, 14:38)popcornmix Wrote: [ -> ]
(2016-12-27, 12:57)makruiten Wrote: [ -> ]Edit: It was not clear that I'm talking about the HDMI sound output.

HDMI output doesn't use ALSA (make sure you have the top option "HDMI" selected in system/audio setting), so this issue shouldn't exist for HDMI.

I started from scratch with a clean LibreELEC install and there is no mixer for HDMI, like you said. After I installed Spotify Connect Web, the PCM mixer I was talking about immediately appeared. So I'm sorry to have bothered you with this, as this is obviously an issue that has nothing to do with LibreELEC/Kodi itself. I have opened an issue for this.
I'm seeing odd behavior when trying to jump around with right/left or up/down keys. This is on #1212b

http://pastebin.com/QuZqc15D

It jumps back to the beginning of the recording. Very annoying.

Thanks!
(2016-12-27, 17:18)alphatech69 Wrote: [ -> ]As an FYI, maybe you are already aware of it, I would like to mention that HDhomerun is not working anymore, it will play a channel with a constant buffering and the logo will stay on the screen while the message box down on the right of the screen will indicate that is trying to load the recording (Do not remember the exact world) but nothing shows up. It was working about 10 versions ago.
Thanks

See this post: http://forum.kodi.tv/showthread.php?tid=...pid2485687. Also, here.

The problem appear to have started with build #1213, which happens to be when some infobools were removed, so presumably the addon needs updating to take account of this change.
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 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495