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.