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
Oftentimes Bandcamp releases will offer individual tracks as pre-release singles. When using Harmony to import these tracks as such, the track number from the track's position on the album is carried over, producing a one-track release with a track number other than 1. Is there a way to put a stop to this, or at least warn users about it?
The text was updated successfully, but these errors were encountered:
Do you have one or two examples? Are they "real singles" if they are considered part of an album rather than just pre-release tracks?
If the page / the embedded JSON lists these tracks with the track number from the album, they might also have this metadata in the downloaded files?
Here's an example: https://chillhop.bandcamp.com/track/friends which is simultaneously available as a single on other platforms: https://chillhop.ffm.to/cr471.PBT. That, along with the presence of track art (which isn't always the case) is the metric I use to determine whether or not a Bandcamp track should be entered as a single.
I can't speak for downloaded files since I don't buy downloads from Bandcamp.
Oftentimes Bandcamp releases will offer individual tracks as pre-release singles. When using Harmony to import these tracks as such, the track number from the track's position on the album is carried over, producing a one-track release with a track number other than 1. Is there a way to put a stop to this, or at least warn users about it?
The text was updated successfully, but these errors were encountered: