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.

    • Blastboom StriceOPEnglish
      2·
      1 day ago

      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)

      • Asparagus0098@sh.itjust.worksEnglish
        3·
        18 hours 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).

        • Blastboom StriceOPEnglish
          1·
          11 hours ago

          I see what you mean, I had made a very thorough post in this community on fetching and applying song metadata in batch, but it got too complicated and moving to linux (nixos specifically) made it even more complicated that made me realise I should figure a more automated and simple process.

          I’d like to make a server and one of its functions is probably going to be a spotify-like service with jellyfin or something. I’m thinking of using streamrip with a qobuz token (I will also have to check the arr suite), but until I make that I’m a bit lazy and use lucida.