Small issues with autocorrection feature
I've noticed a few small problems with the autocorrection feature.
(1) It doesn't change the word "and" to an ampersand "&". For example, the Metallica song "Seek and Destroy" is not autocorrected to "Seek & Destroy".
(2) Sometimes it makes autocorrections that aren't right. For example, it always changes the Dream Theater song "A Change of Seasons: I The Crimson Sunrise" to "A Change of Seasons: VII The Crimson Sunset".
I understand that any autocorrection feature will always have little problems like this. But I just wanted to document these issues in case the autocorrection feature is ever updated.
-
leglessmoof commented
Overall, I like the improved autocorrection. However, I have noticed one or two issues.
(1) Adding or editing a setlist with autocorrection enabled takes a long time, usually about 10 - 20 seconds. I'm guessing this is because it has to query the MusicBrainz database? This delay might be unavoidable but I just wanted to point it out for future improvement, if possible.
(2) The old autocorrection would always fix capitalization mistakes to match what was in the setlist.fm database. The new autocorrection fixes capitalization errors sometimes, but definitely not all the time. I have no idea what might be causing this.
-
Adminsfussenegger (Admin, setlist.fm) commented
It took me somewhat longer than expected, but an improved autocorrection is now online.
1. Songs won't be changed if they are spelled as on musicbrainz.org, even if similar songs are in the setlist.fm DB.
2. Covers shouldn't be removed if a you add them explicitly. They might still be added though.
3. It's now possible to revert autocorrections with a single click.Please let us now how it works for you.
Cheers
-
Beau commented
Yep, I've also run into that issue regarding cover songs with Bruce Springsteen's setlists.
-
leglessmoof commented
Another problem -- if you add a setlist that has a NEW SONG for the band (meaning the song doesn't exist in the Setlist.fm database), and that song is a cover song, the autocorrection feature always removes the @Cover tag.
E.g. I added a setlist for Metallica with the song "Motorcycle Man" which is a Saxon cover, first time ever played by Metallica. Autocorrection removed the @Cover tag...
-
Adminmsparer (Admin, setlist.fm) commented
leglessmoof you're right in both points, I also experienced some problems with the autocorrection feature -> definitely room for improvement
-
leglessmoof commented
For the second issue, "A Change of Seasons: I The Crimson Sunrise" and "A Change of Seasons: VII The Crimson Sunset" are both valid songs and they both exist in the database. But "The Crimson Sunrise" always gets autocorrected to "The Crimson Sunset" which is wrong.
-
leglessmoof commented
Dan's comment is not relevant to either of my issues.
For the first issue, "Seek & Destroy" is the correct spelling and that's how it exists in the database and all the other setlists. But if you create a new setlist with "Seek and Destroy" it doesn't get autocorrected.
-
Dan commented
The auto correction feature is partially based upon whats already in the Setlist.fm database. If a song was entered incorrectly the first time this is what Setlist.fm uses as its correction. Go to the artists page and check how its spelt there. If there's a mistake, contact a mod as we can batch change songs. Hope this made some sense. You can find me at:
http://www.setlist.fm/user/mr_magpie -
midnightrider commented
How about the thing with capital letters. I Think every word in a song should start with a capital letter or there should be no difference for the stats
-
Beau commented
Yeah, I've seen your second example come up.
Bruce Springsteen has a song called "Out In the Street" AND another called "Racing In the Street". The autocorrect feature always treats "Racing In the Street" as wrong when it shouldn't be.