You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm curious if pairing the data source with a submitted song is possible? I have a rather idiosyncratic setup, but it would be simplified so much if I could split data by source.
I have 2 last.fm accounts, one for logging absolutely everything, and a second for logging everything I listen to outside of Apple Music. This can be from Web Scrobbler or Finale. The goal of splitting my data in this way is to make it so I can import the listening I do outside of Apple Music into my Apple Music library. If I didn't split the data, I'd be creating a recursive loop of reimporting songs I already have in my library.
To do the syncing between the 2 accounts, this is where I use libre.fm. I log the plays to it, then sync those to my second last.fm account. For Spotify, since it allows multiple app integrations, I can log plays directly to the second account.
I use SongShift to do the importing of my tracks to Apple Music. It has the ability to pull the 100 Recently Scrobbled, but this is a misnomer, as I'm pretty sure it'll submit up to 1000, the last.fm API limit. These songs go into my library and in turn immensely improve the recommendations I get from Apple Music.
Now with all that said, I'd love to be able to identify the source that's logging the tracks, then be able to pull them out direct from libre.fm based on whether it was non-Apple Music plays.
The text was updated successfully, but these errors were encountered:
I'm curious if pairing the data source with a submitted song is possible? I have a rather idiosyncratic setup, but it would be simplified so much if I could split data by source.
Now with all that said, I'd love to be able to identify the source that's logging the tracks, then be able to pull them out direct from libre.fm based on whether it was non-Apple Music plays.
The text was updated successfully, but these errors were encountered: