Kodi Community Forum

Full Version: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
(2016-10-11, 18:13)popcornmix Wrote: [ -> ]
(2016-10-11, 17:46)drdwridav Wrote: [ -> ]Is there any other adjustment I can try?

Yes, I did add some settings for this sort of thing. Let me check...
okay, by default there is a config.txt setting:
Code:
hdmi_muting=0x00640032

which decodes to:
hdmi_mute_period_before_change_in_ms=0x64=100ms
hdmi_mute_period_after_change_in_ms=0x32=50ms

When changing hdmi mode we "mute" the signal (not an audio mute, but telling the display to ignore the signal during the change).
Possibly your display will be happier with a longer mute either before or after the hdmi mode change.

What I would suggest is to try doubling it a few times to see if that helps. Try, in order, one setting at a time each of these:
Code:
hdmi_muting=0x00640032
hdmi_muting=0x00c80064
hdmi_muting=0x019200c8
hdmi_muting=0x03200192
and see if any of those makes the display happier.

e.g. Add "hdmi_muting=0x00640032", reboot. Test video playback. If no better try "hdmi_muting=0x00c80064", reboot. Test video playback, etc.

Champion! 99% there.
The first two settings made no difference

hdmi_muting=0x019200c8 worked. Film starts fine in 3D. On exiting it takes me back to 2D, though it's a bit 'messy' with the screen flashing between black and the menu three or four times before settling down.

hdmi_muting=0x03200192 is much 'cleaner'. Exit film, screen goes black for a while, then back to menu in 2D (perfect). The only problem with this one is that when you start a 3D film it actually starts in the background behind the menu and I then have to select fullscreen.

Is there a fine tweak now based on the above I could try?

Ta
(2016-10-11, 20:25)drdwridav Wrote: [ -> ]So 0x019200c8 starts a film perfectly, and 0x03200192 closes it perfectly. Can the values be tweaked to reflect this?

Can we work out if the "before" or "after" change that is required?
Does one of the following fix it?
Code:
hdmi_muting=0x03200032
hdmi_muting=0x00640192
(2016-10-11, 20:31)popcornmix Wrote: [ -> ]
(2016-10-11, 20:25)drdwridav Wrote: [ -> ]So 0x019200c8 starts a film perfectly, and 0x03200192 closes it perfectly. Can the values be tweaked to reflect this?

Can we work out if the "before" or "after" change that is required?
Does one of the following fix it?
Code:
hdmi_muting=0x03200032
hdmi_muting=0x00640192

We have a winner!
0x00640192 does it just fine.

(for the record 0x03200032 had identical behaviour to 0x03200192 if that helps identify the ultimate cause)

Thanks again!!!
(2016-10-11, 21:18)drdwridav Wrote: [ -> ]We have a winner!
0x00640192 does it just fine.

Okay so that is:
hdmi_mute_period_before_change_in_ms=0x64=100ms
hdmi_mute_period_after_change_in_ms=0x192=402ms

That's quite a bit higher the old default. Can you see if it can be tweaked down at all?

0x0064015e (350ms)
0x0064012c (300ms)
0x006400fa (250ms)
0x006400c8 (200ms)
(2016-10-10, 18:57)Korrigan Wrote: [ -> ]I just tried #1009 and couldn't find the "use limited color range" option in Settings -> System -> Display (as mentioned here Settings/System/Display (wiki)).
I wanted to set everything up as explained in Video_levels_and_color_space (wiki) but it seems Kodi is always scaling the videos to Full RGB (RPi config.txt is already set to Full RGB and confirmed with tvservice -s) so I'm losing BtB (0-15) and WtW (236-255)
How is this supposed to work?

I have been complaining about this for over a year 231424 (thread)
I still don't believe it visually displays correctly, it works fine on an old WDTV Live Plus.
New LibreELEC.tv Krypton build #1011: RPi / RPi2
(Supercedes previous build)

Code:
# uname -a
Linux rpi512 4.8.1 #1 Tue Oct 11 21:06:16 BST 2016 armv6l GNU/Linux

# vcgencmd version
Oct 11 2016 15:51:55
Copyright (c) 2012 Broadcom
version f911c71d4af710b1eb459ff1b4c13b471889025e (clean) (release)

# lsb_release
LibreELEC (Milhouse) - Version: devel-20161011210318-#1011-g5661f32 [Build #1011]

Based on tip of LibreELEC.tv master (5661f325, changelog) and tip of XBMC master (01c5bc96, changelog) with the following modifications:
  • Includes newclock5 patches
  • Excludes the LibreELEC linux-01-RPi_support patch in favour of sourcing these and possibly more recent patches directly from kernel branch rpi-4.8.y
  • Includes latest bcm2835-driver master (a021d6e7)
  • Includes latest kodi-platform master (c8188d82)
  • Includes latest libcec master (62b8520c, ahead +15)
  • Includes latest libnfs master (2edbd147)
  • Includes latest p8-platform master (041a8c6c, ahead +1)
  • Includes latest addons: inputstream.mpd (94d8a71d, +9), inputstream.rtmp (70cb86f6), inputstream.smoothstream (081c6c43), peripheral.joystick (d9b83d8f, +10), pvr.argustv (87cb6780), pvr.demo (01c68c88), pvr.dvblink (e842db92), pvr.dvbviewer (f72c62ff), pvr.filmon (675c2b4e), pvr.hdhomerun (eef1bd15), pvr.hts (c091da30), pvr.iptvsimple (adee8a7f, +3), pvr.mediaportal.tvserver (845479b6), pvr.mythtv (b1b426f3), pvr.nextpvr (f99b17d3), pvr.njoy (b5d65655), pvr.pctv (d6d969fe), pvr.stalker (168e35f7), pvr.vbox (c966c5fd), pvr.vdr.vnsi (dd95edef), pvr.vuplus (7ab30d34), pvr.wmc (d9eac84f)
  • Exclude [env] libcec-PR208.patch: merged upstream (libcec)
  • Include [env] patch: Add kodi binary addons (pvr, adsp, other)
  • Include [env] patch: Don't build ADSP addons
  • Include [env] patch: linux: use in-tree rtl8192cu for RPi/RPi2
  • Include [env] patch: Bump included addon versions to prevent online updates
  • Include [env] patch: Add experimental splash video for RPi
  • Include [env] patch: HACK: Disable multiple PVR addons during migration. Always enable inputstream.* and os.*
  • Include [env] PR:759: linux: update to linux-4.8.1
  • Include [env] PR:792: scripts/build: use MinSizeRel cmake build type
  • Include [env] PR:796: scripts/build: cleanup
  • Include [env] PR:800: xf86-video-intel: enable dri3 and make it default
  • Include [env] PR:807: Network: smb & ntfs config mods
  • Include [env] PR:810: path: remove regex dependency when processing packages
  • Include [env] PR:812: libdrm: update to libdrm-2.4.71
  • Include [env] PR:813: scripts/build: no need to setup toolchain twice and before really building
  • Include [env] PR:826: libnfs: update to 1.11.0
  • Include [env] PR:828: xf86-video-nvidia: update to 367.57
  • Revert [env] 46b9b7b3: rtmpdump (Reason: use newclock5 bump)
  • Revert [env] PR:793: projects/*/options: disable lcdproc for all projects except Generic/Virtual (Reverted until add-on available)
  • Include [pkg] patch: [skin.estuary] Hide watched items on home (kodi-theme-Estuary)
  • Include [pkg] PR:8824: videodb: fix smart playlists not honoring "Show empty TV shows" setting.
  • Include [pkg] PR:10370: Add settings to control notification rumble duration and strength
  • Include [pkg] PR:10572: [CryptThreading] replace hardcoded value for CRYPTO_LOCK by macro
  • Include [pkg] PR:10641: [video] fix NFO parsing of <namedseason>'s
  • Include [pkg] PR:10677: [xbmc/xbmc] [MediaSettings] - fixed loading interlacemode_none from defaultsettings
Build Highlights:
  1. New firmware - removes max_usb_current
    popcornmix Wrote:FYI: max_usb_current setting has been removed and it is now always enabled. This has always been the case on Pi3, so this only affects B+/Pi2.
  2. Restore BCM270X_DT kernel commit reverted in yesterdays build
  3. Kernel/architecture cleanup
Build Details:
  1. Firmware (Oct 11):
    • firmware: platform: Remove max_usb_current and default to enabled
    • firmware: arm_dt: Only mask interrupts for enabled DT nodes. See: link
    • firmware: ISP tuner: Lower rate at fast fps
    • firmware: resize: Fix for no padding giving incorrect pitch. See: link
    • firmware: arm_dt: Populate the /serial-number property. See: link
    • firmware: deinterlace: Provide a mode where frame flags are exclusively used
    • firmware: arm_loader: do not allow qpu usage when arm owns the 3d. See: link
    • firmware: vcinclude: Fix macro for IS_ALIAS_L1L2_NONALLOCATING
  2. XBMC:
    • [PVR] Recording home screen widget: Fix info dialog (show recording info, not generic video info). (PR:10676, 1 commit, 3 files changed)
    • support reusing of CFile::m_pFile (PR:10658, 1 commit, 6 files changed)
    • Add explicit ordering on song join queries - fix bug on MariaDB (PR:10657, 1 commit, 2 files changed)
    • [cmake] Fix double install of skins (PR:10656, 3 commits, 6 files changed)
  3. inputstream.mpd:
    • -Wl, --no-undefined only for android (94d8a71d)
  4. peripheral.joystick:
    • Fix extra call to RefreshButtonMaps() (f902039d)
    • Fix controller transformation not working correctly (f3afc3da)
    • Add debug logging when overwriting a feature (6e891ac7)
    • [storage] Capture by reference (d3b36c4a)
    • .gitignore: Add ".settings" (d1d343ec)
    • Improve readability of CButtonMapXml::IsValid() (1cf4ae49)
    • Fix button maps refreshing from disk during wizard (121ea70e)
    • [buttonmaps] cocoa: Add button map for Retrolink SNES controller (d9b83d8f)
  5. pvr.iptvsimple:
    • fixup build on windows after 053298623e8a58153eab425d1f2c7d892bc15ac2 (PR:90, 1 commit, 1 file changed)
  6. kernel 4.8.y:
    • New commits in this build:
      • bcm270x: Remove dead files (8255db7f)
      • bcm270x: Drop bcm2835-aux-uart hack (4d200f67)
      • Revert "bcm2835: Add support for uart1" (e745b4e6)
      • bcm270x: Remove unnecessary of_platform_populate (04e627ac)
      • bcm270x: Remove 4MB dma coherent pool (f9f60179)
      • bcm270x: Drop map_io device mapping (b50787df)
      • bcm270x: Use DT_MACHINE_START (8b1d6e38)
      • Merge pull request #1678 from notro/bcm270x-cleanup-1 (de0f4d62)
      • Use DT rather than modules params for board rev and serial (a71d473f)
      • Register the clocks early during the boot process, (bcc804ce)
      • Add Adafruit pitft35 touchscreen support (#1657) (43e86e44)
      • BCM270X_DT: Update CM3 to use sdhost interface (46149430)
      • Revert "Register the clocks early during the boot process," (d1eec13f)
(2016-10-11, 21:45)popcornmix Wrote: [ -> ]
(2016-10-11, 21:18)drdwridav Wrote: [ -> ]We have a winner!
0x00640192 does it just fine.

Okay so that is:
hdmi_mute_period_before_change_in_ms=0x64=100ms
hdmi_mute_period_after_change_in_ms=0x192=402ms

That's quite a bit higher the old default. Can you see if it can be tweaked down at all?

0x0064015e (350ms)
0x0064012c (300ms)
0x006400fa (250ms)
0x006400c8 (200ms)

Been getting quite fit running up and down the stairs to edit config.txt!
Nope, none of the above worked. All reproduced the original behaviour (i.e. TV eventually staying in 3D mode).
Cheers
Something isn't right with the latest release (#1011) when playing recorded shows or live TV via pvr.mythtv. The video starts and you will hear sound but the video is stuck on one frame and when I look at kodi.log I see the following loop over and over. Eventually the audio will restart but the video is still on the same frame and then the audio will cut out and the same error below loops. As always a debug log is below as well.

UPDATE: Just tried it on #1010 and it works as expected.

Code:
08:49:32  99.159462 T:1405092768   ERROR: CMMALPool::GetBuffer - failed pool:0x73c25ea0 omvb:(nil) mmal:(nil) timeout:500
08:49:32  99.159576 T:1405092768   ERROR: CDecoder::FFGetBuffer Failed to allocated buffer in time
08:49:32  99.160690 T:1405092768   ERROR: ffmpeg[53C003A0]: [mpeg2video] get_buffer() failed
08:49:32  99.160751 T:1405092768   ERROR: ffmpeg[53C003A0]: [mpeg2video] thread_get_buffer() failed
08:49:32  99.160797 T:1405092768   ERROR: ffmpeg[53C003A0]: [mpeg2video] get_buffer() failed (-1 (nil))
08:49:32  99.160858 T:1405092768   ERROR: Decode - avcodec_decode_video returned failure
08:49:32  99.160912 T:1405092768   DEBUG: CVideoPlayerVideo - video decoder returned error

http://sprunge.us/TAYe
Hello,

I noticed if i use the new tags for kodi17 like:
Code:
<cache> instead <network>
<memorysize> instead <cachemembuffersize>
or <readfactor> instead <readbufferfactor>
the video cache dont work well and have buffering issues.
But if i use the old tags from kodi 16 everything works well.
(2016-10-12, 14:53)pyrodex Wrote: [ -> ]Something isn't right with the latest release (#1011) when playing recorded shows or live TV via pvr.mythtv. The video starts and you will hear sound but the video is stuck on one frame and when I look at kodi.log I see the following loop over and over. Eventually the audio will restart but the video is still on the same frame and then the audio will cut out and the same error below loops. As always a debug log is below as well.

UPDATE: Just tried it on #1010 and it works as expected.

Code:
08:49:32  99.159462 T:1405092768   ERROR: CMMALPool::GetBuffer - failed pool:0x73c25ea0 omvb:(nil) mmal:(nil) timeout:500
08:49:32  99.159576 T:1405092768   ERROR: CDecoder::FFGetBuffer Failed to allocated buffer in time
08:49:32  99.160690 T:1405092768   ERROR: ffmpeg[53C003A0]: [mpeg2video] get_buffer() failed
08:49:32  99.160751 T:1405092768   ERROR: ffmpeg[53C003A0]: [mpeg2video] thread_get_buffer() failed
08:49:32  99.160797 T:1405092768   ERROR: ffmpeg[53C003A0]: [mpeg2video] get_buffer() failed (-1 (nil))
08:49:32  99.160858 T:1405092768   ERROR: Decode - avcodec_decode_video returned failure
08:49:32  99.160912 T:1405092768   DEBUG: CVideoPlayerVideo - video decoder returned error

http://sprunge.us/TAYe

I'm not seeing that with my setup. I have 2 RPi3 devices, one hooked to an lcd tv by hdmi and the other to an old crt tv using composite. From the logs, it looks like your recorded content is MPEG2. Mine is as well. I'm actually using an HDHomeRun Prime device with MythTV to tune and record my cable provider's content. I don't know that I looked at 720p recordings last night but I definitely watched some 1080i after updating.
(2016-10-12, 15:29)Zpower Wrote: [ -> ]I noticed if i use the new tags for kodi17 like:
Code:
<cache> instead <network>
<memorysize> instead <cachemembuffersize>
or <readfactor> instead <readbufferfactor>
the video cache dont work well and have buffering issues.
But if i use the old tags from kodi 16 everything works well.

If you use the old tags then they will be ignored. Does it behave the same with the cache tags removed?
(2016-10-12, 15:29)Zpower Wrote: [ -> ]the video cache dont work well and have buffering issues.
But if i use the old tags from kodi 16 everything works well.

Please upload a link to your log (you can use the "Submit log" option in the LibreELEC Settings add-on).
(2016-10-12, 15:57)Milhouse Wrote: [ -> ]
(2016-10-12, 15:29)Zpower Wrote: [ -> ]the video cache dont work well and have buffering issues.
But if i use the old tags from kodi 16 everything works well.

Please upload a link to your log (you can use the "Submit log" option in the LibreELEC Settings add-on).

http://sprunge.us/cHKZ
(2016-10-12, 10:42)drdwridav Wrote: [ -> ]
(2016-10-11, 21:45)popcornmix Wrote: [ -> ]
(2016-10-11, 21:18)drdwridav Wrote: [ -> ]We have a winner!
0x00640192 does it just fine.

Okay so that is:
hdmi_mute_period_before_change_in_ms=0x64=100ms
hdmi_mute_period_after_change_in_ms=0x192=402ms

That's quite a bit higher the old default. Can you see if it can be tweaked down at all?

0x0064015e (350ms)
0x0064012c (300ms)
0x006400fa (250ms)
0x006400c8 (200ms)

Been getting quite fit running up and down the stairs to edit config.txt!
Nope, none of the above worked. All reproduced the original behaviour (i.e. TV eventually staying in 3D mode).
Cheers

Hi Popcornmix,
Meant to ask, can you envisage any other problems with the higher mute period I've now set? Have to say I've had a good play now and it seems pretty flawless!
Thanks for your help
(2016-10-12, 17:18)drdwridav Wrote: [ -> ]Hi Popcornmix,
Meant to ask, can you envisage any other problems with the higher mute period I've now set? Have to say I've had a good play now and it seems pretty flawless!
Thanks for your help

It will take longer for the kodi side of the hdmi mode change to complete (by an extra third of second) which probably results in playback taking a fraction longer to start.
As you found with some of the higher settings, if this takes too long (I think 1 second) the configure times out and video plays in the background.

That's why I'm a little reluctant to change this for everyone. If I hear more reports like yours I'll be more inclined to change it, but there is a (very small) performance cost to this change.

Assuming the problem is really specific to your TV, then a local config.txt setting is probably the right solution.
If evidence emerged that it affects multiple TVs then we may want to do something else.

One option is to use the shorter mute period for normal 2D changes and only use the longer mute period when switching between 2D and 3D modes.