Tidal-wave

What's Changed
* Simplify README.md and Fix ReplayGain Metadata Tags by ebb-earl-co in https://github.com/ebb-earl-co/tidal-wave/pull/205
* Bump Dependencies' Versions and Allow Python 3.13 by ebb-earl-co in https://github.com/ebb-earl-co/tidal-wave/pull/214
* Bump Python Version in GitHubActions Workflows by ebb-earl-co in https://github.com/ebb-earl-co/tidal-wave/pull/215

**Full Changelog**: https://github.com/ebb-earl-co/tidal-wave/compare/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`](https://aria2.github.io/), particularly using its [`--checksum` option](https://aria2.github.io/manual/en/html/aria2c.html#cmdoption-checksum): 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`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/get-filehash); macOS can get `sha256sum` with Brew or similar.
Disclaimer
This software uses code of [FFmpeg](http://ffmpeg.org/); particularly, version 7.0, licensed under the [LGPLv2.1](http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html). Its source can be downloaded [here](https://github.com/FFmpeg/FFmpeg/tree/n7.0).

What's Changed
* HOTFIX: Version Number Bump by ebb-earl-co in https://github.com/ebb-earl-co/tidal-wave/pull/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](https://arjancodes.pages.dev/blog/guide-to-structuring-python-projects/); etc.
2. addressing [issues](https://github.com/ebb-earl-co/tidal-wave/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**: https://github.com/ebb-earl-co/tidal-wave/compare/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`](https://aria2.github.io/), particularly using its [`--checksum` option](https://aria2.github.io/manual/en/html/aria2c.html#cmdoption-checksum): 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`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/get-filehash); macOS can get `sha256sum` with Brew or similar.
Disclaimer
This software uses code of [FFmpeg](http://ffmpeg.org/); particularly, version 7.0, licensed under the [LGPLv2.1](http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html). Its source can be downloaded [here](https://github.com/FFmpeg/FFmpeg/tree/n7.0).

What's Changed
* Kick MQA and Sony 360 Reality Audio Out of `tidal-wave` by ebb-earl-co in https://github.com/ebb-earl-co/tidal-wave/pull/199
* Pin Python Version to 3.12.6 in GitHub Actions, Documentation by ebb-earl-co in https://github.com/ebb-earl-co/tidal-wave/pull/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](https://arjancodes.pages.dev/blog/guide-to-structuring-python-projects/); etc.
2. addressing [issues](https://github.com/ebb-earl-co/tidal-wave/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**: https://github.com/ebb-earl-co/tidal-wave/compare/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`](https://aria2.github.io/), particularly using its [`--checksum` option](https://aria2.github.io/manual/en/html/aria2c.html#cmdoption-checksum): 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`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/get-filehash); macOS can get `sha256sum` with Brew or similar.
Disclaimer
This software uses code of [FFmpeg](http://ffmpeg.org/); particularly, version 7.0, licensed under the [LGPLv2.1](http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html). Its source can be downloaded [here](https://github.com/FFmpeg/FFmpeg/tree/n7.0).

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](https://astral.sh/)'s new neat tool, [`uv`](https://docs.astral.sh/uv/).

Moreover, a re-formatting process is partly finished. It's based on the output of the tool [`ruff`](https://docs.astral.sh/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 https://github.com/ebb-earl-co/tidal-wave/pull/196
* Bump version to 2024.8.1 in preparation for next release by ebb-earl-co in https://github.com/ebb-earl-co/tidal-wave/pull/197

**Full Changelog**: https://github.com/ebb-earl-co/tidal-wave/compare/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`](https://aria2.github.io/), particularly using its [`--checksum` option](https://aria2.github.io/manual/en/html/aria2c.html#cmdoption-checksum): 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`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/get-filehash); macOS can get `sha256sum` with Brew or similar.
Disclaimer
This software uses code of [FFmpeg](http://ffmpeg.org/); particularly, version 7.0, licensed under the [LGPLv2.1](http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html). Its source can be downloaded [here](https://github.com/FFmpeg/FFmpeg/tree/n7.0).

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 https://github.com/ebb-earl-co/tidal-wave/pull/185
* Address Issue, Restrict to Python < 3.13, and Allow 2-Digit TIDAL IDs by ebb-earl-co in https://github.com/ebb-earl-co/tidal-wave/pull/188

**Full Changelog**: https://github.com/ebb-earl-co/tidal-wave/compare/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`](https://aria2.github.io/), particularly using its [`--checksum` option](https://aria2.github.io/manual/en/html/aria2c.html#cmdoption-checksum): 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`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/get-filehash); macOS can get `sha256sum` with Brew or similar.
Disclaimer
This software uses code of [FFmpeg](http://ffmpeg.org/); particularly, version 7.0, licensed under the [LGPLv2.1](http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html). Its source can be downloaded [here](https://github.com/FFmpeg/FFmpeg/tree/n7.0).

What's Changed
* Fix Track `title` Metadata Field by ebb-earl-co in https://github.com/ebb-earl-co/tidal-wave/pull/179
* Release Artifact Uploading as "Storage" by ebb-earl-co in https://github.com/ebb-earl-co/tidal-wave/pull/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**: https://github.com/ebb-earl-co/tidal-wave/compare/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`](https://aria2.github.io/), particularly using its [`--checksum` option](https://aria2.github.io/manual/en/html/aria2c.html#cmdoption-checksum): 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`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/get-filehash); macOS can get `sha256sum` with Brew or similar.
Disclaimer
This software uses code of [FFmpeg](http://ffmpeg.org/); particularly, version 7.0, licensed under the [LGPLv2.1](http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html). Its source can be downloaded [here](https://github.com/FFmpeg/FFmpeg/tree/n7.0).