PDA

View Full Version : problem with certain tracks?



Adam Hirsch
2004-01-18, 16:48
Hey there -- I'm a prospective squeezebox buyer, trying out slimserver v
5.0.1, running on a linux box. The software's working great to stream to
other computers around the house, with a couple of exceptions. There are
certain tracks/albums that it just won't play, and I'm mystified as to why.

The tracks' tags read and display just fine, and they'll queue perfectly
happily into playlists with other non-problem tracks. When the list gets
to the bad tracks, though, the web UI displays them as "playing," but then
seconds later, it moves on to the next track. If I have a playlist
containing only these problem tracks, trying to play them just makes the
web UI flip back to "stop".

File permissions seem fine, the tracks play fine if I take them and play
them directly on another machine... Has anyone seen this behavior?
Nothing's getting logged that looks suspicious, and short of digging
through the thousands of lines resulting from stracing the running
slimserver process, I've run out of where to look for debugging
information...

Title: Makimadni
Artist: Derek Trucks
Album: Live 11-29-2003
Genre: Other
File Format: MP3
Duration: 14:35
Year: 2003
File Length: 14,013,420 Bytes
Bitrate: 128kbps CBR
ID3 Tag Version: ID3v1 / ID3v2.3.0
Location: /music/Derek_Trucks/makimadni.mp3
Date Modified: Sunday, January 18, 2004, 11:25:50 AM

Adam

--
We either make ourselves miserable or we make ourselves strong.
The amount of work is the same. - Carlos Castaneda
<adam (AT) baz (DOT) org> adam hirsch <http://web.baz.org/~adam/>

kdf
2004-01-18, 16:59
Quoting Adam Hirsch <slimserver (AT) quakerporn (DOT) com>:

> Hey there -- I'm a prospective squeezebox buyer, trying out slimserver v
> 5.0.1, running on a linux box. The software's working great to stream to
> other computers around the house, with a couple of exceptions. There are
> certain tracks/albums that it just won't play, and I'm mystified as to why.

I've run out of where to look for debugging
> information...

try running the server with the --d_source command-line option. It should show
you why the song is stopping. If you run right from command line, the debugging
into will just come up on the same console. use --logfile test.log to store the
info to a file for later inspection.

otherwise, I can't see anything immediately wrong with the song info you posted.

-kdf

Adam Hirsch
2004-01-18, 18:34
Here's some of the output from trying to play an album of "bad" tracks.

(the nutshell version is that slimserver appears to read the song's info
correctly, but then it reads through the entire song in mere seconds,
silently, and through to the end of the album about 5 seconds later.
Nothing to indicate why, and these tracks play flawlessly on every other
player I can find. I'm truly baffled, and it definitely gives me pause
before ordering a squeezebox. :( anyone seen this behavior, or am I alone
in this, and should be looking at the box I'm running this on?)

Here's what I saw in the logs, with my read on it:

===

Reads the song, seemingly correctly. Gets the length and size right, at
least.

>> 2004-01-18 19:35:51 openSong on: /stuff/mp3/Guster/Keep It Together/01-Guster-Diane.mp3
>> Use of uninitialized value in concatenation (.) or string at Slim/Player/Source.pm line 684.
>> 2004-01-18 19:35:51 openSong: getting duration 225.93306122449, size 7119428, and offset for /stuff/mp3/Guster/Keep It Together/01-Guster-Diane.mp3
>> 2004-01-18 19:35:51 openSong: this is an mp3 file: /stuff/mp3/Guster/Keep It Together/01-Guster-Diane.mp3

the "line 684" error gets logged when I'm successfully playing tracks, too,
so I'm reading that as a red herring.

>> 2004-01-18 19:35:51 openSong: opening file /stuff/mp3/Guster/Keep It Together/01-Guster-Diane.mp3
>> Use of uninitialized value in concatenation (.) or string at Slim/Player/Source.pm line 705.
>> 2004-01-18 19:35:51 seeking in into /stuff/mp3/Guster/Keep It Together/01-Guster-Diane.mp3
>> 2004-01-18 19:35:51 Streaming with format: mp3
>> 2004-01-18 19:35:51 New play mode: play
>> 2004-01-18 19:35:51 127.0.0.1: Current playmode: play
>> 2004-01-18 19:35:51 realpos 0 calcuated from bytes received: 0 minus buffer fullness: 0
>> 2004-01-18 19:35:51 songTime: 0 = (0(realpos) / 7119428(size) * 225.93306122449(duration) * 1(rate)) + 0(time offset of started stream)
>> 2004-01-18 19:35:51 read a chunk of 32768 length
>> 2004-01-18 19:35:51 metadata now: 0

[...] Many, many more chunk reads, culminating with:

>> 2004-01-18 19:36:00 read a chunk of 32768 length
>> 2004-01-18 19:36:00 metadata now: 0
>> 2004-01-18 19:36:00 Reduced chunksize to 8772 at end of file (7119428 - 7110656)
>> 2004-01-18 19:36:00 read a chunk of 8772 length
>> 2004-01-18 19:36:00 metadata now: 0
>> 2004-01-18 19:36:00 Reduced chunksize to 0 at end of file (7119428 - 7119428)
>> 2004-01-18 19:36:00 end of file or error on socket, opening next song, (song pos: 7119428(tell says: . 0), totalbytes: 7119428)
>> 2004-01-18 19:36:00 opening next song...

Notice that this 225 second song took 9 seconds to read through, despite
having correctly read in the duration. The rest of the album streaks by in
6 seconds, nothing ever having come from the speakers. Timestamps like so:

>> 2004-01-18 19:36:00 openSong: getting duration 220.16, size 7196939, and offset for /stuff/mp3/Guster/Keep It Together/02-Guster-Careful.mp3
>> 2004-01-18 19:36:00 openSong: getting duration 214.935510204082, size 7189891, and offset for /stuff/mp3/Guster/Keep It Together/03-Guster-Amsterdam.mp3
>> 2004-01-18 19:36:01 openSong: getting duration 175.595102040816, size 5211994, and offset for /stuff/mp3/Guster/Keep It Together/04-Guster-Backyard.mp3
>> 2004-01-18 19:36:01 openSong: getting duration 215.04, size 7029739, and offset for /stuff/mp3/Guster/Keep It Together/05-Guster-Homecoming King.mp3
>> 2004-01-18 19:36:02 openSong: getting duration 182.909387755102, size 5352259, and offset for /stuff/mp3/Guster/Keep It Together/06-Guster-Ramona.mp3
>> 2004-01-18 19:36:02 openSong: getting duration 136.515918367347, size 4524835, and offset for /stuff/mp3/Guster/Keep It Together/07-Guster-Jesus On The Radio.mp3
>> 2004-01-18 19:36:03 openSong: getting duration 220.238367346939, size 7103381, and offset for /stuff/mp3/Guster/Keep It Together/08-Guster-Keep It Together.mp3
>> 2004-01-18 19:36:03 openSong: getting duration 316.055510204082, size 8441927, and offset for /stuff/mp3/Guster/Keep It Together/09-Guster-Come Downstairs And Say Hello.mp3
>> 2004-01-18 19:36:04 openSong: getting duration 204.094693877551, size 6055519, and offset for /stuff/mp3/Guster/Keep It Together/10-Guster-Red Oyster Cult.mp3
>> 2004-01-18 19:36:05 openSong: getting duration 271.438367346939, size 7247300, and offset for /stuff/mp3/Guster/Keep It Together/11-Guster-Long Way Down.mp3
>> 2004-01-18 19:36:05 openSong: getting duration 197.694693877551, size 5489529, and offset for /stuff/mp3/Guster/Keep It Together/12-Guster-I Hope Tomorrow Is Like Today.mp3
>> 2004-01-18 19:36:06 openSong: getting duration 296.411428571429, size 8206875, and offset for /stuff/mp3/Guster/Keep It Together/14-Guster-Two At A Time.mp3


Adam

--
adam hirsch | Human speech is like a cracked kettle on which we tap
| crude rhythms for bears to dance to, while we long to
adam (AT) baz (DOT) org | make music that will melt the stars. -- G. Flaubert

kdf
2004-01-19, 00:15
Quoting Adam Hirsch <slimserver (AT) quakerporn (DOT) com>:

> Here's what I saw in the logs, with my read on it:
>
That is not something I've seen occur. I'm guessing these MP3's are nothing
ususual, ripped and encoded from cd using stereo and 44kHz, compressed to
128kb/s or more. However, were it not, I'd still expect some audio.

I hate to keep tossing this out as the solution to everything, but perhaps
trying a nightly build will help. They are located here:

http://www.slimdevices.com/downloads/nightly/

Many changes have been made since 5.0.1. There are a couple issues outstanding,
but at new release is said to be on its way shortly, if you prefer to wait for
something official.

cheers,
kdf

Adam Hirsch
2004-01-19, 11:03
kdf (slim-mail (AT) deane-freeman (DOT) com) wrote:

> I hate to keep tossing this out as the solution to everything, but
> perhaps trying a nightly build will help. They are located here:

Lo and behold, the nightly build lets the problem tracks play. Awesome. I
wonder why.

Adam

--
Never retreat. Never explain. adam (AT) baz (DOT) org
Get it done and let them howl. adam hirsch
- Benjamin Jowett (1817-1893) http://web.baz.org/~adam/

kdf
2004-01-19, 11:13
Quoting Adam Hirsch <slimserver (AT) quakerporn (DOT) com>:

> kdf (slim-mail (AT) deane-freeman (DOT) com) wrote:
>
> > I hate to keep tossing this out as the solution to everything, but
> > perhaps trying a nightly build will help. They are located here:
>
> Lo and behold, the nightly build lets the problem tracks play. Awesome. I
> wonder why.

I wish I could give you a quick answer. MANY little quirks have been ironed out
since 5.0.1, plus many new features added, so I can't remember now what it might
have been. Glad it works now :)

-kdf