Hi. I've got the new version of zenses but with the same problem as ever. Cowon D2 in MTP mode. Windows XP. Successfully log on last.fm. Zenses finds the device and fetches tracks, it founds many unscrobbled tracks. I try to scrobble few tracks each time, setting the date after the last scrobbled track on last.fm (in august, maybe is it the problem? The date is too far?). Zenses tells that the tracks are succesfully scrobbled, but they don't appear on my last.fm profile (I'm in Italy, my profile is in www.lastfm.it, maybe is this the problem?).
I'm sorry to tell it here, I appreciate very much what you're doing with zenses but I've to say to others like me that are not being able to use it that I've just found a software that works with cowon D2: it's QTScrobbler (http://www.lastfm.it/group/QTScrobbler). Maybe it's useful for further development of zenzes: the difference between the two programs is that scrobbling many tracks zenses seems to do it in a moment (but then nothing appears on the profile) when doing it with QTScrobbler takes more time (and the tracks appear on the profile).
Sorry to here your having issues, how does Zenses differ from QTScrobbler? You should be able to successfully see your scrobbles on Last.fm using the latest version of Zenses2, otherwise Zenses will display an error asking you to correct the date.
Do you know how long QTScrobble leaves per track scrobble? This could be an issue with Zenses.
I used allthe beta versions of Zenses2, then tried QTScrobble. Here's the main differences i found:
- Zenses2 fetch the tracks in about 3 hours,QTS in a couple of minutes
- QTS uses the song length to calculate the scrobble interval, and has a function to calculate from a date/time backward (startng from the last song and going up to the first).
- With Zenses2 no matters how many songs i scrobble, only 6 to 10 songs appears in last.fm,with QTS all songs scrobblead appears in last.fm.
I use Cowon D2,win XPHome SP3, WMP11.
- Zenses2 fetch the tracks in about 3 hours,QTS in a couple of minutes
On Windows Zenses uses a Java lib that communicates with the Windows Media SDK, Im not sure what QTS uses but I know the library we are using isnt too good. We really need to write something better that uses the Windows Media SDK or libMTP.
- QTS uses the song length to calculate the scrobble interval, and has a function to calculate from a date/time backward (startng from the last song and going up to the first).
Zenses does this apart from it goes the other way around, you select the date that you want to scrobble from and then Zenses will calculate all the lengths.
- With Zenses2 no matters how many songs i scrobble, only 6 to 10 songs appears in last.fm,with QTS all songs scrobblead appears in last.fm.
Are you using the latest Zenses build (2.0.4b2)? Also did you scrobble the tracks into the future or the past (in comparison to the last scrobble to Last.fm)?
I used the latest build 2.0.4b2, and i scrobbled the tracks (about 20 tracks) after my last scrobble to Last.fm,but only 6 songs were correctly recorded (apparently the first six).
I also forgot to mention that QTS supports the deletion of one ormore songs from the scrobbling list, but it does not tracks a "Scrobbled songs history". Furthermore i think the tracks fetching seems to change something into my Cowon D2 database, because after using QTS the device scan and rebuild the internal DB.
Were going to add the future to ignore unscrobbled tracks in the future, we have some ideas about what is causing the missing scrobbles on last.fm. We have been in contact with Last.fm to help solve the problem, hopefully soon we will have some answers.
Zenses doesnt write to your MTP database it only reads, im not sure why QTS would rebuild your MTP database because that would involve copying all your tracks from your device and then back to it (as the MTP db stores the files). If its your MTP device that is automatically rebuilding your MTP database after you use QTS then I would assume that QTS is corrupting your db.
My guess would be - perhaps QTS is zero-ing listen count for the tracks it manages to scrobble, this way it doesn't have to keep track of what it already scrobbled, and perhaps that is causing the DB to be rebuilt.
I suppose a problem in Zenses with cowon d2: I see that when I scrobble track using QTS only few tracks come with the righ lenght, most of them are with 0 lenght. Than I have to change manually the lenght of each track and let QTS to calculate the intervals between tracks, before scrobbling to last.fm (than everything appears on the profile). In zenses I don't see a way to change the lenght of the tracks. Maybe the problem is that on the D2 most of the tracks appear with 0 lenght, so when they're scrobbbled they don't appear on last.fm.
That would make sense, is manually entering the track length the best idea? I wonder if its possible to get this information automatically from Last.fm, we will look into it.
Are you sure you transferred the files in MTP mode? If you use MSC and then switch to MTP the tracks appear as 0 length.
I had the same problem, and found out by accident that that was the cause.. I'm pretty much a layman, so it might just be me who didn't know you have a actually transfer the files in that mode.
@andreapg - Due to all the issues people were having with disappearing tracks because of going to far into the future we have actually changed the way zenses works - it uses a constant interval between tracks (1minute for all I remember) rather than calculating it so whatever your cowon reports, won't actually matter that much. We will go back to calculating mode once we have a better way of validating if last.fm accepted the scrobble or not.
Hi guys, I have exactly the same problem as the OP. I have a Cowon D2, FW 2.13. I load up Zenses2 2.0.7b2, it authenticates fine, it finds my Cowon, gets the unscrobbled tracks. I go to the unscrobbled tracks history, select the tracks (there was 3), set the time to 5mins from now, click on scrobble, I get a message that the tracks were scrobbled successfully but they never appear on Last.fm. Any ideas?
These are the logs:
[album=?????-2, artist=????, deviceId=0250310043F84002207061615063CBC1, filename=06. ?????.flac, id=205, lastRead=2010-02-13 13:50:30.934, length=0, persistentId={10001946-0000-0000-0000-000000000000}, playCount=1, submissions=[], title=?????, zenId=o10001946] 13:51:32,912 INFO TracksSubmitterImpl:68 - Submitted DeviceTrackDto [album=?????-2, artist=????, deviceId=0250310043F84002207061615063CBC1, filename=06. ?????.flac, id=205, lastRead=2010-02-13 13:50:30.934, length=0, persistentId={10001946-0000-0000-0000-000000000000}, playCount=1, submissions=[], title=?????, zenId=o10001946] 13:51:33,119 INFO DeviceTrackServiceImpl:52 - Submission added to db: DeviceTrackDto [album=?????-2, artist=????, deviceId=0250310043F84002207061615063CBC1, filename=05. ????.flac, id=204, lastRead=2010-02-13 13:50:30.932, length=0, persistentId={10001945-0000-0000-0000-000000000000}, playCount=1, submissions=[], title=????, zenId=o10001945] 13:51:33,119 INFO TracksSubmitterImpl:68 - Submitted DeviceTrackDto [album=?????-2, artist=????, deviceId=0250310043F84002207061615063CBC1, filename=05. ????.flac, id=204, lastRead=2010-02-13 13:50:30.932, length=0, persistentId={10001945-0000-0000-0000-000000000000}, playCount=1, submissions=[], title=????, zenId=o10001945] 13:51:33,610 INFO DeviceTrackServiceImpl:52 - Submission added to db: DeviceTrackDto [album=?????-2, artist=????, deviceId=0250310043F84002207061615063CBC1, filename=04. ????.flac, id=203, lastRead=2010-02-13 13:50:30.919, length=0, persistentId={10001944-0000-0000-0000-000000000000}, playCount=1, submissions=[], title=????, zenId=o10001944] 13:51:33,610 INFO TracksSubmitterImpl:68 - Submitted DeviceTrackDto [album=?????-2, artist=????, deviceId=0250310043F84002207061615063CBC1, filename=04. ????.flac, id=203, lastRead=2010-02-13 13:50:30.919, length=0, persistentId={10001944-0000-0000-0000-000000000000}, playCount=1, submissions=[], title=????, zenId=o10001944]
At first I thought the problem was related to the fact that it seemingly is unable to display Japanese characters (hence the ????) (although they show up fine in the program), I tried to scrobble tracks with normal latin characters and get the same problem: 14:16:15,557 INFO DeviceTrackServiceImpl:52 - Submission added to db: DeviceTrackDto [album=Beau Dommage, artist=Beau Dommage, deviceId=0250310043F84002207061615063CBC1, filename=01. Tous Les Palmiers.flac, id=206, lastRead=2010-02-13 14:14:28.696, length=0, persistentId={10001770-0000-0000-0000-000000000000}, playCount=1, submissions=[], title=Tous Les Palmiers, zenId=o10001770] 14:16:15,557 INFO TracksSubmitterImpl:68 - Submitted DeviceTrackDto [album=Beau Dommage, artist=Beau Dommage, deviceId=0250310043F84002207061615063CBC1, filename=01. Tous Les Palmiers.flac, id=206, lastRead=2010-02-13 14:14:28.696, length=0, persistentId={10001770-0000-0000-0000-000000000000}, playCount=1, submissions=[], title=Tous Les Palmiers, zenId=o10001770] 14:16:16,144 INFO DeviceTrackServiceImpl:52 - Submission added to db: DeviceTrackDto [album=Beau Dommage, artist=Beau Dommage, deviceId=0250310043F84002207061615063CBC1, filename=02. À Toutes Les Fois.flac, id=207, lastRead=2010-02-13 14:14:28.698, length=0, persistentId={10001771-0000-0000-0000-000000000000}, playCount=1, submissions=[], title=À Toutes Les Fois, zenId=o10001771] 14:16:16,144 INFO TracksSubmitterImpl:68 - Submitted DeviceTrackDto [album=Beau Dommage, artist=Beau Dommage, deviceId=0250310043F84002207061615063CBC1, filename=02. À Toutes Les Fois.flac, id=207, lastRead=2010-02-13 14:14:28.698, length=0, persistentId={10001771-0000-0000-0000-000000000000}, playCount=1, submissions=[], title=À Toutes Les Fois, zenId=o10001771]
It looks like you're new here. If you want to take part in the discussions, click one of these buttons!