FYI: Matching process has been improved a lot in build 2256 (posted today)

This time the script will be updated automatically during install of 2256

FYI: I have moved the script from /sampleScripts directly to /Scripts (to be pre-installed) for the next build so all will be updated automatically starting from 2256.

Thx.

Update: just reinstalled beta 5.0.0.2255 in portable mode and restarted fine. Afterwards I've added spotify.mmip from /SampleScripts and Spotify or better the playlists now sync properly.

cu,
Michael

Hi,

It is really hard and complicated to update a JS file if you don't know where this is located or where it should be placed, e.g. in /helpers or in Scripts/spotify/helpers/

This get's more annoying if MM5 crashes each time when it starts and is serching for the file cloudServices_add.js or cloudServices.js. I bet I've seen both files in crash logs the last 10 minutes.
If MM5 crashes and crashes again, even while or after sending the log files and restarting in safe mode also does not work, I could start crying :cry:

I've now manually delete the spotify subfolder from /Scripts and removed cloudServices_add.js from folder ./helpers and tried a restart - no luck either MM5 still tries to load /herlpers/cloudServices.js.

So I've manually downloaded a file from [url]https://www.dropbox.com/s/sksdz39bzvw00d5/cloudServices_add.js?dl=0[/url] and saved it to ./helpers again. However, the file from Dropbox reads cloudServices_add.js and MM5 complaints about cloudServices.js This is driving me nuts, you know ^^ so I renamed this one and started MM5 again.

Next crash happens because MM5 now cannot set any property 'spotify'... see log files just sent in...and once again I'm caught in a crash loop that I can only exit with the help of Windows Task Manager.

With other words I gave up now: how can I safely remove all occurrences of Spotify plugin to start over?

Hi Michael (Zonky),
I see crash A04C382A in 2255 from you here.

This is because you haven't updated the Spotify script (in the 2255 install folder /sampleScripts/spotify.mmip )
Please re-install the script by the version from 2255 and it will no longer crash for you

Fixed with this cloudServices_add.js : https://www.dropbox.com/s/sksdz39bzvw00d5/cloudServices_add.js?dl=0

Will be in 2251: https://www.ventismedia.com/mantis/view.php?id=16521#c57753

Thx, I see, the problem is with this playlist: https://open.spotify.com/playlist/4173ENNA5eMzHrz9pipvxI
It is broken and includes items with track value null, I'll workaround it. Thx.

[quote=Ludek post_id=468499 time=1590067016 user_id=7319]
It fixes the issue...
[/quote]

Unfortunately no :( See subsequent logs and last one: A04CA4BC

Michael

Thanks, try with this cloudServices_add.js : https://www.dropbox.com/s/dg0i3bckqfp5lxw/cloudServices_add.js?dl=0

It fixes the issue, will be in 2251: https://www.ventismedia.com/mantis/view.php?id=16521#c57753

Done and some crash logs sent. e.g. FF31B1D8.

Unfortunately, right after sending the crash reports, MM5 is behaving a little weired. One crash after another happens and there is no chance to quit MM5 unless stopping multiple processes with the help of Windows Task-Manager.

cu,
Michael

[quote=Zonky post_id=468444 time=1590001699 user_id=38131]
I've send some crash logs, the most recent was ID C491F22F

I was about to sync my Spotify playlist to MM5 database. This action crashed various times including the above.

Michael
[/quote]


Hi, I saw your crash logs C491F22F yeasterday when checking logs from 2250.
But I needed to add more debug info to see why it is happening for you.

Please replace your current /scripts/spotify/helpers/cloudServices_add.js by this one: https://www.dropbox.com/s/8gjmidw2vr37qnx/cloudServices_add.js?dl=0
and submit new crash log, thanks!

[quote=Ludek post_id=467767 time=1588537560 user_id=7319]
As for the matching: yes, this will need some more tuning and certainly will never be 100% accurate. I am afraid that matching just based on artist/title (without comparing album) could result in false matches which is probably even worse case. Probably just some tuning like removing the " (remastered)" appendix when comparing could be enough.
[/quote]

I think that matching on just artist/title would be OK as a second pass. ... ie. first attempt match on full artist|album|track, and then try to find matches for those which failed, on just artist & title.

I've send some crash logs, the most recent was ID C491F22F

I was about to sync my Spotify playlist to MM5 database. This action crashed various times including the above.

Michael

Yes, I imagine it would. As you say, being able to match the album title more loosely would work - I also notice sometimes this happens with titles that have 'remastered' attached them, and really is just the labels that release the music being too specific!

Again, I have no idea what is possible in regards to coding, but would a possible function being able to match them purposely? That is, to "right click" a song in Spotify and than select an option to match it with a local file?

Will install your script update and continue playing. Many thanks, I really like where this extension is going! :)

Hi, thanks for trying.

BTW: There is already a new version of the script that supports also MM5 > Spotify playlists sync, i.e. supports exporting MM library playlists to Spotify.
You need to install the newest beta build 2245 and the script is within the /SampleScripts/Spotify.mmip available to install as extension.

As for the matching: yes, this will need some more tuning and certainly will never be 100% accurate. I am afraid that matching just based on artist/title (without comparing album) could result in false matches which is probably even worse case. Probably just some tuning like removing the " (remastered)" appendix when comparing could be enough.