View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020471 | MMW 5 | Casting (Google Cast / UPnP) | public | 2023-12-12 21:20 | 2023-12-22 16:44 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 2024.0 | ||||
| Target Version | 2024.0 | ||||
| Summary | 0020471: Casting to UPnP device stops partway through the track | ||||
| Description | A user is experiencing a bug with MMW 5.1 (but not MMW 4.x) in which casting via DLNA/UPnP to the standalone HiFi audio player stops after some time (e.g. 17sec). The seekbar continues to move forward, but without sound. This works correctly with MM4. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Analyzing the "MM5_PLAYNOW_ALBUM_DLNA_NO_SOUNDSTOP_AFTER_seconds.LOG" MM5 played file D:\data\Uwe\Downloads\BitComet\Ramsey Lewis - Maiden Voyage (1968, Cadet) [LP 24-192]\01 - Maiden Voyage.flac to RS520WiFi as link http://192.168.1.102:10328/TokenID=7ENV57NDKAY1BXTQ And seeing that RS520WiFi gone by itself from Status: PLAYING on RS520WiFi , pos: 16750/287000 ms ** to Status: PAUSED_PLAYBACK on RS520WiFi , pos: 17422/287000 ms ** i.e. it looks like something paused the playback on the RS520WiFi player, but based on the log it was not MM5 that sent the PAUSE command -------------------------------------- In the other log 'MM5_FULL_START_ERROR_STOP.LOG' I also see that the device goes from status PLAYING to status PAUSED_PLAYBACK after 17 seconds of playback, what is particularly strange that the device is not reading the files from MM5 server al all, so it looks like it has the files "cached" and is playing "cached" variants.. |
|
|
I am not in contact with the user (he has not replied my email), ideally if he could open eSupport ticket and assign to me.. Some questions: 1) Does the issue occurs also for tracks added to library -- or only for the non-library tracks? 2) Does it occur for tracks that hasn't been played before, because based on the log the Rose 520 has cached variants of the already played tracks and after the firmware update the cached variants has been shortened to 17 seconds in the Rose 520 cache... |
|
|
Solving via [Ticket # 6645] it was a firewall issue... |
