Login at Kodi Home

Korrigan · (This post was last modified: 2016-10-10, 19:38 by Korrigan.)

(2016-10-10, 19:02)popcornmix Wrote: You are not losing anything. The Pi knows if the video is limited or full range.
It knows if it is outputting limited or full range and will scale between the two if necessary.
It signals to the display whether the signal is limited or full range.

In general you should just leave everything alone and you will get the right results.
The only instance you need do anything is if the display doesn't handle the limited/full range signalling, but that is pretty rare.

But I tried a full range video (http://www.avsforum.com/forum/139-displa...ation.html) and I can't get 0-15 to show.

**popcornmix** · 2016-10-10, 19:48

(2016-10-10, 19:37)Korrigan Wrote: But I tried a full range video (http://www.avsforum.com/forum/139-displa...ation.html) and I can't get 0-15 to show.

That's rather a long article and includes several downloads.
Can you describe exactly which video file you played? (ideally provide a sample that shows the problem).

Korrigan · (This post was last modified: 2016-10-10, 19:59 by Korrigan.)

(2016-10-10, 19:48)popcornmix Wrote:
(2016-10-10, 19:37)Korrigan Wrote: But I tried a full range video (http://www.avsforum.com/forum/139-displa...ation.html) and I can't get 0-15 to show.

That's rather a long article and includes several downloads.
Can you describe exactly which video file you played? (ideally provide a sample that shows the problem).

I tried the MP4 version from the above link -> Basic Settings -> 1-Black Clipping.mp4 (https://drive.google.com/open?id=0B_-Wwz...Ux6RHc1T1U)
Works as intended on my PC but I cant get Kodi/RPi to show 0-15

**popcornmix** · 2016-10-10, 20:02

Code:
mediainfo "./MP4-2c/Basic Settings/1-Black Clipping.mp4"

General

Complete name                            : ./MP4-2c/Basic Settings/1-Black Clipping.mp4

Format                                   : MPEG-4

Format profile                           : JVT

Codec ID                                 : avc1 (isom/avc1)

File size                                : 15.1 MiB

Duration                                 : 5mn 0s

Overall bit rate                         : 422 Kbps

Encoded date                             : UTC 2010-09-20 04:04:57

Tagged date                              : UTC 2010-09-20 04:04:57

Video

ID                                       : 1

Format                                   : AVC

Format/Info                              : Advanced Video Codec

Format profile                           : Main@L4

Format settings, CABAC                   : Yes

Format settings, ReFrames                : 3 frames

Format settings, GOP                     : M=1, N=48

Codec ID                                 : avc1

Codec ID/Info                            : Advanced Video Coding

Duration                                 : 5mn 0s

Bit rate                                 : 421 Kbps

Nominal bit rate                         : 15.0 Mbps

Maximum bit rate                         : 616 Kbps

Width                                    : 1 920 pixels

Height                                   : 1 080 pixels

Display aspect ratio                     : 16:9

Frame rate mode                          : Constant

Frame rate                               : 23.976 (23976/1000) fps

Color space                              : YUV

Chroma subsampling                       : 4:2:0

Bit depth                                : 8 bits

Scan type                                : Progressive

Bits/(Pixel*Frame)                       : 0.008

Stream size                              : 15.1 MiB (100%)

Writing library                          : x264 core 104 r1713 c276662

Encoding settings                        : cabac=1 / ref=4 / deblock=1:0:0 / analyse=0x1:0x131 / me=tesa / subme=10 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=24 / chroma_me=1 / trellis=2 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=-2 / threads=12 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / constrained_intra=0 / bframes=3 / b_pyramid=1 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=0 / keyint=48 / keyint_min=4 / scenecut=40 / intra_refresh=0 / rc_lookahead=48 / rc=2pass / mbtree=1 / bitrate=15000 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=15000 / vbv_bufsize=9000 / ip_ratio=1.40 / aq=1:1.00 / nal_hrd=none

Encoded date                             : UTC 2010-09-20 04:04:57

Tagged date                              : UTC 2010-09-20 04:18:24

Color range                              : Limited

Color primaries                          : BT.709

Transfer characteristics                 : BT.709

Matrix coefficients                      : BT.709

Note the

Code:
Color range                              : Limited

Korrigan · 2016-10-10, 20:09

(2016-10-10, 20:02)popcornmix Wrote: Note the

Code:
Color range : Limited

So the video contains 0-15 but is set to "limited"? And that causes Kodi to scale from Limited to Full and discard 0-15?

**popcornmix** · 2016-10-10, 20:11

(2016-10-10, 20:09)Korrigan Wrote: So the video contains 0-15 but is set to "limited"? And that causes Kodi to scale from Limited to Full and discard 0-15?

Yes, any values from 0-15 in a limited range video are out of spec and should be clamped (to the same value that 16 produces - effectively as black as possible).

Korrigan · 2016-10-10, 20:17

(2016-10-10, 20:11)popcornmix Wrote:
(2016-10-10, 20:09)Korrigan Wrote: So the video contains 0-15 but is set to "limited"? And that causes Kodi to scale from Limited to Full and discard 0-15?

Yes, any values from 0-15 in a limited range video are out of spec and should be clamped (to the same value that 16 produces - effectively as black as possible).

But why scale at all if the Wiki says Kodi limited -> GPU full -> TV limited produces the best results?

**popcornmix** · 2016-10-10, 20:23

(2016-10-10, 20:17)Korrigan Wrote: But why scale at all if the Wiki says Kodi limited -> GPU full -> TV limited produces the best results?

The wiki is for PCs where it is unknown whether the video driver defaults to limited or full range.
The Pi doesn't have this problem and shouldn't normally require changing.

Milhouse · 2016-10-11, 01:59

(2016-10-10, 19:29)cojms1 Wrote: I did a little bit of research and it seems that TP-LINK have a linux driver but only for kernel versions 2.6-3.16 (http://www.tp-link.com/en/download/Arche...tml#Driver). Is there anything that can be done to get this available in LibreELEC?

You probably should have done your research before buying, that way you would have avoided buying unsupported hardware. LibreELEC is not a general purpose distribution (such as Raspbian) and for that reason doesn't support the thousands of different wireless devices that are available (often very badly supported by the chip manufacturers with outdated drivers), it focuses instead on those devices that are well supported by the mainline kernel plus a handful of incredibly common Realtek devices.

You could try asking on the LibreELEC forum if support can be added for this dongle (apparently it needs the mt7610 driver) but this thread isn't for feature requests.

Milhouse · 2016-10-11, 02:33

(2016-10-10, 18:17)polo_joe Wrote: @Milhouse

your addon LibreELEC Tvh-addon v.105-#1009-milhouse-v4.1-2267-g6efcfd2 is actually Build: 4.1.2236
Could you check this please?

tl;dr: the file is correct, the addon.xml is garbage.

The version number in my file (4.1.2267) is automatically generated from git - the top of tree in the tvheadend42 git is 4.1.2267. The file is correct.

The addon.xml for tvheadend42 is generated from the version number configured in LibreELEC master, which is not top of tree - it is 4.1.2236. This appears only in the description text for tvheadend42, it is garbage as I don't build the addon using that version.

It's not typical for addons to include a version number in their description - there's absolutely no reason to do this - and the fact that tvheadend42 does this is annoying but not something I have any intention of fixing.

I'll remove the bogus version from addon.xml, that will end this.

Milhouse · (This post was last modified: 2016-10-11, 06:03 by Milhouse.)

New LibreELEC.tv Krypton build #1010: RPi / RPi2
(Supercedes previous build)

Code:
# uname -a

Linux rpi512 4.8.1 #1 Tue Oct 11 04:30:30 BST 2016 armv6l GNU/Linux

# vcgencmd version

Oct  4 2016 19:03:30 

Copyright (c) 2012 Broadcom

version c844c61ad08f94946910d0d5e1be076df4c8c56d (clean) (release)

# lsb_release

LibreELEC (Milhouse) - Version: devel-20161011042930-#1010-g5661f32 [Build #1010]

Based on tip of LibreELEC.tv master (5661f325, changelog) and tip of XBMC master (57eb7af8, 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 (ec63df14)
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 (b45f98ff, +8), inputstream.rtmp (70cb86f6), inputstream.smoothstream (081c6c43), peripheral.joystick (9db9cc59, +2), pvr.argustv (87cb6780), pvr.demo (01c68c88), pvr.dvblink (e842db92), pvr.dvbviewer (f72c62ff), pvr.filmon (675c2b4e), pvr.hdhomerun (eef1bd15), pvr.hts (c091da30), pvr.iptvsimple (57b546a3, +2), 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:10658: support reusing of CFile::m_pFile
Include [pkg] PR:10676: [PVR] Recording home screen widget: Fix info dialog (show recording info, not generic video info).
Include [pkg] PR:10677: [xbmc/xbmc] [MediaSettings] - fixed loading interlacemode_none from defaultsettings
Revert [pkg] 6e8485a9: BCM270X_DT: Use bcm283x.dtsi, bcm2835.dtsi and bcm2836.dtsi (Reason: kodi fails to start) (linux)

Build Highlights:

Watchdog and BCM270X_DT kernel commits - latter reverted for now (or kodi.bin will crash)
Fix relative seeks

Build Details:

XBMC:
- [estouchy] update (PR:10673, 1 commit, 6 files changed)
- VideoPlayer: fix general synchronize after 48301edd6a88c044243e6468ce… (PR:10669, 2 commits, 3 files changed)
- [estuary] smartplaylist rules container did not work with a mouse (PR:10672, 1 commit, 1 file changed)
- [guilib] make onclick override conditional. Fallback to default actio… (PR:10663, 1 commit, 1 file changed)
- [Win32] DynamicDlls are not system-dll's (PR:10661, 1 commit, 3 files changed)
- Dont load inputstream addons on startup if they are disabled (PR:10675, 1 commit, 1 file changed)
peripheral.joystick:
- [Fix] Resource leak (PR:54, 2 commits, 3 files changed)
newclock5:
- New commits in this build:
  - VideoPlayer: pass parameters for seek mode in a structure (1fed6b70)
  - VideoPlayer: do not block caller on relative seeks (e3407e95)
  - squash: VideoPlayer: pass parameters for seek mode in a structure (459aebfc)
- Commits no longer in build:
  - VideoPlayer: fix general synchronize after 48301edd6a88c044243e6468ceeb54ff65f35f26 (f263018d)
  - VideoPlayer: do not wait for teletext msg queue to be empty, makes no sense (a4b9d3b6)
kernel 4.8.y:
- New commits in this build:
  - BCM270X_DT: Use bcm283x.dtsi, bcm2835.dtsi and bcm2836.dtsi (6e8485a9)
  - Merge pull request #1664 from notro/bcm283x-dtsi-1 (554c6680)
  - watchdog: bcm2835: Support setting reboot partition (5dc93ff7)
  - bcm270x: Use watchdog for reboot/poweroff (dc2d56de)
Additional commits/pull requests/changes not yet merged upstream:
- Added: [env] PR:826: libnfs: update to 1.11.0
- Added: [env] PR:828: xf86-video-nvidia: update to 367.57
- Added: [pkg] PR:10676: [PVR] Recording home screen widget: Fix info dialog (show recording info, not generic video info).
- Added: [pkg] PR:10677: [xbmc/xbmc] [MediaSettings] - fixed loading interlacemode_none from defaultsettings
- Reverted: [pkg] 6e8485a9: BCM270X_DT: Use bcm283x.dtsi, bcm2835.dtsi and bcm2836.dtsi (Reason: kodi fails to start) (linux)

polo_joe · 2016-10-11, 07:41

(2016-10-11, 02:33)Milhouse Wrote:
(2016-10-10, 18:17)polo_joe Wrote: @Milhouse

your addon LibreELEC Tvh-addon v.105-#1009-milhouse-v4.1-2267-g6efcfd2 is actually Build: 4.1.2236
Could you check this please?

tl;dr: the file is correct, the addon.xml is garbage.

The version number in my file (4.1.2267) is automatically generated from git - the top of tree in the tvheadend42 git is 4.1.2267. The file is correct.

The addon.xml for tvheadend42 is generated from the version number configured in LibreELEC master, which is not top of tree - it is 4.1.2236. This appears only in the description text for tvheadend42, it is garbage as I don't build the addon using that version.

It's not typical for addons to include a version number in their description - there's absolutely no reason to do this - and the fact that tvheadend42 does this is annoying but not something I have any intention of fixing.

I'll remove the bogus version from addon.xml, that will end this.

I got the build number from webui of tvheadend and in journalctl tvheadend also reported build 4.1.2236, so I thought it is not top of tree.

cojms1 · 2016-10-11, 08:19

(2016-10-11, 01:59)Milhouse Wrote: You probably should have done your research before buying, that way you would have avoided buying unsupported hardware. LibreELEC is not a general purpose distribution (such as Raspbian) and for that reason doesn't support the thousands of different wireless devices that are available (often very badly supported by the chip manufacturers with outdated drivers), it focuses instead on those devices that are well supported by the mainline kernel plus a handful of incredibly common Realtek devices.

You could try asking on the LibreELEC forum if support can be added for this dongle (apparently it needs the mt7610 driver) but this thread isn't for feature requests.

I'll ask in the LibreELEC forum. It's not an issue either way. The dongle was actually bought for another purpose, I just thought I'd plug it in and see if it worked - knowing that at some point I'd probably end up attempting to reuse it.

Thanks for the reply.

drdwridav · 2016-10-11, 17:46

(2016-08-12, 17:26)drdwridav Wrote:
(2016-08-12, 15:11)popcornmix Wrote:
(2016-08-10, 23:30)drdwridav Wrote: EDIT: one other quick finding. If I disable adjust display refresh rate -obviously playback jerky - but kodi does switch back to 2d properly on exiting. Interesting?

Not something I would have predicted, so I guess interesting. I suspect this is timing related and there is a subtle change in timing, but not sure yet.

Does increasing "delay after change of refresh rate" in system/display settings help?

That's the badger! Cheers popcornmix. Sorted! First tried 0.5 second delay - no difference. Then a 1 second delay and I've started and stopped 6 different 3D films in various containers - all switched back to 2d mode properly. So it was all about the delay which must be default longer in 7.9.4 then?!

Hi popcornmix. You may recall the conversation above from a few weeks ago about my Samsung TV not switching back to 2D after a 3D film. With the increased delay it's now ok with OMX, but with MMAL it's the same old problem regardless of the delay set. MMAL is the better player now (especially as there are no issues fast forwarding 3D films) so this is getting to me a bit (only because I'm a perfectionist and want it all flawless!). It's a pretty mainstream TV (48 inch H series 2014) so I'm surprised no one else is getting the issue too!

What I have noticed though which might be of interest is that on exiting the 3D film the TV does momentarily switch to 2D (you can see the menu fine for a glimpse), it then goes black and switches back to a garbled 3D image. Is there any other adjustment I can try? Failing that is it possible to remote keymap change resolution or refresh rate? Because at the moment my way to cure this after a 3D film is to go into system settings, select a different refresh rate or resolution - then reject the change when it is offered....back to normal.

Cheers

**popcornmix** · 2016-10-11, 18:13

(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.