It is currently September 29th, 2022, 4:43 pm

Does Rainmeter still support Spotify?

Get help with creating, editing & fixing problems with skins
khaldrogo
Posts: 1
Joined: March 23rd, 2021, 5:35 am

Does Rainmeter still support Spotify?

Post by khaldrogo »

Hello !

Recently I've been making awesome-looking desktop and I really wanted to put the Lano Visualizer on my desktop, but it seems not to work anymore with Spotify. I've looked up online for solutions, and saw a lot of people saying it does not support Spotify anymore, is it true or is there any way to make it work again ?

Thanks to everyone who will try to help me!
User avatar
balala
Rainmeter Sage
Posts: 14564
Joined: October 11th, 2010, 6:27 pm
Location: Gheorgheni, Romania

Re: Does Rainmeter still support Spotify?

Post by balala »

khaldrogo wrote: September 15th, 2022, 9:56 am Recently I've been making awesome-looking desktop and I really wanted to put the Lano Visualizer on my desktop, but it seems not to work anymore with Spotify. I've looked up online for solutions, and saw a lot of people saying it does not support Spotify anymore, is it true or is there any way to make it work again ?
The visualizer does work. Not just with Spotify, but with any source. A visualizer skin works no matter of the source of sound. Accordingly the Lano-Visualizer-master\visualizer.ini should work, no matter of the used player. Please check.
What is probably not entirely working is the Song Information part of the skin (the Lano-Visualizer-master\Song Information\Left.ini and Lano-Visualizer-master\Song Information\Right.ini skins). When used with Spotify these skins are using the Spotify plugin, which at least as far as I know, is not supported anymore by the author. But if I'm not wrong, there are some other plugins out there, which work with Spotify. I'm not using Spotify, so am not sure, but I think there is a well-maintained plugin for Spotify. Someone who is using Spotify will be needed here for help, but me at least think there is such a plugin.
Or another possibility is to use the NowPlaying measures. With this kind of measures, the skin will return the title and the artist, but doesn't return the other information (for instance the state of the player). As such, you'll see the artist and the title, but won1t see anything else. Probably not an entirely desirable situation, so you should look for help from someone using Spotify and the newer working Spotify plugin.
User avatar
xenium
Posts: 702
Joined: January 4th, 2018, 9:52 pm

Re: Does Rainmeter still support Spotify?

Post by xenium »

Song Information from Lano Visualizer only displays the name of the song and the artist, so the NowPlaying measure can be used.
Go to Documents\Rainmeter\Skins\LanoVisualizer\@Resources\include, open the MeasureSpotify.inc file and replace the measures [MeasureTrack] and [MeasureArtist] with these:

Code: Select all

[MeasureTrack]
Measure=NowPlaying
PlayerName=Spotify
PlayerType=Title
Substitute="":"#NoTrackNameText#"
UpdateDivider=100

[MeasureArtist]
Measure=NowPlaying
PlayerName=Spotify
PlayerType=Artist
Substitute="":"#NoArtistNameText#"
UpdateDivider=100
Then save, refresh the SongInformation skin and start the song in Spotify
User avatar
balala
Rainmeter Sage
Posts: 14564
Joined: October 11th, 2010, 6:27 pm
Location: Gheorgheni, Romania

Re: Does Rainmeter still support Spotify?

Post by balala »

xenium wrote: September 15th, 2022, 12:45 pm Song Information from Lano Visualizer only displays the name of the song and the artist, so the NowPlaying measure can be used.
I didn't study deeply the code, just saw there are measures which should return further information (for instance I assumed the [MeasureCover] should return the cover, [MeasurePosition] the current position, [MeasureDuration] the duration and finally [MeasureProgressPrecent] the progress of playback). This is why have I said
balala wrote: September 15th, 2022, 12:19 pm the skin will return the title and the artist, but doesn't return the other information (for instance the state of the player).
My bad if I was mistaken. Sorry...