Dynamic changes to Camilladsp pipeline problem

[tonywsea]

Hello,

I have been experiencing problems with changes made in the pipeline editor that are not taking effect in the dsp.

Background is I am using dsp pipelines to split 2 to 4 channels, and then using HP/LP to create temporary crossover, delaying thje HP channels 5ms to time-align with subwoofer, then recombining 4-2 channels.

The symptom is that when making dynamic changes in the editor, such as mute a channel for testing, or changing the delay, it seems to work if there is a song currently playing, but when starting a new song, the changes are lost.

What I have learned is that both the Apply automatically and Save automatically must be checked, AND the default config file in the Moode Audio settings must be the same config, rather than any default config that may be set up - e.g. Flat.yml.

The reason why seems to be that dynamic changes are being saved to the configuration file correctly, but that Moode re-loads the default configuration when starting each song, thus throwing away the currently loaded dsp confiiguration if the default is not set to the same as the pipeline editor.

A secondary symptom is that when the new song plays and I notice the change has been lost, sometimes I can press the load config button in Shortcuts and it will activate my changes.  Probably this is because it is overriding the Moode default config temporarily until next song plays.  I would say this symptom is not reliably reproducible.

It's my lack of knowledge that has had me struggling with this for a couple of months.  Maybe the documentation could be updated to raise awareness of this procedure. Also, maybe Moode Audio tab gui could have some narrative related to this, and/or a checkbox to not override current dsp configuration when starting a new song. The developers will know the correct way to handle this.

As an aside, the same issue occurs in Volumio within Fusiondsp.

If my assessment is correct or not, please let me know any of your thoughts.

Cheers.

[Tim Curtis]

I don't quite understand your usage scenario but The Pipeline Editor is part of CamillaDSP and not moode so any issues with the editor need to be reported to the main CamillaDSP Thread at diyAudio.

Moode's main role is to allow you to specify via the CamillaDSP Config screen which configuration file to use for "Signal processing" and to provide a convenient way via the "Default device options" toggle  to make use of the audio output device specified in Audio Config.

These are static configuration steps. There is no dynamic reloading of configs being done by moode.

If you can use one of the built-in configurations for example the Flat config to demonstrate your issues then post the exact steps and I'll try a repro on my end.

[bitlab]

Some direction appying and saving the pipeline:

• Assume that in the moode config the camilla expert mode is off.
  
• Select the camilla configuration you want to use from the moode camilladsp configaration page (or if one already active, you can use the quick menu cdsp cfg selector on the moode main screen). 
  
• (Don't use the shortcuts from the CamillaDSP pipeline editor, mooOde and CDSP will get out off sync concerning what is the active configuration file)
  
• (Same reason to don't use the the load config from the Files menu in expert mode)
  
• (When expert mode is used, don't manage what the active configuration is from the pipeline edtior, but use moode configuration for it).
  
• Open the pipeline edtior'
  
• Make your changes
  
• On the let side:
  
• Wen no music is playing you will notice that only 'save to file is available (the used configuration file is just on top of it.)
  
• When music is playing press Apply & Save to apply the changed and make it persistent. Only apply will not make it persist on on restart.
  
• Allternative, if you prefer, you can apply the automatic apply & save check boxes. 
  

This apply vs save behaviour, but just the way CamillaDSP and the CamillaDSP configuration edtior works.
Only for moOde the special case it that camilladsp is also quit, when the music stops (or sample rate/bit depth is changed).

The confusion about where to activate the config and get out of sync is indeed confusing and could be improved. That has historical reasons, but I will spare you that story ;-)

[tonywsea]

Thank you Tim.  I'll work through these steps in the next while.  I realize that I am going further than most.  But the dydnamic change capability is very useful to compare different filters, conv files, and to use for measurements with REW. There may not be a lot of people aware of this functionality, So I'm really happy to get this resolved.

I'll post back if I uncover any further information of value.

Regards
Tony