Guest - Testers are needed for the reworked CDateTime core component. See... https://forum.kodi.tv/showthread.php?tid=378981 (September 29) x
  • 1
  • 222
  • 223
  • 224(current)
  • 225
  • 226
  • 342
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server
(2016-03-04, 13:26)_Spook_ Wrote: I will try the new build after work and see if it has fixed the "black screen and mouse pointer only"-issue. If not I will provide logs.

It seems we got an issue with service addons - will investigate.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
you can fix the black screen by installing service.xbmc.versioncheck from https://github.com/XBMC-Addons/service.x...ree/master
at least this solved it for me
Reply
Yeah - and that should not be needed and I want to know why.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2016-03-03, 16:34)the-dreamer Wrote: xrand http://sprunge.us/OdCM
kodi log: http://sprunge.us/IhaH
dmesg http://sprunge.us/JJTI

first codec info show: 33 skip / 2 drop
second codec info show 80 skip / 2 drop

fyi: it is my own build based on yours from 22 feb with fix for my edid problem and allow passthrough even on realtime streams.

This shows (and you've mentioned) that you're outputting interlaced mode to the TV. You don't want to do this. Since your TV accepts 1080p input, you want to send it 1080p. What you are doing now is taking interlaced source material, deinterlacing it to progressive, then converting back to interlaced before sending it to the TV. Or with progressive source material, you're just destroying it by converting it to interlaced before sending to the tv.
Reply
It might be even worse ... as kodi cannot output interlaced ... it's all done "somewhere" ...
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2016-03-04, 14:47)puithove Wrote: This shows (and you've mentioned) that you're outputting interlaced mode to the TV. You don't want to do this. Since your TV accepts 1080p input, you want to send it 1080p. What you are doing now is taking interlaced source material, deinterlacing it to progressive, then converting back to interlaced before sending it to the TV. Or with progressive source material, you're just destroying it by converting it to interlaced before sending to the tv.

sadly my tv is only able to do 1080i :-(
Reply
(2016-03-03, 08:02)n2vwz Wrote:
(2016-03-03, 07:52)Matt Devo Wrote: I'd just add a ~2s delay using an autostart script:
Code:
#!/bin/sh
sleep 2

I will play with this. Does the script get wiped out when I do a firmware/software update?

Matt,

I loaded the latest Milhouse KODI 17 build (#0226, 26-Feb-2016) and have found that no delay whatsoever is required to make the NAS SMB shares visible. I did notice, however that the OpenELEC settings menu is missing from the SYSTEM top level menu. Is this a permanent condition in consideration that this is test software?

Jim
Reply
(2016-03-04, 16:14)n2vwz Wrote: Matt,

I loaded the latest Milhouse KODI 17 build (#0226, 26-Feb-2016) and have found that no delay whatsoever is required to make the NAS SMB shares visible. I did notice, however that the OpenELEC settings menu is missing from the SYSTEM top level menu. Is this a permanent condition in consideration that this is test software?

Jim

I'd have to guess it's an issue with you having upgraded from a 6.0 build, assuming you didn't do a clean install or reset afterwards. But since I haven't tried it myself I can only guess.
Reply
(2016-03-04, 18:04)Matt Devo Wrote: I'd have to guess it's an issue with you having upgraded from a 6.0 build, assuming you didn't do a clean install or reset afterwards. But since I haven't tried it myself I can only guess.

I guess that it is a non-issue for now. It's too early to speculate how the official KODI 17 releases will act.

FYI - Several other people over on the OpenELEC forum have reported what appears to be the same 6.0.x missing SMB share problem that I encountered. I originally posted my problem over there, but got no response.

I don't remember having the missing share issue with 5.x builds.
Reply
(2016-03-04, 18:54)n2vwz Wrote: I guess that it is a non-issue for now. It's too early to speculate how the official KODI 17 releases will act.

FYI - Several other people over on the OpenELEC forum have reported what appears to be the same 6.0.x missing SMB share problem that I encountered. I originally posted my problem over there, but got no response.

I don't remember having the missing share issue with 5.x builds.

I'm unfortunately not able to reproduce the issue here, as I'm running my OE7 build on my main box currently, with a shared mysql db and smb shares all located on my NAS, which is mapped via IP, not name. I have a new dev box arriving later today, will try to reproduce with 6.02+

edit: just did a clean install of 6.0.398, with a single mapped SMB share for movies (added via Kodi dialog, browsing the network shares). Rebooted, played a movie, no issues. Didn't even need to use the 'wait for network' setting.
Reply
Images updated. Should work now ™. Still on kernel 4.4 as connman has compile issues against 4.5-rc6.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
I just tried the http://fritsch.fruehberger.net/openelec/...aaae43.tar build. Stil just black screen and pointer.

Here are the logs:
journalctl -a | pastebinit http://sprunge.us/TjWK
dmesg | pastebinit http://sprunge.us/NFGJ
cat /storage/.kodi/temp/kodi.log | pastebinit http://sprunge.us/DICB
vainfo | pastebinit http://sprunge.us/MVMI
AppleTV 4K, LG 65E6 OLED TV, Marantz NR1606, Harmony Elite
Reply
Uploading new build ... this service.xbmc.versioncheck seems very stubborn :-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2016-03-04, 15:37)the-dreamer Wrote:
(2016-03-04, 14:47)puithove Wrote: This shows (and you've mentioned) that you're outputting interlaced mode to the TV. You don't want to do this. Since your TV accepts 1080p input, you want to send it 1080p. What you are doing now is taking interlaced source material, deinterlacing it to progressive, then converting back to interlaced before sending it to the TV. Or with progressive source material, you're just destroying it by converting it to interlaced before sending to the tv.

sadly my tv is only able to do 1080i :-(

Hmh, HD ready? If so, set video output to 720p instead of 1080i and everything else according to the instructions in thread #1. You might have to calibrate the sceen, but should solve your issues. Alternatively, exchange your HD ready TV for a used Full HD one instead. That's what I did. One of my better decisions.
Reply
(2016-03-04, 20:23)fritsch Wrote: Uploading new build ... this service.xbmc.versioncheck seems very stubborn :-)

All good. No more black screen. Thanks Smile Will do some soundchecks now to see if passthrough audio works on my miniDP1.2->HDMI 2.0 adapter again Smile

EDIT: Still no go on passthrough audio when using the adapter. No biggie. The new skin takes some getting used to Smile
AppleTV 4K, LG 65E6 OLED TV, Marantz NR1606, Harmony Elite
Reply
  • 1
  • 222
  • 223
  • 224(current)
  • 225
  • 226
  • 342

Logout Mark Read Team Forum Stats Members Help
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server18