- Kodi security
- Password protected Media Center
- Unsupported Media
No video starts on Chromecast, or a message can not play this file is shown in local video player, or a message incompatible media type is shown.
This is most of the time due to a problem with Kodi internal security.
To confirm this just try to offline download a file from Yatse and see if it shows error 401. See here for help on testing that. If you see error 401 then you are facing this problem. If not then see the second part of this article.
After having fixed the Kodi part, to avoid synchronisation problem it is recommended that you force a sync in Yatse, swipe to refresh (pull down) in corresponding screens
The Kodi security system include 2 different things:
- Each file remotely accessed must be part of a source that have the allowsharing value to true. On some Kodi distribution, your media are scraped without being part of a source so can not be accessed.
- The source check is made with case sensitivity, so if you have declared your source as SMB://server/share but your Kodi database contains media with a smb://server/Share path access will be denied.
Missing or bad sources¶
Sometimes your media can be automatically scrapped without a corresponding source being present (rPI, Android, Linux). This is often the case for auto mounted drives like USB devices.
To fix this problem the simplest solution is to add a dummy source pointing to the root directory (Do not set a content type to those sources to avoid duplicates):
- On the Pi, go into Videos (And/Or Audio) > Files > Add Source and add the following two sources: /var/media and /media if you are unsure of where your media are stored.
- On other devices you need to find the root folder containing your media then add it as a source go into Videos (And/Or Audio) > Files > Add Source then enter the media path.
If have manually added your sources in sources.xml, there's chances that you forget the allowsharing part or that you use login/password directly in urls. In that case please remove the source and them back from Kodi GUI.
If you use MySQL as a Kodi database, then you can see all your media on all your Hosts even if you have not declared your sources on each clients. Unfortunately this does not allows remote access to your media. So you need to declare them on all your host (With correct case, so it's better to copy your sources.xml file to avoid mistakes)
Case sensitivity problem.¶
The attempt to correct this at Kodi level was refused (See here) so you need to correct this on your side.
This is cause by a change in your sources between the first scrape and the access time. If there's a case difference (SMB:// vs smb:// for example) then access will be denied.
Since Kodi scraping does not take in account those case changes a rescrape does not fix the problem.
The only solution is to remove your faulty sources, accept the Kodi message asking to delete all related content, then add the source again and scrape it again from scratch.
To be sure you can also delete the MyVideoXX.db or MyMusicXX.db files in your Kodi home directory then rescrape.
See http://wiki.xbmc.org/index.php?title=Media_sources for help on dealing with sources in Kodi and http://kodi.wiki/view/sources.xml if you want to deal with them manually (the allowsharing is the important part) (This Wiki is not 100% up to date regarding login/password in sources.xml, they will prevent remote access while working inside Kodi).
Password protected Media Center¶
Yatse support connecting to Media Center with password and can stream the content to other devices like UPnP. But some players (UPnP / Chromecast) does not support access to those protected media. You can use the Force UPnP for streaming advanced settings to force the usage of Kodi UPnP server to serve the media, as this one is not password protected.
But you need to activate all UPnP related option in Kodi settings for this to work.
Yatse is a powerful application that allows a lot of things to be connected even if they where not supposed to. But still Yatse is not a magic application and can not make impossible things happens.
Since Kodi does not support transcoding (The action of changing a media from a format to another) if your media are not compatible with the player that you chose then it won't play or play with limitations (no sound or no video).
- See http://yatse.tv/redmine/projects/yatse/knowledgebase/articles/8 for details on Chromecast limitations.
- See http://yatse.tv/redmine/projects/yatse/knowledgebase/articles/7 for details on addind support for DTS/AC3 to Mx Player.
Kodi also offer PVR integration and addons support that allow access to lot's of media, the problem is that Kodi addons API is limited and does not allow Yatse to gather the necessary data to access those data most of the time.
Meaning Yatse can not stream PVR and most addons that gives access to protected content, since Yatse can not have access to the security information needed for that.
If you still have problems or do not understand this FAQ then open a proper issue with logs for support: Support