VeroV Crashed, now won't pair remote

Help and Support Vero V
1

My Vero V had a spectacular crash, the video froze and the sound kept going. After I cycled the power, it booted up OK but…

  1. The remote stopped working
  2. It won’t output 4K anymore, only 1080p (I was able to use KORE to control it). *RESOLVED

I tried pairing the remote again, no luck.

Reinstalled OSMC from an SD card, all good up to “Pair Remote”. When I hold Home and OK nothing happens although I see lights on the remote.

Already tried new remote battery also, no change. Nothing is plugged into the USB ports. :frowning:

What can I try next?

*RESOLVED as not a Vero or OSMC problem but a bad file.

2

Hi

Can you please upload some logs (you can use Kore to get them) so we can take a look?

Sam

3

An update. It seems to play some 4k content but not other. The file that it crashed on was playing in 4K before the crash, but now only in 1080p.

Logs are here: https://paste.osmc.tv/kajozixaqu

1st file (at 2025-07-15 13:39:10.069 T:2929 in KODI log) plays fine in 4K HDR. Mediainfo Link

2nd file (at 2025-07-15 13:39:50.221 T:2929 in the KODI log) does not play in 4K, only 1080p but still in HDR (as reported by the Projector) - MediaInfo Link

I noticed the one that plays has Chroma subsampling 4:2:0 (Type 0) while the one that does not has 4:2:0 (Type 2) and there are some errors in the log that seem related, many lines like this:

ffmpeg[0xb06746a8]: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.

Still no luck with the remote though, using KORE to control.

4

I’m surprised Ballerina played as 4k before your crash. IMVHO people who remux to a resolution of 3828x1588 also declaring the aspect ratio as 2.4:1 (3828/1588 = 2.41) should be made to sit in a dark room with no internet for a month or two or until they repent.

We’ll see if the whitelist algo can be changed to accommodate this. I’m pretty sure that’s the problem.

That’s expected - I think it relates to thumbnails, not video.

5

Interesting… it’s possible I’m wrong. I usually peek at the bottom corner of the screen when the projector settles on a resolution, it’s possible it was actually only in 1080p in that case!

Yes not my remux, waiting for the BD to arrive from Amazon then I will replace with the proper file.

In theory, remuxing it and setting the correct Aspect Ratio would fix it?

Thanks for you help :slight_smile:

Any thoughts on the remote situation?

6

Sorry. Not my department.

7

I checked. If you use the whitelist it should play at 4k. If you don’t specify a whitelist, then either the width or the height has to be an exact match.

I guess if either the width or height are exact you can expect a better picture as there will be less scaling going on.

Actually, Kodi takes no notice of the aspect ratio - just uses height and width.

1 Like
8

Will check shortly.

1 Like
9

I checked. If you use the whitelist it should play at 4k. If you don’t specify a whitelist, then either the width or the height has to be an exact match.

Thanks, seems this issue was entirely the file and not Vero / OSMC / KODI so I feel this is resolved and good. All my own files work fine, including 4K HDR.

When I opened that file with MKVtoolNix it shows a resolution of 3828 x 1588 as set in the MKV which seems odd. Wont be in such a rush and will stick to my own remuxes in future!

10

I tried a few things for the remote:

  1. Re-installed OSMC
  2. Moved to a totally different spot away from any other equipent
  3. Tried my Vero4K remote + Dongle
  4. Tried setting a different remote and then back to osmc-remote-lirc in OSMC section in KODI
  5. Switched On / Off the “Disable RC6” toggle on same page
  6. Tried re-syncing several times, but only ever get blue light, not flashing.
  • For 3, I put the 4k in the same location and checked the remote, worked perfectly.
  • Resynced the remote to the 4K, still working. (flashing blue light)
  • Unplugged the dongle, move it to the VeroV
  • Rebooted VeroV
  • Re-synced the remote (flashing blue light)

But the remote didn’t work :frowning:

UPDATE: Reading through the many “VeroV remote not working” post here (seems to be a common issue with the V?) I came across this:

And hey presto, the old Vero4K remote works when plugged into the USB port furthest from the SD card slot, but does not work when the other one.

Of course would be nice to get the VeroV one working too, as my 4K was in the bedroom, but for now at least I can navigate without a phone!