RudeySH / lastfm-bulk-edit

Bulk edit your scrobbles for any artist, album or track on Last.fm at once.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Suggestion: add "edit scrobble" button for now scrobbling track

flickur opened this issue · comments

I know this is perhaps not directly related to bulk editing but would be a nice QoL feature and I couldn't think of a better place to suggest this. Would it be possible to add the "edit scrobble" button to the current playing track so you could edit it straight away without waiting for it to finish scrobbling?

image

The "Scrobbling now" track hasn't actually been scrobbled yet. At least not until you've played at least 50% of the track. And I even suspect some scrobble integrations like Spotify don't actually scrobble until you're 100% done playing the track.

You can't edit a scrobble that doesn't exist yet.

Although, I wonder if you can use the new "Automatic edit" feature for tracks that haven't been scrobbled yet...

Yeah the automatic edit feature is what got me thinking about this. But also I'm thinking about a scenario where I have scrobbled that track before and you could just add a button that forwards you to the editing window of said track (since it's already been scrobbled to my library before). Just like if you would click the track name -> track page -> track page of my library ->edit scrobble, so you could skip all this.

I added the option to edit scrobbles in the Recent Tracks section on January 24th, 2022 (v0.4.0, 6773a72), which includes the "Scrobbling now" track. If you edit the now scrobbling track, be sure to check "Automatic edit", because otherwise it only edits your existing scrobbles of the track, and the incoming scrobble won't be edited. If you try to edit a track that you haven't scrobbled before, my userscript won't let you continue at the moment.

Today, I realized the edit scrobbles option in Recent Tracks was disappearing after 20 seconds, because Last.fm is continuously refreshing the list while you're scrobbling, and my script did not yet account for that. This bug has been fixed today (v0.5.1, f5bd0ea).