Replies: 5 comments 12 replies
-
|
looks great a couple of thoughts
|
Beta Was this translation helpful? Give feedback.
-
|
There will be a proper openapi docs for all of these, with schemas for both success and error responses. Although there isn't so much that can fail, short of the device hanging or being disconnected in the middle of an update. Good call on Updates are applied sequentially, the entire request is validated at first and the whole operation bailing out at the first (hardware) error. I haven't seen any device error feedback outside of the "this command opcode isn't recognized". Most parameters are blindly writing stuff to the dsp's memory - if values are out of range the device behaviour is undefined. It's also going to let you do Bad Things(tm) if you send concurrent update requests that mutate the device state in conflicting ways, there will need to be some locking at some point but it gets tedious with the plugin app capable of being connected. Rolling anything back isn't possible until enough data is kept to know what the previous state was. |
Beta Was this translation helpful? Give feedback.
-
|
This doc should be a little easier to read https://minidsp-rs.mrene.workers.dev/ |
Beta Was this translation helpful? Give feedback.
-
|
Websocket is implemented, streaming changes done through the IR remote (due to some protocol differences, this won't show updates done through the plugin app, or through minidsp-rs) |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Do you have any idea what is it related to? Tried with two other versions of websocat with no luck. I also noticed another issue:
When service is started with connected minidsp, then I've got error: |
Beta Was this translation helpful? Give feedback.
-
|
These were implemented after 0.1.0-pre1, try this build https://github.com/mrene/minidsp-rs/releases/tag/v0.1.0-pre2 The issue of using minidsp while the service is running is also fixed (it didn't have world read/write permissions). |
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.
-
|
Hey! That looks like an interesting setup. Are you just polling for the current master volume (and source, preset, mute)? These get asynchronous device events, so it's possible to get them without actively polling the device. For current meter levels (for inputs, outputs, compressors), these can be polled to display the amount of signal going through the device (that's what the app is polling a few times a second, when you have the associated section of the plugin opened) I was planning on adding these as websocket streams, so a webapp could connect, indicate what its interested in, and get async events. I could put it in the command line tool as well, which you would call as something like Feel free to open an issue for dirac support, I've seen some forum threads that have the address so it should be quick to add. One more thing, could you send me the output of It'll look like this: |
Beta Was this translation helpful? Give feedback.
-
|
Hi,
Yes, very basic python script to run separate thread and send simple "minidsp" command few times per second to retrieve the current status. It's cpu-consuming :)
That sounds brilliant! Looking forward for such functionality in your further versions
I was inspired with this project: MiniDSP Preamp but Andrej used separate microcontroller to drive the OLED display. Also some values have been stored locally without minidsp feedback (only read once on startup).
I'll do that :)
Here's the response: Maybe this link could be also useful (info about command/response for minidsp settings)
|
Beta Was this translation helpful? Give feedback.
-
|
@kukocz I want to achieve exactly the same thing! Would you be willing to share? |
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.
-
|
The URL is transport-dependent. If it's via USB it'll represent the device path in an OS-specific way. The information includes the device's serial number, which should, when not garbled and reset to 65535 by random bugs, be somewhat reliable. |
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.
-
|
the Unix socket is the exact same http server as the tcp one, if you detect a file present and can connect to it, it's easier to connect via Unix. This is the default command line behaviour too, it makes it easier to work with widg devices because they only send advertisement packets so often. |
Beta Was this translation helpful? Give feedback.
-
|
This crude example taken from websocket-client's docs work: import socket
from websocket import create_connection
def main():
my_socket = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM)
my_socket.connect("/tmp/minidsp.sock")
ws = create_connection("ws:https://localhost/devices/0?levels=true", socket = my_socket)
while True:
try:
msg = ws.recv()
print(msg)
except Exception as e:
print(e)
if __name__ == "__main__":
main()Prints out: {"master":{"preset":0,"source":"Toslink","volume":-34.0,"mute":false},"input_levels":[-131.49413,-131.49413],"output_levels":[-166.56247,-166.24278,-120.0,-120.0]}
{"master":{},"input_levels":[-131.47736,-131.47736],"output_levels":[-166.51753,-166.20457,-120.0,-120.0]}
{"master":{},"input_levels":[-131.4203,-131.4203],"output_levels":[-166.42278,-166.11952,-120.0,-120.0]}
{"master":{},"input_levels":[-131.40881,-131.40881],"output_levels":[-166.39104,-166.09303,-120.0,-120.0]} |
Beta Was this translation helpful? Give feedback.
-
|
ok thanks, I raised #134 to cover the issue I was seeing as it seems more like some bug to me |
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
minidspddaemon replacesminidsp serverwith 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.serviceis 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.mdfor a summary of available APIs.On unix platforms, the
minidspcommand 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