feat: Soundcloud Support

[Lioncat6]

#5
#35

SoundCloud currently implements the following:

• Looking up releases as a set/playlist or track
  • Unlike Bandcamp, there is no way to determine if a track has a parent playlist/album with the v1 API
• Getting track ISRC, duration, author, and region information (Though, I haven't found a track, yet that has a set region restriction)
• Track/Playlist publish date, falling back to the creation date if not present
• Track and album artwork
• Getting playlist type
• Determining playlist label from tracks

[Lioncat6]

Looking at #35, and I should see about adding CC license detection

As for GTINs, those are only available when using the v2 API, which requires a user oath and client ID, as opposed to an application auth. At the moment, this implementation only uses the public v1 API, lacking support for proper label, copyright, and barcode information.

[Lioncat6]

I also still need to add tests to SoundCloud, it seems.

[Lioncat6]

I have also determined that some releases simply can not be fetched with the v1 API, for example: https://soundcloud.com/stevie-wonder-official/sets/so-what-the-fuss-3

[kellnerd]

Thank you for looking into SoundCloud!
Although this is still a draft and I haven't made an account to obtain API credentials yet, I couldn't resist to review the code once.
I have left a few comments but I guess there will be more once I get to play with the v1 (and maybe v2) API.

P.S. CI is complaining about code formatting, see here how to reproduce that locally.

[kellnerd]

I was able to obtain bigger images (about 1500px) with Image Max URL, so we should check that again.

[Lioncat6]

500x500 is the highest we can get for sure. Using original in the url instead of t500x500, we can get the original file, which I've personally seen up to 3000x3000, the ending of the url changes depending on what the artist uploaded the file as: either .jpg or .png

[Lioncat6]

Update, just found one at 3071x3071.

[Lioncat6]

Further update: After messing around with my own images, there is no image resolution limit, but compression is applied to whatever you upload

[Lioncat6]

Since there is no way to determine the url extension for the -original urls, I think it should stay with the t500x500 URL and let the image importer userscript handle it.

Otherwise, a request could be made here to determine the extension

harmony/providers/SoundCloud/mod.ts

Lines 342 to 355 in bf0554b

	getArtwork(release: SoundcloudPlaylist | SoundcloudTrack): Artwork[] | undefined {
	const artworks: Artwork[] = [];
	const artworkUrl = release.artwork_url;
	if (artworkUrl) {
	artworks.push({
	thumbUrl: artworkUrl.replace(/-(large|medium|small)\./, '-t300x300.'),
	url: artworkUrl.replace(/-(large|medium|small)\./, '-t500x500.'),
	types: ['front' as ArtworkType],
	provider: this.provider.name,
	});
	return artworks;
	}
	return undefined;
	}

[kellnerd]

Thank you for adding a few provider tests! For today I have a couple of questions and a few refactorings which went wrong.

[kellnerd]

Do the URLs ever have a www subdomain? The provider implementation doesn't accept it at least.

[kellnerd]

The website says 14 January 2016 when I hover the "9 years ago". Even if there is a timezone offset, it can't be two days?
We should investigate all the available date fields, ideally for a release with a known release date (for example from another platform).

[Lioncat6]

As it turns out, SoundCloud entities have 4 "release" dates... the most reliable being the dedicated release fields, as those are manually entered by the artist (usually pretty rarely, similar to ISRC and UPC data). The date that appears on the website is the display_date field, which mirrors the last_modified date. The date I'm currently using as a fallback for the actual release date is the created_at date, which isn't what's displayed on the website.