Help - Search - Members - Calendar
Full Version: foobar and winamp both won't play this file
Hydrogenaudio Forums > Hosted Forums > foobar2000 > Support - (fb2k)
demogorge
I have a file that will not play in foobar or winamp3 (uninstalled winamp2 when I discovered foobar tongue.gif ). It will play in Windows Media Player (using l3codecx.ax) and in my nomad mp3 player.

I can split it with mega mp3 splitter and it's still broke, but if I use BeSplit it plays fine with this message:

CODE
[00:00:00:000] +------- BeSplit -----                          
[00:00:00:000] |  Input : D:\BeSweetv1.4\Split21.mp3
[00:00:00:000] |  Source Sample-Rate: 44.1KHz
[00:00:00:000] |  Channels Count: 1, Bitrate: 24kbps
[00:00:00:000] |  Output : D:\BeSweetv1.4\Split21_Fixed.mp3
[00:00:00:000] +---------------------                          
[00:00:00:417] Stream error : Sync found after 128 bytes
[00:15:04:176] |  Writing D:\BeSweetv1.4\Split21_Fixed.mp3
[00:15:04:176] +---------------------                          
[00:15:04:176] Operation Completed !
[00:00:04:000] <-- Process Duration


Ok so this is a bad but easily fixable file. Should foobar be able to play this or is it better not to bother with bad files?
kode54
Upload the file here.
demogorge
Allright thanks. The file is here.
neoufo51
Interesting...

Foobar stops like a rock after a nanosecond.
BSplayer .86 gets a watery sound for the whole playback.
WMP9 plays back fine. (seems to be a Harry Potter audiobook)
MPC 6.4.6.7. with the MAD filter enabled also plays back fine.

Looks like an issue to be addressed in 0.7.2.
criZZb
QUOTE
CODE
Stream error : Sync found after 128 bytes


That's because this file seems to be 2 concatenated files. Those 128 bytes is id3v1 tag!

And that's why the file is broken ph34r.gif Foobar stops playing it as soon as it tracks the tag...
demogorge
Well I don't know if you can say the file is broken, since the file can be played in other players.

Yes there is lots of bad splitting and concatenation at work. My nomad muvo does not resume (or seek very well) :'( so I needed to split the source into manageable chunks.

But you are correct, an id3 tag is found at 0x573.
Case
QUOTE(demogorge @ Oct 16 2003, 08:31 PM)
Well I don't know if you can say the file is broken, since the file can be played in other players.

I won't comment on brokeness of the file but the reason why foobar won't fully play anymore such mp3s is added gapless support. It wouldn't work if foobar didn't respect length infos in mp3 files.
demogorge
Then that goes back to my OP. Will foobar support this file or not bother because it is bad?
criZZb
I think Case has cleared it...
demogorge
Is that correct? The file plays fine in winamp2 with gapless support...
/\/ephaestous
QUOTE(demogorge @ Oct 20 2003, 09:52 PM)
Is that correct? The file plays fine in winamp2 with gapless support...

winamp2 gapless support is not the same as in Foobar, winamp's gapless support is more like the Gap Killer plugin.

you can fix it with an hex editor and 'Fix Mp3 header'


People shouldn't use Copy /b for mp3 files...
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.