Edit: turns out .su seems to work, while .to doesnt
I’m noticing that about half the time I try to download music from lucida, it fails reporting:
uh-oh!
An error occurred. JSON.parse: unexpected
character at line 1 column 1 of the JSON data
To test it, I tried:
- different download sources (qobuz, deezer, tidal etc.)
- different qualities/encodings (opus, flac, original etc.)
- random different songs/albums (and even downloading tracks individually)
- using different devices
But still it fails. Do they have issues with the accounts they use to download the tracks or is it something else? This kind of issue tends to be fixed a few hours later.
I always fail to download in lucida it give me error after paste link. Luckily telegram bot still works
The website is either brilliant or atrocious. No middle ground.
From my experience, almost everything fails except for one combo: Amazon + United Kingdom. This combo has been flawless every single time, no failures, even when all others fail in the same session.
That being said, the downloaded audio format is hardly consistent. I’ll download a whole album, and half will be in FLAC, the other half in OPUS. Not a big deal with ffmpeg available, but still weird.
Hmm, thats interesting, will keep in mind
Yes. When it doesn’t work, I use squid.wtf .
Oh thats what I had tried few days ago, thanks for confirming it:)
(I think the squid site didnt fetch all the metadata, but whatever)
Personally, I always use MusicBrainz Picard to tag any music I download, so it doesn’t matter if what I downloaded has incomplete metadata.
If I don’t end up finding the correct release for metadata on MusicBrainz, then I just add it to the database myself (there’s tools and scripts to make it easier to add digital releases).
I also recommend yams.tf
Wow, never heard of that one. Seems cool, thanks!
