Vero V / 2026.05-01
Embuary Skin
Emby for Kodi Next Gen Plugin
One of my favorite unique aspects of the Embuary skin is the widgets showing relevant and timely info such as “Continue Watching” and “Next Up” and “Latest Shows” and the like. These work via a multi-step process. The Embuary Helper reaches out to the Emby API for the list of videos for the widget and gets it in JSON or XML format. It then shows a spinning wheel while it gets all of the thumbnails for the movies/shows before finally showing the full list.
Generating these lists takes a very notable amount of time on my new Vero V – five or more seconds.
This is an eternity compared to my original and now ancient Kodi HTPC running on a dual-core 2014 Intel i3 and 7200 RPM spinning drives. Most of those lists populate essentially instantly and, at most, I might see a spinning wheel for some fraction of a second. The difference between the decade plus system and new Vero V is very stark in this case and not in the direction I’d expect.
The skin, plugins, Emby, and physical switch configuration (latency) is exactly the same between the two Kodi instances.
Comparing the drives (for cache), I’d expect the internal emmc to be much faster than my older hard drives.
The 2014 i3 is only dual core compared to the Amlogic’s quad core design (but this might be mostly single threaded) but does have almost double the max CPU speed. Both seem to hover around 1Ghz when I watch them, though. And if it’s just the CPU speed difference, then I’d expect it to be maybe twice as slow, not many many times slower.
What I’m hoping for is a either the knowledge that the Amlogic chip is so hyper focused on playing media that it’s general CPU work is many times slower than even a decade old entry-level Intel CPU OR that there is some hidden setting that I should be looking that is directly affecting this.
Thoughts?