Home of the Squeezebox™ & Transporter® network music players.
Page 99 of 489 FirstFirst ... 4989979899100101109149199 ... LastLast
Results 981 to 990 of 4883
  1. #981
    Senior Member
    Join Date
    Apr 2005
    Posts
    6,937
    Quote Originally Posted by balle3201 View Post
    On iPeng, however, the Spotify Icon does not change at all. It may seem that the app itself, caches the icon, either on the iPhone, or uses another cached version located on the server/pc, which may not be updated unless you reinstall the plugin...?
    iPeng includes the icon within the app - you will need to ask pippin why, but it means you are unlikely to be able to change it.

  2. #982
    Junior Member
    Join Date
    Aug 2010
    Posts
    9
    Quote Originally Posted by Triode View Post
    I changed an option on the build of 1.0.3 to see if this would help you. This has removed spotifyd's dependancy on GLIBC_2.4, but it looks libspotify still has a problem for you. I can't do anything about this as it comes direct from spotify. If you can't get this to work then I think its better I put back the thing which was relying on 2.4 as it was providing extra protection against coding errors. [1.0.3 is compiled with -fno-stack-protector for those who understand the details]
    I don't know if you must be able to run libspotify.so.4, but when I do ./libspotify.so.4 I get a segmentation violation...

    Is there a way to make the GLIBC_2.4 working on the Synology DS1010+?

    Other question, Is there anybody with a DS1010+ or another Synology NAS that got it working?

    PS: Triode, really appreciate your help!!

  3. #983
    Senior Member
    Join Date
    Apr 2005
    Posts
    6,937
    Quote Originally Posted by groennom View Post
    I don't know if you must be able to run libspotify.so.4, but when I do ./libspotify.so.4 I get a segmentation violation...
    No you should not be able to execute it - this is normal.

    Is there a way to make the GLIBC_2.4 working on the Synology DS1010+?
    Glibc 2.4 is quite old - it would be worth asking Synology if they have a more up to date build available. Is there a Synology support forum you can ask this on?

  4. #984
    Senior Member
    Join Date
    Apr 2005
    Posts
    6,937
    Quote Originally Posted by balle3201 View Post
    3. It have occured that for some reason some tracks are unable to play, if I browse to an artist --> Album --> tracks etc. BUT, if I use Spotify for PC i.e., and locate the song there, and then save it to a playlist, or "Star" it, and then try to play it from either my favorites, starred songs, playlist the playback works fine. Any idea why this is happening?
    The example you give is an "album" with a single track within it - is this the case for your other problem tracks? If so which interface is causing you the problem. I think there may be some bugs relating to this case.

  5. #985
    Junior Member
    Join Date
    Aug 2010
    Posts
    9
    Quote Originally Posted by Triode View Post
    No you should not be able to execute it - this is normal.
    Is it possible to download a correct version that can be run?

    Quote Originally Posted by Triode View Post
    Glibc 2.4 is quite old - it would be worth asking Synology if they have a more up to date build available. Is there a Synology support forum you can ask this on?
    There is a support forum, I will take a look there!

  6. #986
    Senior Member
    Join Date
    Apr 2005
    Posts
    6,937
    Quote Originally Posted by groennom View Post
    Is it possible to download a correct version that can be run?
    No it should not be runable - its a shared library.

  7. #987
    Junior Member
    Join Date
    Aug 2010
    Posts
    1

    Spotify plugin for ReadyNAS

    Quote Originally Posted by Triode View Post
    Edit: Updated with Release status - Release 1.0.1 is now available from the 3rd Party Plugin list

    Scope:
    - for Spotify users with a Premium account
    - plays back 320k or 160k streams
    - requires a PC based server running Squeezebox server (linux, windows or mac)
    - will play back via Squeezebox 2 and later hardware players only
    - supports a single playback session at one time which may be synchronised across multiple players (i.e. does not support multiple differently playback sessions at one time - this is a Spotify limitation)

    If you are a Spotify Premium subscriber, then to try it out:

    1) Make sure you are running 7.5 or 7.5.1 Squeezebox server
    2) Go to the Settings/Plugin page and select "Show all 3rd party plugins", click apply
    3) Select the Spotify plugin from the list and then click apply as per normal plugin installation
    4) Ensure the server has restarted
    5) Go to the Plugin, Settings page for "Spotify" either via the advanced menu or from the plugin page
    6) Read and agree the Spotify restrictions, then add your username and password to the settings page.
    7) If you refresh the settings page a couple of times you should see that a "helper app" is running and it is logged into Spotify. If not there may be an error to help...
    9) Go to the "radio" menu on one of your hardware players and you should be able to browse and play tracks from Spotify....

    Linux:
    The binary files included in the plugin include the Spotify library libspotify and a closed source application built around this. This is 32bit only so on 64 bit linux you probably need ia32-libs installed. For both 32bit and 64bit machines you will need libFLAC.so.8 installed (usually in flac or libflac packages of your distro).

    Windows:
    The binary is 32bit and should work on 64bit as well.

    Mac:
    The binary will work on 10.6 machines, but issues have been reported using them on 10.5 intel based machines. If you have a 10.5 intel based machine, the workaround is to find the location of 'spotifyd' and 'spotifdppc' within the plugin and to rename them so that spotifyppc becomes spotifyd. This will mean the helper app runs in ppc emulation mode but it has been reported to work on 10.5 macs.

    Please provide feedback and let me know if this plugin is interesting to people on this thread
    Have tried this plugin on my ReadyNAS only to find the helper app will not start. After further search I have found that the plugin will not run on ReadyNAS.
    Quote from ReadyNAS forum:
    it's good news a spotify plugin was created for Squeezebox,
    unfortunately, this does not work on ReadyNAS Duo (essentially because libspotify only is provided for linux-libc6 x86 architectures)
    it's disappointing
    anyone here having an idea about how this should progress? is there anything to do to overcome these limitations?
    Unquote

    Any chance an update to support ReadyNAS will be made?

  8. #988
    Junior Member
    Join Date
    Aug 2010
    Posts
    3

    Transport endpoint is not connected

    Hello!
    I have just installed and started the excellent plugin you have created Triode. Just to say quick: Ive been waiting for this for years! Thank you!

    Ofc I have some problems getting it to work, as it should be .

    Server info:
    Version: 7.5.1 - r30836 @ Tue Jun 1 05:57:28 PDT 2010
    Host: NAS
    Serverns IP-adress: 192.168.1.3
    HTTP-serverns portnummer: 9000
    Operativsystem: Debian - SV - utf8
    Plattformsarkitektur: i686-linux
    Perl-version: 5.10.1 - i486-linux-gnu-thread-multi
    Totalt antal anslutna spelare: 1

    Log information:
    2010-08-11 12:24:18 squeezeboxserver_safe started.
    [10-08-11 12:24:18.1508] main::init (323) Starting Squeezebox Server (v7.5.1, r30836, Tue Jun 1 05:57:28 PDT 2010) perl 5.010001
    [10-08-13 04:44:38.0075] Slim::Networking::SqueezeNetwork::Players::_player s_error (308) Unable to get players from SN: Couldn't resolve IP address for: www.mysqueezebox.com, retrying in 300 seconds
    [10-08-14 09:41:57.5618] main::init (323) Starting Squeezebox Server (v7.5.1, r30836, Tue Jun 1 05:57:28 PDT 2010) perl 5.010001
    [10-08-14 09:50:53.4963] Plugins::Spotify::Spotifyd::startD (33) unable to write log file: /var/log/squeezeboxserver/spotifyd.log
    [10-08-14 09:50:53.5604] Plugins::Spotify::Settings::__ANON__ (134) error fetching status: Connect timed out: Transport endpoint is not connected, retries left: 3
    [10-08-14 09:50:53.8644] Plugins::Spotify::Settings::__ANON__ (134) error fetching status: Connect timed out: Transport endpoint is not connected, retries left: 2
    [10-08-14 09:50:54.1682] Plugins::Spotify::Settings::__ANON__ (134) error fetching status: Connect timed out: Transport endpoint is not connected, retries left: 1
    [10-08-14 09:50:54.4719] Plugins::Spotify::Settings::__ANON__ (134) error fetching status: Connect timed out: Transport endpoint is not connected, retries left: 0
    [10-08-14 09:58:34.7369] Slim::Formats::XML::gotErrorViaHTTP (332) Error: getting http://192.168.1.3:9001/playlists.json
    Connect timed out: Transport endpoint is not connected
    [10-08-14 09:58:40.3054] Slim::Formats::XML::gotErrorViaHTTP (332) Error: getting http://192.168.1.3:9001/playlists.json
    Connect timed out: Transport endpoint is not connected
    [10-08-14 10:15:22.8279] Slim::Formats::XML::gotErrorViaHTTP (332) Error: getting http://192.168.1.3:9001/playlists.json
    Connect timed out: Transport endpoint is not connected

    Thank you for any help if you have the time.

    Best Regards
    David Lussi

  9. #989
    Senior Member
    Join Date
    Apr 2005
    Posts
    6,937
    Quote Originally Posted by Finn View Post
    Have tried this plugin on my ReadyNAS only to find the helper app will not start. After further search I have found that the plugin will not run on ReadyNAS.
    Quote from ReadyNAS forum:
    it's good news a spotify plugin was created for Squeezebox,
    unfortunately, this does not work on ReadyNAS Duo (essentially because libspotify only is provided for linux-libc6 x86 architectures)
    it's disappointing
    anyone here having an idea about how this should progress? is there anything to do to overcome these limitations?
    Unquote

    Any chance an update to support ReadyNAS will be made?
    Well it can't be supported at present as Spotify do not make an apppropriate version of their library available for the ReadyNAS.

  10. #990
    Senior Member
    Join Date
    Apr 2005
    Posts
    6,937
    Quote Originally Posted by humpen View Post
    Hello!
    I have just installed and started the excellent plugin you have created Triode. Just to say quick: Ive been waiting for this for years! Thank you!

    Ofc I have some problems getting it to work, as it should be .

    Server info:
    Version: 7.5.1 - r30836 @ Tue Jun 1 05:57:28 PDT 2010
    Host: NAS
    Serverns IP-adress: 192.168.1.3
    HTTP-serverns portnummer: 9000
    Operativsystem: Debian - SV - utf8
    Plattformsarkitektur: i686-linux
    Perl-version: 5.10.1 - i486-linux-gnu-thread-multi
    Totalt antal anslutna spelare: 1

    Log information:
    2010-08-11 12:24:18 squeezeboxserver_safe started.
    [10-08-11 12:24:18.1508] main::init (323) Starting Squeezebox Server (v7.5.1, r30836, Tue Jun 1 05:57:28 PDT 2010) perl 5.010001
    [10-08-13 04:44:38.0075] Slim::Networking::SqueezeNetwork::Players::_player s_error (308) Unable to get players from SN: Couldn't resolve IP address for: www.mysqueezebox.com, retrying in 300 seconds
    [10-08-14 09:41:57.5618] main::init (323) Starting Squeezebox Server (v7.5.1, r30836, Tue Jun 1 05:57:28 PDT 2010) perl 5.010001
    [10-08-14 09:50:53.4963] Plugins::Spotify::Spotifyd::startD (33) unable to write log file: /var/log/squeezeboxserver/spotifyd.log
    [10-08-14 09:50:53.5604] Plugins::Spotify::Settings::__ANON__ (134) error fetching status: Connect timed out: Transport endpoint is not connected, retries left: 3
    [10-08-14 09:50:53.8644] Plugins::Spotify::Settings::__ANON__ (134) error fetching status: Connect timed out: Transport endpoint is not connected, retries left: 2
    [10-08-14 09:50:54.1682] Plugins::Spotify::Settings::__ANON__ (134) error fetching status: Connect timed out: Transport endpoint is not connected, retries left: 1
    [10-08-14 09:50:54.4719] Plugins::Spotify::Settings::__ANON__ (134) error fetching status: Connect timed out: Transport endpoint is not connected, retries left: 0
    [10-08-14 09:58:34.7369] Slim::Formats::XML::gotErrorViaHTTP (332) Error: getting http://192.168.1.3:9001/playlists.json
    Connect timed out: Transport endpoint is not connected
    [10-08-14 09:58:40.3054] Slim::Formats::XML::gotErrorViaHTTP (332) Error: getting http://192.168.1.3:9001/playlists.json
    Connect timed out: Transport endpoint is not connected
    [10-08-14 10:15:22.8279] Slim::Formats::XML::gotErrorViaHTTP (332) Error: getting http://192.168.1.3:9001/playlists.json
    Connect timed out: Transport endpoint is not connected

    Thank you for any help if you have the time.

    Best Regards
    David Lussi
    [10-08-14 09:50:53.4963] Plugins::Spotify::Spotifyd::startD (33) unable to write log file: /var/log/squeezeboxserver/spotifyd.log

    I suspect this is a permissions issue - could you try creating the log file and ensuring the squeezebox user can write to it.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •