View Full Version : Playback problem
I've been thinking about purchasing a SB2 for a while now, so I've been doing some testing and have run across some issues that I'm not sure of the cause of/solution to.
Configurations include both Slimserver running on a Windows server, and a ReadyNAS 600, with verions 6.1.1 on either, with the music in question both local and on networked locations. Of couse, not having a SB2 yet I'm using the latest version of softsqueeze.
What happens is some songs simply refuse to play through the Slimserver. This includes songs within a single album, some track work fine, others just refuse to play (it's not like they "play" but there is silence which is what I've been able to see occuring in my searches of the forums).
I've tried clearing and re-indexing the collection, but no change.
Of course these .mp3's all play fine through WinAmp and WMP9/10 and Musicmatch, so.... I'm real confused.
I did some poking around, clearing, and normalizing of the ID3 tags thinking maybe something was wonky there, but nada.
Also of note these are all tracks I've ripped @ 256K (overkill yes I know) from my CD's.
Anyone able to help me?
Try the two fixes suggested in this thread and see if they work:
I had actually found that thread previously, and I'm not having that problem. The few FLAC files I have all seem to play (though only one or two of the mp3 version of the same songs that I created from those FLAC files do).
Many mp3's play just fine, many don't/won't play at all. All play fine using alternate players.
Nada? Anyone? Bueller? Tech support?
Have you had anyone else try to play one of the unplayable tracks? If not, send me a PM if you want me to try it. I'll delete the song immediately after, so you don't have to worry about piracy.
I actually have, and can play then fine on the half dozen or so PC's and Mac's around the house as well. Again, this is via WinAmp or iTunes, not from/via the slimserver/softsqueeze.
I'm confused about your answer. Forget winamp and iTunes for the momemt.
I'm still not sure that you've responded that others can play back those unplayable files via SoftSqueeze/SB2. What I'm trying to isolate is if the file has trouble with SS/SB2 or its your setup. If I or others can play the same song using SS/SB2, then the fault is with your setup. If several cannot play via SS/SB2, then it might be a server or SS/SB2 player problem.
Fair enough, I've posted one of the mp3's at <yanked> for you to try on your setup. Let me know how it goes.
Let me know when you've gotten it downloaded so I can yank it off my host.
I tried it on my setup - also won't play. This is the error:
2005-09-22 22:07:12.3496 00:04:20:05:a3:c5: Switching to mode play from stop
2005-09-22 22:07:12.3532 openSong on: file:///E:/Music/01%20-%20Not%20Gonna%20Get%20Us.mp3
2005-09-22 22:07:12.3578 openSong: getting duration , size , endian and offset 0 for file:///E:/Music/01%20-%20Not%20Gonna%20Get%20Us.mp3
2005-09-22 22:07:12.3579 openSong: not bothering opening file with zero size or duration
2005-09-22 22:07:12.3580 Error opening current track, so mark it as already played
2005-09-22 22:07:12.3608 Couldn't open song. Stopping.
Looks like slimserver isn't able to parse the file for some reason and thinks it's zero duration. As you mentioned, winamp and other players don't have any problem with it. Guess we need someone with more knowledge of the file parsing code to take a look at it.
Nor does it play for me. I get the same error. You can remove the file now. You should probably submit a bug on this one.
SB2 is able to report on the size of the file (8.3meg or so).
zero size, zero duration...looks like a corrupt file to me. Have you
tried re-ripping it?
if that fails, and you do file a bug report, please attach that track
to the report.
No, its not corrupt, and it does play fine in WMP and other players. The file size is clearly seen by SB2 as 8,398,085 bytes. SB2 just bails and says that it can't play the file.
Thanks for taking a look at it for me guys, I'm always glad to find out I'm not insane :)
FWIW I rip my tracks with AudioGrabber & lamemp3 codec, pretty standard from what I understand (also used CDEX some). I have *a lot* of tracks that behave this way, and I have re-ripped a CD to make sure I'm not somehow screwing that up. No idea why the 0-size, etc...
It strikes me as particularly bizarre that only some tracks on the same CD behave this way, for example tracks 01-03 (01 was the one I had posted) won't play, but tracks 04-07 work fine, then 08-13 don't. Though it's all over the map which tracks play from some discs.
I will be sure to include that track in the bug report.
I tried every test I could think of to see if anything would fix the file, but every diagnostic could read it fine and even when I rebuilt the header it didn't work. Other apps could all happily read the ID3v1 and v2 headers, duration, bitrate, size etc.
I had initially wondered if perhaps it had something to do with non-standard character sets used in the ID3 tags (I first noticed the problem on some Japanese pop imports I ripped), but that song I posted is about standard as it gets.
It would be really helpful if somebody could file a bug on http://
bugs.slimdevices.com with a link to that file and any relevant log
On Sep 22, 2005, at 7:17 PM, radish wrote:
> I tried it on my setup - also won't play. This is the error:
> 2005-09-22 22:07:12.3496 00:04:20:05:a3:c5: Switching to mode
> play from stop
> 2005-09-22 22:07:12.3532 openSong on: file:///E:/Music/01%20-%
> 2005-09-22 22:07:12.3578 openSong: getting duration , size ,
> endian and offset 0 for file:///E:/Music/01%20-%20Not%20Gonna%20Get
> 2005-09-22 22:07:12.3579 openSong: not bothering opening file
> with zero size or duration
> 2005-09-22 22:07:12.3580 Error opening current track, so mark it
> as already played
> 2005-09-22 22:07:12.3608 Couldn't open song. Stopping.
> Looks like slimserver isn't able to parse the file for some reason and
> thinks it's zero duration. As you mentioned, winamp and other players
> don't have any problem with it. Guess we need someone with more
> knowledge of the file parsing code to take a look at it.
It is submitted as bug 2175.
Powered by vBulletin® Version 4.1.12 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.