IssuesFAQ - Please Read First

  • 50 points-+

    Q: What players are supported by Zenses2? Is it enough if it has MTP ?

    A: Unfortunately the answer is - it doesn't seem that all players having MTP will be supported. My Sansa Clip for example is allowing me to access the information about stored tracks, but it doesn't keep the count of the tracks that I listen to. Of course it may change over time (if Sansa releases new hardware). We will simply keep a list of players that are confirmed to work. If your player was working with previous zenses and is not working with the new version (not showing any tracks to submit) let us know, we'll try to investigate.

  • 0 points-+

    Q: Not all tracks I am submitting are appearing in my profile, why? What can I do ?

    A: The reason for that is - last.fm keeps a sanity check of submitted tracks and (at least for some users) ignores anything that has a submission timestamp earlier than what is already in your profile. So if you listened to even one track from your Winamp/Foobar or whatever you're using in the evening after coming from work, you will not be able to submit songs from your player giving them timestamp of - say - early morning. Zenses2 will now try to prevent you from doing that and will only let you submit tracks that are after your last submission - which sometimes might take them into the future! However, that means that until you get to that point of time when the last submission from Zenses2 was made, no tracks from your normal player will be accepted by last.fm.

    Also, it seems that you cannot go to far into the future and after some point last.fm will again stop accepting tracks.

    The worst part about all this is that during submission we don't get any error or warning from last.fm so there is no way we can tell that something went wrong and your track will not appear in the profile. There is NOTHING we can do about it so there is no point complaining about it here.

    As per last.fm documentation: "The server may at its discretion ignore track details submitted by the user. Typical reasons for submissions being dropped include (but are not limited to): Submissions with inaccurate dates, e.g. in the far future or past, or before the last submitted entry (i.e. tracks must be submitted in chronological order according to when they were listened to). [...] In these cases, the client will receive an OK response, however the tracks will not be registered."

    If you want zenses2 to work, PLEASE send an email to last.fm asking them to change this ridiculous policy.

  • 0 points-+

    Q: Why is it so slooooooow? Is anything even happening or is it just hanging?

    A: The short answer is: because every time you scan for tracks, it needs to process every single track on your device.

    Slightly longer answer is: Processing involves reading and updating a lot of data from your local database that's stored in file zenses.data.script). It's a text file and you can safely open and view it as long as you don't have zenses2 running at the same time. That's why your hard drive is working like crazy and as long as it's doing it, it didn't hang. It can really take a looooot of time, especially the first time you run.

    We plan to replace this version of the database with something slightly smarter (i.e. MySQL) but that will take some more time, especially that we would need to somehow migrate the data.

  • 0 points-+

    Q: Why is Zenses2 trying to rescrobble everything that Zenses 0.2 already scrobbled?

    A: Short answer is - because Zenses2 has no way of telling what Zenses 0.2 scrobbled. It only has access to your device information, which is telling it that a particular track was listened to - say - 5 times. If you want to avoid rescrobbling tracks, you'd need to run something that would set all listen counts on your device to zero and then start from scratch.

    We may add at some point a possibility to set listen count to 0 on particular tracks (if it's possible through MTP) but at this point there are too many other things to be done. Therefore your choice is to a) wait for the final release b) live with rescrobbled tracks c) start from scratch by zero-ing listen counts for everything.

  • 0 points-+

    Q: I don't want to lose all my tracks, what can I do to be safe?

    A: First of all, Zenses2 doesn't change anything on your device. All the playcounts stay there safe and sound so if Zenses2 doesn't work for you and scrobbles don't appear and you find a better app for your device - go ahead, it's all there. Zenses2 only ever operates on its own database - that's where it stores play counts for your tracks and the counts of how many plays it already scrobbled. At any given point it just compares what is your current playcount and what is it's submissions count and if they differ, it will try show you that you have unsrobbled tracks. BTW that also means that you shouldn't zero your playcounts meanwhile, or if you do, you'd need to wipe out Zenses2 db of the scrobbles history, which is not that easy to do.

  • 0 points-+

    Q: Why do you have a new forum over the Last.fm forum?

    A: The Last.fm forum is all well and good for discussion but we have found that the user reported issues were to hard to view and work through because of the lack of support for categories and multiple forums. Using the new forums, we can split user discussion into threads and different categories allowing us (the developers) to find the bugs that users are reporting.

    The developers will be actively watching and replying to users on the new forum, we will continue to check Last.fm every now and then and remind users to use the new forums.

  • 0 points-+

    Q: Do you post updates and release information to Twitter?

    A: You can follow 'sixones', one of the developers at http://twitter.com/sixones

  • 0 points-+

    Q: Is the source-code available for Zenses2?

    A: At the moment the source is kept private, we want to tidy it up before releasing the source.

  • 0 points-+

    Q: Why zenses is not showing correct name for my device? A: Honestly, we don't know. Most likely you have in the name characters outside of a set A-Z, a-z, 0-9. They should be safe, others may or may not work (including spaces). In any case, whatever it shows as the name shouldn't really affect the work of the program and since it's just aesthetically relevant, with all the other problems we get reported it's rather low on our priority list.

Want to take part in this discussion? Click one of these: Sign In Register For Membership

Howdy, Stranger!

It looks like you're new here. If you want to take part in the discussions, click one of these buttons!

Sign In Register For Membership

In this Discussion