You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ playerctl -p tidal-hifi metadata
tidal-hifi xesam:title When The World Stopped Moving
tidal-hifi xesam:artist Lizzy McAlpine
tidal-hifi xesam:album Guitar Songs
$ playerctl -p chromium metadata
chromium xesam:album When The World Stopped Moving: The Live EP
chromium xesam:artist Lizzy McAlpine
chromium xesam:title When The World Stopped Moving
Shows "Guitar Songs" (the playlist name) instead of "When The World Stopped Moving: The Live EP" (the album name). As you can see with the second command, the underlying chromium instance reports the correct value, so it should be possible to report the correct value with MPRIS too.
Steps to reproduce:
Open tidal-hifi
Right click on a playlist on the left
Click "Play now" or similar
Observe the incorrect metadata
It seems opening the playlist or album makes it report the correct album name (I assume you scrape it from the HTML page). On the webpage you should have access to the MediaSession API to get access to the album name that is reported by Chromium/Electron: https://developer.mozilla.org/en-US/docs/Web/API/Media_Session_API
Tested with v5.17.0
The text was updated successfully, but these errors were encountered:
Shows "Guitar Songs" (the playlist name) instead of "When The World Stopped Moving: The Live EP" (the album name). As you can see with the second command, the underlying chromium instance reports the correct value, so it should be possible to report the correct value with MPRIS too.
Steps to reproduce:
It seems opening the playlist or album makes it report the correct album name (I assume you scrape it from the HTML page). On the webpage you should have access to the MediaSession API to get access to the album name that is reported by Chromium/Electron: https://developer.mozilla.org/en-US/docs/Web/API/Media_Session_API
Tested with v5.17.0
The text was updated successfully, but these errors were encountered: