Edited by dlanor at Fri Nov 14, 2014 23:49 |
mattrix replied at Fri Nov 14, 2014 22:17
I can actually change the resolution via command line.
So, I will make a single image, which can easily be changed between 720 / 1080 by looking for a file
If this file is present, it will set the screen to 1080p.
I orignally had this - but wasn't sure on a good DPI.
DPI choice can be tricky. Essentially what looks good and readable with a given DPI in 720p will need that DPI multiplied by 1.5 for use in 1080p with same appearance. But this rule is complicated by the fact that some apps have preconceived ideas of their own, such as using font rendering methods which fail when DPI is too low.
For example, I consider a DPI of 180 to be a good compromize between readability and a good number of objects per screen for 1080p (decent browser pages, and Plex client screens), and for 720p this corresponds to a DPI setting of 120, which is what I'm currently testing. But this causes the supplied launcher to cut off the bottom pixels of all the text titles of apps on the desktop. I do not see any similar cuts in other apps however, and since I've installed the Nova launcher it doesn't matter how the old launcher would render the titles. (But of course there may be other apps using similar bad rendering methods.)
I think this latest Kodi isn't the great.
Might revert to the Alpha4 I originally used.
It was a lot quicker in the 1080p.
For me the main problem is that the latest ones lose backwards compatibility with skins made for Gotham, so this will apply to ALL newer versions to come as well, at least until someone ports the needed XBMC skins to Helix Kodi (if that ever happens).
SMB is a bit of a pain.
To test it here, I was just playing SMB videos via the XBMC filemanager.
Maybe paths for scanned files is different...
That's what I was doing too. I never scan files for the XBMC 'library', since all my 'library' type needs are handled through Plex.
So I either play files scanned by Plex, which works fine through the PlexBMC addon, or else I play files not scanned at all, through normal SMB fileshares, which works fine when browsing the files with 'ES File Explorer' to pass the files on to 'MX Player', but never works when trying to do it through XBMC/Kodi. But from what you said in your reply I now understand that this is probably an authorization issue. (More on that below.)
Also, it's not going to work for password shares.
I agree that it doesn't work as-is, but I disagree in the sense that it definitely would work if the access links were handled properly by XBMC.
(In the same way they are handled by 'ES File Explorer', which has no problems invoking 'MX Player' with SMB links.)
I always use password protection (in my LAN nothing is shared for anonymous access), and for that reason I naturally include username and password for each XBMC source path defined. This being the case XBMC is aware both of the passwords needed and the fact that their use is required (due to their very presence), so for proper access the username and password MUST be included in the access link passed to an external player, in order for that player to be able to gain access to the fileshares. I'm fairly sure that this is exactly what the XBMC/Kodi programmers have neglected, which makes it impossible to use external players for XBMC in a LAN with decent access security.
Btw: I have tested that this bug stretches far back in time, long before the first Kodi alphas, so reverting to older versions would not fix this.
But I will still revert to a slightly older version, so as to regain compatibility with the PlexBMC-supporting skins.
That is the top priority for me, as I have a lot of media handled by my Plex server (somewhere around 16 TB at present).
Best regards: dlanor