I bought a Vero 4K + in 2019, and almost everything is working good. My issue is about files with original language names (as well as the character set, like cyrillic or kanji) which seems to create an error on OSMC as it’s trying to access the files without success.
My medias are all on /media and it is a shared file system with CIFS. As I recall, it was always like that, but it’s getting annoying now that I fill my storage with more movies from these countries, so I don’t think it is a bug introduced in a recent update.
The actions I did through it:
Power on the device
Wait until OSMC automatically start and be ready on the main page
Select Movies
Select a movie which is named “Брат”
OSMC tells me the movie isn’t present anymore, so I delete from the library
Update the library (not ‘Cleaning’, just update)
Select a movie which is named “Брат”
OSMC shows an error “One or more items failed to play. Check the log for more information about this message.”
My device is kinda fresh, I didn’t try to do a full reset yet, but I haven’t install things as I recall, except recently things like:
cifs-utils
rsync
console-cyrillic
xfonts-cyrillic
locales-all
(the last three are because of things I read on internet, trying to support the character set…)
And I was about to forget: when I update the library, I see the little notification panel on the top-right with the names of the files being scanned, and each time cyrillic letters or kanjis appears as interrogation marks ‘?’. And when I go on the movie information page, the option ‘Refresh’ shows the path to the movie, but here, again cyrillic letters or kanjis appears as interrogation marks ‘?’.
I hope I gave you everything. Thanks you for reading so far ^^’
This sounds like a second issue unrelated to the one with scraping. When you see that dialog don’t remove the file. When using fstab to manualy create a mount point sometimes it can be slow making the connection or it can become interupted after some time. You can try (if not already done) setting wait for network in the My OSMC add-on or add a wait time in Kodi’s power settings. Even still it can happen (under what circumstances I don’t know) and if that is the case then you would probably have better luck changing the manual mounts over to using autofs. You can find a guide for that [here]
Your logs for Kodi didn’t upload with the rest. It might be a bit more clear what is going on if you included those.
Someone else would need to chime in about the font issue as that is not something I’m familiar with. On a completely unrelated topic you should switch your UI over to 1080p as running in 4k like you are is prone to causing issues.
I don’t know, it is strange because if the device is on for 10 minutes already, and I am able to play another movie from the same shared storage, I should be able to play this “Брат” movie as well I guess. Anyway, I just changed from fstab to autofs with the guide you linked (thank you), and checked the option to wait network in the power settings.
Unfortunately the exact same error is displayed again, I only tried to start the movie, I didn’t remove it from library, didn’t do a library update neither a clean.
About the logs I’m not sure to understand, what is missing? I followed the guide to ask for help and did the command to automatically grab logs and upload them to the pastebin.
About the UI, just to be clear, you mean “GUI Resolution: 3840x2160 @ 60p” to change to “1920x1080 @ 60p”? If so, are you sure, because in the log file, we can see my screen details in “Display Cap CTA” and it has the support “2160p60hz*”?
The Kodi.log and Kodi.old.log didn’t upload with the rest. Those are the ones that would show what file paths Kodi is trying to access. They may have been too large to upload so if you rebooted a couple times and then tried again that may resolve that issue.
I would try adding “vers=3.0” to your mount options and see if that makes a difference. They are currently mounting using SMBv1.
You might also try a normal Kodi path to see if the issue is also present connecting that way. By this I mean going to videos>files>add videos>browse>add network location>[put your NAS’s IP address in the server name field and you user/pass]>OK then click on the new location (smb://192.168…) and then OK and OK. When the dialog box pops up asking to set content click cancel or else your going to make a mess of your library. You can then just play from Video>files>192.168…> to see how it acts with Kodi paths.
We recommend people with 4K TVs set their user interface (UI) to 1080p. Kodi’s UI is not optimized for 4K yet and this can put unnecessary demands on your device and can lead to a suboptimal picture quality, as well as potentially cause other issues.
With the above settings your UI will be output in Full HD and your 4K content will be output in 4K.
*Information regarding the whitelist can be found here. If you have any doubt, feel free to upload some logs so we can verify that your settings are indeed correct.
We recommend people with 4K TVs set their user interface (UI) to 1080p. Kodi’s UI is not optimized for 4K yet and this can put unnecessary demands on your device and can lead to a suboptimal picture quality, as well as potentially cause other issues.
I switched to 1080p, then I restarted my backend storage and the device Vero 4K, and it seems it worked, I could do the library update and the names appeared with the specific alphabet, and also for playing the movie. It seems it’s the combination of the screen resolution and autofs that solved my issues. Thank you very much darwindesign and sam_nazarko
I would try adding “vers=3.0” to your mount options and see if that makes a difference. They are currently mounting using SMBv1.
It was solved before that but I changed it after anyway to use the highest version, and remove the SMBv1 support from my backend storage.