View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016595 | MMW 5 | General | public | 2020-05-11 16:16 | 2022-07-19 12:57 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | unable to reproduce |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0.3 | Fixed in Version | 5.0.3 | ||
| Summary | 0016595: Issues when playing to Raspberry DLNA client | ||||
| Description | Debugging with user via RNZ-952-82555 where MM4 is casting to his Raspberry client and the Respberry skips some songs randomly (reads 130 KB and then reports transport status STOPPED). When this happens MM4 should cast the next song in the queue. Currently the playback just stops entirelly. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2600 | ||||
|
|
Fixed in 4.1.29.1906 and merged to 5.0.0.2248 |
|
|
Fix confirmed via RNZ-952-82555 |
|
|
Verified 1906 and 2250 No regressions found on other devices. |
|
|
Based on log [Ticket # 3332] this can still happen with Respberry. Very similar steps to repro, it can happen after track skip (initiated manually using Next in MM5). Details+logs in [Ticket # 3332] Moving to MM5 to fix this for 5.0.3 |
|
|
Fixed in 5.0.3.2600 |
|
|
Re-opened: Based on the new logs from ticket [Ticket # 3332] the 'Raspberry' device is specific and sends messages for the PREVIOUS track while the CURRENT track is already playing. This confuses MM5 and can result in skips OR playback stop. To be workarounded somehow. |
|
|
I implemented the workaround and shared new testing EXE with the user via ticket [Ticket # 3332] to confirm. Note that the same workaround should work also for the Onkyo's issue ([Ticket # 3309] -- but the user is not willing to test/debug further). Fixed in 5.0.3.2600 |
|
|
Verified 2615 Raspberry Pi 3 |
