RPi + CamillaDSP Tutorial

[john61ct]

5B is not a bad device, but IMO if an SBC needs active cooling, it's intended for different use than passively cooled ones.

What a device "is intended for" often has little to do with the uses it ends up serving.

How many million taps do you need?

I need 8 analog ports per RPi, therefore only RPi5 will do. Processing power has nothing to do with it, just a nice side effect.

> Why CM5? Have you seen how it looks?

How is that relevant?

I want an ITX mobo so a neat stable case for standard PCIe cards

 

[Frunse]

I looked in my Setups and used most time around 16000 Tabs and LR 96dB @96kHz Filter but i guess for that Multichanel Setup i used only 76dB or 72dB LR not sure anymore.

Also on Bass i used 100 Hz with 72dB and let the Filter optimized on rephase with highest Value, so it took some Time til it was Calculated but it looked than near perfect.



In the World of Millions off Taps

 

[Frunse]

What a device "is intended for" often has little to do with the uses it ends up serving.



I need 8 analog ports per RPi, therefore only RPi5 will do. Processing power has nothing to do with it, just a nice side effect.

> Why CM5? Have you seen how it looks?

How is that relevant?

I want an ITX mobo so a neat stable case for standard PCIe cards

Like This :



I used an M-ATX Board and an M-ATX Case included an RPI4 with Moode for Streaming and RME HDSPe AES Card for CamillaDSP on the Intel Board LOOOL
With an 16,2" IPS TFT Screen 2608x720Pixel could be upgradet up to 32 digital Processed Channels In and Out Work in Progress!

 

[Frunse]

BTW i got my PCIe X1 extension Board for RPI5 so in my new Apartment around at the End of Juli i could do my first tests with an REM HDSPe AES PCIe Card on an RPI5 with CamillaDSP!!!



PCB 37.55x85.23mm

If this would work you could realy use an 19" 1 HE Enclosure, may be like that i mentioned here earlier from Caseking for 16 Channel in and out, digital thrue AES up to 192kHz.

But not sure yet how to add the additional Card than from RME that don't need an PCIe Slot.

https://rme-audio.de/hdspe-aes.html

 

[john61ct]

For CM5 not RPi

Sanctuary Systems "Sentinel Core" mobo, fit in any ITX case.

Might need to go vertical rather than a low-profile horizontal riser

 

[john61ct]

What are "tabs" in tbis context?

 

[Frunse]

What are "tabs" in tbis context?

taps has todo with Processingpower needs to calculate the Filter the right Way. MiniDSP HardwareDSP offers not realy more than around 2000 to 4000 Taps!

For 48kHz and 24dB/octave its probably enough but not perfect at 80 Hz or lower i would say.

The Lower the Frequency and the higher the db/octave you wan't the higher Taps Number you need to calculate the right FIR Filter slope on an DSP.

That why the most HardwareDSP chips used only for IIr Filter and not much alow FIR at all.

I am not an Matematician so probably anyone else could descripe it better.

CamillaDSP is softwarebased and uses 64Bit for calculation and it is realy capabel to use high TAP numbers. Also it can use larger RAM Amount so it has much higher capability than any Hardwarebased DSP i know.

Also the higher the Tap number is used the longer processing Time is so it took some time to go thru the DSP Pipeline and you get an larger Delay between In and Out Signal

For Surround you need to use Lipsync then Some Prozessors alow up to 1000ms Lipsync Delay may be more.

I need to check how long my Setup need to play thrue with 16xxx Taps used on a Filter

Look here the Picture from above, if i would use only 48dB/octave the Tap number could be probably half the Value for an perfect calculated Filter Slope



If youre DSP don't allow more Taps and you still want this Filter it become not that precise in Slope you get more Destortion and such things you could see it on this Picture.
My Filter is cleen down to -120dB and not much DACS could play down to -130dB without adding his own Destortions.

Here how it looks at 100Hz with only 4000Tap blue is how it should red how it would be:



with 8000Tap



And perfect with 16000Tap



But i guess all down to -115dB is fine and you couldn't here it realy if it goes down to -130dB clean on Low frequencys.

And this is what ihave used on my SUB with 96dB / Oktave at 96kHz, still very good down to -100dB than a bit dirty down to -120dB and destortions starts from -120db below.

 

[Frunse]

For CM5 not RPi

Sanctuary Systems "Sentinel Core" mobo, fit in any ITX case.

Might need to go vertical rather than a low-profile horizontal riser

i looked to the CM5 Module prices last week and i better stay with my normal RPI5

But that Board looks well also already an PCI slot there, didn't know it til now, would also fit into my Case

With an angled PCI Adaptercard you could use it also on an 1HE or 2HE 19" Case in an Rack i guess.

 

[john61ct]

Aha, you kept writing "tabs". Yes I know what taps are.

With your RME daughterboard I was thinking better to stay vertical.

 

[Frunse]

Here an example for an Hypex DSP:


Max 1024 Tap's per Chanel FIR Filter possible, this willl never work precise with FIR at 80Hz with an Sub. May be 48kHz and 12dB/octave Slope LOL

48kHz 1024Tap's 24dB/octave:



12dB/octave:



16384Tap's 96kHz 96dB/octave (not Perfect but much much better , 48dB / octave already Perfect down to -150dB)

 

[Frunse]

What are "tabs" in tbis context?

If you know what Taps are why this question and what you mean with "tbis" ??? i didn't know this word but i am German may be that why LOL

 

[somebodyelse]

If you know what Taps are why this question and what you mean with "tbis" ??? i didn't know this word but i am German may be that why LOL

Clarification. It's better to ask if not sure about the meaning than to assume, and end up with a misunderstanding as a result. This is especially true when people aren't using their first language.

 

[Frunse]

Aha, you kept writing "tabs". Yes I know what taps are.

With your RME daughterboard I was thinking better to stay vertical.

Vertikal only possible in an Big enclosure but not in an 19" 1HE Rack enclosure for people that like to have an smal DSP Device in his Setup.

It is the only reason why i would use an RPI5 for an DSP...to keep it smal.

For me, i got big with an Intel M-ATX Board and Ubuntu Studio and thats works already very well!

I do the RPI Test for people that like to do it the smal way, not for me only

I didn't found anything in the Internet about CamillaDSP to use an PCIe X1 Sounddevice on an RPI5 so i will do the Test.

I like to have the possibility to add an second RME Card for 32 Channels, may be in the Future.
Also i like to have an biger Screen my eyes not the Best anymore with 56 Years LOL

 

[Frunse]

Clarification. It's better to ask if not sure about the meaning than to assume, and end up with a misunderstanding as a result. This is especially true when people aren't using their first language.

Its all good that was only the reaction to "Aha, you kept writing "tabs". Yes I know what taps are."
My Mistake i wrote Taps wrong but every one understand the meaning even i write Tabs LOL

Some People may be are Teacher in real World and like to correct People even it is not importand to do!

I am not here to learn Englisch

Also he wrote "this" wrong so don't do the same Mistakes and juge other Persons for doing the same i would say

Or better to say don't throw Stones in an Glashouse

 

[Blew]

I assume there still needs to be some kind of process running in daemon mode that translates the VOL20 actions to CamillaDSP or LMS remote calls.

I finally got around to putting this together. The Vol20 now controls my CamillaDSP volume and switches the profiles between the three inputs that I use: https://github.com/sirblew/vol20-camilladsp

 

[john61ct]

I need 8 analog ports per RPi, therefore only RPi5 will do. Processing power has nothing to do with it, just a nice side effect.

Of course a class compliant USB interface allows use of the lower powered RPi versions, as would DSPi's new ADAT I/O

But the former path, while likely better SQ than the HAT route, would not save on costs.

And the latter is a bit above my pay grade technically.

 

[john61ct]

I finally got around to putting this together. The Vol20 now controls my CamillaDSP volume and switches the profiles between the three inputs that I use: https://github.com/sirblew/vol20-camilladsp

Fantastic!!

spawned a new thread

Big Knob at MLP ideally Wireless for ad-hoc Volume control with Loudness, mute etc

Inspired by https://github.com/sirblew/vol20-camilladsp which can of course be implemented anywhere in the chain if inserting a dedicated RPi just for that My current Volume Level control is Schiit's Eitr 2 + Forkbeard, which includes the auto-variable LC but that requires using a phone or...

www.audiosciencereview.com

 

[Frunse]

I finally got around to putting this together. The Vol20 now controls my CamillaDSP volume and switches the profiles between the three inputs that I use: https://github.com/sirblew/vol20-camilladsp

Thats sounds nice, but i ask me if this Device would work also this way with CamillaDSP.

https://www.amazon.de/dp/B0GK8LYJ9R...VwF0p&sp_csd=d2lkZ2V0TmFtZT1zcF9kZXRhaWw&th=1

I like it more than this clunky Fosi Device, it has also some more Buttons for Track skip, stop, play and so on, better to find, reach the Buttons.

It should run 60 Days, sounds also better to me with 1000mAh and no LED Light needed at all.

I have CamillaDSP running on Ubuntu Studio right now and it will recognice this Device as an defoult HID Device with Default mapping but you could remap Commands descriped here:

https://simontv.org/p/ulanzi-d100h-dial-preset-for-kdenlive

What you guys think?

Ordered it, recived tomorow

 

[Frunse]

I tested the Device on Windows for now as Volumecontrol Dial and it works fine so far.

Also used AutoHotkey Software and an Script to change Volumesteps from 2 to 1 on Windows. (2 is defoult on Windows, didn't find an other solution to change it)

https://ahkde.github.io/

Put the *.ahk File into "startup" Folder

Use Win+R and type "shell:startup" in hit Return after installing AutoHotkey
if you double klick on this File the first Time AutoHotkey detects that it needs the 1.* Version and wan't to install it!
after that it works fine after each Windows Startup
Found that on the Internet but forgot the Link.

If you rotate the Dial the whole Time the Batterie will last for 2,5 Hour on Standby it last for 60 Days.

If you want to use it intensive you can deaktivate the Force feedback thing and i guess it will last more than 2,5 Hour on continius Rotation

But for Volumecontrol how offten you realy use it in a row

Next i need to test it on Linux

 

[john61ct]

I tested the Device on Windows

Which device?

Man, AHK was all the hotness for windoze automation, I had some HUGE codeblocks going back in the 90's