Moode Forum
Camilla DSP side effect - Printable Version

+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: Camilla DSP side effect (/showthread.php?tid=6257)

Pages: 1 2

Camilla DSP side effect - Tom.O - 02-25-2024

In the new moode audio version when I open GUI mode I got config error.
It seems that Camilla was updated but GUI comes from previous version. As consequence it tries to add old incompatible fields into config file causing errors. It happen also after clear installation.


  1. Issue is caused by CDSP config error
    ✗ Configuration is not valid
    Invalid config file!
    devices: unknown field 
    enable_resampling


  2. , expected one of 
    samplerate

  3. , 
    chunksize, queuelimit
  4. , silence_threshold, silence_timeout, capture, playback, enable_rate_adjust, target_level, adjust_period, resampler, capture_samplerate, stop_on_rate_change, rate_measure_interval, volume_ramp_time at line 14 column 3


RE: Camilla DSP side effect - bitlab - 02-25-2024

@Tom.O you can check a the camilladsp pipeline editor if you have the correct version.
Open the pipeline editor and notice the version numbers in left lower corner.
backend 2.0.0; that means that you have the new pipeline editor gui. Version of CamillaDSP is only shown when it is active.

Make sure you have first activated the camilladsp config in moode settings(this will apply patches if needed).

RE: Camilla DSP side effect - Tim Curtis - 02-25-2024

Yes, set "Signal processing" to your selected config and then SAVE. The config file will be patched to update it to CamillaDSP version 2.

If this does not work then post your config file.

RE: Camilla DSP side effect - Tom.O - 02-26-2024

(02-25-2024, 11:01 AM)Tim Curtis Wrote: Yes, set "Signal processing" to your selected config and then SAVE. The config file will be patched to update it to CamillaDSP version 2.

If this does not work then post your config file.

Issue is related to Safari browser.
It seems that editing config using Chrome works OK.
This configuration is causing an error. I just selected the default configuration and changed the sample rate

description: null
devices:
  adjust_period: 3
  capture:
    channels: 2
    extra_samples: 0
    filename: /path/to/file
    format: S16LE
    read_bytes: 0
    skip_bytes: 0
    type: File
  capture_samplerate: 44100
  chunksize: 1024
  enable_rate_adjust: false
  enable_resampling: false
  playback:
    channels: 2
    device: hw:0
    format: S16LE
    type: Alsa
  queuelimit: 4
  rate_measure_interval: 1
  resampler_type: FastAsync
  samplerate: 44100
  silence_threshold: 0
  silence_timeout: 0
  stop_on_rate_change: false
  target_level: 1024
  volume_ramp_time: null
filters: {}
mixers:
  Unnamed Mixer 1:
    channels:
      in: 2
      out: 2
    description: null
    mapping:
    - dest: 0
      mute: false
      sources:
      - channel: 0
        gain: 0
        inverted: false
        mute: false
        scale: null
pipeline: []
processors: null
title: null

RE: Camilla DSP side effect - Tom.O - 02-27-2024

(02-25-2024, 11:01 AM)Tim Curtis Wrote: Yes, set "Signal processing" to your selected config and then SAVE. The config file will be patched to update it to CamillaDSP version 2.

If this does not work then post your config file.

I cleared browser cache it it is solved.
Without this action I could still see the old UI or black screen.

RE: Camilla DSP side effect - Tim Curtis - 02-27-2024

Good to hear its working :-)

RE: Camilla DSP side effect - brissoukun - 03-06-2024

Hi everyone and Tim,

Many thanks as always for working hard on Moode.
Please allow me to get into the thread as I updated the install today and I have similar issue that the one mentioned here...

When I open the pipeline editor, I am getting the error:
Additional properties are not allowed ('volume_ramp_time' was unexpected)

Now, I tried different browsers and I am getting the same issue.
One thing that attracts my attention is that the different versions in the bottom left looks like this:

CamillaDSP 2.0.1 / pyCamillaDSP 1.0.0 / Backend 1.0.1

Refering to what @bitlab mentioned before, the Backend should be 2?

Please let me know if I should something specific to correct things.

RE: Camilla DSP side effect - Tim Curtis - 03-06-2024

What does the update log show?

Code:
moodeutl --updlog


RE: Camilla DSP side effect - brissoukun - 03-07-2024

Hi Tim,

Many thanks for your time and checking this issue with me. :-)

This is what I am seeing when issuing the comand:

pi@moode:~ $ moodeutl --updlog
20240306 205022 updater: Start 2024-02-23 update for moOde
20240306 205022 updater: ** Step 01-31: Remove package hold
20240306 205023 updater: ** Step 02-31: Update package list
20240306 205037 updater: ** Step 03-31: Install timesyncd
20240306 205039 updater: ** Step 04-31: Update Linux kernel to 6.1.21
20240306 205039 updater: ** - Kernel is current, no update required
20240306 205039 updater: ** Step 05-31: Install moode-player=8.3.9-1moode1
20240306 205050 updater: ** Step 06-31: Install bluez-alsa-utils=4.1.0-2moode2
20240306 205054 updater: ** Step 07-31: Install libasound2-plugin-bluez=4.1.0-2moode2
20240306 205101 updater: ** Step 08-31: Install camilladsp=2.0.1-1moode1
20240306 205112 updater: ** Step 008-31: Apply package hold
20240306 205112 updater: ** Step 0008-31: Post-install cleanup
20240306 205113 updater: ** Step 00008-31: Sync changes to disk
20240306 205113 updater: Finish 2024-02-23 update for moOde
20240306 205113 updater: Update installed, restart required

Let me know if I should check something else.
Cheers!

RE: Camilla DSP side effect - Tim Curtis - 03-07-2024

Looks like some breakage in the install script. I'll investigate.