Hi
It seems that kodi (17.6) ignores the file advancedsettings.xml
I put it in /home/user/.kodi/userdata (also tried /usr/share/kodi/addons/skin.estuary/xml and /usr/share/kodi/userdata and /usr/share/kodi/system)
<advancedsettings>
<video>
<enablehighqualityhwscalers>true</enablehighqualityhwscalers>
</video>
</advancedsettings>
Only has "bilinear" or "nearest neighbour" in Video Setting during playback (1080P or 720P movies).
(P.S. It also didn't work with android tv (mi box) )
OS Ubuntu MATE 16.04
Thanks
It seems to be okay.
Did you initially create the advancedsettings.xml file with a Windows editor?
The EOL format may be wrong.
Quote:17:51:17.438 T:140307655481728 NOTICE: Contents of special://profile/advancedsettings.xml are... <advancedsettings>
<video>
<enablehighqualityhwscalers>true</enablehighqualityhwscalers>
</video>
</advancedsettings>
Different file to your first post
(2017-12-10, 18:13)trogggy Wrote: [ -> ]Quote:17:51:17.438 T:140307655481728 NOTICE: Contents of special://profile/advancedsettings.xml are... <advancedsettings>
<video>
<enablehighqualityhwscalers>true</enablehighqualityhwscalers>
</video>
</advancedsettings>
Different file to your first post
Tried to make it simple.....
Please don't paste log files directly into the forum. Use
https://pastebin.com or similar websites. Thanks in advance.
Do I understand? The log shows the advancedsettings.xml read, but the expected behavior is missing?
Do I understand? The log shows the advancedsettings.xml read, but the expected behavior is missing?
I note in
http://kodi.wiki/view/Advancedsettings.xml "Allow turning on the spline36 and lanczos3 shader (for GL builds)." Maybe this means versus the "standard X11" builds?
I'm having the exact same issue, with 3 Raspberry Pi units. Advancedsettings was working great before the update (dateadded 1) but no longer.
Android: No support -> not implemented for GLES
RPI: Are you serious?
x86: works -> just verified on X11 with GL
Post a
Debug Log, please
(2017-12-20, 15:32)fritsch Wrote: [ -> ]RPI: Are you serious?
How do you mean?
Anyway, debug posted below. It would appear to be loading the advancedsettings file, but not taking any notice of it as my "recently added movies" shows films in order of scan date (or alphabetical) rather than file time/date as it did before.
https://pastebin.com/B9TE1Fyk
(2017-12-20, 16:24)fritsch Wrote: [ -> ]Disable MMAL and it will be there. But I am quite sure you don't want that. The PI implements this, when MMAL is in use: http://www.imagemagick.org/Usage/filter/#mitchell <- no other hq scaler we have is better than that.
Hi fritsch
My reason for using advancedsettings is different to the OP, but the fact remains that it would appear to be ignored by Kodi 17.6
(2017-12-20, 16:39)digitalface Wrote: [ -> ] (2017-12-20, 16:24)fritsch Wrote: [ -> ]Disable MMAL and it will be there. But I am quite sure you don't want that. The PI implements this, when MMAL is in use: http://www.imagemagick.org/Usage/filter/#mitchell <- no other hq scaler we have is better than that.
Hi fritsch
My reason for using advancedsettings is different to the OP, but the fact remains that it would appear to be ignored by Kodi 17.6
It's not fact! You posted a RBPI log. Don't mix facts with alternative facts.
My query isn't about MMAL or any of that, it's rather the fact that Kodi seems to be ignoring advancedsettings.xml (and the dateadded parameter within). This applies to 3 different Pi units that I've been using, all which worked with advancedsettings on 17.5 but no longer use it on 17.6
Unfortunately I'm told I'm unable to downgrade Kodi version on the Pi so for now I have to hope someone else is able to test on theirs to compare.