When building the binary on a RaspiPI 4 with Ubuntu Server 23.10 it cannot connect to the CamillaDSP web port.
maybe the problem is related with the websockect library which is libwebsocket.so.19, instead of the .17 version the included binary is built against.
When installing the older release of the websockets library in parallel to the stock one the binary file included in the GIT repository runs without problems.
maybe the problem is related with the websockect library which is libwebsocket.so.19, instead of the .17 version the included binary is built against.
When installing the older release of the websockets library in parallel to the stock one the binary file included in the GIT repository runs without problems.
Thank you for spotting this issue. Unfortunately, I use Dietpi instead of Ubuntu. On Dietpi the latest stable release is libwebsockets17 (version 4.1.6-3). Thus I have no means of conducting tests. When Dietpi one day upgrades to libwebsockets19, I will do so.
In any case, I understand from the changelog that there are no relevant differences between the two versions with regard to the basic use camilladsp-setrate makes of the library.
I installed everything, but when I check the service (systemctl status camilladsp-setrate), I get this error:
When I check the capture cards, I see the UAC2Gadget and I see it also in alsamixer.
Below is the result of the command arecord -l
I do not understand what is wrong...
When I check the capture cards, I see the UAC2Gadget and I see it also in alsamixer.
Below is the result of the command arecord -l
I do not understand what is wrong...
@Nicosia
I would suggest you to test the UAC2Gadget capture device directly with the arecord command:
If you get the "Cannot get card index" error, then try with:
(but please check the card and device numbers, as those may change on reboot)
In both cases, if you get the error, then something went wrong with the configuration of the gadget device. In this case, please have a look at the guides on this topic you can find on this forum.
If the above commands dump the capture device capabilities with no errors, then there is something wrong with camilladsp-setrate or with its use. In this case please:
1) Let me know the command line options you used
2) Enable logging at the highest level of detail (--loglevel notice) and report back to me the log lines concerning the issue.
I would suggest you to test the UAC2Gadget capture device directly with the arecord command:
arecord -D hw:UAC2Gadget --dump-hw-params -d1 > /dev/null If you get the "Cannot get card index" error, then try with:
arecord -D hw:0,0 --dump-hw-params -d1 > /dev/null (but please check the card and device numbers, as those may change on reboot)
In both cases, if you get the error, then something went wrong with the configuration of the gadget device. In this case, please have a look at the guides on this topic you can find on this forum.
If the above commands dump the capture device capabilities with no errors, then there is something wrong with camilladsp-setrate or with its use. In this case please:
1) Let me know the command line options you used
2) Enable logging at the highest level of detail (--loglevel notice) and report back to me the log lines concerning the issue.
Is your systemd unit running in correct order - is the gadget device already loaded? How do you create the audio gadget function?
Below what I get with the first suggested command line:
I think usb gadget is properly setup, it works, I can hear music from my iPhone when connected directly to the Pi4 by USN cable, providing that I use the proper configuration.yml to match frequency of the song (44.1Khz, 48K etc.)
Below the camilladsp-setrate.service --loglevel notice
Below the error with the
Still not working...
It is setup when you login and check. But is it setup when the setrate process is being started by systemd? Did you check that?
Ok, it seems that the UAC2Gadget works.
Probably occurs what @phofman suspects, i.e. camilladsp-setrate tries to open the gadget device before it is ready. You could check this in the syslog.
Also, redirect to a file the lines written by camilladsp-setrate to the syslog, as follows:
sudo journalctl | grep camilladsp-setrate > camilladsp-setrate.log and then attach the camilladsp-setrate.log file to your reply.
What method do you use to launch the gadget configuration procedure? Do you use a systemd service?
Please also check if camilladsp is up and running and if camilladsp logfile reports any errors concerning the capture device.
NOTE: if you use the "--loglevel notice" option, you don't need to add the "--err", "--warn" and "--user" flags.
Last edited:
Please change "Restart=no" to "Restart=always"
Also try starting camilladsp-setrate manually. If it works, then there is clearly a timing error, as suspected.
sudo systemctl start camilladsp-setrate
Last edited:
If I put "Restartr=always", I get the following checking twice the status of the service:
I attached the log file.
Below the message for camillaDSP service (while I am listening without any problem music from my iPhone to USB connection):
Below the camilladsp.service:
I attached the log file.
Below the message for camillaDSP service (while I am listening without any problem music from my iPhone to USB connection):
Below the camilladsp.service:
The USB_HD660S_cross3.yml is the camilla configuration I use to start the service and as the USB gadget as source.
Last edited:
camilladsp-setrate failed 5 times, 1 second between restarts. Thus it seems that the capture device is unavailable after at least 5 seconds after the first attempt to access it (if the issue is a timing issue).
What method do you use to setup the gadget capture device? If you use a systemd service, please post the related .service file.
Please do the checks I suggested in my posts #49,50.
The log file you attached confirms that the gadget capture device is unavailable to camilladsp-setrate.
IMPORTANT:
Make sure the dietpi user is a member of the audio group. To get the list of groups to which dietpi belongs:
If not a member, add dietpi to the audio group:
Then reboot and see if camilladsp-setrate works.
If the issue persists, please start camilladsp-setrate manually and report the status of the service:
Please also report the status of camilladsp:
IMPORTANT:
Make sure the dietpi user is a member of the audio group. To get the list of groups to which dietpi belongs:
groups dietpiIf not a member, add dietpi to the audio group:
sudo usermod -a dietpi -G audioThen reboot and see if camilladsp-setrate works.
If the issue persists, please start camilladsp-setrate manually and report the status of the service:
sudo systemctl start camilladsp-setrate
sudo systemctl status camilladsp-setratePlease also report the status of camilladsp:
sudo systemctl status camilladspI asked you for the .service file that starts the gadget device setup.
Last edited:
I did this:
groups dietpiNow the service is running!
But it does not change the frequency, unless I restart manually the camilladsp.service, every time a song has a different frequency compared to the previous one.
Below camilladsp.service status:
Maybe something wrong with the first part of the camilladsp configuration I use? Here it is:
I do not have any .service to start the I asked the gadget device setup.
I followed the instructions on this page: Using a Raspberry Pi as equaliser in between an USB Source and USB DAC
but I stopped at the gaudio_ctl section.
On another Pi4, everything works fine with the gaudio_ctl as per the instructions in the link above, but I need several configurations for each frequency. If you want to use different headphones, you need more configurations and a script to run different execution commands in the camilladsp.service. It could be more handy.
Your script is much more elegant and handy because I need only one configuration for each pair of headphones I can select from the Camilla GUI. Your script will change the frequency when needed.
I can imagine that you also ran the command to add dietpi to the audio group.
Glad to hear that!
An error is reported in the configuration file of CamillaDSP. It is probably what prevents the overall system from working properly.
Please remove the capture_samplerate specification.
I would also suggest using names instead of card and device numbers (numbers may change on reboot), and using the "hw" device type instead of "plughw", as follows:
YAML:
..........
devices:
..........
capture:
..........
device: "hw:UAC2Gadget"
..........
playback:
..........
device: "hw:<name of your playback device>"
..........
capture_samplerate: null
samplerate: 44100
..........Please pay attention to the indentation of the configuration file.
The syslog traces all the steps in the procedure by which camilladsp-setrate updates the samplerate and communicates it to camilladsp.
Any issues should as well be reported in the syslog.
sudo journalctl | grep camilladsp-setrate
Last edited:
I removed the capture_samplerate specification:
Thank you so much for the wonderful support and the great plugin!
Hopefully all the lessons learnt above will help the community also 🙂
Maybe collecting the tips about audio group and capture_samplerate null in a FAQ or paragraph in GitHub could be useful?
Many thanks again! Grazie di cuore!
and… now it works like a charm!
Thank you so much for the wonderful support and the great plugin!
Hopefully all the lessons learnt above will help the community also 🙂
Maybe collecting the tips about audio group and capture_samplerate null in a FAQ or paragraph in GitHub could be useful?
Many thanks again! Grazie di cuore!
Great!
I now suggest you to set
--loglevel=errI updated the .service file and the README.md file, based on the contribuitions posted in this thread. In particular look at step 4. in the installing instructions and the fifth of the endnotes.
Thank you all for pointing out the need for these improvements to my little tool.
Last edited:
Hello I am new with CamillaDSP and use it now for a week or so and it works already great but one thing i need for the whole Projekt i build up,
Is to detect the Input Samplerate on an RPI'S 5 I2S Input (Multichannel) I got already an HDMI (1.4) to I2S Board running but for now i need to switch the Incomming samplerates Manualy on CDSP. And this isn't realy funn to do.
Look at the Attached Picture. That is my Plan to build up an nice complete DSP Solution (waiting for the Boards i ordered already) for an 7.2 full aktiv Surround Setup with CamillaDSP as the Heart of all.
Outputdevice for now is an MOTU UL mk5 but i need at all 16 Channels with Volumecontroll on all Channels, so i need to switch it any day to may be an MOTU Ao 24 or A16.
At minimum all Channels on Motu need to run at 96kHz
For the Capturdevice i use this:
hw:CARD=GenericStereoAu,DEV=0 (I2S Input on RPI5)
Would be the camilladsp-saterate the right tool to switch automaticly to any incomming samplefrequenz on I2S ???
Than i would give it an try.
Other Option would be to use an SRC Like that Chip "AK4128A 8 Channel Asyncronous SRC" but i cant find an DIY Board with it or an aviable Evaluationboard with this Chip
Damm this is EOL, now Ti has only an 4 CHannel SRC4194 and EVAL Board with one of them cost 300€ 🙁
Dont think that anyone will have an DIY Board with 2 of them for 8 Channels.(Digi-key Price is 19,17€)... 😉
I use UBUNTU 23.1 on the RPI5 for camilladsp with Squezzeliteserver on it and on my second RPI 4 is the Picoreplayer, with for now, HDMI Out to HDMI IN Board to I2S on RPI5 later i will use also I2S Out instead of HDMI Out on RPI4 with Picoreplayer.
I am not an Linux Expert so any advice will help me 😉
Robert
Is to detect the Input Samplerate on an RPI'S 5 I2S Input (Multichannel) I got already an HDMI (1.4) to I2S Board running but for now i need to switch the Incomming samplerates Manualy on CDSP. And this isn't realy funn to do.
Look at the Attached Picture. That is my Plan to build up an nice complete DSP Solution (waiting for the Boards i ordered already) for an 7.2 full aktiv Surround Setup with CamillaDSP as the Heart of all.
Outputdevice for now is an MOTU UL mk5 but i need at all 16 Channels with Volumecontroll on all Channels, so i need to switch it any day to may be an MOTU Ao 24 or A16.
At minimum all Channels on Motu need to run at 96kHz
For the Capturdevice i use this:
hw:CARD=GenericStereoAu,DEV=0 (I2S Input on RPI5)
Would be the camilladsp-saterate the right tool to switch automaticly to any incomming samplefrequenz on I2S ???
Than i would give it an try.
Other Option would be to use an SRC Like that Chip "AK4128A 8 Channel Asyncronous SRC" but i cant find an DIY Board with it or an aviable Evaluationboard with this Chip
Damm this is EOL, now Ti has only an 4 CHannel SRC4194 and EVAL Board with one of them cost 300€ 🙁
Dont think that anyone will have an DIY Board with 2 of them for 8 Channels.(Digi-key Price is 19,17€)... 😉
I use UBUNTU 23.1 on the RPI5 for camilladsp with Squezzeliteserver on it and on my second RPI 4 is the Picoreplayer, with for now, HDMI Out to HDMI IN Board to I2S on RPI5 later i will use also I2S Out instead of HDMI Out on RPI4 with Picoreplayer.
I am not an Linux Expert so any advice will help me 😉
Robert
Attachments
Last edited: