Quote from: regor on 2024-02-16 12:28:14

That's probably the problem. The version I put at the readme works. But it's 64 bit.

Have you tried this? 21.6 should be more similar to 22.7 than the one you got xd
https://www.npackd.org/p/org.miktex.MiKTeX/21.6

EDIT: you can also try any other LaTeX suite, is just that I recommend that one because I have tested it and works from win 11 to win7 in 64 bits oses. But feel free to try other latex installations (and adjust the CMD at the settings if needed). Can not test LaTeX on Wine 32 bits, sorry. And again, nothing stops you to manually compile it with any LaTeX editor (or wait for my html version).

Great sucess!!!!

the version you pointed out works

[attach type=thumb]29057[/attach]

Various artists have a huge advantage, maybe could be interesting more focus in the artist tag.....

That's what testing is for hahahaha

I don't use a "various artists" value as an artist, but it's just a matter of skipping it. I can add a filter for specific artist like this then.

Will add that version to the readme for 32 bit builds too.

EDIT: going to update all repositories now (with the fixes from this thread), I would appreciate if you update them and report problems you found on other scripts in their threads. In case they persist.

Quote from: regor on 2024-02-18 20:05:07

That's what testing is for hahahaha

I don't use a "various artists" value as an artist, but it's just a matter of skipping it. I can add a filter for specific artist like this then.

Will add that version to the readme for 32 bit builds too.

EDIT: going to update all repositories now (with the fixes from this thread), I would appreciate if you update them and report problems you found on other scripts in their threads. In case they persist.

Various artists are from the album artist tag, in my tags there is no single various in artist. Is very noticeable because this little time of 2024 I listen to a lot of BSO and label compilation and the artists was very varied, but the album artists are always various artists and soundtracks or label name as grouping. Only Angelo Badalamenti can enter the top, thanks to David Lynch's films.

I'll give it a try tomorrow at the new builds. Hope that it will include the artist instead of album artists to see the difference

No, but there will be the possibility to remap artist to %ARTIST% instead of %ALBUM ARTIST%. I can not offer a single setting for everybody, I don't use album artist tag to group various artists albums, and just substituting as you said would break the scrip for others.

(I prefer to use TF to group various artists albums dynamically on the album list)

Genre can already be remapped to style, so I don't understand your request.

I want to be able to merge multiple tags (genre + style) but that requires a rewrite of the statistics framework which was initially thought for one tag per axis (timeline script).
EDIT: will be possible as long as you separate tags by ', ': '%GENRE%, %STYLE%'

Already noticed the problem with title duplication for different artists, which again requires a rewrite.

About your last concern, what do you mean by duplicates? Show an example. The online version just uses whatever ListenBrainz reports.

Edit 2: Is so good that it predict the song of March XD. I didn't notice that, in the artist graph, some have highlighted March instead of February

Edit: Out of context question, how do you put the description when you insert a thumbnail in the forum?

The playlist have 90 items, after removing the duplicates 31. Is only in suggested artists, the rest of playlist seems fine, in fact very good.

"getEntitiesByTag: 400 {"code":400,"error":"multiple tags are specified but the condition param is missing"}" . Not sure if it was there before but the pdf is produced and the playlist too.

Quote

Edit 2: Is so good that it predict the song of March XD. I didn't notice that, in the artist graph, some have highlighted March instead of February

xd ok, just noticed it too. It's one month less, so it's January and February.

Quote

Edit: Out of context question, how do you put the description when you insert a thumbnail in the forum?

I just attach them to the post, but I don't insert it into the text though

Quote

The playlist have 90 items, after removing the duplicates 31. Is only in suggested artists, the rest of playlist seems fine, in fact very good.

Have to investigate it, since that playlist is generated with ListenBrainz suggestions using the data I retrieve, and never had so many duplicates (I will also deduplicate it anyway on next updates).
Fixed.

Quote

"getEntitiesByTag: 400 {"code":400,"error":"multiple tags are specified but the condition param is missing"}" . Not sure if it was there before but the pdf is produced and the playlist too.

That doesn't make any sense on the current code an looks to me an API error on the server, since the param is always present.

I made one report from 2023 and the most listened track was "untitled" with 29, that seems to integrate all untitled songs from every artist.

This happens as well with typical title like "movement",  "part", etc and in general with all songs with the same title from different artists.

EDIT: will be possible as long as you separate tags by ', ': '%GENRE%, %STYLE%'

All points should now be fixed on the latest commit.

Quote

I made one report from 2023 and the most listened track was "untitled" with 29, that seems to integrate all untitled songs from every artist.

This happens as well with typical title like "movement",  "part", etc and in general with all songs with the same title from different artists.

Including this one. With duplicated titles being assigned to different artists internally (please check this one, since I have not been able to test it properly).

Quote

EDIT: will be possible as long as you separate tags by ', ': '%GENRE%, %STYLE%'

And this is now possible.

Wrapped: retrieving images...
lookupArtistMBIDsByName: Retrying request for  to server on 500 ms...
search: 400 {
  "error" : {
    "status" : 400,
    "message" : "No search query"
  }
}
search: 400 {
  "error" : {
    "status" : 400,
    "message" : "No search query"
  }
}
lookupArtistMBIDsByName: 400 {"help":"For usage, please see: https://musicbrainz.org/development/mmd","error":"The given parameters do not match any available query type for the artist resource."}
lookupArtistMBIDsByName: 1 artists (1 failed)
Wrapped: processing track images with nconvert.exe

Not going to fix user errors while tagging their files but glad you finally sorted it out.

Also if an entire album has all their tracks tagged with the same title... then... xd just use the global filter to remove it. Can not account for it unless I force people to tag all their tracks with picard to get unique musicbrainz ids. I could offer a setting to switch between tittle or ids though.

Do you have tracks without artist? That's weird.

.\main\spotify\wrapped.js
Go to line 49 and set bDebug to true.

And paste the log here.

You say all have artists.. but the log clearly states there are tracks without %ARTIST% tag.

Check the track Through Abraxas III

The photo is whatever Spotify has.

The report does not necessarily has to match last.fm or listenbrainz stats, since you can also filter the listens by query. By default it filters tracks rated with 1 or 2 stars, since they don't give any interesting info. But all that is up to you and your settings. People can change the filter or tags to whatever they want.

About the 20 jun data, that's something you will have to investigate yourself xd using %played_times% I suppose and some TF expression to check for 20023-06-20- Maybe you played a track multiple times but not fully, so the playcount was increased...

Will also add support for https://marc2k3.github.io/foo_playcount_2003/ plugin, now that it also offers the played times (and they can be edited).

The script currently takes times from:
- LASTFM_PLAYED_TIMES
- PLAYED_TIMES

And merges them (it may well be that I forgot to deduplicate this step, and therefore you have double times for everything). Since I don't use last.fm I never experienced this problem. Please post here the tag values for such track so I can check.

If those 2 return nothing then..
- LAST_PLAYED_ENHANCED
- FIRST_PLAYED_ENHANCED

And checks if the first and last played fall in the checked range, in such case it adds fake listens starting with the first listen date and then repeats the last played date until it reaches the total playcount. This was done to get something for tracks which were logged with foo_playcount but not with the enhanced version.

Now... it could be that case, and therefore it added all plays to the 20 jun date.

The algorithm was coded before I created wrapped, and the aim was just playlist creation so It was irrelevant... but now that dates are needed, I could fake those listens and space out the dates in a random way.