View Issue Details

IDProjectCategoryView StatusLast Update
0020051MMANow Playingpublic2024-02-06 16:08
Reporterrusty Assigned To 
PriorityurgentSeverityminorReproducibilityalways
Status closedResolutionreopened 
Product Version2.0.0 
Target Version2.0.0Fixed in Version2.0.0 
Summary0020051: Performance: Play controls in Playing > Queue
DescriptionPlaying controls in the Playing > Queue perform much worse than in other views. Tapping 'Next' causes:
- the metadata for the newly playing track to appear after about half a second
- the playing list to update after a bit longer than half a second

This can most easily be observed by swiping 'Next' several times in this view.
TagsNo tags attached.
Fixed in build1161

Relationships

related to 0020009 assignedmartin Performance: delay in response to playback controls with consecutive taps (regression) 

Activities

martin

2023-06-08 10:07

developer   ~0072178

Fixed in build 2.0.0.1088

rusty

2023-06-09 16:57

administrator   ~0072195

Last edited: 2023-06-09 17:34

Tested 1088, and performance is much improved, but it is still worse in the Playing queue than in other views. This can be replicated as follows:

1 Navigate to the middle of a playlist and initiate playback (e.g. track 14)
--> Tracks play in Playing > Artwork
2 In Playing > Artwork, press BACK 2x or 3x (depending on how far into the current track playback has proceeded)
--> whenever this is done, the 2nd track back (track 12) plays immediately as expected
3 Switch to the Playing > Queue and press BACK 2x or 3x (depending on how far into the current track playback has proceeded)
--> playback of the 2nd track back is usually delayed by half a second as MMA plays the 1st track back (track 11) for half a second and then plays the 2nd track back (track 10)

martin

2023-06-21 13:57

developer   ~0072256

I think this is only feeling, because Playing > Queue and Playing > Art has and also Playing > Lyrics have same player. There is no difference in command execution and is processed by the same instance UI player.
Because original issue is fixed and this remaining feeling is more related to 0020009. I'm resolving this and I keep only 0020009

martin

2024-01-26 20:09

developer   ~0074147

Fixed in build 2.0.0.1161

peke

2024-02-06 16:08

developer   ~0074208

Verified 1161

Both react same.

Test Note: I screen recorded both screens and compared timings in Video editing app next to each other. Also tested when track is playing (<5s moves two tracks back), when track is playing (>5s moves one tracks back) in playing and paused states.