View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004475 | MMW v4 | Other | public | 2008-03-17 00:40 | 2008-12-02 16:58 |
| Reporter | peke | Assigned To | |||
| Priority | immediate | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Fixed in Version | 3.1 | ||||
| Summary | 0004475: Specific corrupted WAV files can freeze MM | ||||
| Description | I have confirmed that File from forum topic http://www.mediamonkey.com/forum/viewtopic.php?t=27281 Freezes MM My findings are described here: http://www.mediamonkey.com/forum/viewtopic.php?p=137489#137489 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1199 | ||||
|
|
I'll Upload Files my edited files to FTP, source file is not uploaded to save space. Dilemma is should we disable Metadata seek thrum WAVE byte by Byte (which proved that it founds Metadata even file is corrupted) or Ignore and truncate File where all data after Spec will be lost (I think it will corrupt WAVE even more and there is possibility of Data Loss) or even Assume that appended data is actually correct Audio Data and Update File so that Players and Editors now Read That as Audio. here is what Editing Software do for this example: AudioCity: Truncate Invalid Sample Loop (Most likely it do not Support it in first place) and Truncate File (remove 247ms appended to file) to reported length SoundForge 9.0: Reset Invalid Sample Loop (length of Loop is 0ms or empty) and Truncate File (remove 247ms appended to file) to reported length Thing that I have Done is that I have Manually calculated break point according to WAVE "data" Chunk and the using Hex editor updated length of file and "data" chunk. After I have checked that Appended data do not contain any Text that may look as Metadata, Truncated Invalid Sample Loop from Wave and Saved file. After opening manually corrected file in Both WAVE editors. File was 247ms longer and contain all data. Seek function that doo corrections are located in I thought also f_WAVE.DPR algorythm for Seek should be changed Lines 761-802 |
|
|
Fixed in build 1150. - Prevented the freeze and added a safe fixing of the corrupted WAV file, so that it can be properly tagged. |
|
|
Verified 1151. |
|
|
I found out that the fix to this issue can cause WAV tag corruption in some cases. |
|
|
Fixed in build 1199. |
