I have been struggling to get this new Zenzes to work for me for months, but i think i may finally have it down.
when you first start up the application the lower left corner says "Loading..." and then changes to "0 unscrobbled tracks found". this was my first source of confusion and had me stumped for a long time; i assumed that when it was "Loading..." it was searching my player for unscrobbled tracks and then didn't find any (the original zenzes begins searching automatically upon starting the application), when really it was just loading the application and "0 unscrobbled tracks" referred to tracks that had already been found the last time i used the application but i hadn't done anything with. this is a simple but important misunderstanding that could be remedied with some more descriptive language. instead of it going from "Loading..." to "X unscrobbled tracks found", it could go from "Loading..." to something like "X tracks were left unscrobbled last time you used Zenzes. Find your device and Fetch Tracks to find new unscrobbled tracks".
But, once i figured out that at this point you actually have to go to File>Find Devices then click Fetch Tracks, the problems still weren't over. Doing so changes the status to "Connecting to device and fetching track information..." and ultimately to "Device tracks collected and ready for scrobbling" except that no new unscrobbled tracks would appear. i now realize that there is just a very long strange delay at this point and if you wait long enough, the unscrobbled tracks do actually appear and the status changes to "X unscrobbled tracks found". i thought for a while you actually had to click Fetch Tracks one more time to get them to appear, which made no sense, but seemed to work. i guess clicking things like that just kept me busy for long enough for the tracks to actually show up. it would be better if "Device tracks collected and ready for scrobbling" had the amendment "Device tracks collected and ready for
scrobbling. Please wait for them to appear" or something along those lines to account for this delay.
Also confusing is the Scrobbled History. Why does it only ever list 50 tracks? Why does it have tracks on it from devices other than the one i'm working with from last.fm accounts other than the one i'm working currently with? Why does it have tracks on it that i ignored and didn't actually scrobble? The part that really interferes with the intuitiveness of it all is that on the main page it says right in the middle of everything "Scrobbled a total of 50 tracks!" When you are trying desperately to actually get the thing to find some tracks and scrobble them this is very antagonizing. When were these tracks scrobbled? Just now? Or some other time when i used the application? But i've only ever ignored tracks before, when the hell did some tracks actually get scrobbled? And why does it max out at 50? i guess i'm still not totally sure, but the "Scrobbled a total of XX tracks!" is supposed to be a running total of tracks scrobbled through the life of the application? That's cool, but you'd have to make it actually work (go higher than 50 and not count ignored tracks). And change it to something like "Zenzes has scrobbled a running total of XX tracks!"
so i guess that's it. there are maybe some other small things i'm still a little confused about, but at least i think i've got it working. hopefully this account will be helpful for people. by the way, i'm using a Creative Zen x-fi 32gb and no, you don't have to listen to a track all the way through for it to count. if you listen to even a second of a song on this player, it counts it as a play.
Edit concerning the second dilemma i faced, the very long strange delay dilemma: The reason it seemed like it 'worked' to click Fetch Tracks a second time was simply that doing so kind of froze the application and actually forced you to wait a minute or two until it regained consciousness and the unscrobbled tracks were found, whereas otherwise there was no real indication that waiting would do any good. The application functions normally during this long strange delay and so the user is inclined to think that it just didn't work, maybe mess around clicking on things for a little bit, then just get pissed, give up and close the application, all the while not realizing that, given a little patience, the unscrobbled tracks would have appeared any minute. This being said, it seems like, in addition to editing the status message to reflect a wait time, it might be pertinent to lock up the application while it gets itself into presentable order and those tracks are brought up.
It looks like you're new here. If you want to take part in the discussions, click one of these buttons!