Difference between revisions of "Beta:DsDavaar112:Release Notes"
(Created page with "== Davaar 112 Build 562 (4.110.562) Released on 15 May 2025 == * Update to to Airplay SDK version 2.0.11 to address security issue * Added extra Roon logging to aid in diagnos...") |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | == Davaar 112 Build 562 (4. | + | == Davaar 112 Build 566 (4.112.566) Released on 24 Jul 2025 == |
| + | * Reboot device on Roon error to combat discovery issues | ||
| + | |||
| + | == Davaar 112 Build 563 (4.112.563) Released on 12 Jun 2025 == | ||
| + | * Fix for WiFi Moving Coil noise issue | ||
| + | * Fix button mapping on the dial for the new Majik DSM (1170). Left/Right press on dial should trigger a skip track (not a volume change) | ||
| + | * Updated jquery version on Web UI to address potential vulnerability | ||
| + | |||
| + | == Davaar 112 Build 562 (4.112.562) Released on 15 May 2025 == | ||
* Update to to Airplay SDK version 2.0.11 to address security issue | * Update to to Airplay SDK version 2.0.11 to address security issue | ||
* Added extra Roon logging to aid in diagnosing a customer issue | * Added extra Roon logging to aid in diagnosing a customer issue | ||
Latest revision as of 15:43, 24 July 2025
Davaar 112 Build 566 (4.112.566) Released on 24 Jul 2025
- Reboot device on Roon error to combat discovery issues
Davaar 112 Build 563 (4.112.563) Released on 12 Jun 2025
- Fix for WiFi Moving Coil noise issue
- Fix button mapping on the dial for the new Majik DSM (1170). Left/Right press on dial should trigger a skip track (not a volume change)
- Updated jquery version on Web UI to address potential vulnerability
Davaar 112 Build 562 (4.112.562) Released on 15 May 2025
- Update to to Airplay SDK version 2.0.11 to address security issue
- Added extra Roon logging to aid in diagnosing a customer issue
- #8749: Remove potential deadlock scenario during Exakt updates
- #8760: Fix for headphone downmixing not working
- #8769: Fix for crash caused by incorrect handling of AirPlay parameters