Vero4K takes more than 20 seconds to start playing files

For a while I’ve had issue where vero randomly froze once in a while but I’ve been a little lazy to look into it and raise it here.

From today when I try to play any video file, (one that I had on my drive and always worked) it takes more than 20 seconds to start playing.

I’ve recently reinstalled vero a few months back so the install is pretty clean and there isn’t a lot of stuff on Kodi or the OS.

This new issue appeared out of nowhere and I have not install anything new on it so I’m surprised this is happening. It almost looks like some hardware issue that happened over time which started with random freezes about 6 months ago.

The random freezes were experience on the original install and when I recently installed it clean so it’s not relate to the state of the OS or Kodi which hasn’t changed much or at all.

Any advice?

To be honest I was considering to buy a vero4k+ (mostly cause of the 1Gb interface) but it has been out for more than 2 years now and I’d be a bit regretful if in 6 months or so there is an hardware upgrade.

Anything in the pipeline Sam?

Ideally I’d like to fix the vero4K i have but the random freeze have been getting more frequent and quite annoying, in addition to that I now have this delayed play/freeze issue whenever I play any file.

Are your files located on a hard drive attached to and powered by the Vero? It is kind of hard to speculate without logs or any details that may give us a clue.

As for your question about a Vero update, OSMC products are not announced in advanced of release.

As @darwindesign already requested: To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.

Depending on the used skin you have to set the settings-level to standard or higher, in summary:

  • enable debug logging at settings->system->logging

  • reboot the OSMC device twice(!)

  • reproduce the issue

  • upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A

  • publish the provided URL from the log set upload, here

Thanks for your understanding.

OSMC skin screenshot:

As a hunch, not seeing any logs, my guess would be that you are using SMB and you need to enable the ‘Mitigate SMB issues’ option we added under Settings -> Services -> SMB.

But some full logs uploaded as advised by @darwindesign should let us see what is going on.

Thanks for your replies.

Apologies if it has taken me a bit long to answer, was a bit of a busy weekend (at home hehehe)

Of course logs, i’ll provide that when I get a chance later. I’ll do a bit more digging as well.

Btw I tried playing files from 3 locations, sd card, network SMB mount and locally attached usb disks. All of this worked perfectly fine until a few days ago.

Thanks for the suggestion i’ll try that but considering the issue is also present on sdcard and usb, I’m not sure.

Also make sure that your system is up to date

Sam

ok I fixed the issue.

before enabling debugging I looked at kodi.log file just to see if there was something odd and I found this:

2020-12-06 19:05:26.607 T:3776950496  NOTICE: script.tv.show.next.aired: ### starting data update
2020-12-06 19:05:26.608 T:3776950496  NOTICE: script.tv.show.next.aired: ### grabbing a new country mapping list
2020-12-06 19:05:28.242 T:3776950496   ERROR: script.tv.show.next.aired: ### ERROR retreiving updates from thetvdb.com: File is not a zip file
2020-12-06 19:05:28.939 T:3776950496  NOTICE: script.tv.show.next.aired: ### data update finished
2020-12-06 19:20:31.471 T:3776950496  NOTICE: script.tv.show.next.aired: ### starting data update
2020-12-06 19:20:31.472 T:3776950496  NOTICE: script.tv.show.next.aired: ### grabbing a new country mapping list
2020-12-06 19:20:33.103 T:3776950496   ERROR: script.tv.show.next.aired: ### ERROR retreiving updates from thetvdb.com: File is not a zip file
2020-12-06 19:20:33.780 T:3776950496  NOTICE: script.tv.show.next.aired: ### data update finished
2020-12-06 19:40:36.054 T:3776950496  NOTICE: script.tv.show.next.aired: ### starting data update
2020-12-06 19:40:36.055 T:3776950496  NOTICE: script.tv.show.next.aired: ### grabbing a new country mapping list
2020-12-06 19:40:37.801 T:3776950496   ERROR: script.tv.show.next.aired: ### ERROR retreiving updates from thetvdb.com: File is not a zip file
2020-12-06 19:40:38.520 T:3776950496  NOTICE: script.tv.show.next.aired: ### data update finished
2020-12-06 20:05:41.006 T:3776950496  NOTICE: script.tv.show.next.aired: ### starting data update
2020-12-06 20:05:41.006 T:3776950496  NOTICE: script.tv.show.next.aired: ### grabbing a new country mapping list
2020-12-06 20:05:42.587 T:3776950496   ERROR: script.tv.show.next.aired: ### ERROR retreiving updates from thetvdb.com: File is not a zip file
2020-12-06 20:05:47.283 T:3776950496  NOTICE: script.tv.show.next.aired: ### data update finished

it looks like this plugin started erroring a few days ago and for some reason is causing kodi to take ages for the player to play a file.

Strangely the errors don’t seem directly related to the issue since they do not occur everytime you play a file but after uninstalling the plugin the issue disappeared and I’m now back to normal :slight_smile:
Clearly it was slowing things down because of the failure.

I was surprised to be honest I didn’t really expect it to fix the issue but always good to remove the anomalies first (if possible) even when they seem unrelated right?

Anyway I should have looked at the log file before raising this request (and without providing logs).

Sorry Guys!

Believe it or not being also one of those that gets easily quite irritated when users don’t look at issues at all and just raise tickets without info I find myself a little puzzled by why I did just the same as an end user :frowning:

Anyway thanks, and again I don’t enjoy wasting people’s time although I’m afraid I’m guilty of the crime in this occasion.

2 Likes

Glad to hear this is now working well now