![]() |
|
[WIP] XBMC + Spotify = True (an XBMC implementation that uses Spotify's official API) - Printable Version +- XBMC Community Forum (http://forum.xbmc.org) +-- Forum: Announcements, Info, and General Discussion (/forumdisplay.php?fid=85) +--- Forum: XBMC General Discussion (/forumdisplay.php?fid=6) +--- Thread: [WIP] XBMC + Spotify = True (an XBMC implementation that uses Spotify's official API) (/showthread.php?tid=67012) Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 |
- arfoll - 2010-12-11 13:16 LeGrandHorg Wrote:"best practice" for integrating Spotify with XBMC? There seems to be a whole lot of information but it is scattered and gathering it all seems to take a couple of nights at least. It's easy you go on my blog (follow the instructions :nod and fix the patch for whatever version of dharma you are using and off you go... The real solution would be to either get this patch included or have someone maintain it properly but I dont think they want this in trunk and I don't have the time to fix the patch and make builds for every OS. A loan patch like this one will always be for the not faint of heart! Glad you got it working ;-) - zteifel - 2010-12-11 15:48 Has anyone got a solution to control spotify in xbmc from the web interface? - LeGrandHorg - 2010-12-11 23:47 arfoll Wrote:It's easy you go on my blog (follow the instructions :nod Well, it built. However, XBMC just bails on start with no error messages even after setting the log level to 1. The log lists the remotes supported...and then XBMC dies a quick clean death and restarts (rinse and repeat ad nauseum). I guess I have myself to blame, going with your patch and SVN trunk. ![]() Now, let's see what happens if I actually really really follow your instructions and use RC1. But what's the fun in that?
- arfoll - 2010-12-12 12:26 LeGrandHorg Wrote:Well, it built. However, XBMC just bails on start with no error messages even after setting the log level to 1. The log lists the remotes supported...and then XBMC dies a quick clean death and restarts (rinse and repeat ad nauseum). if you use libspotify 0.0.3 it should work with trunk (at least it did 2 weeks ago). Good luck ;-) - LeGrandHorg - 2010-12-13 23:35 I got it working well enough using RC1 and libspotify 0.0.3, thank you very much! However, as my wife started it today XBMC just failed on start. When I got back home and had a look at it I was quite surprised when I found this in the xbmc user's ~/.xsession-errors: Code: /usr/local/lib/xbmc/xbmc.bin: error while loading shared libraries: libspotify.so: cannot open shared object file: No such file or directoryPuzzled, I checked /usr/local/lib and the files where there alright. Uninstalled libspotify, reinstalled it. No go. Scratching my head, I ran ldd on xbmc.bin and found this: Code: [hakan@xbmc:~]% ldd /usr/local/lib/xbmc/xbmc.bin | grep spot [21:56]Code: /usr/local/lib:Googling the issue I found a post on the Spotify Community Support outlining how broken libspotify 0.0.3 really is, missing SONAME header and everything. Anyhow, I installed 0.0.4 which actually sort of fixed the problem - XBMC can now start and function, but the Spotify functions don't do anything. Reverted back to 0.0.3 to verify, and yes, it is still broken. I feel the urge to use inappropriate language here to vent some frustration but I realize none of the XBMC developers (or users!) are to blame. libspotify 0.0.3 is just plain broken. After even more investigation, I found that the problem (missing header information in libspotify) is triggered when I run ldconfig. ldconfig uses SONAME to retrieve names for the symlinks it creates, and libspotify is missing this, so the ld.so.cache will simply not list libspotify.so. I finally tricked XBMC back to working with 0.0.3 by installing 0.0.4, then running ldconfig, uninstalling 0.0.4 and finally installing 0.0.3 again - and this time I did NOT run ldconfig. So far so good, but ldconfig can be triggered by Ubuntu security updates, and I don't look forward to having explain to my wife over the phone how to make it work again. :-P So... How's the progress on 0.0.6 and XBMC?
- akezeke - 2010-12-14 06:44 @LeGrandHorg I gave 0.0.6 a go a couple of days ago, I changed all necessary calls etc in the code but I´m missing something, on linux using any newer library than 0.0.3 nothing happens. No callbacks whatsoever. If anyone finds out whats wrong please inform me and I will update the source, It sure would be nice to use the newest library. - arfoll - 2010-12-14 11:48 akezeke Wrote:@LeGrandHorg If you post the patch I can have a look before the end of the week. I've been wanting to move the newest library but haven't quite had the time. - LeGrandHorg - 2010-12-14 15:15 akezeke and arfoll, if you two put your heads together and hammer out a patch I promise I will dedicate some time to testing it. Great job getting this stuff working, both of you. - tsint - 2010-12-14 21:15 @LeGrandHorg, i got it working thanks to your explanation about the ld-stuff, thanks!
- LeGrandHorg - 2010-12-14 22:36 tsint Wrote:@LeGrandHorg, i got it working thanks to your explanation about the ld-stuff, thanks! You're welcome! I hoped posting about my "solution" could help others in the same state of confusion as I was in. |