Kodi 16

Rascas

No, Kodi default resolution is the "DESKTOP" setting and that is either the native resolution of your TV/Monitor, or the resolution you force in config.txt.
I tested this a bit more and I still cannot find any problem playing videos, either SD, 720p and 1080p, no matter what combination of resolution settings I have in config.txt and Kodi itself. You must have changed something in your setup that is causing that issue.

What I can confirm is your 2nd issue. If you set one resolution in config.txt and a different one in Kodi, (eg: config.txt 720p, kodi 1080p) when you exit Kodi, the resolution is not set back in ES and happens what is in your 2nd foto.
You can easily fix this by editing /usr/bin/kodi and adding the next line in the end of the file, after the last "done":
sudo tvservice -p >/dev/null 2>&1

I am almost sure that this would happen in the previous versions of Kodi also, because I didn't changed anything related to this.

If this works for fine for other people, specially the ones with a hdmi LCDs/touchscreens, I can include this on the next version of Kodi, 16.1 when it comes out, it shouldn't take long.

herb_fargus

@Rascas are you using the runcommand menu (https://github.com/retropie/retropie-setup/wiki/runcommand) to force resolution or config.txt because it's possible that may affect it as I don't know how kodi responds to render res changes with runcommand. I've never changed the runcommand settings for kodi.

mad61190

ya desktop ok that was what it was set to before i had to change it to get the videos to work but isn't retropie's default resolution set for 1280X720 on a clean install or is it diffent per tv. Well im going to clean install retropie 3.6 update it and reinstall kodi and see if im still having the problem because I dont remember changing anything in config other then hdmi_drive=2 and its the only thing uncommitted other then the stuff at the bottom

Rascas

@herb_fargus said:

@Rascas are you using the runcommand menu (https://github.com/retropie/retropie-setup/wiki/runcommand) to force resolution or config.txt because it's possible that may affect it as I don't know how kodi responds to render res changes with runcommand. I've never changed the runcommand settings for kodi.

No, I don't use runcommand, I have a personalized menu with some programs, either program has one .sh script that ES launches.
This is the menu in es_systems.cfg:
<system>
<fullname>Pipplware</fullname>
<name>pipplware</name>
<path>/etc/emulationstation/pipplware-menus/pipplware</path>
<extension>.sh .SH</extension>
<command>%ROM%</command>
<platform>pc</platform>
<theme>pipplware</theme>
<directlaunch/>
</system>

And the kodi.sh is just that:
#!/bin/bash
setterm -cursor off
kodi &>/dev/null
setterm -cursor on

For you maybe it's better to use kodi-standalone, because you don't have an automounter, etc.
Like this, everything works fine, apart from the mad61190 2nd issue. But I think that issue is "normal" on the RPi + Kodi combination, Kodi always had problems to exit (not reboot or shutdown) in Raspberry Pi. The line in /usr/bin/kodi should fix it.
I don't think that some udev rule is missing in Retropie afterall, i think it is something misconfigured in mad61190 setup.

herb_fargus

@Rascas the script RetroPie uses is kodi-standalone. I don't have any of the issues described above so I agree it is likely user error or hardware issues.

mad61190

Alright so I think I found the setting messing things up. I just got done with a fresh install of retropie 3.6, updating it to the latest commit on github, and reinstalling kodi. At first start my videos play fine again yay but re configuring kodi for smooth playback by changing the adjust refresh rate to always and playing a video Ill get the blue screen with no signal again. I had this setting set in the previous kodi before updating, so can you see if you get the same results when trying to play a 1080p file after changing that setting.

Rascas

@mad61190
Yes it is working fine for me, in the matter of fact I always use that setting on, it is recommend to turn it on, unless your TV/Monitor doesn't like it, and maybe that is your case.

mad61190

then i dont understand it. like I said it worked previous with that setting on 15.2 with it being set that way since i received my raspberry pi 3 but now with 16 that setting is what is cause it to not work right.

Rascas

@mad61190 Try adding this line to config.txt:
config_hdmi_boost=7

If it still doesn't work, try with another HDMI cable.

mad61190

Well still no luck tried

old hdmi wire | config_hdmi_boost=7
new hdmi wire | config_hdmi_boost=7
and just new hdmi wire

seems the only way the 1080p videos will work with adjust refresh rate to always is if kodi is set to a resolution of 1080 itself

mad61190

so I just reload retropie 3.6 on another micro sd card this time did not update it but went straight to install kodi so i got version 15.2 on it turn on the adjust refresh rate to always and my videos play fine like they should so there got to be an issue somewhere in kodi between versions 15.2 and 16 not working properly i just dont understand why its only happening to me. both installs are fresh so no other setting have been change or addons installed to mess with it yet. Going to see if i can locate another sd card around here and see if openelec has this issue on there 16.1rc beta builds

UPDATE: So it has to be an issue with kodi it self because even on openelec beta builds im getting the same issue. so im going to attempt later to set a help post over there after looking to see if anyone else is mentioning the problem

Rascas

@mad61190 Yes it is better to report that upstream.

mad61190

@Rascas and everyone else thanks for the help trying to figure out the issue with me ill update back here if I find out whats going on, on the other forums.

mad61190

so with the help of popcornmix on the kodi forums we seem to figure out what the issue is here is a link to the posting if you want to see what was going on.

Rascas

@mad61190 Yes, like I tought. That is your monitor that isn't passing the right info to the Raspberry/Kodi. A fix for that can only be made in Kodi program itself.