View Issue Details

IDProjectCategoryView StatusLast Update
0014149MMW v4DLNA/UPnPpublic2017-04-02 02:11
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version4.1 
Target Version4.1.16Fixed in Version4.1.16 
Summary0014149: UPnP: Playback anomalies when 'Continuous' is enabled in MMW
DescriptionIf MMA is casting via UPnP to MMW, and MMW has 'Continuous playback' enabled, then the currently playing track always repeats unless the user presses 'next'.
Steps To Reproduce1 Play Playlist 1 consisting of tracks 1-10
--> 'track 1' plays
2 Press 'Next'
--> 'track 2' plays
3 Wait for track 2 to end
--> Track 2 starts playing again instead of advancing to 'track 3'!
4 Enable 'Repeat Track' in MMA
--> At conclusion of 'Track 3', Track 3 repeats
5 Enable 'Repeat Playlist' in MMA
--> At conclusion of 'Track 3', Track 3 repeats instead of starting over!
TagsNo tags attached.
Fixed in build1832

Activities

martin

2017-03-28 10:23

developer   ~0047642

Yes 'Continuous playback' should be controlled on MMA side only, because only current track is casting (not all tracklist) and when 'Continuous' is enabled in MMW, then really the currently playing track always repeats, because no next track is available in Now Playing list.
Same behavior with Bubble UPnP.

Ludek

2017-03-29 15:05

developer   ~0047674

I haven't tested this scenario yet, but in this scenario 'Now playing list' is maintained by MMA -- so I guess that there is no need to repeat track 3 once there is another track to advance (in the Rusty's case 4 of 10) ?

Ludek

2017-03-29 15:18

developer   ~0047675

Last edited: 2017-03-29 17:53

Nevertheless testing casting from WMP, Bubble and MMA and in all cases the track is repeated -- so Martin seems to be true.

The control-points are waiting for MMW to stop playback of the active track (which doesn't happen in case the Continuous is ON)

Assigned to me to tweak this on MMW side (to supress continuous when casting)

Ludek

2017-03-29 19:24

developer   ~0047676

Fixed in 4.1.16.1832 and merged to 5.0

peke

2017-04-01 01:10

developer   ~0047701

Verified 1832