It's somewhat arbitrary, but chosen so that the range doesn't get too large. It would be easy to allow -100 for example, but that larger range makes it more difficult to do small adjustments.Why is the lower limit at -51dB?
I could make it configurable.
I could make it configurable.
That would be great. I normally just need a range of 25 to 30 dB.
Min and max value would be perfekt from my point of view.
Thanks for the clarification.It's somewhat arbitrary, but chosen so that the range doesn't get too large
Currently I'm developing some home assistant integration, where the volume range needs to be mapped to 0..1
If -51 is a constant value, I could also hardcode that.
Would be great.I could make it configurable.
Then I would appreciate extending the API to request current limits.
Like http://<host>/api/getparam/volumerangedb
Btw...
Calling http://host/api/getparam/signalrangedb returns a 500 error on my instance
Also cant see any related entry in the log file.
To clarify, the -51 to 0 dB limit exists only in the gui, to make the slider easier to use. Camilladsp itself allows -150 to +50 dB. I mean to make the limits in the gui configurable, so anyone that wants a different range for that slider can customize it.
It's possible to restrict the max allowed volume in a camilladsp config, from +50 to something lower. When using that, camilladsp still accepts -150 to +50, but the applied volume setting won't exceed the given max. The lower limit is fixed at -150.
It's possible to restrict the max allowed volume in a camilladsp config, from +50 to something lower. When using that, camilladsp still accepts -150 to +50, but the applied volume setting won't exceed the given max. The lower limit is fixed at -150.
I'll take a look. Was there nothing interesting in the gui backend logs?Calling http://host/api/getparam/signalrangedb returns a 500 error on my instance
I mean to make the limits in the gui configurable, so anyone that wants a different range for that slider can customize it.
Yes, that’s, what I meant too 😉
Configure the min and max value for the slider in the gui.
Last edited:
To clarify, the -51 to 0 dB limit exists only in the gui, to make the slider easier to use. Camilladsp itself allows -150 to +50 dB. I mean to make the limits in the gui configurable, so anyone that wants a different range for that slider can customize it.
Henrik, while you are in the GUI, could you make the digits for volume in the display a bit bigger ? - in the pic could the -46 be a bit bigger and therefore easier to read on a display.
There is nothing at all in the backend logs.Was there nothing interesting in the gui backend logs?
First it was set to log to camilladsp.log:
log_file: "~/camilladsp/camilladsp.log"
Nothing was added.
Then I tried setting a dedicated log file for backend:
log_file: "~/camilladsp/camillagui.log"
After restarting backend, no file was created.
Creating an empty one and restarting backend again, resulted in an empty log file.
Even setting an absolute path did not change anything.
Should there be at least some status/debug information in it?
Used versions are:
CamillaDSP 2.0.3
pyCamillaDSP 2.0.2
Backend 2.1.1
Help with my first config file
My first goal is to run camillaDSP and GUI for that I need a valid config file.I just want to be able to play some music from tidal on my windows 11 laptop run it through CamillaDSP and get sound out of my laptop speakers.
next step will be to make a bass boost just to try out a filer.
When that is done, I can move on to play with my new MOTU 5.
So, how does a minimum 2-channel setup looks like?
Hi Martin
In my case: works as it should 😉
I am not sure… I just installed everything with the setup scripts, without any self configured config files… startet the gui and did all setup in the gui. This file i saved and made it as standard to load on startup.My first goal is to run camillaDSP and GUI for that I need a valid config file.
In my case: works as it should 😉
If you hit "New blank config" button on the Files tab and then fill in your specifics in the Devices tab - you are good to go ;-)
//
//
Hi all,
I was just wondering, where would be the best place to make some constructive recommendations to improve the software GUI, and useability?
I was just wondering, where would be the best place to make some constructive recommendations to improve the software GUI, and useability?
Is the scripts you have used?I am not sure… I just installed everything with the setup scripts
https://github.com/HEnquist/camilladsp-setupscripts
Here I think!
Either way works 🙂Or with proper tracking and dedicated discussion https://github.com/HEnquist/camillagui/issues
I have the UI up and running 😊
In the UI I created a config file and downloaded so I could use it to start CamillaDSP.
But the config file is not valid for my PC.
In the UI I created a config file and downloaded so I could use it to start CamillaDSP.
But the config file is not valid for my PC.
Last edited:
How to choose input and output devices
I have selected this as my output deviceBut I don't know what I should choose for my capture device.
Should I install https://vb-audio.com/Cable/ ?
If you have CamillaDSP running on windows with a multi-channel dac, I would really appreciate some one-on-one help. maybe using teams or face to face if you live in Denmark.
- Home
- Source & Line
- PC Based
- CamillaDSP - Cross-platform IIR and FIR engine for crossovers, room correction etc