Hi, this are the files I ripped and batch encoded, but Mp3tag (3.28) detects one file differently (wrong?).
You can check this file with MPEG 1 Layer I with the tools mentioned here:
Or - if possible - you can share this track and we can have a look at it.
Interesting. MP3val reports:
(offset 0x10b0): MPEG stream error, resynchronized successfully
VBR detected, but no VBR header is present. Seeking may not work properly.
Non-layer-III frame encountered. See related INFO message for details.
Different MPEG versions or layers in one file. See related INFO message for details.
What could cause this? The file itself sounds and plays ok.
Only a file without findings is a good file.
And right now you have 2 applications that report problems.
I would still investigate why this file leads to findings and others don't.
For short:
Your ripping software or your batch encoding software.
You have to check which one create this MPEG 1 Layer I / Stereo for this specific file.
As we don't know what do you use and how you have set them up it is not possible for us to guess.
I suggest to just rip and encode this specific file again.
Can you reproduce the Codec problem?
I tried to rerip and encode the track again using the same tools, but I could not reproduce the problem.
Audio data is the same, so I suspect it might have been somehow caused by the wrong metadata write? I am using Discogs as a Tag source.
I used MP3val to fix the file.
By the way, when comparing the fixed and the new file, I noticed a size difference and it was only those few bytes. Is that something that MP3val writes and Mp3tag doesn't?
A simple copy Tag copy in Mp3tag didn't 'fix' it.
If the audio part is damaged then MP3tag does not help a lot as MP3tag does not treat the audio part.
The original problem was that 2 programs reported a problem and you doubted that this was correct.
After you re-encoded the file and repaired it - is the problem gone?
Yes, I haven't encountered the 'wrong' Codec problem after ripping and encoding the file again.