Skip to content

FluentDL 2.0.0.0

Latest
Compare
Choose a tag to compare
@DerekYang2 DerekYang2 released this 06 Feb 03:02
· 16 commits to master since this release
de08f5c

This release brings important improvements to authentication and bug fixes, including the Youtube API and conversions.

Change List

  • Youtube API fixed.
  • Added email/password authentication option for Qobuz (stored only locally and encrypted).
  • Support for both new/old Qobuz tokens, automatically handled.
  • Added automatic Spotify authentication, user just needs to be logged into the web player. Option to use app id/secret is still there, just not required anymore.
  • Bug fix to conversions that prevents tracks from being skipped. Bug occurred when a source was in both input and output (e.g. Deezer, Qobuz -> Deezer or Spotify, Youtube -> Youtube).
  • Increased default thread numbers in settings, though feel free to change to preference. These can significantly speed up conversions and downloading.

TODO:

  • Add a button to directly download all items in queue. Currently, conversion output must be set to local, which can be awkward and hard to find.
  • Newer version notification.
  • Settings backup/upload? Currently, running the MSIX or powershell save previous settings but uninstalling removes all data.
  • Display max bit and sampling rate in preview panel.
  • User guide and Wiki.

Installation

Download the FluentDL_2.0.0.0.zip below. Right click on Install.ps1 and press Run with Powershell.

The script is safely auto-generated by Visual Studio.

If you do not have this option or it is crashing, see README installation section for the other alternative.

Normally, if you have already installed previous versions, it is sufficient to directly run FluentDL_{VERSION}_x64_MSIX.msix. HOWEVER, you have to run the powershell script for this release because the certificate was changed. It was updated so that it now expires in 2026.

Authentication

Certain features, such as downloading high-quality sources, require authentication. ARLS, tokens, email/password etc. can be entered in the settings tab. See README authentication section for more details.