xenium wrote: ↑May 16th, 2023, 10:42 am
Thanks for the explanations.
So, those who use Windows 10 and do not want the Spotify logo to be displayed under the cover image, must use version 1.2.0 of the WebNowPlaying plugin.
If you don't care about any of the 2.0.0 features there is no reason not to use 1.2.0 then, yup.
I'll always have the browser extension be backwards compatible !!
Edit: and as of right now, the spicetify extension is only compatible with 1.2.0 or older (even including 0.5.0 and such ofc)
keifufu wrote: ↑May 16th, 2023, 10:45 am
If you don't care about any of the 2.0.0 features there is no reason not to use 1.2.0 then, yup.
I'll always have the browser extension be backwards compatible !!
Edit: and as of right now, the spicetify extension is only compatible with 1.2.0 or older (even including 0.5.0 and such ofc)
keifufu wrote: ↑May 16th, 2023, 6:57 am1.2.0 can only read from Spotify with Spicetify installed.
In 2.0.0 I switched to using Windows' system media controls API. This allows WebNowPlaying to to pick up any player that reports info to windows, not just Spotify.
Like I said, the issue with there being a Spotify logo under the cover image is due to Spotify adding it, on windows 10 specifically, before handing that cover to Windows. You can see this by changing volume to bring up the Windows volume popup where all media being reported to windows is displayed.
Everything about this seems to indicate that it's some sort of Spotify watermark against non Spotify importing of data. This probably changed in (recent?) Windows 11 installments and it may have to do with something like this or related...
