Audioserver Changelog

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:

2022_01_13

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.