Using DC to change settings

[MeestorX]

How much is known regarding using DC to change inferno settings like latency, bit rate/depth, etc? Has this protocol already been sniffed in the netaudio library?

[teodly]

Yes, according to their README it is already reverse engineered.

However, changing most settings requires device restart. Exceptions:

• bit depth, which is merely a hint and will be negotiated with peer devices anyway
• TX_LATENCY_NS, which is only a metadata advertised in mDNS, however, to make other devices reestablish connections with different latency, our device should be restarted too.

The remaining question is how to handle device restarts gracefully in alsa_pcm_inferno. We can just return error as if audio device was unplugged and wait for the host application to restart it. This would result in less-than-ideal UX, but is probably the only option when changing the sample rate. Probably we can assume that, in unattended systems, an auto-recovery mechanism is implemented anyway.

[DrEVILish]

Virtual Plug, replug would be sensible. I would for client side of long running "apps" build an inferno detector if the flame goes out wait then restoke the fire. I'm kinda working on something in my spare spare time, when not playing with things more fun, that would do something like this.

[teodly]

Have you seen #2 ? I was thinking of creating kind of supervisor, too. Haven't started working on this at all so feel free to start. The only thing I request is don't make it Electron app.

[MeestorX]

Any more thought on how this could be implented? It would be great to be able to set everything in DC.