This is another sizable release that includes some major new features as well as many bug fixes and improvements.
The biggest addition is the optional web UI and websocket API. It's designed to be used as a second screen for informational purposes and not to be a full-fledged desktop application, so functionality is limited.
Using the --web cli argument, an internal web server that listens at 0.0.0.0:9888, by default, will be started. The web UI can be found at http://<ip>:9888 and the websocket server at http://<ip>:9888/ws.
NOTE: The web server has no authentication. Any devices that can connect and interact with websockets can interact with the server. To help reduce security issues, the server will ignore any messages that do not fit the shape of any predefined actions and the data received by the API is only used with the player or the Qobuz API to retreive data. In addition, files are only served from embedded within the binary and the server does not interact with the file system at all.
Additional changes include:
Reducing the size of the data objects used internally by the player. This lowers memory usage and makes handling data more efficient. It's also a potential first step to introducing other services.
Add actions for retrieving data, not just controlling player. This helps remove the API client as a dependency in other modules while giving a uniform way for external modules to retreive information needed. This also allows data requested by one client to be sent back to that client. Not all messages are notifications.
This is another sizable release that includes some major new features as well as many bug fixes and improvements.
The biggest addition is the optional web UI and websocket API. It's designed to be used as a second screen for informational purposes and not to be a full-fledged desktop application, so functionality is limited.
Using the
--webcli argument, an internal web server that listens at0.0.0.0:9888, by default, will be started. The web UI can be found athttp://<ip>:9888and the websocket server athttp://<ip>:9888/ws.NOTE: The web server has no authentication. Any devices that can connect and interact with websockets can interact with the server. To help reduce security issues, the server will ignore any messages that do not fit the shape of any predefined actions and the data received by the API is only used with the player or the Qobuz API to retreive data. In addition, files are only served from embedded within the binary and the server does not interact with the file system at all.
Additional changes include: