YouTube playback - random blank video with 'input not supported' monitor message


My vero4k is connected via hdmi to a 27" Acer S271HL 1080p PC monitor.

I’ve had three instances now in which playback of YouTube video causes the monitor to display an in-built message ‘input not supported’. Audio is via the vero’s 3.5mm jack, so I know the vero is still playing the stream.

Power cycling the monitor, or connecting via ssh and rebooting the vero resolves the issue.

The first time this occurred was some weeks ago. I was using my PC, connected via dvi to the monitor. I manually switched inputs via the monitor controls, and received the message.

The 2nd instance (7th november) occurred after two streams from the same channel failed to play. Attempting to start a third caused the error.

Today the error happened when attempting to resume a stream which had previously been watched part-way through.

[Edit] Attempting the play the same video after uploading logs triggered the issue again. I rebooted the vero, hoping to recreate the error, and provide smaller logs, but was unable to.

Recently I’ve updated to the official October Vero4k build (Kodi17 based), and latest YouTube plugin, however the issue has occurred twice using earlier YouTube versions, on the custom build @sam_nazarko created to test fixes for the h265 8bit colourspace problem.

I’m assuming the YouTube plugin is sending some display mode signal which isn’t the expected 1080p60, or one of the numerous other combinations of resolution / refresh rate (60hz maximum) supported by the monitor.

I’m providing a log, which unfortunately is very large, as full debugging is enabled; as the issue is rare in occurring, it’s the best I can provide:

[Edit: redacted]

Many thanks in advance

Can you try the latest improvements?

I’d appreciate it if you could test this and provide feedback before we potentially release this as an update to other users. To test this update:

  1. Login via the command line
  2. Edit the file /etc/apt/sources.list
  3. Add the following line: deb stretch-devel main
  4. Run the following commands to update: sudo apt-get update && sudo apt-get dist-upgrade && reboot
  5. Your system should have have received the update.

Please see if the issue is resolved.

I also recommend you edit /etc/apt/sources.list again and remove the line that you added after updating. This will return you to the normal update channel.


Hi Sam,

The error is pretty hard to reproduce, but I’ll certainly give this a try and let you know how I get on.

Updated. Just to confirm, Uname -a output:

Linux Osmc_Vero_4K 3.14.29-119-osmc #1 SMP Wed Sep 5 19:09:21 UTC 2018 aarch64 GNU/Linux

System Info reports:
Compiled: Oct 31 2018

Many thanks

Yes — we only want to downgrade the kernel here



I’m running tests now.

One thing I’ve noticed for a while on YouTube, which didn’t used to occur, is seeking / resuming tends to play the video without audio for c. 5 seconds.

Will this remove the h265 8bit colourspace fix (not an issue if it does, just asking so I know what to expect)?

From the top of my head: yes.

1 Like

I can confirm that the colourspace issue fix has been undone (just for the record)

You can try staging to upgrade.
This should fix the issue here and fix colour space.

Hi Sam,

Can you point me to the steps to do this?


I’ve been starting a lot of random YouTube videos for an hour or so, with no issues, however the problem occurs too rarely for this to be significant. I’ll continue testing.

It’s explained in the second post.

Thanks, but I’ve already done that. Sam’s talking about combining the kernel rollback with the specific colourspace fix from staging.

No — from your kernel version you have downgraded via hotfix

If you update to staging you will be on the latest where things should be improved

Sorry Sam, I’m operating on very little sleep.
I completed all the steps in the second post on this thread.
I can dig back through the colourspace thread to obtain the steps to obtain the test fix you built for mebefore the October release, but i don’t know which kernel version that’ll leave me on.
I’ve no recollection of applying any hotfixes.

[Edit] @sam_nazarko, I’m leaving the system as-is in case I inadvertently change to an incorrect kernel; I can easily get by without the colourspace fix for now. Just to reiterate, all I’ve done is apply the exact steps you provided in your reply to my first post in this thread.


OK – don’t worry.
I think if you followed those instructions you should be on a newer version; but things might’ve got mixed up.

When you are ready let me know and we can follow some steps or you can wait for the next update.


Thanks Sam; ready when you are.
Kernel and build versions are as per the third post in this thread.
Full logs are available whenever required.

Can you try updating again? You should be on a newer version

Hi Sam,

Sure. Should i repeat the steps in the second post on this thread (as opposed to updating to the latest release via My OSMC)?


Yes – that should do it for you.

Cheers Sam,

I’ll give that a go later today, and perform a round of testing.

Many thanks,

1 Like

Hi Sam,

I repeated the update process, however the h265 8bit colourspace issue persists.

I noted that no packages were updated:

osmc@Osmc_Vero_4K:~$ sudo apt-get update && sudo apt-get dist-upgrade
Hit:1 stretch/updates InRelease
Ign:2 stretch InRelease
Hit:5 stretch-updates InRelease
Hit:6 stretch Release
Hit:3 stretch InRelease
Hit:4 stretch-devel InReleaseReading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.