View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005580 | MMW v4 | Help / Docs / Localization | public | 2009-05-05 02:30 | 2011-05-11 21:41 |
Reporter | peke | Assigned To | |||
Priority | urgent | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 3.1 | ||||
Target Version | 4.0 | ||||
Summary | 0005580: MP3 with bad CRC not Playable | ||||
Description | I noted that there are still there is some MP3 files that can't be played in MM but play just fine in AIMP and gSpot. Example file apps that play it are uploaded to FTP. | ||||
Tags | No tags attached. | ||||
Fixed in build | |||||
|
Tested in 1242 |
|
Peke, the file has a bad CRC (checksum) protection field. That allows the decoder to check the file on the fly and mute (or lower) the output if it detects corruption as players like MediaMonkey and WMP does. Players like iTunes, WinAmp ignores the bad CRCs and therefore play the file anyway, but without being protected. If you hit 'Alt+3'(View File Info) in WinAmp then you can see whether CRC is enabled (CRCs: Yes/No). All my MP3s have CRCs disabled. It's a choice you have when you encode an MP3. Bad CRCs can be fixed by using the mpTrim PE, see: http://www.mptrim.com/mpTrimPE-moreinfo.html I guess that this should be added to KB. |
|
I wonder if MM should be capable of fixing Bad CRC for MP3 files but at least it should be possible to be ignored as file is fully playable. MP3Trim PE is not free for fixing bad CRC, but http://www.gromkov.com/faq/repair/mp3_validator.html |
|
We can't influence whether CRC is taken into account or not, the decoder makes the decision - which depends on the codec installed. I suppose that by installing an alternative plug-in (in_mpg123?) this would be fixed. As for possible fixing of CRC in MM - I'd say that it isn't a task for MM, but rather for some Add-On, e.g. a script based interface to the mp3 validator. |
|
Updated KB. |