form beta26? or beta27? and beta28, I notice that some songs can't be fully played, and almost at the end, it jump to the next song. These songs have played in winamp and older version foobar(0.667), all things are normal.

when error happens, the console window prompt sth "clip???" (I can't remember it)

My English is poor.

clipping detected?
Then you have to do:

1. enable advanced limiter in dsp section. move it to the end of the dsp chain
or
2. replaygain all your files

You can also untick "show clipping warnings" in playback preferences if infos about clipping are flooding console.

You may not need to activate Advanced Limiter if you have checked the box 'Use peak info to scale down tracks that still clip after applying replaygain.' (Playback dialog window)

Clipping has nothing to do with track skipping, I suspect your files are MP3s and their header states incorrect length. If they are "Fix MP3 header" context menu function should solve it.

But why has no this problem with foobar20000.7beta22 and before version(include foobar2000 0.667) and Winamp?

This is a problem with corrupted files having wrong headers. Please read the replies you've got.

Winamp for some odd reason has support for broken mp3s, it seems to 'fix' them on-the-fly. I think it's stupid to allow broken mp3s to be played, takes more system resources I would guess.

Not the classic stream corruption, more like bad headers, which other players (not supporting gapless playback) don't really care about.

Yes, "Fix MP3 header" solved this problem, but there is another problem, I have many mp3s with wrong header, I found I have to "fix" them one by one, so annoyed. can I "fix" them at one operation?

I just encountered a similar problem with my new mp3 files!

foobar would not report the correct file length until I manually fixed the header. Hope it will be possible to fix more than 1 mp3 header at a time soon

I think this is a foobar problem.

EAC thinks my files were ripped at 100%

LAME 3.9.3-1 has no problems.

mp3Trim 1.86 doesn't see a problem

Various other players have no problem.

When only one app reports errors, I suspect that app.

When only small group of people is having a problem, it's usually a problem with their setups.

I see a article talk about "wrong VBR header" sth, it says some mp3s will report wrong header while use new arithmetic about mp3 header while programing. fix header can solve it, or use new vesion lame to compress the mp3s, I guess this problem is the lame version and the foobar not compatible in arithmetic about mp3 header.

I found "mp3-tag studio" can fix the wrong header in batches. But can foobar2000 include the function "fix the header" automatically while playing?

By the way, my operating system and my foobar2000 setups absolutely has no problem. with foobar0.667 and version before 0.7b22, the mp3s played fine even with wrong header and wrong length.

I don't think this problem happens with any version of LAME exept 3.93.1. Does anyone else agree with this?

Always a possibility.

Although I'm happy to hear that I have stumbled upon the perfect app. I can take 0.7 RC 10's opinion of my files as gospel. I'll just ignore the other tools that I have used for a long time when they say there is no problem.

After all, I'm sure LAME and EAC do a terrible job of ripping and encoding. mp3Trim and EncSpot clearly have no idea how to examine an MP3 header.

Thanks for the valuable insight.

I think it would be more interesting if you uploaded one of problematic files so we can examine what causes the error to pop up.

I can certainly do that.

Frankly I'm baffled. I have let foobar fix the header of some and it is happy then.
The other tools do not report differences in the playtime, length, etc afterwards.

Shall I upload a file here?

Perhaps if I just sent the header?

Do you use some kind of LAME's builtin id3 tag writer ? I think it sets header's file size field to file size including id3 tag (bigger than size of actual data) while foobar2000 expects it to be size of MP3 data without tags; that would explain the error (I think I can add fix for that without getting one of those files then).

I have EAC set for using an external compressor, LAME.
This is option set I use:
--preset extreme --scale 1%h %s %d

And the options checked are:

Delete WAV
High Quality
Add ID3 tag

I believe that would pass the tag info to LAME and it would write it as you suspect.

Actually that is EACs own tagging. Also since you are using your own command line, you should probably set EAC to "user-defined encoder" (if you havent already done so, otherwise EAC will set extra command line parameters for bitrate etc. which may have undesired effect)

If you want to eliminate EAC you could try ripping to PCM WAV (Copy uncompressed in EAC), then encoding to mp3 manually.

Extremely sorry for the error.
That is how I have EAC setup, Parameter passing scheme: User defined encoder.

Now so many people talk about this "wrong header" problem, I am so glad!

I restate that my mp3s with "wrong header(wrong length)" played very well in Foobar0.667 and version before 0.7B22, Winamp too.
So, I suspect it's a problem with new version foobar2000!

How about check the difference between 0.667(or version before 0.7B22) and 0.7RC of the program on this part?

That's because other players (including old foobar2000) didn't support gapless mp3 playback, and your files have corrupted gapless playback info, so they can't be played correctly anymore. This is not a bug and will not be changed.

But if you let me chose "gapless" or "full correctly play", I'd rather the later!

"gapless" and "full correctly play", which is the most important?

I'm at a loss of your opinion. I guess many people encounter this problem will not agree with your opinion.

BTW, This is my last post. I don't say any more about this.

That option being togglable would cause even more mess because track length reported when enabled would be different than track length reported when disabled, forcing users to manually reload info from files after toggling. Just manually fix all problematic files and you will be fine.

I like foobar, so I say:
many people only know foobar2000 sometimes can't full correctly play some songs, but so many other players works fine.

And you tell me I can manually fix all problematic files, I suspect beginners(me too) can quickly fix so many problematic files.

At last, I strongly suggest the developer consider the "full correctly play" first.
not such "gapless" still unknow for many people.

Corrupted files aren't common. Unless you *cough* pirate music from p2p networks. And if you do, you have a worse problem somewhere else.

Could be possible in far future to "Fix MP3 Header" for multiple selected files?

Thanx Narag

Well, I have revisited the files with a different tool. Anyone have any experience with MP3Utility?

MP3Utility Info and Download

It looks like an excellent tool and it gives quite complete results. It did find several files that foobar did not complain about.

Whether this helps with my foobar problem or not remains to be seen. But it will help toward having a cleaner collection I think.

I'd like any opinions on this tool though. I don't want to spend time if the tool is not accurate. As I said, it certainly looks complete/accurate.