Bug 427397 - Media Player unsynced
Summary: Media Player unsynced
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: Media Player widget (show other bugs)
Version: master
Platform: Neon Linux
: NOR minor
Target Milestone: 1.0
Assignee: Kai Uwe Broulik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-06 18:53 UTC by matheus.epstein
Modified: 2021-05-22 12:43 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description matheus.epstein 2020-10-06 18:53:50 UTC
SUMMARY
My Media Player when I play a Spotify song and open the media player it gets unsynced. For EX: I start playing a song on Spotify 46 seconds in but the Media Player only starts counting the time when I open it so the time would say 0:00 then it would start counting up.

STEPS TO REPRODUCE
1. Play a Song
2. Open the Media Player

OBSERVED RESULT
Song times unsynced.

EXPECTED RESULT
Song times match and continue to match until next song.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Neon
(available in About System)
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION
Comment 1 Simon Foglein 2021-05-14 15:00:54 UTC
I can confirm this issue, but I'm pretty sure this is not a KDE bug. VLC, for example, works fine, the media controller applet shows the time correctly. It seems to me that for some reason, Spotify resets the time counter. If you play a song in Spotify and then run "playerctl position" several times in Konsole, it only shows a few milliseconds even if your song has been playing for minutes. Also, the value doesn't necessarily increase. With VLC, however, the same command outputs the correct time in seconds. This may be because Spotify is missing a time property (see "playerctl metadata").
All in all, this bug is most likely in the Spotify app itself, not the Plasma media controller applet.
Comment 2 Nicolas Fella 2021-05-22 12:43:21 UTC
This is indeed a known issue with Spotify's MPRIS integration. You can find plenty of reports for this on Spotify's community page: https://community.spotify.com/t5/forums/searchpage/tab/message?q=mpris