Audacious Discord RPC version 2.3 is a minor update, mostly fixing oversights and minor issues from v2.2. The field sanitation is made UTF-8 aware, seeking will cause a RPC update, and RPC updates are now lock-guarded by a mutex (especially relevant for cover fetch tasks).
It also fixes inconsistent user agents between Linux (Audacious Discord RPC/2.3) and Windows (Audacious-Discord-RPC/2.3). Both operating systems now use Audacious-Discord-RPC/2.3. Self-compiled versions from master will show Audacious-Discord-RPC/master instead.
This release was planned for last week due to #8 problem, but was unfortunately delayed for a) RL j*b and b) attempts to add a reconnection mechanism to Discord. Unfortunately, as the used RPC library doesn’t allow re-initialising the IO handler, Audacious cannot reconnect, and thus must be started after Discord is already running. I will later try to explore other options to not make this a necessity (input, ideas or PRs are very welcome).
Compatibility
Compiled for Audacious 4.5.x on Linux and Windows (10 & 11).
x86 (Intel / AMD) architecture only.
Installation
Please find the included INSTALL.<platform>.txt file or the ‘Installation’ section in the README for installation instructions.
Changes
Diff: v2.2...v2.3
Additions
- 159e0a9 Seeking (manually changing position of a track) updates the RPC now
Fixes
- 6c6b8d2 Triggers RPC on direct execution (calls
playback_to_presenceafter connecting; #8) - 0785299 Made
field_sanitizeUTF-8 aware - ab720fa Unified user agent between Linux (cURL) and Windows (WinHTTP)
Other Changes
- e69935d Made RPC updates mutually exclusive with a mutex lock-guard
- 77d6ef7 Improved building guide in
README.md
Known issues
- Timestamps are not cleared properly when paused, resulting in an unfortunate counter of how long was the user idle (#2)
Any help with fixing this issues would be much appreciated! ❤️