View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020939 | MMW 5 | Playback | public | 2024-05-23 22:29 | 2024-06-04 19:17 |
| Reporter | lowlander | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.1 | ||||
| Target Version | 5.1 | Fixed in Version | 5.1 | ||
| Summary | 0020939: Playback looping for files played from network under network load | ||||
| Description | When there is some network load it seems MediaMonkey struggles to play files from network. Note that the PC has a 2.5Gbs connection to a 10Gbs NAS, load tends to not exceed 500Mbs during these events. Seen both with WASAPI and MediaMonkey DirectSound (logs from latter). | ||||
| Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?t=106222 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3028 | ||||
|
|
Not sure what we can do. In case MM does not receive data from NAS, it cannot play them. The looping is caused by playing the same buffer again, which did not receive new data. |
|
|
If it truly is an issue with not receiving data, MediaMonkey should: 1. Pause at end of buffer (not loop) 2. Display toast informing user file can't be read |
|
|
lowlander: is the looping state temporary (i.e. when network load is lower, it continues to play file as it should), or is it looping sometimes forever? In case of the latter, there could be some processing deadlock, possibly related to 0020693. Then please use Help - Debug - Send Logs in this looping state and send me crash log, thanks. |
|
|
It can be either, but the network load can be hours long too. For background, I did a clean install with a backup import and it seems playback is more sensitive. However I also moved files to a new NAS and upgraded the network (which actually should've made things better) in the meanwhile. So there have been lots of changes. Still MediaMonkey should not loop, it should either show buffering Toast or network to slow, buffering Toast. |
|
|
Fixed for WASAPI in build 3028. It pauses audio rendering instead of playing silence or looping, also track position should be now correct during this. Buffering toast displayed. MMDS solution postponed, I could not find any working workaround, it is older framework and the looping in case of lack of data is inside this framework hardcoded and cannot be changed. |
|
|
Resolved, so WASAPI fix can be tested in 3028. |
|
|
Verified WASAPI on 3028. |
