2024.11.1

What's Changed

• Simplify README.md and Fix ReplayGain Metadata Tags by @ebb-earl-co in #205
• Bump Dependencies' Versions and Allow Python 3.13 by @ebb-earl-co in #214
• Bump Python Version in GitHubActions Workflows by @ebb-earl-co in #215

Full Changelog: 2024.9.2...2024.11.1

Discussion

This release mainly fixes a long-standing bug that did not allow tracks to be retrieved when Dolby Atmos version as well as HiRes format were available. Now, when a track has multiple formats available, it will follow the logic of all other --audio-format= options.

Verification

Please download the .sha256 text file that corresponds to the release artifact and verify the checksum before using said binary! A good, all-in-one tool to do this is aria2, particularly using its --checksum option: if the checksum does not match, aria2 does not save the file to disk! Otherwise, post download: sha256sum is built in to GNU/Linux systems; Windows has Get-FileHash; macOS can get sha256sum with Brew or similar.

Disclaimer

This software uses code of FFmpeg; particularly, version 7.0, licensed under the LGPLv2.1. Its source can be downloaded here.

2024.9.2: HOTFIX

What's Changed

• HOTFIX: Version Number Bump by @ebb-earl-co in #201

Discussion

The 2024.9.* versions incorporate the first API-breaking change to tidal-wave in some time, but it was necessitated by changes to TIDAL itself. As of 24 July 2024, TIDAL no longer offers tracks in MQA or Sony 360 Reality Audio format. Accordingly, tidal-wave no longer will have command-line flags to request tracks in these formats.

Future development of tidal-wave will be focused on 3 things

1. making the code more modular. Ideally, the httpx library will replace requests; ffmpeg-python will be dropped in favor of using subprocess; dataclass-wizard will make way for pydantic; Ruff recommendations will be worshiped; changing code structure to use a src/ directory; etc.
2. addressing issues. First candidate is to support albums containing tracks and videos in the same album.
3. adopting the tool uv from Astral as the all-in-one packaging, dependencies, and virtual environment tool.

Full Changelog: 2024.9.1...2024.9.2

Verification

Please download the .sha256 text file that corresponds to the release artifact and verify the checksum before using said binary! A good, all-in-one tool to do this is aria2, particularly using its --checksum option: if the checksum does not match, aria2 does not save the file to disk! Otherwise, post download: sha256sum is built in to GNU/Linux systems; Windows has Get-FileHash; macOS can get sha256sum with Brew or similar.

Disclaimer

This software uses code of FFmpeg; particularly, version 7.0, licensed under the LGPLv2.1. Its source can be downloaded here.

2024.9.1: MQA and Sony 360 Reality Audio REMOVED

What's Changed

• Kick MQA and Sony 360 Reality Audio Out of tidal-wave by @ebb-earl-co in #199
• Pin Python Version to 3.12.6 in GitHub Actions, Documentation by @ebb-earl-co in #200

Discussion

This is the first API-breaking change to tidal-wave in some time, but it was necessitated by changes to TIDAL itself. As of 24 July 2024, TIDAL no longer offers tracks in MQA or Sony 360 Reality Audio format. Accordingly, tidal-wave no longer will have command-line flags to request tracks in these formats.

Future development of tidal-wave will be focused on 3 things

1. making the code more modular. Ideally, the httpx library will replace requests; ffmpeg-python will be dropped in favor of using subprocess; dataclass-wizard will make way for pydantic; Ruff recommendations will be worshiped; changing code structure to use a src/ directory; etc.
2. addressing issues. First candidate is to support albums containing tracks and videos in the same album.
3. adopting the tool uv from Astral as the all-in-one packaging, dependencies, and virtual environment tool.

Full Changelog: 2024.8.1...2024.9.1

Verification

Please download the .sha256 text file that corresponds to the release artifact and verify the checksum before using said binary! A good, all-in-one tool to do this is aria2, particularly using its --checksum option: if the checksum does not match, aria2 does not save the file to disk! Otherwise, post download: sha256sum is built in to GNU/Linux systems; Windows has Get-FileHash; macOS can get sha256sum with Brew or similar.

Disclaimer

This software uses code of FFmpeg; particularly, version 7.0, licensed under the LGPLv2.1. Its source can be downloaded here.

2024.8.1

Python package dependencies updating their versions is enough reason to cut a new release, right? In any case, this version is the first to feel the effects of dabbling with Astral's new neat tool, uv.

Moreover, a re-formatting process is partly finished. It's based on the output of the tool ruff.

In the next version, all references and options surrounding MQA format will be removed as TIDAL has converted its entire catalog of MQA to FLAC.

What's Changed

• Take Ruff's Recommendations Really Rigorously by @ebb-earl-co in #196
• Bump version to 2024.8.1 in preparation for next release by @ebb-earl-co in #197

Full Changelog: 2024.7.1...2024.8.1

Verification

Please download the .sha256 text file that corresponds to the release artifact and verify the checksum before using said binary! A good, all-in-one tool to do this is aria2, particularly using its --checksum option: if the checksum does not match, aria2 does not save the file to disk! Otherwise, post download: sha256sum is built in to GNU/Linux systems; Windows has Get-FileHash; macOS can get sha256sum with Brew or similar.

Disclaimer

This software uses code of FFmpeg; particularly, version 7.0, licensed under the LGPLv2.1. Its source can be downloaded here.

2024.7.1

Release Tidbits

Issue #186 is addressed, and the option to have tidal-wave report its version is added with the --version flag!

What's Changed

• Allow 2-Digit TIDAL Artist and Album IDs and Bump Dependence Versions by @ebb-earl-co in #185
• Address Issue, Restrict to Python < 3.13, and Allow 2-Digit TIDAL IDs by @ebb-earl-co in #188

Full Changelog: 2024.6.1...2024.7.1

Verification

Please download the .sha256 text file that corresponds to the release artifact and verify the checksum before using said binary! A good, all-in-one tool to do this is aria2, particularly using its --checksum option: if the checksum does not match, aria2 does not save the file to disk! Otherwise, post download: sha256sum is built in to GNU/Linux systems; Windows has Get-FileHash; macOS can get sha256sum with Brew or similar.

Disclaimer

This software uses code of FFmpeg; particularly, version 7.0, licensed under the LGPLv2.1. Its source can be downloaded here.

2024.6.1: Correct Track `title` Metadata

What's Changed

• Fix Track title Metadata Field by @ebb-earl-co in #179
• Release Artifact Uploading as "Storage" by @ebb-earl-co in #180

Release Tidbits

Track and Album Names with Special Characters

The main purpose of this release is to fix a bug in how track's title metadata was populated (see issue #177). Briefly, for the names of tracks or albums that have special characters, a "sanitized" title is created and used as the name of the album directory or track name (or both, as necessary) on disk. The metadata in the file, however, should specify the un-sanitized name of the track and/or album, not the sanitized version. This release fixes the issue.

Artifacts Not Created at Release Time

When a release is created, for each of the release artifacts (.exe file, or binary for the other platforms), a GitHub Actions workflow is automatically kicked off. All the workflows have operated flawlessly, except the Windows PyInstaller workflow to create the version's tidal-wave_windows.exe file.
This process has been changed to upload all binary artifacts to GitHub's artifact "storage", where they will live for a period of 7 days. This gives time for me to download them and manually add them to the release if the step in the GitHub Actions workflow(s) fails to upload the binary to the release.

Full Changelog: 2024.5.2...2024.6.1

Verification

Please download the .sha256 text file that corresponds to the release artifact and verify the checksum before using said binary! A good, all-in-one tool to do this is aria2, particularly using its --checksum option: if the checksum does not match, aria2 does not save the file to disk! Otherwise, post download: sha256sum is built in to GNU/Linux systems; Windows has Get-FileHash; macOS can get sha256sum with Brew or similar.

Disclaimer

This software uses code of FFmpeg; particularly, version 7.0, licensed under the LGPLv2.1. Its source can be downloaded here.

2024.5.2 - Now Using Ubuntu 24.04

What's Changed

• Bump Dependencies Versions by @ebb-earl-co in #169
• Update GitHub Runner and Python Dependencies' Versions by @ebb-earl-co in #170
• Update Versions of Python Dependencies by @ebb-earl-co in #173
• Bump Version for Next Release by @ebb-earl-co in #174

Full Changelog: 2024.5.1...2024.5.2

Verification

Please download the .sha256 text file that corresponds to the release artifact and verify the checksum before using said binary! A good, all-in-one tool to do this is aria2, particularly using its --checksum option: if the checksum does not match, aria2 does not save the file to disk! Otherwise, post download: sha256sum is built in to GNU/Linux systems; Windows has Get-FileHash; macOS can get sha256sum with Brew or similar.

Disclaimer

This software uses code of FFmpeg; particularly, version 7.0, licensed under the LGPLv2.1. Its source can be downloaded here.

2024.5.1

What's Changed

• Change Filename Pattern for Videos by @ebb-earl-co in #165
• Higher-Resolution Artist Images by @ebb-earl-co in #166

Full Changelog: 2024.4.3...2024.5.1

Verification

Please download the .sha256 text file that corresponds to the release artifact and verify the checksum before using said binary! A good, all-in-one tool to do this is aria2, particularly using its --checksum option: if the checksum does not match, aria2 does not save the file to disk! Otherwise, post download: sha256sum is built in to GNU/Linux systems; Windows has Get-FileHash; macOS can get sha256sum with Brew or similar.

Disclaimer

This software uses code of FFmpeg; particularly, version 7.0, licensed under the LGPLv2.1. Its source can be downloaded here.

2024.4.3

What's Changed

• Get Rid of 100-Element Limitation by @ebb-earl-co in #158
• Add new feature: Retrieval of Original, High-Resolution Album Covers by @ebb-earl-co in #161
• Small Change to README.md by @ebb-earl-co in #162

Bonus Release Binary

Because today marks the release of Fedora 40, a binary built with PyInstaller for that distribution is included in this release.

Full Changelog: 2024.4.2...2024.4.3

Disclaimer

This software uses code of FFmpeg; particularly, version 7.0, licensed under the LGPLv2.1. Its source can be downloaded here.

2024.4.2: New and Improved Binaries

New Release Artifacts

There is now just one release artifact for each of the following operating systems:

• GNU/Linux 64-bit (Ubuntu): tidal-wave_ubuntu_amd64
• macOS 64-bit x86: tidal-wave_macos_amd64
• macOS 64-bit ARM: tidal-wave_macos_aarch64
• Windows 64-bit: tidal-wave_windows.exe

Each of these bundles FFmpeg 7.0, Python 3.12.2, and the tidal-wave program, version 2024.4.2, into one executable file. I.e., there is no need to download, install, or configure Python3 or FFmpeg! Simply download the program for the desired OS and execute it.

What's Changed

• Remove PyApp GitHub Actions Workflow Files by @ebb-earl-co in #147
• Update to Version 2024.4.2 by @ebb-earl-co in #149

Full Changelog: 2024.4.1.1...2024.4.2

Disclaimer

This software uses code of FFmpeg; particularly, version 7.0, licensed under the LGPLv2.1. Its source can be downloaded here.