CamillaDSP for Room Correction
#21
(09-Sep-2023, 01:00 PM)Snoopy8 Wrote:
(24-Aug-2023, 10:09 PM)hkphantomgtr Wrote:
(24-Aug-2023, 07:12 PM)Snoopy8 Wrote:
(24-Aug-2023, 01:14 PM)hkphantomgtr Wrote: Would you please advise or share your experience more about installing and running CamillaDSP in SO?  Much appreciated.
Please have a look at post #9 in this thread. It contains all my notes from my original install.

Alright, Thanks a lot, Snoopy8!
Did you manage to get CamillaDSP working?

My NUC failed and I had to build a new box using Ubuntu 22.04. I followed the instructions on post #9 and it worked. Also, no need to install Pulse Audio. However, I have the advantage that I had a working config file doing convolution.

I'm sorry that I didn't try.  Now I'm testing another OS with build in convolution dsp filter.
Reply

#22
Recommend rebooting after enabling or disabling CPUsets within SnakeOil. Just realised that the maximum latency goes crazy after the change.
Reply

#23
Notes for AK for 1.3.1 implementation of CamillaDSP.

Been using this webpage to routinely reinstall CamillaDSP for 1.3 testing.  Have not done the web gui.
https://github.com/HEnquist/camilladsp-config

There is a good long tutorial on ASR to install CamillaDSP ​on a Pi. Has links to other web resources as well.
https://www.audiosciencereview.com/forum...ial.29656/

Some things that require attention:
  • config.yaml is the critical configuration file.  Suggest providing several standard ones like what Moode does.  Users can, of course create their own config files but put warning that debugging can be painful.  
  • While config file has rate and format settings, need to ensure that asound.conf has matching settings
  • Set priority of CamillaDSP.service to less than 50.  Otherwise, it could interfere with IRQ of USB, causing huge latency problems.
  • Suggest setting aside a CPU for DSP using cpuset. And a separate CPU for player.  LMS has a much higher max latency than Mpd 
Happy to assist with getting CamillaDSP into SnakeOil. AK, please let me know what you need.
Reply

#24
(23-Dec-2023, 06:58 AM)Snoopy8 Wrote: Happy to assist with getting CamillaDSP into SnakeOil. AK, please let me know what you need.
Need help testing everything is working is a good start, more importantly not break as an on-going concern. As I'm unlikely going to use DSP in my home rig. 

But before that, just aiming to get the 1.3.0 out this weekend, and focus on 1.3.1 immediately after.
Snakeoil Operating System - Music, your way!
[-] The following 1 user Likes agent_kith's post:
  • Snoopy8
Reply

#25
(23-Dec-2023, 07:12 AM)agent_kith Wrote: Need help testing everything is working is a good start, more importantly not break as an on-going concern.
Have both my NUC and Mercury (CM4) running CamillaDSP as system service. The use of loopback to capture and process the signal may throw users off.  And it did interfere with the 1.3 firmware upgrade, with the Music Player stuck until I stopped CamillaDSP.  

Having CamillaDSP in the chain can also cause latency problems.  Add in CPUsets and it can be a headache.  I have gone back to using standard SO CPUsets and minimum change in process priority to reduce the number of variables to manage. As an aside, my latency problems were caused by using too large a convolution filter (lesson learnt: don't be greedy!)

The biggest danger is users being too ambitious with the custom use of DSP and we may end up spending too much time solving these. Note that my use is limited to convolution.  Any other use case will be new for me.
​​​​​​
Having said all that, the documentation is much better than I first started. And I have both X86 and Pi versions running which will make testing easier.
 
(23-Dec-2023, 07:12 AM)agent_kith Wrote: As I'm unlikely going to use DSP in my home rig. 
You should give convolution room correction a go. I see it as having more of an impact than real time kernels.
Reply

#26
(31-Dec-2023, 11:37 AM)Snoopy8 Wrote: Have both my NUC and Mercury (CM4) running CamillaDSP as system service. The use of loopback to capture and process the signal may throw users off.  And it did interfere with the 1.3 firmware upgrade, with the Music Player stuck until I stopped CamillaDSP.  

Having CamillaDSP in the chain can also cause latency problems.  Add in CPUsets and it can be a headache.  I have gone back to using standard SO CPUsets and minimum change in process priority to reduce the number of variables to manage. As an aside, my latency problems were caused by using too large a convolution filter (lesson learnt: don't be greedy!)

The biggest danger is users being too ambitious with the custom use of DSP and we may end up spending too much time solving these. Note that my use is limited to convolution.  Any other use case will be new for me.
​​​​​​
Having said all that, the documentation is much better than I first started. And I have both X86 and Pi versions running which will make testing easier.
Thanks for that. I am/was a bit too ambitious thinking I can release 1.3.1 in 10 days time with Convo added to the WebApp. Unfortunately in 10 days I only managed to add the page, and not actually populate the contents.

Ten days sound like a long time, but it's gone just like that. Confused 2

Did get a lot of things done though, just don't feel like it's enough. Maybe it's because I'm getting older, things just can't get finished quickly.

(31-Dec-2023, 11:37 AM)Snoopy8 Wrote: You should give convolution room correction a go. I see it as having more of an impact than real time kernels.
My worry is my computer are so low powered I'm not confident any advantage it brings will be offset by the additional power it consumes. Tongue
Snakeoil Operating System - Music, your way!
[-] The following 1 user Likes agent_kith's post:
  • Snoopy8
Reply



Bookmarks



Users browsing this thread:
2 Guest(s)

[-]
Our Sponsors

[-]
Welcome
You have to register before you can post on our site.

Username/Email:


Password:





[-]
Latest Threads
Fail to install myMPD
Last Post: sjtuross
18-Feb-2024 03:10 PM
» Replies: 4
» Views: 79
LMS Upgrade ?
Last Post: uglymusic
18-Feb-2024 05:25 AM
» Replies: 6
» Views: 77
More Problems with Squeezelite in 1.3
Last Post: Coacharnold
17-Feb-2024 09:47 PM
» Replies: 2
» Views: 25
Announcing Snakeoil Measurements 1.3.0
Last Post: Snoopy8
17-Feb-2024 11:29 AM
» Replies: 90
» Views: 2976
Snakeoil Music server & Snakeoil its own...
Last Post: Snoopy8
17-Feb-2024 11:20 AM
» Replies: 8
» Views: 279
RoonBridge (64 bit only)
Last Post: scrarfussi
15-Feb-2024 08:26 PM
» Replies: 3
» Views: 4025
How to upgrade to low latency kernel on ...
Last Post: uglymusic
14-Feb-2024 03:18 PM
» Replies: 11
» Views: 204
Problems with Squeezlite in 1.3
Last Post: Coacharnold
14-Feb-2024 03:20 AM
» Replies: 7
» Views: 140
Install RoonLab's RoonBridge
Last Post: scrarfussi
04-Feb-2024 02:24 AM
» Replies: 2
» Views: 5462
ZimaBoard 2x NIC, 2x SATA, 2x USB, 1x PC...
Last Post: hkphantomgtr
21-Jan-2024 06:26 PM
» Replies: 11
» Views: 507

[-]
SnakeoilOS Mission Statement

Our mission is to create a free to use computer OS that is easy to install, intuitive to operate and play music that will connect and engage with you emotionally.

SnakeoilOS gives you the freedom to spend more time on listening, enjoying and exploring music. Wasting time on computers is now a thing of the past! Everything is constantly evolving/improving. Please check back often for updates.

If you like this project, do show your support with a small token donation. All donations collected will be used to run this website, and for purchasing new equipment for the project.


Powered By MyBB, © 2002-2024. Theme © Melroy van den Berg.