Guest - Testers are needed for the reworked CDateTime core component. See... https://forum.kodi.tv/showthread.php?tid=378981 (September 29) x
  • 1
  • 73
  • 74
  • 75(current)
  • 76
  • 77
  • 342
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server
(2015-09-22, 15:27)aesthetiker Wrote: EDIT: Ok update over ssh works! New Image up and running.All PVR add ons are in the gui on status invalid

Ok that could be the problem. I can't install the latest error invalid. dependencies not satisfied. Tried to install from .zip same issue. Thank you for any tips.

(2015-09-22, 14:40)fritsch Wrote:
(2015-09-22, 14:38)aesthetiker Wrote: Tried last Jarvis release maybe update first page and add PVR addons are incompatible. Back to older release.

The ones from this morning? They should work -as the bump is already in. Make sure you tried the latest and greatest ...

pvr addons are quite well compatible. you've hit one of the many pvr/addonmanager bugs. delete your userdata/Databases/Addons*.db
Reply
(2015-09-22, 14:17)fritsch Wrote: Btw. as you are a new tester right now. Your screen also goes blank every some seconds while watching something?

Just wanted to confirm that I've watched several hours of video, and have experienced no unusual behavior. No dimming, flashing, or whatever. Seems to be working great!
Reply
(2015-09-20, 21:22)fritsch Wrote:
Quote:21:09:27 T:140225146599488 NOTICE: Display resolution ADJUST : 1080i 16:9 (0) (weight: 1.000)

That is fixed in kodi's master already. I will rebuild when fernet rebases next time. Can you please give me the output of /usr/lib/kodi/kodi-xrandr please?

Edit: Just seen you run the ppa version. Retry with the version from coming Tuesday.

Here it is (sorry for delay):

Code:
<screen id="0" minimum_w="8" minimum_h="8" current_w="1920" current_h="1080" maximum_w="32767" maximum_h="32767">
  <output name="DP1" connected="false">
  </output>
  <output name="DP2" connected="false">
  </output>
  <output name="DP3" connected="false">
  </output>
  <output name="HDMI1" connected="true" w="1920" h="1080" x="0" y="0" crtc="0" wmm="698" hmm="392">
    <mode id="0x4b" name="1920x1080" w="1920" h="1080" hz="50.00000" current="true" preferred="true"/>
    <mode id="0x106" name="1920x1080" w="1920" h="1080" hz="60.00000" current="false" preferred="false"/>
    <mode id="0x107" name="1920x1080" w="1920" h="1080" hz="59.94020" current="false" preferred="false"/>
    <mode id="0x10a" name="1920x1080" w="1920" h="1080" hz="24.00000" current="false" preferred="false"/>
    <mode id="0x10c" name="1920x1080" w="1920" h="1080" hz="23.97608" current="false" preferred="false"/>
    <mode id="0x108" name="1920x1080i" w="1920" h="1080" hz="30.00000" current="false" preferred="false"/>
    <mode id="0x109" name="1920x1080i" w="1920" h="1080" hz="25.00000" current="false" preferred="false"/>
    <mode id="0x10b" name="1920x1080i" w="1920" h="1080" hz="29.97010" current="false" preferred="false"/>
    <mode id="0x10d" name="1280x720" w="1280" h="720" hz="60.00000" current="false" preferred="false"/>
    <mode id="0x10e" name="1280x720" w="1280" h="720" hz="50.00000" current="false" preferred="false"/>
    <mode id="0x10f" name="1280x720" w="1280" h="720" hz="59.94020" current="false" preferred="false"/>
    <mode id="0x110" name="720x576" w="720" h="576" hz="50.00000" current="false" preferred="false"/>
    <mode id="0x111" name="720x576i" w="720" h="576" hz="25.00000" current="false" preferred="false"/>
    <mode id="0x112" name="720x480" w="720" h="480" hz="60.00000" current="false" preferred="false"/>
    <mode id="0x113" name="720x480" w="720" h="480" hz="59.94006" current="false" preferred="false"/>
    <mode id="0x114" name="720x480i" w="720" h="480" hz="29.99889" current="false" preferred="false"/>
    <mode id="0x115" name="720x480i" w="720" h="480" hz="29.97003" current="false" preferred="false"/>
    <mode id="0x116" name="640x480" w="640" h="480" hz="60.00000" current="false" preferred="false"/>
    <mode id="0x117" name="640x480" w="640" h="480" hz="59.94048" current="false" preferred="false"/>
  </output>
  <output name="HDMI2" connected="false">
  </output>
  <output name="HDMI3" connected="false">
  </output>
  <output name="VIRTUAL1" connected="false">
  </output>
</screen>

I've fullHD plasma TV (Panasonic ST50).
Reply
(2015-09-22, 13:44)fritsch Wrote: I wrote a systemd service that sets the screen to full range automatically. No need for autostart.sh hacks.

For those of us with older builds before 15/09/20 if we update should we remove the autostart.sh?
Reply
(2015-09-22, 17:46)oshan Wrote:
(2015-09-22, 13:44)fritsch Wrote: I wrote a systemd service that sets the screen to full range automatically. No need for autostart.sh hacks.

For those of us with older builds before 15/09/20 if we update should we remove the autostart.sh?

It does not harm, it just "doubles" the effect - but you can savely remove it.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
After all the hassle with the pvr addons - just uploading a new Jarvis version with addons directly integrated ...
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
PVR addons have been updated in the PPA
Reply
(2015-09-22, 17:41)Sunflux Wrote:
(2015-09-22, 14:17)fritsch Wrote: Btw. as you are a new tester right now. Your screen also goes blank every some seconds while watching something?

Just wanted to confirm that I've watched several hours of video, and have experienced no unusual behavior. No dimming, flashing, or whatever. Seems to be working great!

I can also confirm no problems at all after several hours of progressive h264 video, on latest Isengard.
Reply
I just update to the latest ppa ( the last time was more than 1 week ago )
I see that "AdjustRefreshrate: Switch to higher resolution" patch is now in Smile

but now I have that when switching in mode higher than 1080p : I see unity menu in fullscreen mode :

Image

Is that the consequence of not following the rule of the first post -> ubuntu server + openbox instead of standard ubuntu version with unity.
or is it something else ? I didn't have such problem until the switching > 1080p

log : http://www.xbmclogs.com/pjb0qhs40
Reply
Unity is not able to switch resolutions at all from kodi - it will always end up like this ... Furtheremore this is not possibility to disable compiz automatically ... Use it from lightdm instead ... no Uniyt support.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
It's clear now no unity for Kodi

Thanks for the lightdm idea
Reply
Feedback:

Now with mesa 11, and Kodi compiled from fernetmenta's master yesterday, just for fun, I retried my previously reported issue with interlaced content. So far, it looks like something has fixed this. On my Haswell i5 NUC, I'm able to run VAAPI decode, with MCDI for full HW decode and render. I previously had to rely on Yadif deinterlace. Of course this is a welcome reduction in CPU use.

Referring to this: http://forum.kodi.tv/showthread.php?tid=...pid2052702
Reply
Recompile from current - does it still work?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Update. Fixed a nice memmove bug. memmove semantics should be killed with fire :-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
With today's ppa version bug with audio starting to play before changing display refresh rate is gone, thanks :-)

But there is still bug with floating audio when "Synchronise audio playback to display" is enabled.
Reply
  • 1
  • 73
  • 74
  • 75(current)
  • 76
  • 77
  • 342

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