-
Notifications
You must be signed in to change notification settings - Fork 42
A list of common issues that you may find when running Spotimc.
Q: After I login to Spotify, the loading animation spins forever.
Short answer: You need to restart XBMC.
Long Answer: That's because libspotify's design allows only one session initialization per process, and all XBMC addons are run in the same process space. Because of that, most session initializations other than the first one (of the running process) fail to start properly.
Q: What's the meaning of "This addon needs to install some extra resources"?
A: Spotimc uses custom fonts and includes in order to show a consistent look between skins and minimize redundant code. As they are not natively supported by XBMC, a trick is performed to circumvent this limitation. What Spotimc is really doing is copying the shared (and unwritable) skin data to your userdata folder, so it can install these resources. Don't worry about these installed resources, as they are uninstalled when Spotimc exits.
Q: Occasionally, tracks take too long to start, or they don't start at all.
A: That's something we'll have to live with for now. XBMC's single process architecture (mentioned some questions before) renders a fix for this difficult.
Q: How does it work?
A: Spotimc is developed in pure python and is able to access to the Spotify service via pyspotify-ctypes.
A local proxy server thanks to pyspotify-ctypes-proxy works as a bridge that delivers image an track data to XBMC, protecting them with some basic token authentication mechanism. This proxy server's sole purpose is to bring the Spotify music service to the XBMC platform.
NEVER attempt to use it as a mean to make permanent copies of track and image data. Libspotify's terms of service forbids this kind of use.