LastBASH » Diskussionen

new last.fm API causing problems?

 
    • lordpings schrieb...
    • Benutzer
    • 11. Aug. 2008, 14:43

    new last.fm API causing problems?

    Hi,

    I'm using LastBASH on my OpenWRT Router and have run into two problems, which are caused by last.fm changing things again, I suppose:

    On track change, the metadata is not refreshed (which can be worked around by pressing R, refreshing manually).
    The bigger annoyance is, that I cant skip tracks...


    I also can't get it to recognize my mpg123, even if it works... LastBASH always complains about not finding any compatible player...
    Manually starting mpg123 with the cmd shown on the HP works...


    Keep up the good work,
    Lord

    Permalink  Zitat
    • jzarecta schrieb...
    • Benutzer
    • 27. Aug. 2008, 6:57

    Same problem here

    I also have the same issues experienced on lastbash however I tried to do it manually using mplayer and I got the following issue:

    Playing http://87.117.229.85:80/last.mp3?Session=c3330d13a2249afe9592b7f6a47a8e1c.
    Resolving 87.117.229.85 for AF_INET6...
    Couldn't resolve name for AF_INET6: 87.117.229.85
    Connecting to server 87.117.229.85[87.117.229.85]: 80...
    Cache size set to 320 KBytes
    Cache fill: 0.02% (61 bytes)

    La Ciudad Respira
    Permalink  Zitat
    • cstroie schrieb...
    • Benutzer
    • 22. Dez. 2008, 15:00

    Yes, the API is causing problems

    Yes, indeed, the new API breaks the compatibility with the old one and there are some issues. Nonetheless LastBASH is still working, even if clumsy.

    Permalink  Zitat
Anonyme Benutzer dürfen keine Beiträge schreiben. Bitte log dich ein oder registriere dich, um Beiträge in den Foren schreiben zu können.