Kodi Community Forum

Full Version: No Video in Full Screen
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I've had this problem before, but it started again two nights ago... When I have Kodi in full screen mode, there is no video. The last version that worked for me with no black video issue was 15.2.

I was using 17.3 successfully for months, but paused a video from my library and when I pushed play again, screen went black, but sound played. I uploaded version 17.4, with same effect. Is there anything I can do, short of go back to 15.2, which had other issues?

I am running on Windows 7 Home Premium, sp1, 64-bit. The below log shows that I tried to change to full screen. This is a fresh install!

Thanks, in advance, for any assistance you can provide.

https://pastebin.com/jhmDUqh3
I had a similar problem with 17.4 - again with no apparent cause after many trouble-free years.

I got video back by activating 'Use fullscreen window' in Kodi's display settings. You can't do it directly from windowed Kodi, so you have to switch to fullscreen and then make the change blind. It's a bit tricky but I managed to set it after some trial and error (listening for the UI clicks helped).

I am, however, keen to use the true fullscreen option if I can because Kodi doesn't take the focus if my mouse cursor happens to be on the task bar when I start Kodi.

My own log file is at https://paste.ubuntu.com/25514014/

I started Kodi under debug logging. Tried to switch from 'fullscreen window' to 'true fullscreen'. That appeared to work but, if I'd shut down and restarted I'd have got a blank screen. Switched back to 'fullscreen window'. Switched to windowed mode (I have that mapped to the 3 key). Switched back to 'fullscreen window' and got the blank screen.

Problem is easily reproduced if necessary.

Andy

Sorry forgot details:
Windows 10 32-bit creator's update fully patched
Kodi 17.4
HDMI wasapi to an Onkyo tuner and from there HDMI to a Phillips 1080p TV
Silverlake CPU on an Intel motherboard (internal display adapter disabled)
@AndyHenderson Intel® HD Graphics 4600 https://www.intel.com/content/www/us/en/...05524.html looks like you're sharing graphic memory on board, you might either be running short of graphic memory or fragmentation of what you have could be creating an issue, see if there's a way of increasing the proportion of gfx memory.

@dschroed Intel® HD Graphics https://en.wikipedia.org/wiki/Feature_le...irect3D_11 See if you have the routines that fit.

Supported hardware (wiki)
(2017-09-11, 20:53)PatK Wrote: [ -> ]@AndyHenderson Intel® HD Graphics 4600 https://www.intel.com/content/www/us/en/...05524.html looks like you're sharing graphic memory on board, you might either be running short of graphic memory or fragmentation of what you have could be creating an issue, see if there's a way of increasing the proportion of gfx memory.

@dschroed Intel® HD Graphics https://en.wikipedia.org/wiki/Feature_le...irect3D_11 See if you have the routines that fit.

Supported hardware (wiki)

Thanks for your help, @PatK. I did confirm that I have Direct3D 11_0, which I tested and confirmed it is working. My hardware matches the supported hardware list. I am still at a loss. Anything else I can try?
(2017-09-11, 20:53)PatK Wrote: [ -> ]@AndyHenderson Intel® HD Graphics 4600 https://www.intel.com/content/www/us/en/...05524.html looks like you're sharing graphic memory on board, you might either be running short of graphic memory or fragmentation of what you have could be creating an issue, see if there's a way of increasing the proportion of gfx memory.

@dschroed Intel® HD Graphics https://en.wikipedia.org/wiki/Feature_le...irect3D_11 See if you have the routines that fit.

Supported hardware (wiki)

Thanks for the suggestion.

I found an option to increase graphics memory in the BIOS settings. I increased it quite a bit but the change had no effect. Presumably the reboot would have eliminated any fragmentation. So, I'm still stuck with using fullscreen window.

Andy
In both cases, it comes down to the graphics, and in windowed mode, Kodi is using the built in windowing routines MS supplies, while in full-screen Kodi is in control utilized through the graphic engine and nothing is standing out in the logs. Windows 7 sans areo will give you a bit more punch in the graphic area. For the windows 10 users, might try the 64 bit Kodi Leia to shake up things. Failing that, I'm going to suggest LibreElec from a USB drive would eliminate the o/s as the culprit and prove out the set-up, and might give some joy.

Streamline your systems, eliminate unneeded background tasks. Use portable mode for testing different Kodi installations, it will save a lot of greif in the end. http://kodi.wiki/view/Windows_FAQ#Portable
(2017-09-12, 02:34)PatK Wrote: [ -> ]Streamline your systems, eliminate unneeded background tasks. Use portable mode for testing different Kodi installations, it will save a lot of greif in the end. http://kodi.wiki/view/Windows_FAQ#Portable

So finally had time to work with the portable version. I can run 17.4 in full screen, using a usb stick! I don't understand why I can't run full screen when I install it on my dedicated computer. Any thoughts on why it would work from usb and not on the computer would be greatly appreciated. (I don't think I have any unneeded background tasks.) I would continue to just run in portable mode, except there are other underlying issues with that.(i.e., having to remove and replace usb on computer restart, where to change the keymap for my remote, changing some of the font sizes, etc.).

Thanks for any advice.
You can install Kodi portable on any of your sources (even the C: or F: drive), I have multiple Kodi portable installs all over the place for testing purposes. There's nothing special regarding a system install vs portable mode other than the portable folder designation, hence if one works and the other does not... there's some difference between the two.
Thank you for your help @PatK! I partitioned a drive, just for Kodi. It works in full screen mode from that drive! There must be something on the C: drive that was messing it up. Thanks, again!