Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


CamillaDSP
#11
Sooooo I started playing around with this yesterday after purchasing a new pi. 

my plans are the following. 

1. Stream airplay audio to moode which will be connected to my Denon receiver via HDMI off a PI 4
2. Use CamillaDSP to implement my convolution DSP files I setup using AudioLense.. These convolution DSP files will be used for room correction, phase adjustment and proper integration of my subs with a crossover etc. This means I need at least 3 channels out (2 channels in) but with all things HDMI you will need to include more as your sub channel is probably on channel 3 or 5. 

I have accomplished this with Roon and love the results but do not love paying ~100 a year for Roon plus another ~180 a year for Qbuz (one of the only two supported streaming platforms in Roon)

Now with Apple music offering redbook cd quality (which is included with my VZW account for free).. It is very desirable to have an airplay streaming device with DSP built in.

Along the way I have found a few issues though.

1. I was able to setup a custom pipeline and include all 8 channels with filters on the three channels I needed.

   

This works right too.. I was able to back out and applying the changes to the pipeline and verify that audio was working.. 

   

Although if I change to a different configuration file (such as "quick configuration file") via the CamillaDSP configuration page or even just reboot the device. The custom pipeline configuration file I crated with 8 channels reverts back to 2..

   

Setting the device back to 8 channels in the pipeline editor fixes this until you reboot or decide to change the configuration file to something else. The fact that this is happening on every reboot will be a bigger issue IMHO. 

2. Another issue I noticed was that on the Main CamillaDSP configuration page if you happen to be trying to use a 32bit float convolution file for the "quick configuration filter" option, you will get the following error

   

I would assume this attribute needs to be changed to FLOAT32LE

3. The last issue I noticed was that if I use a wav file if I to choose wave as my IR type (not sure this is the right IR type for wav just assuming it is) it gives me the following error. Not only that, all other IR types give me very high distortion. If I manually log into the pi via putty and use the sox command to change them to raw they work fine.

   

Technically I think I can still make this work and will continue to work around the issue until I get it at least functioning.. In the mean time I wanted to report these bugs.. 

Hope this was the right place to do it.
Reply


Messages In This Thread
CamillaDSP - by zulizu - 03-25-2021, 05:16 PM
RE: CamillaDSP - by bitlab - 03-25-2021, 08:44 PM
RE: CamillaDSP - by zulizu - 03-27-2021, 05:45 PM
RE: CamillaDSP - by bitlab - 03-27-2021, 06:45 PM
RE: CamillaDSP - by zulizu - 03-27-2021, 06:59 PM
RE: CamillaDSP - by newbie - 03-27-2021, 10:54 PM
RE: CamillaDSP - by zulizu - 03-28-2021, 07:59 AM
RE: CamillaDSP - by JWahle - 04-04-2021, 04:39 PM
RE: CamillaDSP - by bitlab - 04-04-2021, 06:01 PM
RE: CamillaDSP - by bitlab - 03-27-2021, 07:17 PM
RE: CamillaDSP - by kejar31 - 07-12-2021, 04:57 PM
RE: CamillaDSP - by bitlab - 07-12-2021, 05:55 PM
RE: CamillaDSP - by bitlab - 07-12-2021, 06:21 PM
RE: CamillaDSP - by kejar31 - 07-12-2021, 06:38 PM
RE: CamillaDSP - by Tim Curtis - 07-12-2021, 06:42 PM
RE: CamillaDSP - by kejar31 - 07-12-2021, 07:05 PM
RE: CamillaDSP - by bitlab - 07-12-2021, 08:35 PM
RE: CamillaDSP - by kejar31 - 07-12-2021, 09:23 PM
RE: CamillaDSP - by kejar31 - 07-12-2021, 10:33 PM

Forum Jump: