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:

  1. different download sources (qobuz, deezer, tidal etc.)
  2. different qualities/encodings (opus, flac, original etc.)
  3. random different songs/albums (and even downloading tracks individually)
  4. 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.

  • Asparagus0098@sh.itjust.worksEnglish
    0·
    10 days ago

    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).