| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016138 | MMW 5 | Other | public | 2019-11-23 00:43 | 2021-07-27 19:57 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | tweak | Reproducibility | sometimes |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0.1 | Fixed in Version | 5.0.1 | ||
| Summary | 0016138: Waveform seekbar: Tracks Waveform is not fully calculated | ||||
| Description | It happened to me few times during prolonged testing of playback, but can't replicate constantly. We should add that when Waveform Seekbar is shown MM5 should be capable to check if correct one is generated eg. length of Waveform is lower than track length. But occurs randomly and it is not format dependent, like generating task is terminated and partial waveform data is cached. Only way to correct it is to either delete all wavedata cache or if track is not volume analyzed to analize as it tells mm5 to rehash wavedata. So this check would prevent such cases. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2416 | ||||
|
|
Peke, is this more likely to occur with certain tracks or file formats? If yes, can you provide a couple of sample tracks that it occurred with? |
|
|
Assigned to see if it is easy to add/fix otherwise postpone for 5.1 |
|
|
1) During fixes related to this issue I have uncovered serious problem, that is causing freeze or crash, when waveform is going to be computed. It needs to be fixed immediately, increasing priority. 2) maybe we could add some "recompute waveform" context menu item above waveform seekbar, the file could be changed outside MediaMonkey and user could want to recompute waveform even in case it was computed previously till the end. |
|
|
1) fixed in build 2219. 3) there is problem related to some MP3 VBR files, that do not contain correct samples count, such have displayed waveform in wrong proportions. |
|
|
2) implemented "Update waveform" feature in build 2219, it recalculates waveform, so no need to delete manually from cache |
|
|
Fixed in build 2220. Some VBR files still could have slightly inaccurate waveform, but it should be only minor difference now. |
|
|
Verified 2220 I am not being able to find any file whose waveform is not correctly calculated. |
|
|
Should be fixed in 2413. I have reproduced it occasionally by the same steps as here: https://www.ventismedia.com/mantis/view.php?id=17754#c63734 It is fixed now. |
|
|
Verified at 0017754. |
|
|
lowlander: was it on clean installation with empty Temp? In case wrong waveform was already saved to Portable\Temp\Waveforms folder before, it is used. The only way of detecting wrong waveform is recompute it again, but we prefer speed and lower CPU load. |
|
|
No, not a clean install,but the file had never been played. It just happened on another file as well. image-2.png (15,861 bytes) |
|
|
Fixed in build 2416. |
|
|
Verification concluded with 2418 I have not observed this in past three version, but Calculation seams a fraction slower. Please close after second verification. |
|
|
Not seen on recent builds (up to 2427) |
