CamillaDSP IIR format output?

  • Post hidden due to user being banned.
Although I have a couple of convolution engines at hand, I might be interested in trying CamillaDSP for FIR room correction on MacOS... Is there a Users Doc that describes straight forward steps for installation and an example filter chain for a vanilla 2 channel stereo FIR convolution?
 
  • Post hidden due to user being banned.
  • Post hidden due to user being banned.
  • Post hidden due to user being banned.
  • Post hidden due to user being banned.
  • Post hidden due to user being banned.
The random digits are snakyaml's representer getting a bit over-enthusiastic with doubles. I looked at replacing its numeric representer but it was a bit of a faff so I didn't bother :)

Your file is not valid YAML, the error messages are spectacularly unhelpful but the problem is an extra space in front of the label for the first filter.
 
  • Post hidden due to user being banned.
Your file is not valid YAML, the error messages are spectacularly unhelpful but the problem is an extra space in front of the label for the first filter.
What the heck kind of parser worries about spaces... Come on CamillaDSP give me a break... OMeta anyone?

@TNT had said "If you don't fancy installing things etc perhaps use one of one of the packages that is delivered with CDSP integrated is a way to do it e.g, in Moode."

No worries, been using one version or another of Nix since the early 80's... AT&T Sys V + BSD enhancements anyone?
 
Last edited:
YAML uses spaces for nesting, like Python, so that's a feature of the configuration file format rather than CamillaDSP.
 
  • Post hidden due to user being banned.
It just seems silly that in this day and age we have off-side languages where strict formatting is for "human readability"... That's what parsers, pritty-printers, browsers and xtanslation utilities are for... If you don't like my style of writing a program then just whip out your favorite TXL or browser and change the "formatting" to your taste... Been smalltalking with a lisp since the late 70s... Not much new in hardware or software in the last 50 years... Just smaller and faster... And a lot of bad ideas codified by the likes of Micro$oft and others...

White space... Three too many, four not enough? Lol...
 
Last edited:
  • Post hidden due to user being banned.
Could the Model field which currently is set to Filters be able to be overwritten so that the input is used instead of filter_1: , filter_2: . i.e. if it is set to Right Bass then the filter set is Right_Bass_1: , Right_Bass_2: etc.
REW CamillaDSP Equaliser.jpg
 
Could the Model field which currently is set to Filters be able to be overwritten so that the input is used instead of filter_1: , filter_2: . i.e. if it is set to Right Bass then the filter set is Right_Bass_1: , Right_Bass_2: etc.
No, but REW can prompt for a label to use whenever CamillaDSP filters are saved. I have updated the V5.20.14 early access builds to add that.
 
  • Like
Reactions: TNT
No, but REW can prompt for a label to use whenever CamillaDSP filters are saved. I have updated the V5.20.14 early access builds to add that.
Excellent, it does ask now.

I have attached a .mdat file that says it is 96 kHz file but when I select EQ and then pick CamillaDSP as Equaliser it says Equaliser: CamillaDSP(48kHz) - see attached screengrab, the REW measurement screen shows file details at bottom left and top right.
 

Attachments

  • Nov 1 M150R 20-500 02.zip
    Nov 1 M150R 20-500 02.zip
    105 KB · Views: 59
  • REW 96kHz file showing as 48kHz in CDSP EQ.jpg
    REW 96kHz file showing as 48kHz in CDSP EQ.jpg
    193.7 KB · Views: 90
  • Post hidden due to user being banned.
Excellent, it does ask now.

I have attached a .mdat file that says it is 96 kHz file but when I select EQ and then pick CamillaDSP as Equaliser it says Equaliser: CamillaDSP(48kHz) - see attached screengrab, the REW measurement screen shows file details at bottom left and top right.
It's actually a 6 kHz measurement. The Decimate IR Analysis preference allows REW to reduce the sample rate of measurements made over a limited frequency range to speed up processing and reduce storage. A 500 Hz measurement really doesn't need 96 kHz sampling, but you can turn that option off if you wish.

1669808224229.png
 
  • Post hidden due to user being banned.
Back
Top