If you're a SB Slacker person, kindly read on. If not, you probably won't be interested in this.
When playing Slacker radio via SB devices, songs longer than 6-8 minutes are often truncated after 3-8 minutes of play. Another song promptly starts; it's as if I had hit the 'next song' button. This is especially irritating when settling into a 30+ minute ambient piece only to hear it cut off and another song start. I can't say for sure when this problem started other than it was right around 7.4.1's release when I first noticed it happening. Yes, I have been aware of, working around, and hoping someone else would raise this issue since Novemberish of last year. I have spent many many hours over the past months documenting this problem, so here goes: To reproduce, pick a handy SB player and listen to a Slacker station. My current choice for this is http://www.slacker.com/?sid=stations/9901321/1261363847. When a song starts, note its duration - if it's < ~6 minutes, feel free to skip to the next song. Listen for songs ending early (and abruptly) - it happens several times an hour for me. Things I've Tried / Data Points: 1. Switching players. The problem occurs on all SB players; my Boom, SBR, and (brand new) Radio. 2. Switching Slacker stations. Any song on any station stands a chance of getting whacked if it's long enough. 3. Playing different types of Slacker stations. Whether it's a canned station, artist station, or created from scratch station (as is the one I've shared above), the problem occurs. 4. Playing Slacker on different devices. My G2, Slacker's web player, my iPhone, and my friend's BlackBerry all show no sign of abnormal song termination. 5. Playing different music streams. Pandora, radiotime, Shoutcast -- none manifest this problem. 6. Playing Slacker via my Squeezebox Server. Same problem. 7. Running tcpdump on my network while playing Slacker through SqueezeCenter and analyzing traffic patterns. The HTTP POST and GET sequences to/from SqueezeCenter and SqueezeNetwork (which is channeling Slacker) are the same whether a normal song transition is taking place or an "early truncation" transition is taking place. Note the GET operation differences (or not) that trigger the next song. This is me hitting FFWD on my SBR while playing Slacker on my SBC: GET /api/slacker/v1/playback/getNextTrack?device=7.65&sid=stations/9901321/1259724697&len=265&end=skip&elapsed=103.08 HTTP/1.1 This is before a normal song transition, about 15 seconds before end of song: GET /api/slacker/v1/playback/getNextTrack?device=7.65&sid=stations/9901321/1259724697&len=52&end=end&elapsed=52 HTTP/1.1 This is seen about 15 seconds before an early truncation event: GET /api/slacker/v1/playback/getNextTrack?device=7.65&sid=stations/9901321/1259724697&len=385&end=end&elapsed=385 HTTP/1.1 It's as if incorrect timing information is being passed to the SB player. Sometimes. So. Have you encountered this problem? Anyone? And does anyone (especially current SB developer/engineering folks, read "AndyG"? ;^) have a clue as how to fix this, or what data I can take to Slacker Dev to make them fix it? If it's a Slacker issue it's gotta be something they do especially for SB because Data Point #4 shows it's not their general API. I would open a bug but wanted to see if anybody else (Anyone? Ferris?) has seen this issue. Thanks! -Don -- tdnuerf ------------------------------------------------------------------------ tdnuerf's Profile: http://forums.slimdevices.com/member.php?userid=22385 View this thread: http://forums.slimdevices.com/showthread.php?t=76817 _______________________________________________ squeezenetwork mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezenetwork
