Nothing to sync, or there was an error connecting to Last.fm

[GoogleCodeExporter]

Nothing to sync, or there was an error connecting to Last.fm

[GoogleCodeExporter]

I was able to get it to sync when I had only 3 songs checked but then forgot I 
had
delete log after syncing checked so I lost about 30+ songs that I wanted to 
sync.

Original comment by [email protected] on 29 Jun 2007 at 6:03

[GoogleCodeExporter]

I am also having this problem.

Original comment by [email protected] on 2 Jul 2007 at 11:10

[GoogleCodeExporter]

I'm having this problem too. 0.14 on XP Pro. The log has about 450 entries. I've
tried deselecting a few tracks that had invalid characters in the Track or Album
name, but this made no difference. Also tried the fix zero time stamp, and shift
after last played.

BTW, if you have a long list of scrobbled tracks, 'shift after last played' 
seems to
shift many of the scrobbled log entries into the future. July 2009 in my case!! 
Not good!

Show My Last Posts works, so it's not an issue with my last.fm account 
name/password
entries.

Original comment by [email protected] on 2 Jul 2007 at 11:39

[GoogleCodeExporter]

I am also having this problem.  I tried submitting with only 1 song checked and 
still
got this problem.  Perhaps Last.fm has changed something in their submission 
protocol?

To tim.read: The reason some songs are so far into the future is because of how 
long
your list it.  Surely your list isn't so long as to cause it to go into 2009 
though.
 Perhaps you have a legitimate bug.  I've got a pretty long list and noticed this.

What I have noticed is that when fixing the Zero Time Stamps each subsequent 
song's
stamp is the previous song's "Played At" time + it's "Length".  This is by 
design,
but could it be possible instead to only add the minimum scrobbling time per 
track
for the next time, rather than the entire track length?  This would alleviate 
some of
the problems associated with submitting tracks so far into the future.

Original comment by [email protected] on 4 Jul 2007 at 1:06

[GoogleCodeExporter]

I have this problem from time to time, using WinXP SP2 with the latest version 
of
LogScobbler.
I have found two kinds of solutions to this:

1. Check your system time is correct. Use WinXP to synchronise your clock and 
try
again. This has worked for me on several occasions, especially since the time 
on my
laptop desynchronises quite often.

2. Try submitting the tracks a couple of times in LogScrobbler, sometimes it has
worked on the third or fourth time.

These aren't stead-fast solutions but have worked for me lately.

Original comment by [email protected] on 8 Jul 2007 at 9:00

[GoogleCodeExporter]

It's hard to find the source of the problem with such a vague error message. 
One of
the fixes I hope to do soon is an upgrade to the Audioscrobbler submission 
code, with
more meaningful error messages.

Stay tuned!

Original comment by [email protected] on 11 Jul 2007 at 11:29

[GoogleCodeExporter]

Hi All,

The new version is out! Please download and test it. If you have any issues, 
post em
to the Issue Tracker!

Original comment by [email protected] on 16 Jul 2007 at 11:45

• Changed state: Fixed

[GoogleCodeExporter]

I still have the same problem with the new version

Original comment by [email protected] on 10 Feb 2008 at 8:50