Audioserver Changelog
Audioserver 15.3.12.02
Fixed
- Radiostreams did not start at first hit
- Soundsuit stopped sometimes between tracks
- fixed issue with Sub Speaker on single-output Stereo Extension does not work
- Fixed issue where playback after Event was not correct, could show playing but was muted
- Fixed issue where Soundsuit files are not deleted correctly from Ramdisk leading to an out-of-memory condition
- BG-I32116 fix linein stop when transit to Bluetooth
- Fixed a possible Remote Code Execution Vulnerability in the Communication between Miniserver & Audioserver
New
- Updated Audio Backend Libraries
- Handle permanent Input on ‘Off’ for Audioplayer, Audio Central, Audio Group fixed. When On, Playback and Bell/Buzzer were stopped. Bluetooth sessions are actively disconnected and disabled.
Audioserver 15.1.08.05
New:
- Soundsuit prepared for offline cache download (beta) (attachedUSB stick required)
- added support for Loxone Debug Monitor Tasks & System Status (Audioserver, Extensions, Master Speaker)
- added support for recent played songs controlled by Audioserver (not yet used in App)
- Audioserver can be updated via Miniserver upon request (enforce version equalness and minimum API requirements in a whole installation)
- Using new TTS voices (due to deprecation of currently used voice model)
Fixed:
- BG-I30859 Reboot of Audioserver now invalidates active Webadmin Session Token
- BG-I30824 Fix Error TTS for Spotify issued even if not playing
- BG-I30838 fix issue adding NAS folder that are not dns resolveable
- BG-I30638 add History Event for Players being offline. Event is only created once in an hour to avoid excessive logging.
- BG-I30653 Extension sends online event alongside with current version to sync with Miniserver / Config Device Tree view
- BG-I30629, BG-I30580, BG-I30173 WMA files not played correctly
- BG-I23775 do not auto-repeat single files (local / usb / nas)
- BG-I30251 Master/Client – if Client has Gain factor set, the volume changes periodically
- BG-I29744 Master/Client – if Client is on different Player as Master, change Master volume affects Client
- BG-I30184 add support for temperature units either °F or °C (depends on Miniserver project setting)
- BG-I30224 prevent Custom Sounds Event command for non-existent files
- BG-I30248 fixed command for requesting debug stats into Loxone Monitor
- BG-I29954 fixed misleading Systemerror Message for duplicate Airplay / Spotify Connect names if this service is not activated on the Player
- BG-I29932 fixed some stations initial playback issues (BG-I29931, BG-I29957)
- BG-I29976 fixed CPU Overtemperature toggling issue for Stereo Extensions. Event will now be triggered >= 110°C and cleared when below 105°C
- BG-I29950 fixed Issue where last played SpotifyConnect context survives a logout and can cause wrong player to start when reconnecting
- BG-I29939 fixed handle Pause while Event on central block / fixed group- [Audio] BG-I29939 Audio Central Zoff + TTS at the same time when Music was playing did not stop the music after TTS
- BG-I29725 fixed missing History Event for Spotify Content as RoomFavorite
- BG-I29591 fix Custom Image for Spotify Playlists Coverurl
- (Master/Client) simultaneous bluetooth streams fixed
- (Master/Client) fixed Timing source domain for Master/Client Speaker
- (Master/Client) grouped master and clients, returning from Spotify source, mute state fixed
- (Master/Client) EQ only uses internal DSP & EQ Ratio adapted
- (Master/Client) fixed issue where Login to Master Speaker Webinterface is not possible when paired with MS Compact
- (Master/Client) certified AirPlay included
- (Library) fixed Library rescan of single folder via App not working
- (Library) add NAS Storage with MS AD Authentication in the format domain/username is now possible, format username@domain was already supported
- (Soundsuit) fixed Soundsuit reset-to-default (Accounts)
- (Soundsuit) use new API endpoint ensures that all newly added Soundsuit Accounts are usable
- (Tunein) Tunein fixed stations that only provide ‘aac’ audio format can be played
- (Tunein) optimizations for Tunein Startup Issues
- (Tunein) several improvements for Radio playback & error handling
- (Spotify) fixed issue where Spotify is not playable upon adding an account on Master / Client Speakers
- fixed missing Error TTS Message when spotify encounters a playback issue (network related)
- fixed issue with fixed group Play Input interrupted an event that currently played
- disable Pairing Window Mode while not paired (= Audioserver should be pairable endless on fresh installs)
Audioserver 2.9.02.27
Fixed
- BG-I28440 Audioevents sent out multiple times in stacked environments for same player
- BG-I28392 fixed Stream Error should retry instead of stopping stream
- BG-I27958 fix USB/SD Content mixed up in wrong order
- BG-I27892 cleanup of tts files when exceeding 100M, changed to delete files >= 2d (was 7d)
- BG-I27916 fix crash in TunineSourceFinder
- BG-I28037 fixed issue with Radio Station that sends stream instead of m3u urls
- BG-I28404 fixed missing Contextual Info in Queue view
- BG-I28358 fixed adding custom urls Streaming Servers that do not support HEAD Requests
- fix issue where spotify locally started causes other Players in fixed group (singlemode) to start too.
- removed Stream Prebuffering causing latency issues in Radio playback
- fixed Spotify no playback but shows visual playback (former spotifyconnect patch)
- fixed ‘New Audioserver Software’ reports did not work due to timeouts
- Stream Error Handling for unplayable streams improved
- fixed race conditions that can cause a crash on event playback
- Performance optimizations for Miniserver Compact Audio distribution on local Tree Turbo
- fixed Volume+ command on muted playergroup causing the volume to increase on one player
- Player Default Volumes did not sync on startup could cause unexpected behaviour
- fixed Issue where System Status Messages and Callback Actions were not reliably forwarded
- fixed Custom Sound Event Volumes
Audioserver 2.8.12.05
New:
- added CustomURL Feature (adding own Radio Stations / custom streaming URLs)
- avoiding jingles on radio for first stream start
Fixed:
- fixed Stereo Extensions not having the need for a LAN IP wont request one
- (typically only the case if you have multiple extension outputs connected to a single player where only one extension will be spotify/airplay master)
- fixed Stereo Extension time not accurate (causing spotify not able to re-login)
- fixed Stream distribution not terminated correctly between Compact Miniservers causing duplicate Streams on a single output
- fixed some race conditions for Stereoe Extensions that did not correctly gather an ip from dhcp
- fixed Events not fully restore on stacked players
- fixed Events being interrupted when linein was playing
- fixed a grouped Player’s behaviour when it starts to play while Event is playing in the group. Now the player continues to play after the event
- fixed Source State Synchronisation causing sometimes wrong playing status
- fixed no sound output issue with Volume+ or Play arrive while TTS plays.
- fixed no sound output issue due to sourcefinding algorithm when play or volume+ arrives at 2AS or more at the same time on players of a group
- fixed some systemerror message not shown in systemstatus
- fixed newly added Players did not get the optimized EQ Settings until Audioserver services restarted or another ‘Save into Miniserver’ triggered it
Audioserver 15.0.05.10
New:Â
- Â [Audio] a Player can be configured to always start with the first available Room Favorite when triggered by Presence
- [Audio] added Support for Audio Speaker Search via App
- [Audio] added Support for Healthcheck triggered within Loxone Config
- [Audio] add Systemstatus Message if duplicate Airplay / Spotify-Connect devices in your network are detected
- [Audio] Audioserver starts a Pairing Window to allow Miniserver change. Audioserver must be rebootet and no Miniserver communication for 2 minutes. Then the Audioserver is in pairing mode for 30 minutes, after those 30mins, it is waiting for its Miniserver again. This should ease up the process of miniserver change without the need for a factory reset / new SD card for Audioserver
Fixed:
- [Audio] BG-I29401 fixed issue when rebooting AS, sometimes random Extension hang endless.
- [Audio] BG-I29347 fixed automatic Roomfav selection (if Roomfav n does not exist) failed in certain conditions
- [Audio] BG-I29274 fixed issue where removed NAS Folders did not remove Favorites pointing to them
- [Audio] BG-I29300 fixed Spotify ErrorTTS when account was taken over
- [Audio] BG-I28938 fixed crash at m3u/pls handling from Tunein
- [Audio] BG-I28852,BG-I28854 fixed change from (unavailable) Playlist to Radio did not work properly
- [Audio] BG-I28532 fixed issue where NAS content is not shown directly upon NAS folder add
- [Audio] BG-I28579 fixes unmuting Players of fixed group when switching from Spotify to radio
- [Audio] BG-I28444 fixed volume resets to default when switching from spotify to radio (grouped players only)
- [Audio] BG-I28505 fixed deadlock loop where all audio services keep restarting
- [Audio] BG-I28550 fixed Event Volumes on Audio Central
- [Audio] fixed healthcheck issue with Miniserver behind routing borders (VLAN’s, etc) showing non-pingable
- [Audio] Player does not follow linein to another AS linein without being paused in between
- [Audio] fixed issue with custom radio stations not able to be added
- [Audio] fixed crash in library scan for non-existent files
- [Audio] added correct timestamp of Last Config Timestamp in Admin Interface
- [Audio] fixed Issue with invalid/expired Certificates on Radio Streams
- [Audio] fixed Event Synchronisation among Audioservers
- [Audio] fixed crash in in certain conditions when doing a search for Music in our App
- [Audio] fix issue with Audioserver intercommunication stability
- [Audio] fixed Events being interrupted by Watchdog unintentionally (causing cropped Event playback)
- [Audio] fixed Custom URL Streams being interrupted in some cases
- [Audio] fixed incorrect playstate when changing from Spotify Connect to another source (like radio, linein)
- [Audio] fixed event stop can cause race conditions (ending up in players not continue to play after event) (stacked environments)
- [Audio] fixed ‘variable default volume” Player gets resetted to 0 after Spotify Connect ‘disconnect’ (stacked environments)
- [Audio] fixed Issue with Library Playback not working correctly
- [Audio] fixed resulting volume when Player gets started with Input ‘V’
- [Audio] fixed ‘fixed group pause’ on players with default volume ‘-1’ teared down to volume 0
- [Audio] fixed no sound output when switching from spotify to radio
- [Audio] Sync Event Volumes across Stack and fix ignoring minimum Event volumes
- [Audio] Volume & Event at the same time can interfere on output and causes event playback to be disrupted
- [Audio] fixed list of TreeTurbo devices not properly showing all devices discovered
- [Audio] fixed crashes due to raceconditions in Event Playback
Audioserver 2.8.7.4
NOTE: If a Miniserver Compact is installed with an Audioserver, Config version 14.3.7.4 Beta 1 or higher is required.
Fixed:
- Fix issue with extension launcher process could be started twice
- Fix issue with missing kernelupdate leading to spotify unplayable on Audioserver outputs
- Added Audio Testfiles into Library to easily identify right/left outputs
- Fix incorrect playstates from spotify (show paused whilst playing)
- EQ rebalanced for much better sound when a customer does not configure the EQ of a player
- Will only apply to players with all EQ Bands to 0 at the time of installation of this update
- Of course it will not change anything if there is already a custom setup
- Will only apply once, future updates or changing the EQ back to 0 will not lead to a change again
- Optimized PTP for larger loxone installations where a lot of ptp traffic is expected and could have negative effects on time synchronisation
Audioserver 2.7.12.14
NOTE: If a Miniserver Compact is installed with an stacked audio server, the Miniserver Compact must be at least on Loxone Config 13.2 Beta 3.
Features:
- Custom sound input on the Audio Player FunctionBlock:
To play back a freely definable MP3 file, triggered by logic or API command. - Standby consumption:
The currently very low stand-by consumption has been further improved. - Combination with the Miniserver Compact:
Especially in larger installations where several Miniserver Compact and Audioservers are used in combination, the new update ensures improved communication and stability for cross-device audio zones. - Stability:
Optimized caching and logging to create more memory for audio playback.
Improved synchronicity in cross-device playback via Tree Turbo (latencies < 1ms). - System Messages:
Displayed system messages now describe the error messages even better (Spotify reason for playback error, ….).
Audioserver 2.7.06.28
Audioserver 2.7.06.28
New
- Spotify Connect integration (all Audioserver players are visible and controllable by Spotify app),
which causes a few changes to previous known Spotify handling, using Connect standards:- the visible queue is limited to a maximum of 5 songs (2 previous, current, 2 next)
- the queue isn’t editable in any way out of the Loxone App. You can edit the queue in spotify App, changes will reflect shortly
- Shuffle acts as a Push button toggling between Shuffle and original context.Â
- Dynamic Grouping (static groups and single player grouping on the fly via App)
- Added Spotify Podcasts
- Added possibility to copy/paste Spotify playlist urls into the search box for playlist sharing
- Allow search for episodes and shows in Spotify
- Webadmin Interface: possibility to access admin interface of Audioserver via Miniserver proxy to have access on it when connecting externallyÂ
- Spotify: show the user’s collection (Songs that get tagged with the green heart within Spotify App)Â
- Add Spotify Connect visible/invisible mode via Expert Settings
Fixed
- fix: Spotify playurl/serviceplay command select correct user
- fix: Spotify saving a user’s collection content into a playlist
- fix: Spotify ratelimit messages do appear too often. Coupled with playback failed Error
- fix: Spotify stop playback if underlying account was deleted (BG-I17020)
- fix: Spotify playstates when transferring from/to spotify connect within a group (BG-I17033)
- fix: Spotify Player reverts to default volume when currently playing Spotify and play was triggered again via grouped play (Group Play, Central block) (BG-I17032)
- fix: Spotify health check is stopping music when lwsd restarts (due crash, … )
- fix: DynamicGroups double delete player group can cause crash if second command is seen as a create, fix: remove mute state from connect to sink as volume would also been sent too
- fix: DynamicGroups ungrouping while library was playing now correctly sets new source for players (BG-I17037)
- fix: Playback transition from/to linein can cause a stalled playback
- fix: Playback sink handle source changes always before volume changes & source change do not set pipeline to playing
- fix: Playback Event sound cropped
- fix: Playback sink does not recover from linein correctly causing the sink to struggle
- fix: Admin-Interface is not accessible to non-Admin Accounts anymore
- fix: resettodefault does not pause the player correctly (BG-I17106)
- fix: handle flac if it is tagged as octet-stream too
- fix: Airplay queue not showing correct metadata
- fix: Spotify playurl/serviceplay command select correct user
- fix: Spotify saving a user’s collection content into a playlist
- AUDIO1-I2623 fix: Qa fix when switching sources
- AUDIO1-I2581 fix: roomfav/play with volume behindÂ
- AUDIO1-T763 add confirmation dialog for factory reset via Admin InterfaceÂ
- BG-I15970 Linein Statusupdates other peers interpreted as own linein therefore overwritten their config
- BG-I15802 sort output of getroomfavs to reflect slot ordering, deduplicate roomfavchanged_eventsÂ
- BG-I15994 play Linein while in event
- BG-I15983 Linein Event did not evaluate Mute/Power or each Player
- BG-I15987 Library Play when currently spotify is playing
- BG-I15995 linein stopped but other AS is requesting stream
- BG-I16094 Spotify Resume Context at position fixed (allow higher difts)
- BG-I16080 Spotify click in queue entry may not trigger an action
- BG-I16094 Spotify play on fixed group 2 AS did not resume but start another track
- BG-I16093 Spotify playurl commandÂ
- BG-I15996 EQ Settings not taken over via “copy EQ to Player N”Â
- BG-I16242 When issuing Rtd trigger, Spotify did not recover as expected
- BG-I16242 When issuing Rtd, Spotify should not start playing if it is on the first roomfavorite slot
- BG-I16228 Linein as roomfav stops playing if clicking same roomfav more than once
- BG-I16275 Volume change on Airplay Device causes wrong metadata
- BG-I16294 avoid Qa flicker on transition to SpotifyÂ
- BG-I16286 Spotify to Airplay Transitions causing wrong Metadata displayed
Audioserver 2.7.01.10
Audioserver 2.7.01.10
New
- Volmode & fixed Volume from Loxone Config
Fixed
- Mastervolume scaling when starting at 0
- apply offset volume before maxvolume
- missing EOS signal to other AS
- spdif fixed volume control
- Maxvolume clipping at max, not scaling anymore
- handle Spotify error ‚bad gateway‘ and notify
- suppress events if player is playing and event Volume param is 0
- audio/X/stop causing other players in autogroup stopping too
- fix appending to queue causing wrong playback in stacked AS environments
- correct urlencode output to app for getroomfavs
- overall communication stability improved
Audioserver 2.6.12.3
Audioserver  2.6.12.3
Known Issues:
New
The focus of this Update is on increasing stability and usability:
- New software platform for better synchronicity
- Improvements for installations with multiple Audioservers
- New AirPlay 2 SDK version for better handling, especially with grouped outputs
- Increase in performance and responsiveness
- Improved performance when playing Spotify
What is a known issue?
We work continuously to correct any known bugs in our products and software. This page details a list of bugs and errors found that affect the performance and usability of the software.
In order for an error to count as a known issue, it must be a reproducible error that affects the operation of the Miniserver or Loxone Config.
Please note: We do not list every minor bug/error within Known Issues!
Product failures which are not known issues include:
- Failures of services such as Loxone Cloud Services where these are of short duration (<1 day)
- Minor errors which have no effect on the functionality of the software. These include, for example, minor display errors.
If you have discovered an error which you feel ought to be included in the Known Issues list, please contact our support team.