View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016658 | MMW 5 | Playback | public | 2020-05-25 16:29 | 2020-06-02 17:46 |
| Reporter | michal | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0 | Fixed in Version | 5.0 | ||
| Summary | 0016658: Some MP3 are played extremely distorted until analyzed volume | ||||
| Description | File from the user is played as a mix of original sound and noise, it is fixed after making "Analyze Volume" of the file. Other players (except MM4) do not have such problem with the original file. | ||||
| Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=96645 https://www.mediamonkey.com/forum/viewtopic.php?f=1&t=88646 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2252 | ||||
|
|
Fixed in 2252. The file contains wrong normalization value (way too high), and does not contain peak value, so MM cannot prevent clipping there. Fixed so we do not normalize in such situation. |
|
|
Should MediaMonkey in that case not visually indicate something about this? Otherwise users will not experience leveled playback, but not know why. It would also lead to a lot of troubleshooting. I propose a Peak Value field visible in MediaMonkey and an option (disabled by default) in the volume leveling settings to level files with unknown peak value (may cause distortion). Also Auto-Analyze and Analyze Volume would need to analyze files with known Track Volume, but unknown Peak Value even if option to only analyze volume with unknown leveling is checked. |
|
|
Tested 2252 and there seems to be a problem: 1 Select the track in Locations > Path [List] node and initiate playback --> it plays ok (at reasonable volume) 2 Select the track and 'Analyze Volume' --> success (value changes from +44 to -8) 3 Initiate playback (with Volume Leveling enabled) --> It starts playing (at a much lower volume) and then a crashlog is generated: 428B0000 Note: Upon restarting MM and initiating playback of the same track --> the crash occurred upon pressing STOP p.s. I agree that there should be some sort of indication that there's a problem with the Replay Gain tags. If there's no quick fix, I'll open a new bug. |
|
|
I cannot reproduce. Which track? The one I uploaded has leveling value 25.955 and works ok. According to Eureka log, the crash is not related to this issue at all, it could be coincidence. We cannot detect problem with leveling value without analyzing whole file (we take as wrong values these >50), and we cannot do it before every playback. The peak value is not compulsory there. |
|
|
Resolving. Petr fixed the crash in 2253 (it was regression and really coincidence with this). |
|
|
Verified 2254. |
