Replies: 5 comments 12 replies
-
looks great a couple of thoughts
|
Beta Was this translation helpful? Give feedback.
-
Hi mrene. You've done really great job! What is interesting, when using minidsp server mode and connecting native desktop app - volume is being updated continuously with no effect on CPU on minidsp server side. Is there any way to set up server mode with continuous reading (at 5-10 times per second) which could be read from the pipeline and processed by another script (i.e. display control)? As I'm using DDRC-24 with Dirac Live - it would be great to have possibility to control DL status (on/off) via command line. Best Regards! |
Beta Was this translation helpful? Give feedback.
-
the example response in in https://minidsp-rs.pages.dev/daemon/http#1-list-available-devices includes where does that name come from? i don't see it mentioned anywhere else context here being thinking about how it will expose multiple connected devices (and whether there is some reliable name or id I can refer to) |
Beta Was this translation helpful? Give feedback.
-
is it expected to be possible to use the websocket over the unix socket or just the http based api? |
Beta Was this translation helpful? Give feedback.
-
Since it wasn't a success to run the http server from windows, I've switched to Linux. It all works fine (after building inside my volumio RPI4), however after some time (it varies between 30 min and several hours) the http connection times out:
System info: Edit: |
Beta Was this translation helpful? Give feedback.
-
This is a pre-release of the next version.
Main highlights
minidspd
daemon replacesminidsp server
with a configurable serviceWhen using the debian package, a default configuration is installed at
/etc/minidsp/config.toml
. This configuration only listens on 127.0.0.1 and can be edited to expose the api or the plugin-compatible server to the local network.The daemon will auto-discover WI-DGs on the local network, no further configuration is necessary to use these.
minidsp.service
is automatically enabled and started on debian-based platformsAn HTTP API is now available
The default configuration automatically listens on 127.0.0.1:5380, and on /tmp/minidsp.sock (for unix platforms). See
README-API.md
for a summary of available APIs.On unix platforms, the
minidsp
command line app detects the locally running service and automatically uses itNo more errors because the USB device is already in used by the server component.
New devices supported
The miniSHARC 4x8 is now auto-detected and supports the full feature set.
Other devices supported in this list will work but only allow changing the master status (config preset, source, master volume & mute)
This discussion was created from the release v0.1.0-pre1.
Beta Was this translation helpful? Give feedback.
All reactions