Help - Search - Members - Calendar
Full Version: Stream errors heard with Foobar2k?
Hydrogenaudio Forums > Hosted Forums > foobar2000 > Support - (fb2k)
zecg
Things console describes as:
"
WARNING (CORE) : Clipping detected.
WARNING (foo_input_std) : mpeg stream error at 1115237 bytes, attempting resync
INFO (foo_input_std) : mpeg stream resync successful
"

...are heard as clicks. Now, I am well aware of the fact that this is an mp3 error, but I never heard it using Winamp.
Since, of course, Foobar 2k is far superior when it comes to audio quality, I am merely wondering if there is / will be a solution, or will I have to re-encode these?

BTW, I'm a new user and apart from this Foobar is pure love.
tournet
the same question with me, foobar have this problem after 0.7beta22, the every beta version (also RC3 and RC5) I have tryed, this problem still, So now, I use 0.7beta22.

can this problem be solved?
sld
QUOTE(zecg @ Jun 7 2003, 11:30 PM)
Since, of course, Foobar 2k is far superior when it comes to audio quality...

No, bootlicking like this will get you nowhere biggrin.gif.
You should really go read up, or ABX, to really find out if Foobar is far superior. It may be superior in some aspects of the playback chain, but there's really no practical difference between the mp3 decoders in Foobar and Winamp.

When you say 'stream errors', you don't mean HTTP streaming right? (Hmm, I sound stupid asking this).

If it's your files on your HD that are showing the clipping warning and the resync problem...

To cure clipping: Use Replaygain on your mp3s. You can do this by either using mp3gain, or by installing Foobar's replaygain scanner plugin (included in the default installer) and replaygaining your files using it. Then, pick a replaygain mode in Preferences > Playback, and make sure to check the option 'Use peak info to scale down....'

To cure resync problems, you need to use the 'fix mp3 header' context option. I have absolutely no idea how to use it though, since I don't have to.
tournet
But why there is no this kind of problem with foobar2000 0.7beta22(also foobar0.677) and winamp?

this kind of problem is so despair
treech
just wanted to know why this happens, sadly, it seem to happen on my setup as well... sad.gif

winamp must be doing some funky stuff, at least it works there :-\

http://www.netjuke.org/index.php?name=PNph...&highlight=mpeg
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.