UI for virtual soundcard

[teodly]

Currently we have no UI, all parameters are set by environment variables and command line arguments.

What kind of UI do you want?

Possible inspirations:

• CLI:
  • jack_control
• GUI:
  • qjackctl (1, 2)
  • Cadence
  • Dante Virtual Soundcard

Personally, I would start with exposing all parameters in configuration file and making a simple command line tool like jack_control with commands:

• start/stop the PipeWire virtual device (it works as a regular process)
• enable/disable the ALSA module for all apps (by modifying $HOME/.asoundrc)
• add/remove the Inferno ALSA device to/from PipeWire or PulseAudio graph
• start/stop the JACK audio server with Inferno ALSA module backend
• open configuration files in editor
• view logs / status

Then, a simple GUI app could be made with mode selection and start/stop buttons that would execute the scripts.

[ankostis]

I'd vote for extending existing projects, specifically

• as home-assistant add-on+integration,
• music-assistant plugin (for DC),
• music-assistant player for DANTE streaming-output
• music-assistant provider for DANTE streaming-input (if that would make sense).

[DrEVILish]

Would love a simple CLI tool, list current settings, list avaliable settings.
Ceph has a great set,get interface.

inferno config get property -> property
inferno config set property value
inferno config ls
inferno status
inferno config export filepath
inferno log (tail -f log file equivilant)
inferno jack start/stop/status
inferno pipewire start/stop/status

[DrEVILish]

A simple TUI could be generated using
https://en.wikibooks.org/wiki/Bash_Shell_Scripting/Whiptail
Proxmox VE Helper Scripts uses it nicely to setup some install and config parameters.
Seems to be built into bash as well.

[wargreen]

I think that un integration with a systemd service (if needed), launched by D-Bus, as jackd work can be a good way.
With that, we can have multiple [T|G]UI and make it launched by anything that ask for it.