01-14-2024, 04:26 AM
The 0.4.0 version of mpd2cdspvolume is for Camilla 2 and upcoming moOde 8.3.8. It hasn't been tested with Camilla 1x but it seems like you have it working.
I've experienced some glitches when Airplay 2 initially connects to moOde/Camilla but usually stop/play on airplay client remedies that. I haven't done any debugging but I suspect the additional latency when camilla is in the pipeline is a factor.
The Volume type options:
- Software, Hardware, Fixed (0dB) are for controlling MPD player volume.
- Null and CamillaDSP are for controlling volume using another application. Null is where MPD outputs 0dB but still emits volume change events so another application can process them. Volume type CamillaDSP uses Null internally.
Volume type is automatically switched to "CamillaDSP" when CamillaDSP is enabled and the configuration contains a volume filter. You can override this by manually changing Volume type.
CamillaDSP 2 always maintains an internal volume filter that defaults to 0dB. There is no need to explicitly define a Volume filter in the config unless special capabilities are needed like a fader.
We are still testing CamillaDSP 2 and I'm not sure yet whether the automatic Volume type switch will remain. It could end up being removed in favor of leaving it up to user to manually set the Volume type.
Be **very careful** about experimenting with untested package combinations especially if they involve volume handling. The 0.4.0 version of mpd2cdspvolume for example has a bug that causes unintentional 0dB volume with CamillaDSP 2. A fix is in the works but it hasn't been tested yet.
I've experienced some glitches when Airplay 2 initially connects to moOde/Camilla but usually stop/play on airplay client remedies that. I haven't done any debugging but I suspect the additional latency when camilla is in the pipeline is a factor.
The Volume type options:
- Software, Hardware, Fixed (0dB) are for controlling MPD player volume.
- Null and CamillaDSP are for controlling volume using another application. Null is where MPD outputs 0dB but still emits volume change events so another application can process them. Volume type CamillaDSP uses Null internally.
Volume type is automatically switched to "CamillaDSP" when CamillaDSP is enabled and the configuration contains a volume filter. You can override this by manually changing Volume type.
CamillaDSP 2 always maintains an internal volume filter that defaults to 0dB. There is no need to explicitly define a Volume filter in the config unless special capabilities are needed like a fader.
We are still testing CamillaDSP 2 and I'm not sure yet whether the automatic Volume type switch will remain. It could end up being removed in favor of leaving it up to user to manually set the Volume type.
Be **very careful** about experimenting with untested package combinations especially if they involve volume handling. The 0.4.0 version of mpd2cdspvolume for example has a bug that causes unintentional 0dB volume with CamillaDSP 2. A fix is in the works but it hasn't been tested yet.
