You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the request to store configurations for standalone mode, I say that it would be possible
since related protocols are cleared and already implemented. However, I still have issue blocker.
The configuration of source and frequency of sampling clock for standalone mode is done
by protocol extension defined by TCAT. You can see implementation under libs/dice/protocols/src/tcat/extension/standalone_section.rs:
You can also see implementation for below options specific to ProFire 2626 under libs/dice/protocols/src/maudio.rs:
assignment of main knob
mode of optical interface B
mode of converter
You can see below ALSA control elements when executing the program:
standalone-clock-source
standalone-spdif-high-rate
standalone-adat-mode
standalone-word-clock-mode
standalone-word-clock-rate-numerator
standalone-word-clock-rate-denominator
standalone-internal-clock-rate
master-knob-target
optical-iface-b-mode
standalone-converter-mode
The above configurations can be stored to on-board flash memory by the TCAT protocol extension. You can
see implementation about it under libs/dice/protocols/src/tcat/extension/cmd_section.rs.
The issue blocker is the way for userspace applications to perform the store protocol. In the design of
ALSA control core, boolean type of control element just performs like toggle button, while stateless push
button is required just to trigger the store operation. In the reason, at present, it's impossible to keep the
configuration done via the control elements for next boot yet.
Do you think it would be possible to work out a way to save settings to the Profire 2626? I've always wanted to use it as a standalone converter.
The option was always greyed out in ffado-mixer.
Being able to set the clock source and sample rate would be most welcome.
The text was updated successfully, but these errors were encountered: