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.

  • madame_gaymes@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    19 hours ago

    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.