Error getting release: ('Connection broken: IncompleteRead(1 bytes read, 69334985 more expected)', IncompleteRead(1 bytes read, 69334985 more expected)). Skipping...

[davidavdavid]

This error is occurring more and more frequently:

Error getting release: ('Connection broken: IncompleteRead(1 bytes read, 69334985 more expected)', IncompleteRead(1 bytes read, 69334985 more expected)). Skipping...

[darkblackx]

Getting the same. Was working before. Here is my output, let me know if more is needed.

qobuz-dl dl https://open.qobuz.com/album/0060253749865
Logging...
Logged: OK
Membership: Studio
Set max quality: 27 - 24 bit, >96kHz


Downloading: Nevermind
Quality: FLAC (24/96)

cover.jpg was already downloaded
0.00/114M /// Qobuz Downloads/Nirvana - Nevermind (1991) [24B-96kHz]/.00.tmp
Error getting release: ('Connection broken: IncompleteRead(1 bytes read, 119370445 more expected)', IncompleteRead(1 bytes read, 119370445 more expected)). Skipping...

[NOForker]

I am also getting this more frequently. Qobuz recently updated their own clients, so maybe they changed something in the process?

[powkakashi]

Same, also getting this with Streamrip more and more

[Yuffie513]

Qobuz Reddit is full of posts about this. The official Apps can’t search, download or play many tracks right now. From what I read Qobuz is in the process of moving their servers to the cloud.

To me it has been next to impossible to download any album without missing tracks for like a week now.

@darkblackx I can’t download that Nirvana album either.

[k-stolk]

Got the same, software that rely on this also break. Like QBDLX and its forks

[zapf2000]

Their CDN Caches are not up to date. If you try the next day, it mostly works.

[Sei969]

I have followed the instructions from the update "Fix CDN download resilience & rewrite Qobuz authentication #326" to the letter. This ensures the app connects to the music servers more reliably and handles the login process without any of the previous errors.

The most important addition is a smart new way to handle songs that get stuck. Sometimes, when you try to download a very high-quality song, like a massive 192kHz file, the music server might get overwhelmed or block the connection because the file is too large for your internet speed at that moment. In the past, the app would simply give up after a few tries and skip the song, leaving you with a missing track in your folder.

Now, we have introduced the Graceful Quality Fallback. If a song fails to download at the highest quality after 5 attempts, the app does not quit. Instead, it automatically tries to "rescue" the track by attempting to download it at a slightly lower resolution. It will try 96kHz, then CD quality, and finally MP3 as a last resort until the download is successful.

This change ensures that your album is always complete. It is much better to have one song in CD quality than to have a silent gap in your music collection. To make this work effectively, the app asks the server for a brand-new download link for every different quality level it tries, which almost always clears up any connection issues immediately.

The following logic was added to the heart of the downloader to manage this process:

# List of quality levels to try if the main one fails: 192kHz -> 96kHz -> CD -> MP3
FALLBACK_TIERS = [27, 7, 6, 5]

By using this method, the downloader is now much more resilient. Even if the server is having trouble delivering the biggest files, you are guaranteed to get every single song from the album in the highest quality that the server is currently able to provide.

[bhalejos]

@zapf2000, your statement gave me the idea of trying swapping my locations through VPN... And it worked! Qobuz being a French company (AFAIK), using locations in France (and/or closer to the European "countries of origin" [i.e., language-based] of the albums) allowed me to download all the tracks that failed before.

Thanks!

[catap]

Here another aproach which mimic the web version.

0004-Implement-segmented-download.patch

[Sei969]

@catap Your patch works flawlessly. It successfully downloaded a stubborn 192kHz track via segmented chunks without triggering any Akamai timeout, and the FFmpeg remuxing went perfectly. I've also integrated it with a graceful downgrade logic, and the script is now rock-solid. Brilliant work, thank you!

[catap]

@Sei969 it is slower, but it works. Unfortently here almost no chance that @vitiko98 moved forward and merged it :(

[catap]

actually here additional fix to skip not available tracks

skip-tracks.patch