[SOLVED] Moode 8.3.8 upgrade => MPD Error

[bitlab]

There is a small bug in the post install of moode 8.3.8 related to camilladsp.

1. volume issues and message  
wrong alsa_cdsp config file (only on updated system, on fresh system this is fine):
You can fix  it yourself by running:
sudo cp /usr/share/moode-player/etc/alsa/conf.d/camilladsp.conf /etc/alsa/conf.d/

2. nginx configuration is broken; no pipeline editor:
as workarround editor the pipeline url  directly in your browser like:
http:://moode:15000/gui/index.html

[Tim Curtis]

In CamillaDSP Config a configuration file will be auto-patched to version 2 format when it selected and saved as the current config or (I think) when it's selected or checked in the file management section.

The auto patch only covers the following:

Code:

set volume_ramp_time = 150
delete enable_resampling
delete resampler_type
delete capture_samplerate

If a config is still flagged as invalid then some hand editing will prolly be needed along with a post to the CamillaDSP thread at diyAudio asking for some help.

Alternatively the config can just be recreated from scratch using the Pipeline editor.

Note that there is an option on CamillaDSP Config to download a set of version 2 sample configs for those that are using any.

I use ProtoDac, but with the new version 8.3.8, I have a lot of problems configuring CamillaDSP. The most annoying of all is the impossibility of using the Pipeline editor because when I launch it Camilla's page disappears and it is no longer possible to make changes to the configuration files.

I'm not seeing this issue on my end with 8.3.8.

When you say "new version 8.3.8" do you mean a fresh image or an in-place update applied to 8.3.7 release?

[Tim Curtis]

@the_bertrum @Tim Curtis the config patches are
only applied when a config is selected as current active. Patch is applied by moode software, not by the camilladsp software itself.

Yes I see that in the code. Makes sense to only do it that way.

[Tim Curtis]

There is a small bug in the post install of moode 8.3.8 related to camilladsp.

1. volume issues and message  
wrong alsa_cdsp config file (only on updated system, on fresh system this is fine):
You can fix  it yourself by running:
sudo cp /usr/share/moode-player/etc/alsa/conf.d/camilladsp.conf /etc/alsa/conf.d/

2. nginx configuration is broken; no pipeline editor:
as workarround editor the pipeline url  directly in your browser like:
http:://moode:15000/gui/index.html

After a quick test of in-place update over 8.3.7:

1. I can confirm that camilladsp.conf file not being updated due to bug in postinstall. There is also a bug in the Quick config dropdown that results in no sort or check mark for the selected config.

2. NGINX confs look fine after the update and no problems whatsoever with CamillaGUI

[Tim Curtis]

I have the same problem. I saw some errors related to invalid parameters, basically ramp_time is not valid on V2.
Checking the filesystem in /usr/share/camilladsp/configs I can see the "old" files and the new ones named like loudness.yml.dpkg-dist, this means that a new .deb package has been installed, with newer versions of the config files, but not overwriting the old ones. Of course the .dpkg-dist files are not loaded by Camilla. The package that manages/own those config files is moode-player itself, so it seems that the upgrade of moode-player.deb did not overwrite the old config files.

Then I proceeded to go to CamillaDSP config page (Configure->CamillaDSP) and at the very bottom I clicked on `Update`, it downloaded a bunch of V2-<profile> files, and those work out of the box, but I had the new V2 files, the old broken ones and the .dpkg-dist.

I tried copying loudness.yml.dpkg-dist to loudness.yml and that indeed works, so I assume that copying the .dpkg-dist files over the file with the same name, should fix the problem.

This one liner did the job, copying the old files in filename.old and the .dpkg-dist to the profile name

for p in *.dpkg-dist; do echo $p; prof=$(basename "$p" .dpkg-dist); echo $prof; cp "$prof" "${prof}.old"; cp "$p" "${prof}";  done

And it worked, after this I just did an rm *.old to clean up and that's it, now I have the "old" profiles working and the new V2 ones too.

There are still some leftovers, old profiles that have not been updated, so are not covered by the above command. These are 

• Polarity Inversion with VC.yml
  
• Volume Control.yml
  

and those can be deleted manually.

Another possible solution would be to move away the old configs and just download the new ones, dunno enough about the differences between, for example, loudness.yml and V2-Loudness.yml, though.

I kindly suggest to the developer of moode to keep this in account and maybe release a patch that, during the installation, fixes this issue.

If you are updating by removing the package locks and doing APT upgrade to grab whatever is new in our package repo then you will end up with breakage and will need to start with a fresh image.

The only supported method of updating is via the in-place update option on System Config.

[ECELO]

In CamillaDSP Config a configuration file will be auto-patched to version 2 format when it selected and saved as the current config or (I think) when it's selected or checked in the file management section.

The auto patch only covers the following:

Code:

set volume_ramp_time = 150
delete enable_resampling
delete resampler_type
delete capture_samplerate

If a config is still flagged as invalid then some hand editing will prolly be needed along with a post to the CamillaDSP thread at diyAudio asking for some help.

Alternatively the config can just be recreated from scratch using the Pipeline editor.

Note that there is an option on CamillaDSP Config to download a set of version 2 sample configs for those that are using any.

I use ProtoDac, but with the new version 8.3.8, I have a lot of problems configuring CamillaDSP. The most annoying of all is the impossibility of using the Pipeline editor because when I launch it Camilla's page disappears and it is no longer possible to make changes to the configuration files.

I'm not seeing this issue on my end with 8.3.8.

When you say "new version 8.3.8" do you mean a fresh image or an in-place update applied to 8.3.7 release?

a re-flash of the new image. I can enter the pipeline editor again only by completely deleting all the configuration files, both the old ones and those reloaded with the UPDATE function and marked V2

[Lalsacien]

Hello,

One more question please. Is it normal that some Camilla DSP file makes crash my listening and not other.

For example, I use V2-PEQ 10-Band file without problem when I change radio stations or music tracks. But when I change for example to V2-Loudness file AND when a song is playing there is no problem. But when I change for another radio channel or music track, then I can hear only 1 second music and then it stops with the message : MPD error Failed to open audio output.
To recover I have to return to the V2-PEQ 10-Band file.

The Camilla log gives me that :

2024-02-17 16:25:58.359483 INFO [src/bin.rs:683] CamillaDSP version 2.0.1
2024-02-17 16:25:58.359643 INFO [src/bin.rs:684] Running on linux, aarch64
2024-02-17 16:25:58.410109 INFO [src/alsadevice.rs:142] PB: Starting playback from Prepared state
2024-02-17 16:26:00.522922 INFO [src/bin.rs:383] Capture finished
2024-02-17 16:26:00.524104 INFO [src/bin.rs:366] Playback finished
2024-02-17 16:26:00.566884 INFO [src/bin.rs:683] CamillaDSP version 2.0.1
2024-02-17 16:26:00.566960 INFO [src/bin.rs:684] Running on linux, aarch64
2024-02-17 16:26:00.612994 INFO [src/alsadevice.rs:142] PB: Starting playback from Prepared state
2024-02-17 16:26:03.536513 INFO [src/bin.rs:383] Capture finished
2024-02-17 16:26:03.536771 INFO [src/bin.rs:366] Playback finished
2024-02-17 16:26:03.599281 INFO [src/bin.rs:683] CamillaDSP version 2.0.1
2024-02-17 16:26:03.599402 INFO [src/bin.rs:684] Running on linux, aarch64
2024-02-17 16:26:03.712462 INFO [src/alsadevice.rs:142] PB: Starting playback from Prepared state
2024-02-17 16:30:26.731113 INFO [src/loudness.rs:37] Create loudness filter
2024-02-17 16:30:26.731716 INFO [src/loudness.rs:37] Create loudness filter
2024-02-17 16:30:26.762569 INFO [src/alsadevice.rs:142] PB: Starting playback from Prepared state
2024-02-17 16:31:44.244282 INFO [src/bin.rs:366] Playback finished
2024-02-17 16:31:44.280615 INFO [src/bin.rs:683] CamillaDSP version 2.0.1
2024-02-17 16:31:44.280684 INFO [src/bin.rs:684] Running on linux, aarch64
2024-02-17 16:31:44.292950 INFO [src/loudness.rs:37] Create loudness filter
2024-02-17 16:31:44.293211 INFO [src/loudness.rs:37] Create loudness filter
2024-02-17 16:31:44.321454 INFO [src/alsadevice.rs:142] PB: Starting playback from Prepared state
CDSP Plugin WARN: IO Thread out of data.
CDSP Plugin WARN: IO Thread out of data.
CDSP Plugin WARN: IO Thread out of data.
CDSP Plugin WARN: IO Thread out of data.
CDSP Plugin WARN: IO Thread out of data.
CDSP Plugin WARN: IO Thread out of data.
CDSP Plugin ERROR: XRUN OCCURRED!
Feb 17 16:31 : output: Failed to play on "ALSA Default" (alsa): snd_pcm_writei() failed: Broken pipe
2024-02-17 16:31:44.926702 INFO [src/bin.rs:383] Capture finished
2024-02-17 16:31:45.004809 INFO [src/bin.rs:366] Playback finished
Feb 17 16:31 : exception: Failed to open audio output

any Idea ?

Many thanks for help
Regards
Lalsacien

[ECELO]

ECELO pid='52216' dateline='1708184048']

In CamillaDSP Config a configuration file will be auto-patched to version 2 format when it selected and saved as the current config or (I think) when it's selected or checked in the file management section.

The auto patch only covers the following:

Code:

set volume_ramp_time = 150
delete enable_resampling
delete resampler_type
delete capture_samplerate

If a config is still flagged as invalid then some hand editing will prolly be needed along with a post to the CamillaDSP thread at diyAudio asking for some help.

Alternatively the config can just be recreated from scratch using the Pipeline editor.

Note that there is an option on CamillaDSP Config to download a set of version 2 sample configs for those that are using any.

I use ProtoDac, but with the new version 8.3.8, I have a lot of problems configuring CamillaDSP. The most annoying of all is the impossibility of using the Pipeline editor because when I launch it Camilla's page disappears and it is no longer possible to make changes to the configuration files.

I'm not seeing this issue on my end with 8.3.8.

When you say "new version 8.3.8" do you mean a fresh image or an in-place update applied to 8.3.7 release?

a re-flash of the new image. I can enter the pipeline editor again only by completely deleting all the configuration files, both the old ones and those reloaded with the UPDATE function and marked V2

Hi Tim...I solved it. The damn Chrome cache!! I cleared the cache and everything was visible again. I'm sorry for the trouble. Now I warn the users of my FB group.

[Tim Curtis]

In CamillaDSP Config a configuration file will be auto-patched to version 2 format when it selected and saved as the current config or (I think) when it's selected or checked in the file management section.

The auto patch only covers the following:

Code:

set volume_ramp_time = 150
delete enable_resampling
delete resampler_type
delete capture_samplerate

If a config is still flagged as invalid then some hand editing will prolly be needed along with a post to the CamillaDSP thread at diyAudio asking for some help.

Alternatively the config can just be recreated from scratch using the Pipeline editor.

Note that there is an option on CamillaDSP Config to download a set of version 2 sample configs for those that are using any.

I use ProtoDac, but with the new version 8.3.8, I have a lot of problems configuring CamillaDSP. The most annoying of all is the impossibility of using the Pipeline editor because when I launch it Camilla's page disappears and it is no longer possible to make changes to the configuration files.

I'm not seeing this issue on my end with 8.3.8.

When you say "new version 8.3.8" do you mean a fresh image or an in-place update applied to 8.3.7 release?

a re-flash of the new image. I can enter the pipeline editor again only by completely deleting all the configuration files, both the old ones and those reloaded with the UPDATE function and marked V2

I'm not able to repro after a quick test with fresh image. Pipeline editor comes right up.

Maybe try clearing Browser cache.

[AkelGe]

I have the same problem. I saw some errors related to invalid parameters, basically ramp_time is not valid on V2.
Checking the filesystem in /usr/share/camilladsp/configs I can see the "old" files and the new ones named like loudness.yml.dpkg-dist, this means that a new .deb package has been installed, with newer versions of the config files, but not overwriting the old ones. Of course the .dpkg-dist files are not loaded by Camilla. The package that manages/own those config files is moode-player itself, so it seems that the upgrade of moode-player.deb did not overwrite the old config files.

Then I proceeded to go to CamillaDSP config page (Configure->CamillaDSP) and at the very bottom I clicked on `Update`, it downloaded a bunch of V2-<profile> files, and those work out of the box, but I had the new V2 files, the old broken ones and the .dpkg-dist.

I tried copying loudness.yml.dpkg-dist to loudness.yml and that indeed works, so I assume that copying the .dpkg-dist files over the file with the same name, should fix the problem.

This one liner did the job, copying the old files in filename.old and the .dpkg-dist to the profile name

for p in *.dpkg-dist; do echo $p; prof=$(basename "$p" .dpkg-dist); echo $prof; cp "$prof" "${prof}.old"; cp "$p" "${prof}";  done

And it worked, after this I just did an rm *.old to clean up and that's it, now I have the "old" profiles working and the new V2 ones too.

There are still some leftovers, old profiles that have not been updated, so are not covered by the above command. These are 

• Polarity Inversion with VC.yml
  
• Volume Control.yml
  

and those can be deleted manually.

Another possible solution would be to move away the old configs and just download the new ones, dunno enough about the differences between, for example, loudness.yml and V2-Loudness.yml, though.

I kindly suggest to the developer of moode to keep this in account and maybe release a patch that, during the installation, fixes this issue.

If you are updating by removing the package locks and doing APT upgrade to grab whatever is new in our package repo then you will end up with breakage and will need to start with a fresh image.

The only supported method of updating is via the in-place update option on System Config.

I know that I can't update manually, during the last update moode-player.deb has been updated, and it installed new yaml files, but not overwriting the old one, just adding the new ones as .dpkg-dist. 
I am sure you are aware that packages in Debian can be installed passing -o Dpkg::Options::="--force-confnew" to override the old config file and install a new one. Installing moode-player with that option would have not caused problems, apart for the CamillaDSP profiles created by the user.