Latest WACUP public preview for x86 & x64 is build #21136 (March 9th 2025) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #21254 (March 29th 2025) (x86 & x64 changelogs)


NOTE: Beta testers are added in a limited & subjective manner as I can only support so many people as part of the beta test program to keep it useful for my needs.

Unless I think you're going to be helpful, not all requests will be accepted but might still be later on. Remember that beta testing is to help me & the limitations currently works for my needs for this project.

Author Topic: ATF support for Last.fm scrobble fields  (Read 242 times)

obli

  • Newbie
  • *
  • Posts: 3
    • View Profile
    • poop.pics
ATF support for Last.fm scrobble fields
« on: March 25, 2025, 09:04:14 AM »
Hello!
Would love to see ATF support for Last.fm scrobbling, hopefully similar to the preferences available for Discord's Rich Text Presence, because it does not seem like there's a way for me to solve multi-artist tracks scrobbling each artist as a single combined artist without removing tag information (unless I'm missing something... :-[).
Thanks for all of your work!  :)

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 4939
    • View Profile
    • WACUP (Winamp Community Update Project)
Re: ATF support for Last.fm scrobble fields
« Reply #1 on: March 25, 2025, 11:56:35 AM »
Can you give me an example of the issue? As I'm not sure how adding ATF support would help since that in itself would be relying on title, artist & optionally track, album & albumartist metadata being right to start with unless it's about splitting multi-part values (on artist & albumartist I assume) & if so it might be simpler to have a mode that just tries to get the first value up to a comma or a slash vs ATF overhead.

obli

  • Newbie
  • *
  • Posts: 3
    • View Profile
    • poop.pics
Re: ATF support for Last.fm scrobble fields
« Reply #2 on: March 25, 2025, 03:04:14 PM »
Ah! Gosh, you're right. I realize now that my issue is the artist field doesn't separate each artist with a comma if the file uses multiple artist fields in the metadata. Could there be a way to have that function as so? Apologies for the confusion!

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 4939
    • View Profile
    • WACUP (Winamp Community Update Project)
Re: ATF support for Last.fm scrobble fields
« Reply #3 on: March 25, 2025, 07:27:18 PM »
Would you expect the first 'artist' to be used in that instance? I'm not sure without looking into it what last.fm is doing with possible multiple artists for a song. I'd also need to look into what's going on with the tag reading library I'm using to see what it can do or what I'll need to do with the provided string from it.

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 4939
    • View Profile
    • WACUP (Winamp Community Update Project)
Re: ATF support for Last.fm scrobble fields
« Reply #4 on: March 26, 2025, 04:01:52 PM »
For the next build I've changed the string I'm getting back from the metadata reading library to use commas instead of spaces if it needs to combine duplicate fields together which I hope will do what you're wanting (i.e. acting like the left of the example image instead of the right). This will require a local library refresh to be done for the change to be seen if using any files known to that part.
« Last Edit: March 26, 2025, 04:03:20 PM by dro »

obli

  • Newbie
  • *
  • Posts: 3
    • View Profile
    • poop.pics
Re: ATF support for Last.fm scrobble fields
« Reply #5 on: March 26, 2025, 05:01:34 PM »
Awesome! Thank you! Exactly what I was hoping for so long as there's a space after the comma like "Artist, Artist, Artist".