Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Mp3 playback problem (Read 3302 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Mp3 playback problem

Lately I had a problem with a .mp3 file that in no other .mp3 player occured. At least not in Winamp. With Mp3directcut I cutted out the problem sample. It's about 200kb. You can find it at:
http://members.lycos.nl/xvid/audio/

Any chance this will be fixed? Cause I love foobar, but this file makes me prefer winamp.
A secure audio ripper for linux: code.google.com/p/rubyripper

Mp3 playback problem

Reply #1
It "breaks" in Winamp, too, just not a noticably.  The Fraunhofer decoder may just be more elegant at recovering from errors.  Hardly foobar's fault that the file is broken, though.

Mp3 playback problem

Reply #2
i can make it decode "correctly" (as in: ignore error in the frame, produces no noticeable sound interruption to me), but it will also make a lot of other damaged files produce bleeps instead of silent frames.
Microsoft Windows: We can't script here, this is bat country.

Mp3 playback problem

Reply #3
I'm reluctant to suggest this (a knackered file is a knackered file, after all), but perhaps a solution would be to provide the ability to flag a file in the database as "ignore decoding errors" or something similar?

Personally, I'd never use it, but it's just a thought

Mp3 playback problem

Reply #4
The problem is, there's a near-infinite number of things that could be added.  It's a matter of balancing time, and adding only those worth adding.

That said, it's Peter's call.

Mp3 playback problem

Reply #5
Quote
i can make it decode "correctly" (as in: ignore error in the frame, produces no noticeable sound interruption to me), but it will also make a lot of other damaged files produce bleeps instead of silent frames.

What is the error? What makes the erroneous frame different from a normal frame? I think that the quickest solution would be to have some way for foobar to alter the file to "fix" the frame in the eyes of decoders, especially if it doesn't sound like there's an error there.

Having some error correction options for MP3s in foobar would be an interesting, and possibly "killer" feature.