You are probably using the version LeVvE and i used for debugging, as it has gotten 5 downloads. I removed it to avoid any further misunderstanding. Always download from the first post in the thread.Dimbadboy wrote:Hello,
Excuse me but is there a way to remove the file "log.txt", which appears on the desktop? Thanks in advance.
PS: Everything else is working fine.
It is currently April 23rd, 2024, 6:03 am
Spotify Plugin Released! Now with less bugs!
-
.raptor
- Posts: 220
- Joined: April 3rd, 2013, 11:03 pm
- Location: Norway
Re: Spotify Plugin Released!
-
Dimbadboy
- Posts: 4
- Joined: June 25th, 2014, 5:24 pm
Re: Spotify Plugin Released!
Thanks very much. Now everything is working normaly. 
-
borsTiHD
- Posts: 7
- Joined: June 27th, 2014, 8:09 am
Re: Spotify Plugin Released!
Hi .raptor,
I hope you could help me.
I'm using Spotify and I've tried many player skins, but every skin didn't worked with all options, because they're using the "now playing" plugin.
Now I was hoping that your plugin could help me out of it.
But how could I use this?
For example, I'm using the CLN skin.
The position for the cover looks like this:
I tried a few thinks, from simply copy and paste your example (from the first post)... till to try a few other thinks like this:
Is there a way I could use your plugin with the skin?
Thanks
I hope you could help me.
I'm using Spotify and I've tried many player skins, but every skin didn't worked with all options, because they're using the "now playing" plugin.
Now I was hoping that your plugin could help me out of it.
But how could I use this?
For example, I'm using the CLN skin.
The position for the cover looks like this:
Thanks
-
.raptor
- Posts: 220
- Joined: April 3rd, 2013, 11:03 pm
- Location: Norway
Re: Spotify Plugin Released!
borsTiHD wrote:Hi .raptor,
I hope you could help me.
I'm using Spotify and I've tried many player skins, but every skin didn't worked with all options, because they're using the "now playing" plugin.
Now I was hoping that your plugin could help me out of it.
But how could I use this?
For example, I'm using the CLN skin.
The position for the cover looks like this:
I tried a few thinks, from simply copy and paste your example (from the first post)... till to try a few other thinks like this:
Is there a way I could use your plugin with the skin?
Thanks
Remember that you should always edit the measure when you are changing plugins or plugin options. The meter is just for styling and positioning.
-
borsTiHD
- Posts: 7
- Joined: June 27th, 2014, 8:09 am
Re: Spotify Plugin Released!
Thank you, this works. 
Ok... at least half.
The cover works fine... this is sooo awesome.
But the rest (Track, Interpret, Time etc.) only says "0".
Is there a way to use both plugins, or do I have to change the complete skin?
Because I don't know how... the skin uses the "now playing" plugin on so many places.
But I think everything is based of the [MeasurePlayer] part.
Could you please help me with that?
This is the first time for something like that.
I only edit skins (other images, strech some parts, edit fonts, etc. just simple things).
Here is the complete skin:
Ok... at least half.
The cover works fine... this is sooo awesome.
But the rest (Track, Interpret, Time etc.) only says "0".
Is there a way to use both plugins, or do I have to change the complete skin?
Because I don't know how... the skin uses the "now playing" plugin on so many places.
But I think everything is based of the [MeasurePlayer] part.
Could you please help me with that?
This is the first time for something like that.
I only edit skins (other images, strech some parts, edit fonts, etc. just simple things).
Here is the complete skin:
-
VasTex
- Posts: 407
- Joined: September 20th, 2012, 3:17 pm
- Location: USA - Montana
Re: Spotify Plugin Released!
I'm just going to throw this out there.
The skin you're having issues with is both old and outdated. It also has several features specific to other, fully supported media players using the NowPlaying Plugin. Because of this there is no way that this skin will ever fully work with the Spotify Plugin that Raptor is developing. Spotify, as far as I know, lacks most of the functionality of the other media players. You can play/pause, go to the next or previous songs and stop them as well, but you can't control the volume of Spotify or the track progression.
The skin you're using is 80% made up of meters and measures that handle options that Spotify may not ever be able to handle. On a side note, the code you posted is incomplete. The skin you're using requires variables and styles from other files and without them the code you posted is more or less useless to us since all I get when running it are two sets of very small, plain 0:00's.
Long story short, your skin is old, still works with most major media players, but if you want something that truly works well with the Spotify Plugin from Raptor then you're going to need to just start over or get a brand new skin altogether.
The skin you're having issues with is both old and outdated. It also has several features specific to other, fully supported media players using the NowPlaying Plugin. Because of this there is no way that this skin will ever fully work with the Spotify Plugin that Raptor is developing. Spotify, as far as I know, lacks most of the functionality of the other media players. You can play/pause, go to the next or previous songs and stop them as well, but you can't control the volume of Spotify or the track progression.
The skin you're using is 80% made up of meters and measures that handle options that Spotify may not ever be able to handle. On a side note, the code you posted is incomplete. The skin you're using requires variables and styles from other files and without them the code you posted is more or less useless to us since all I get when running it are two sets of very small, plain 0:00's.
Long story short, your skin is old, still works with most major media players, but if you want something that truly works well with the Spotify Plugin from Raptor then you're going to need to just start over or get a brand new skin altogether.
01010100 01100101 01100011 01101000 01101110 01101111 01101100 01101111 01100111 01101001
01100011 01100001 01101100 00100000 01000010 01100001 01100100 01100001 01110011 01110011
01100011 01100001 01101100 00100000 01000010 01100001 01100100 01100001 01110011 01110011
-
borsTiHD
- Posts: 7
- Joined: June 27th, 2014, 8:09 am
Re: Spotify Plugin Released!
Yeah, I understand.
I dont' want that all from the skin should work, or in other words, I can live with that.
At the moment, with the "now playing" plugin, the skin works for the track, interpret, play/pause and also the next or previous buttons.
If the covers would also show up, I would really love it.
Or... are there already finished skins for .raptor's plugin, or skins that are supporting his plugin?
€dit:
Oh and sorry, I looked in the folder from the skin and found another config.
Here is the skin: http://toastbrotpascal.deviantart.com/art/CLN-216978446
I dont' want that all from the skin should work, or in other words, I can live with that.
At the moment, with the "now playing" plugin, the skin works for the track, interpret, play/pause and also the next or previous buttons.
If the covers would also show up, I would really love it.
Or... are there already finished skins for .raptor's plugin, or skins that are supporting his plugin?
€dit:
Oh and sorry, I looked in the folder from the skin and found another config.
Here is the skin: http://toastbrotpascal.deviantart.com/art/CLN-216978446
-
.raptor
- Posts: 220
- Joined: April 3rd, 2013, 11:03 pm
- Location: Norway
Re: Spotify Plugin Released!
Well, VasTex pretty much said everything that could be said about the subject. Volume and Track search is currently not possible. Track info, album art and progression is still available tho.
If you need info on how a working skin implements this plugin, i have a Soita.zip in here somewhere, you should be able to use it as a reference.
If you need info on how a working skin implements this plugin, i have a Soita.zip in here somewhere, you should be able to use it as a reference.
-
VasTex
- Posts: 407
- Joined: September 20th, 2012, 3:17 pm
- Location: USA - Montana
Re: Spotify Plugin Released!
Alright,
So I've been using this plugin for a few days and have been playing around with a skin of mine trying to work out all the kinks and I have a few questions / suggestions. For starters, the majority of the time everything works really well which is very impressive and I really appreciate the time you've put in to get this working properly. However I've noticed a few minor issues and I'll list them below and describe them as best I can.
Issue 1: This is probably the smallest issue, but I've had a problem where the Album artwork refused to update. It wasn't an issue with my skin as I was watching the folder that the image was stored in and made sure that the only measure / meter running were the ones pulling the image. This has only happened once, but I was unable to fix the issue until I exited from Rainmeter completely and restarted it. I've yet to have an issue regarding this since.
Issue 2: This isn't that important as I managed to get around it fairly easy, but it seems that the default image path gathered by using the Type=AlbumArt is set to C:\...\Default.jpg when in reality the image placed there is actually called cover.jpg and not default.jpg. Thus when trying to use the measure in question for the ImageName parameter of an image meter it fails to grab the right image. It's sent looking for C:\...\Default.jpg when in reality it finds C:\...\cover.jpg and fails. Perhaps this is just a type-o / oversight or have I misunderstood the parameter?
Issue 3: This is probably my biggest concern when it comes to this plugin and it's the fact that, while using it, Rainmeter as a whole tends to lag noticeably. Unloading the skin allows Rainmeter and my other skins to update properly, but while the skin using this plugin is activated it becomes very apparent that every time information is pulled from Spotify it causes Rainmeter to lag. My skins update rate is set to 1000 and thus Rainmeter lags roughly every second. Increasing the update rate of the skin or the measures using your plugin directly effects the rate at which Rainmeter lags. Perhaps it's a performance issue with the plugin. You might consider attempting to thread the plugin across the cores of the CPU to lighten the load.
Suggestion 1: This may simply be a limitation of Spotify or it may be an issue with the plugin, but the track progress is read as a percentage in full percent increments. What I mean is that it steps from 0 to 100% by increments of 1 like 3,4,5,6,7,8,9%. I'm curious, would it be possible to have it represent the exact percentage? Such that it would increase more or less like 1,1.1,1.22,1.35%, etc? I understand it may simply be a stylistic choice in that 1,2,3 looks better than 1.3, 2.12, 3.44, but you could, I assume, add an option to the progress measures like Truncate=1 for example. While Truncate=1 (Default) the progress would increment as it does now (1,2,3,4,5), but when Truncate=0 it could increment in exact steps (1.12, 1.44, 2.39, 3.77, etc). I only ask because of a method I've developed to use your plugin to show current track progress as time and not as a percent. It would allow me to be more accurate if I had a more accurate percentage.
Suggestion 2: I think it would be helpful if the plugin stored the current album artwork in the folder containing the skin using the plugin. It's somewhat disheartening, although not deal breaking, for me to see that it must store the artwork in a new folder without regards to the skin running it. I suppose it's easier to send it to a static folder and simply create that folder if it doesn't exist as opposed to trying to send the file to the containing skin folder, but I think it would be a nice touch if that was possible.
All in all this is a very nice plugin and I hope to see it developed to a point where it becomes as robust and resource friendly as the other, officially supported, plugins for Rainmeter.
Because I'm sure you'll want to know here are my System, Rainmeter and Plugin Specs: *Please note the issues above are present on both machines.
Home PC
Windows 8.1 64bit
Rainmeter 3.1 (r2290) 64bit
Spotify Plugin by Raptor 64bit
Work PC
Windows 7 Enterprise (SP1) 64bit
Rainmeter 3.1 (r2290) 64bit
Spotify Plugin by Raptor 64bit
Please let me know if there's anything I can do to help out or if you have any additional questions for me. Looking forward to an update! Thanks again.
So I've been using this plugin for a few days and have been playing around with a skin of mine trying to work out all the kinks and I have a few questions / suggestions. For starters, the majority of the time everything works really well which is very impressive and I really appreciate the time you've put in to get this working properly. However I've noticed a few minor issues and I'll list them below and describe them as best I can.
Issue 1: This is probably the smallest issue, but I've had a problem where the Album artwork refused to update. It wasn't an issue with my skin as I was watching the folder that the image was stored in and made sure that the only measure / meter running were the ones pulling the image. This has only happened once, but I was unable to fix the issue until I exited from Rainmeter completely and restarted it. I've yet to have an issue regarding this since.
Issue 2: This isn't that important as I managed to get around it fairly easy, but it seems that the default image path gathered by using the Type=AlbumArt is set to C:\...\Default.jpg when in reality the image placed there is actually called cover.jpg and not default.jpg. Thus when trying to use the measure in question for the ImageName parameter of an image meter it fails to grab the right image. It's sent looking for C:\...\Default.jpg when in reality it finds C:\...\cover.jpg and fails. Perhaps this is just a type-o / oversight or have I misunderstood the parameter?
Issue 3: This is probably my biggest concern when it comes to this plugin and it's the fact that, while using it, Rainmeter as a whole tends to lag noticeably. Unloading the skin allows Rainmeter and my other skins to update properly, but while the skin using this plugin is activated it becomes very apparent that every time information is pulled from Spotify it causes Rainmeter to lag. My skins update rate is set to 1000 and thus Rainmeter lags roughly every second. Increasing the update rate of the skin or the measures using your plugin directly effects the rate at which Rainmeter lags. Perhaps it's a performance issue with the plugin. You might consider attempting to thread the plugin across the cores of the CPU to lighten the load.
Suggestion 1: This may simply be a limitation of Spotify or it may be an issue with the plugin, but the track progress is read as a percentage in full percent increments. What I mean is that it steps from 0 to 100% by increments of 1 like 3,4,5,6,7,8,9%. I'm curious, would it be possible to have it represent the exact percentage? Such that it would increase more or less like 1,1.1,1.22,1.35%, etc? I understand it may simply be a stylistic choice in that 1,2,3 looks better than 1.3, 2.12, 3.44, but you could, I assume, add an option to the progress measures like Truncate=1 for example. While Truncate=1 (Default) the progress would increment as it does now (1,2,3,4,5), but when Truncate=0 it could increment in exact steps (1.12, 1.44, 2.39, 3.77, etc). I only ask because of a method I've developed to use your plugin to show current track progress as time and not as a percent. It would allow me to be more accurate if I had a more accurate percentage.
Suggestion 2: I think it would be helpful if the plugin stored the current album artwork in the folder containing the skin using the plugin. It's somewhat disheartening, although not deal breaking, for me to see that it must store the artwork in a new folder without regards to the skin running it. I suppose it's easier to send it to a static folder and simply create that folder if it doesn't exist as opposed to trying to send the file to the containing skin folder, but I think it would be a nice touch if that was possible.
All in all this is a very nice plugin and I hope to see it developed to a point where it becomes as robust and resource friendly as the other, officially supported, plugins for Rainmeter.
Because I'm sure you'll want to know here are my System, Rainmeter and Plugin Specs: *Please note the issues above are present on both machines.
Home PC
Windows 8.1 64bit
Rainmeter 3.1 (r2290) 64bit
Spotify Plugin by Raptor 64bit
Work PC
Windows 7 Enterprise (SP1) 64bit
Rainmeter 3.1 (r2290) 64bit
Spotify Plugin by Raptor 64bit
Please let me know if there's anything I can do to help out or if you have any additional questions for me. Looking forward to an update! Thanks again.
01010100 01100101 01100011 01101000 01101110 01101111 01101100 01101111 01100111 01101001
01100011 01100001 01101100 00100000 01000010 01100001 01100100 01100001 01110011 01110011
01100011 01100001 01101100 00100000 01000010 01100001 01100100 01100001 01110011 01110011
-
LeVvE
- Posts: 50
- Joined: June 20th, 2014, 6:15 pm
Re: Spotify Plugin Released!
I had this a few times but I "fixed" it by adding:VasTex wrote:Issue 1: This is probably the smallest issue, but I've had a problem where the Album artwork refused to update. It wasn't an issue with my skin as I was watching the folder that the image was stored in and made sure that the only measure / meter running were the ones pulling the image. This has only happened once, but I was unable to fix the issue until I exited from Rainmeter completely and restarted it. I've yet to have an issue regarding this since.
[Rainmeter]
RightMouseUpAction=!Refresh <Skin name here>
Rightclick the skin and it will load all the data and also a new album cover.
With your other issue, Rainmeter only acted slow for me running with this plguin if my internet was down, otherwise I have no issue with any slowness.
What I've found is that if you pause music and don't start it for a while the skin will have to be refreshed but if you're listening to music all the time there is no problem.
Also looking to a problem I have with Spotify atm if its related to this plugin but my Spotify uses more and more memory the longer it is running. Probably a memory leak but after running for 24ish hours my Spotify uses over 1.5GB of memory.
Running without the skin using the plugin just to see if its the same.