Synergy not sending CD track names to last.fm?
-
RequiemX
I've been really happy with Synergy's support for last.fm so far. I've been able to remove iScrobbler from my system and gain a few pixels of menubar space.
For some reason, though, the tracks names of CD's I play (as opposed to MP3's) aren't submitted.
Is there something I need to change? Or should I submit a bug?
-
Greg Hurrell
Perhaps Synergy is not seeing these as regular files (the Audioscrobbler protocol requires that only regular file tracks be submitted, not non-file tracks like Internet radio etc). Can you turn on logging and let me know what gets logged when you play CDs?
Instructions for how to turn on logging appear in the beta announcement.
-
RequiemX
You're right. It appears to not submit because it's not a "regular file":
2006-12-10 15:22:22.356 Synergy[5776] Audioscrobbler: Read preferences 2006-12-10 15:22:22.356 Synergy[5776] Audioscrobbler: Perform first-time initialization 2006-12-10 15:22:22.356 Synergy[5776] Audioscrobbler: Initializing WOAudioscrobbler object 2006-12-10 15:22:22.491 Synergy[5776] Audioscrobbler: Read new username 2006-12-10 15:22:22.492 Synergy[5776] Audioscrobbler: Read new password 2006-12-10 15:22:22.492 Synergy[5776] Audioscrobbler: First time we've read the preferences; will start a new session 2006-12-10 15:22:22.492 Synergy[5776] Audioscrobbler: Start Audioscrobbler session 2006-12-10 15:22:22.503 Synergy[5776] Audioscrobbler: Will request handshake 2006-12-10 15:22:22.503 Synergy[5776] Audioscrobbler: Handshake URL is http://post.audioscrobbler.com/?hs=true&p=1.1&c=syn&v=0.1&u=RequiemX 2006-12-10 15:22:22.504 Synergy[5776] Audioscrobbler: Starting connection attempt 2006-12-10 15:22:22.508 Synergy[5776] Audioscrobbler: Waiting for handshake reply 200 206-12-10 15:22:23.095 Synergy[5776] Audioscrobbler: Connection to Audioscrobbler did finish loading (response received) 2006-12-10 15:22:23.096 Synergy[5776] Audioscrobbler: Received an INTERVAL directive 2006-12-10 15:22:23.096 Synergy[5776] Audioscrobbler: Storing interval value: 1 2006-12-10 15:22:23.096 Synergy[5776] Audioscrobbler: Processing handshake reply 2006-12-10 15:22:23.096 Synergy[5776] Audioscrobbler: Received UPTODATE message 2006-12-10 15:24:57.407 Synergy[5776] Audioscrobbler: Received notification from iTunes 2006-12-10 15:24:57.407 Synergy[5776] Audioscrobbler: Current track cannot be submitted because it is not a regular file 2006-12-10 15:24:57.407 Synergy[5776] Audioscrobbler: Cancelling previously existing submission timer, if any 2006-12-10 15:24:57.416 GrowlHelperApp[252] 2006-12-10 15:24:57 -0600 Synergy: Playing: Caught In A Web (Awake Dream Theater ) - Priority 0
-
Greg Hurrell
I had a dialogue about this with another user via email, in whose case the tracks were being played directly off an iPod. I'm going to see if I can find the relevant bits of the exchange... Actually no, it wasn't via email, it was here:
https://wincent.dev/a/support/forums/ubbthreads.php?ubb=showflat&Number=1098
In particular look at this post:
https://wincent.dev/a/support/forums/ubbthreads.php?ubb=showflat&Number=1098&page=1#Post1102
Can you please collect the necessary information to see if a workaround is possible?
-
RequiemX
Cool. First the output of that terminal program:
Notification received 2006-12-10 16:38:44 -0600:
Name: com.apple.iTunes.playerInfo Info: { Album = Awake; Artist = "Dream Theater"; Composer = "Dream Theater"; "Disc Count" = 1; "Disc Number" = 1; Genre = Metal; Name = "Lifting Shadows Off A Dream"; "Player State" = Playing; "Store URL" = "itms://itunes.com/link?n=Lifting%20Shadows%20Off%20A%20Dream&an=Dream%20Theater&pn=Awake&cn=Dream%20Theater"; "Total Time" = 365133; "Track Count" = 11; "Track Number" = 9; Year = 1994;
}
And the output of that script:
alias "Awake:9 Lifting Shadows Off A Dream.aiff"
Does that help at all? I know it must at least be possible since iScrobbler seems to handle it fine.
-
Greg Hurrell
So it's the same problem, no "location" field in the notification. Well of course, it's always possible to workaround these things but it's a question of whether it can be done efficiently. iScrobbler is probably querying iTunes to get more information about the track (requiring an Apple Event exchange), whereas Synergy is just working with the info that iTunes pushes out (essentially "free"). The workaround will probably be to double-check with iTunes just before submitting, at least that way the overhead won't be incurred for tracks which never end up getting submitted.
Will open a ticket for this in the database to track the issue:
-
RequiemX
Okay. Cool.
Thanks!
Reply
This topic is now closed.