Skip to content

v3.4.4 — Non-ASCII device UID fix

Latest

Choose a tag to compare

@mauriciomorkun mauriciomorkun released this 30 Jun 19:17

Fixed

  • Devices whose CoreAudio UID contains non-ASCII characters (e.g. CJK serial-number characters in the Pebble V3) are now found and routed correctly. The Python→C control protocol previously serialised non-ASCII UIDs as \uXXXX escape sequences, which the C helper copied verbatim and then failed to match against the device's real UTF-8 UID ("Device not found" despite the device being present). _send_no_lock() now sends real UTF-8 bytes (ensure_ascii=False).

Reported by bogdanw (MacRumors). No action required — update normally.

Full changelog: https://github.com/mauriciomorkun/AudioRouterNow/blob/main/CHANGELOG.md