OSMC Vero V Review

No one. The person who would be able to figure it out is tanio99 and it hasn’t remained unfixed due to a lack or trying or desire (at least on OSMC’s end). It is more of a ‘some nuts are easier to crack than others’ type of situation.

Has anyone tried accessing Netflix, Disney Plus, Prime Video, etc. on the Vero V yet? I’m interested in what the resolution limits are compared to the Vero 4K.

just took a look at these test clips. The 480i_60 mpeg2 clip is terrible with hardware decoding, a very nasty shimmer to it that is gone when switching to software decoding.

the 1080i/60 VC-1 is interesting. With hardware playback, about 2 seconds in the output switches to 24p, picking up the 3:2 pulldown? Playback is very clean. Software playback sticks at 60 Hz.

Does anyone have similar test clip for 1080i h264? I feel sure the native interlaced scenes in my classic Dr Who blurays have more detail on the V than with the 4K.

I played a DVD rip with 3:2 pulldown and I think it’s equally poor on the V and the 4K.

1 Like

Not precisely, although some of the other clips I posted (the bits from Sherlock, Peaky Blinders and Luther) are 1080i/50 h.264. The Sherlock clip is probably the easiest to analyse visually.

Those wedge patterns come from an old Spears and Munsil calibration disc, so if anyone has a more recent version of such a disc, that might have h.264 equivalents.

If you haven’t already, also check out the Timeflight clip and compare hardware and software decoding - that’s a good one to test for whether it’s correctly applying diagonal filtering when in field-interlaced mode. (I’m guessing not).

Just got around to looking at the Sherlock clip, comparing the Vero V vs an old Pi running August OSMC. On the V Mycroft’s suit has obvious moire. On default settings it’s there on the Pi but with the Pi you can have hardware acceleration and disable deinterlacing, and when we do that the moire in Mycroft’s suit is gone, overall detail level is much improved. Would be great if this could addressed in some way, at present I’m only using the V in my main system for 24p and some 50i h264 content that is fully interlaced. For everything else I’m still using a Pi or the Infuse/ATV combo.

Heartily agree! Give me a shout if you have a chance to test my “Timeflight” clip.

Might want to keep an eye on this thread, btw:

well, I wouldn’t normally watch anything from Timeflight, but I have to give you credit, this is a good test clip.

Given previous comments, no surprises that with the V there are nasty jaggies on the Tardis console with hardware acceleration (I imagine there are as well with the 4K but I did not test). Switching to software playback fixes this, and if it weren’t for the occasional stutter, I’d consider disabling hardware acceleration for MPEG2.

I then played the clip on my OSMC Pi 3B, and I was impressed. Of course the Pi 3B has to use hardware acceleration, and the obvious jaggies with the Vero were pretty much absent as far as I could tell. On the basis of that one clip (yes, Timeflight!) I’m going to look again at putting Pi’s back in to service given the amount of MPEG2 in my collection, pending a fix for the Vero.


Heh, thanks. :slight_smile:

Yes. Sadly the Vero 4K was once capable of doing rather good diagonal filtering in hardware, but this got broken with the move from the 3.14 to 4.9 kernel, and hasn’t been fixed since. If you’ve got a spare Vero 4K (and enough HDMI ports) you could try installing the last Kodi v18.9 release on it (which was also the last with the 3.14 kernel) and using that as your MPEG2 playback device (with hardware decoding enabled); it used to look very good. Hardware cadence detection was also better on DVD remuxes than it is now. 1080i wasn’t much better than now, but the moiré patterns from cadence detection errors were a little less obvious - the diagonal filtering meant they were more blurry and less blocky. Interlaced VC-1 playback is better with a modern image, though. (And of course the Kodi 18.9 install doesn’t support 3D and HDR playback wasn’t as good).

Hi. Trying to do this following old 4k instructions but set up a bit different as it’s already part of an activity. I opened ms media player on app and then bluetooth pairing on myosmc and I’m not getting anything. Is this the process you followed ? Ta

@ac16161 You’ve been extremely helpful already :slight_smile: but if you happen to have some more time to spare, could you have a go at running my “Planet Earth” test clip? (As noted when I first posted it, that one is designed to check for stuttery playback when outputting a 25fps video at 50Hz).

can anyone point me to a link for last V4K image on the 3.14 kernel? The main download page only has 2023 releases that I could see. Curious to see how much of an improvement it is for interlaced MPEG2.

I didn’t notice any obvious stutter, but it’s a very short clip and my eyes may not be tuned in to the issues you’ve picked up.


thanks for the link. I installed https://ftp.fau.de/osmc/osmc/download//installers/diskimages/OSMC_TGT_vero3_20201227.img.gz on a spare 4K, and my goodness, what an improvement on interlaced MPEG2. I see now why @angry.sardine has kept pushing on this. Much better than the current image for the V. It’s not ideal for me to run a K18.9 box given I have a shared database, but the current OSMC on a Pi 3 is delivering similar MPEG2 performance to 18.9 on a V4K, so between them they’ll cover my MPEG2 playback needs pending an update for the V or 4K.

1 Like

It’s nice to have at least one person agreeing with me. :smiling_face_with_tear:

The lack of diagonal filtering since the change to the 4.9 kernel doesn’t just affect MPEG2, incidentally, it affects VC-1 and h.264 as well; but when the source is 1080i rather than SD, the effect isn’t quite so in-your-face obvious.

To be fair, the deinterlacing quality with software decoding (on the 4K+ and I assume also on the V) is much closer to what you used to get in hardware with the 3.14 kernel, although software decoding does occasionally produce other issues.

1 Like

“£149 is the introductory price. That’s what we will allow customers to place an order at. Then, when we have to, we reserve the right to / may need to raise the price.”

Hope you don’t raise the price, rather do sales at lower prices.

Got my Vero V from PiShop.us today, updated the f/w, and did several tests, comparing with my 4K+, Fire Cube 3, and Zidoo Z9X (and Pro). Overall, I’m happy with V… it’s snappier than 4K+, but not by as much a big factor as I’d expected. Still, I’ll take the performance boost over 4K+. Guess I’ve become spoiled with Cube 3’s performance, which is even better than Shield TV Pro’s. Cube 3 does everything + premium streaming, just not 3D MVC. All HDR formats, HD/object-based audio passthrough, and it’s fast/powerful.

With Vero V, 3D MVC and ISO’s seem to work very well; tried several random titles. 3D ISO seeking & chapter skips are no longer laggy like with 4K+. Didn’t get a chance to check (yet) if macroblocking issues still exist w/‘Avatar’, ‘Gravity’, ‘Ready Player One’ & ‘A Christmas Carol’ like w/4K+. Has anyone?

So, why am I saying don’t raise the price, and in fact consider lowering it?! Other than 3D, most S905X4 boxes with CoreELEC will perform as well as V for 1/4 the price, and a couple will even support Dolby Vision (which V doesn’t) for $50 or so less than V. For 3D, I could just as well keep Zidoo Z9X or Z9X pro, or even Dune Real Vision HD Plus, for a bit more and get 3D + all HDR formats + VS10 engine. So, Vero’s V value prop isn’t as good in comparison. Having said this, I’m considering keeping just my Fire Cube 3 for most videos, and Vero V mostly for 3D, and getting rid of my Zidoo’s. But, for others, it could be not worth springing for V because of the price in comparison to what they’re getting with a cheap S905X4 box w/CoreELEC or a Zidoo/Dune, especially if 3D isn’t a factor. Other than 3D (which is a big deal for me, but probably not many others), V doesn’t provide any added value IMHO over a cheap S905X4 box w/CoreELEC.

Unfortunately yes, it still exists. The decoder firmware is either the same or has the same issue :frowning: .

To be very honest - I have never seen a product on the market which such return on investment over years (and I’m speaking 5+ here). The OSMC Team really does an amazing job and is providing the best support in the industry. All the big players bring out a new version of their money making device and forget about the old ones. And that only makes me move to OSMC.

Only thing I miss now is a better UI for Netflix running on it and the possibility to OOTB add a device through bluetooth to listen to my music (phone or whatever).

@sam_nazarko, will this be addressed in future batches?

Maybe I’m dense, but what exactly is the issue with the underside of the Vero V and why is there a concern about a side of the player that isn’t normally on public display?

How can we improve the BT experience? Can you detail how you would like it to work?