MinimServer Forum

Full Version: Error: no valid MPEG header near offset 4096 in file
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi Guys,

I've just started my journey with MinimServer on Synology's NAS.

MinimServer version 2.0.18 update 190

By checking the MinimServer log I've already resolved issue with:
Warning: truncating incorrect value for DATE tag yyyy-dd-mm in file
by changing MP3's version TAG to ID3v2.4

but still have some other errors I can't track

Error: no valid MPEG header near offset 4096 in file
Error: no valid MPEG header near offset 77761 in file
Error: no valid MPEG header near offset 277743
Error: no valid MPEG header near offset 202428
Error: no valid MPEG header near offset 2197
Error: no valid MPEG header near offset 200000

Could you please shed some light on it and let me know where should I start looking for an answer? What supposed to be fixed when I see such errors?
This means the audio data is corrupt. If you listen very carefully, you should be able to hear a slight click or tick at that point in the file.

Unfortunately there is no fix for this other than to re-rip or re-download the file. For some variable-rate MP3 files, MinimServer needs to read a small portion of the audio data to estimate the playing duration of the track. If this fails because of file corruption, this error message is produced and the file is not included in the library.
This is what I was worried about. In mean time I've also found a very useful tool that can help to analyse such files for more details and also try to fix it.
http://mp3val.sourceforge.net

As per analyse the error is related with:

Different MPEG versions or layers in one file.
18513 MPEG frames (2 V1L1, 0 V1L2, 18511 V1L3, 0 V2L1, 0 V2L2, 0 V2L3, 0 V2.5L1, 0 V2.5L2, 0 V2.5L3), +ID3v1+ID3v2, no VBR header, CRC

As per documentation:
Different MPEG versions or layers in one file - Mixing different MPEG versions and/or layers in one file is not very good. As in the previous case, this issue can be fixed only by reencoding.

Anyway after "repair" those files gone from the logs after rescan.

Thank you for this great piece of software. I'll try to use it for some time with BubbleUPnP on my mobile and stream to Onkyo network amplifier to see how response time looks like when searching and moving through the folders. So far I was using Foobar 2000 for indexing. Let's see Wink
Thanks for the pointer to mp3val. It could be useful for other users with the same issue.

I will be interested to hear what you think about MinimServer's performance.
Reference URL's