Nice tool to test your music for errors

There's a nice very fast tool to test your music for encoding errors ... before you blame MEIZU for corrupted sound

-> http://www.vuplayer.com/other.php

Cool, nice tool here. If someone has tested and have gotten a 'fail', please post it here and maybe a link to that song... because all the songs I've tried have passed...

Nice. I haven't tried it but i notice it supports vista as well ( hopefully 64bit since that is what i used :X ).

How does it check if the song is alright or not i wonder :x hm ...

I have a song where i haven't finished downloading using p2p so i will check with that.

Great tool!, All my songs passed because they were encoded by myself :D So naturally they work just fine without any problems on my miniPlayer.

Hello Meizu lobby,

I have tested with this tool five songs which causing a shuttering problem on my M6. Indeed one of the mp3 files has a "LOST SYNC @ END OF FILE" problem. The other are fine! But all of these files are playing on the Mayfield from my wife without any problem. So therefore we have to ask us if the Meizu boxes are a little bit to sensitive for this world! A good product can deal also with lower quality files like a good Managing Director can achive his targets with normal people as his stuff.

I hope you understand me.

M6
8GB

The program called MCP on that site is really neat as well. It lets you play three songs simultaneously and switch easily between them. I converted a song from Flac into mp3's at different bitrates. Wow. I had no idea the difference in quality was as great as it is!

Very Fun Program!
I have tested my nearly 280 songs (Mp3) and 69 songs have failed. Hurray!
Either with message: (LOST SYNC @ END OF FILE), (TRUNCATED) or (BAD ID3v2 TAG).

I have noticed one of my songs, with "stutter problem" have passed this test, so I don't know how much I shall believe this program.
A connection between the fails and the "stutter", I don't doubt there is always a connection here.
Another question I ask myself right now, how do we fix these errors anyway
I have got that kind of problems with ID3 tags before for some months ago, where some files not would show the ID3 information correctly. To fix the errors have I let the files go thought a conversion program.
I have used the free "Switch"
http://www.nch.com.au/switch/plus.html
And then the files was fine again.

But thanks a lot for the link!

Re-encoding lossy files is always the false treatment because you will get less quality.
Bad ID3v2 tags you only can get rid of by deleting the whole tag, then tag again and the problem should be solved.
For your other files you should try a good trim program. I think the problems occur with dull programs deleting silence at the end of the file.

Originally Posted by PeterHamburg

Re-encoding lossy files is always the false treatment because you will get less quality.
Bad ID3v2 tags you only can get rid of by deleting the whole tag, then tag again and the problem should be solved.
For your other files you should try a good trim program. I think the problems occur with dull programs deleting silence at the end of the file.

I understand why Re-encoding not is the world best idea.
Thank for the reply.

Originally Posted by PeterHamburg

Re-encoding lossy files is always the false treatment because you will get less quality.

Debateable really. Unlike dealing with analog media, encoding algorithms are largely determinisitic (an input should always give the same output). MP3 encoding in perticular makes use of frequency cut-offs and other audio effects to trim frequencys we _cannot_ hear. Other than that the settings are largely pre/post processing and ofcourse the bit allocation. In terms of the fourier and cosine transforms used with media like this, the difference over a few encode/decode cycles should be relatively minimal. We are talking mathematical precision errors and nyquist sampling errors (nb: bit allocation is involved there).

Precision errors are inevitable, but providing you dont re-encode at a lower bitrate, the decoded data from the original encoding should be reasonably sampled for a near equivalent re-encoding.

If you are losing quality due to sampling errors, chances are the codecs you are using should upsample before re-encoding - at worst leading to some minor ringing effects (if upsampled through repetition, rather than more intelligent interpolation). Even then, ringing can be minimised in the frequency domain & I would hope atleast some codecs are able to account for it.

Just my 2c.

That tool find all my files ok.

In my humble opinion stutter problem have gone outside of what we can do for the moment, nor Meizu will... nor us will.
I've seen this problem posted in 11-21-2006 here S1.010 Bugs and Annoyances... almost a year ago!!!

I usually pick entire albums from the net due to my hobby of listen all about rock music, especially that hard-to-find of early ages. Such music is not easy to get in CDs, so I don't rip my own material. It's ripped by others, then I can't assure the quality of ripping. Then I depend on a reliable player... I've never had problems with any of my MP4... except my ex-M6 and my actual M3. Only solution I have is to move such albums from my M3 to my Onda or my Teclast.

The stutter issue is ABSOLUTELY RANDOM... I know it happens in MP3 in piano passages of music, not just silence, when a track is ending. It doesn't matter if it's VBR or CBR or whatever concerning ripping... NO FURTHER PATTERN found yet. I know too that re-encoding solve the problem, but in fact, there is a lost of quality re-encoding lossy-lossy formats. Sometimes I re-encode some material from MP3 to OGG, which I like very much.

I am just waiting for M6SL to know if it had the problem, now I know that Philips DAC has been changed to a Wolfson DAC. But who knows if this finally solve this issue?

I would really like to hear if any know a free program to fix these kinds of errors. Have looked around here but couldn't find anything.

My player is beginning stop showing the ID3 tags, but I am not sure if there is a connection with this and the errors I got with this program.
But please send a link.
We can't all go around with music files full of errors, right?
We need to have a chance to fix them to minimizing malfunctioning and stutter if there should be a connection between this.

Hi everyone, new member here.

I used the tool and maybe 1/3 of my songs had one kind of error or another. To fix them I used two utilities:

mptrim- http://www.mptrim.com/ Used the auto feature to fix lost sync at end of file errors.
tidymp3- http://cuemaster.host.sk/tidymp3.php Drag and drop to wipe ID3 tags and start fresh. You can do batch processing and also keep ID3v1 tags using the command line.

Excellent, Tidy MP3 explains this problem and repairs the files.

Copied From Their Web Site -

Frame-reconstructor

Some ID3v1 tagging-tools will overwrite original audiodata if no tag is present (they just blindly OVERWRITE the last 128 bytes, instead of appending the tag to the file). This causes clicks and pops when playing the mp3. Tidymp3 tries to fix this by copying framedata from the valid part of the frame. This frame-reconstructor does the same with 'LYRICS'-data, and works also with partial tags. Have a look at a before/after screenshot here. To disable the frame-reconstructor, use the /F commandline option.

that tidy mp3 is one hell of a good tool to fix your mp3 files! it takes about 10 seconds to fix a whole album and goodbye stutterint-issue! just use the /p switch and it doesn't erase all your id3tags!

A W E S O M E !

here is a little batch that provides drag+drop of mp3s or a folder (with subfolders) with the /P switch of tidymp3 :

Thanks for the links.

This is some of the tools I mentioned here that should solve some problems that affects stuttering.

I am sure that for M6SL it will solve practically all of this stutter problems.