RPi + CamillaDSP Tutorial

[somebodyelse]

Yes, the XX is wrong. The XX can change, it's not always known.

Have you tried using the .local domain? As in http://your_host_name.local:5005/ using whatever host name you originally set it up with? It might work, depending on how your router handles things.

 

[Jukka]

Have you tried using the .local domain? As in http://your_host_name.local:5005/ using whatever host name you originally set it up with? It might work, depending on how your router handles things.

That's what I'm using now, it's more static than IP, but not eternal. But there is a more fundamental issue here: how do I know that it's online and the address/name is still the same? Like when either of those two premises is false. When everything works, there are no problems, but when it doesn't, the real robustness of the system is tried.

 

[melomane13]

ssh [email protected] (your)
hostname
http://your_host_name.local:5005/
The hostname is static and can only be changed manually on the Raspberry Pi.

 

[testp]

while i'm getting familiarized with CamillaDSP in github,

i thought i'll ask, is anyone using RPI4/5 with some hats to do 2.1? if so, how ease of use is it, if all is set and working (like would i need to restart it often, bc something isn't working etc). Or is there some other solutions (other than miniDSP).

(Edit) ah okey, github already mentions passive stereo + subs.

It's just that, i already spent on speakers, need an amp as well, don't want the electronics cost be more than speakers ideally.

 

[paalj]

Microsoft surfacedial as volumecontrol and mute button:
I had google AI to help me making a python script having dual remotes to control camilla. Less than an hour later I had a working script for both my IR remote and surfacedial. I asked google to make a short install instruction so for any of you wanting to have a volume wheel.., have a look at the pdf. The surfacedial have an issue that it goes into deep sleep after a while so in that case you just tap once on the dial and it is online in a couple of seconds..

 

[MCH]

Microsoft surfacedial as volumecontrol and mute button:
I had google AI to help me making a python script having dual remotes to control camilla. Less than an hour later I had a working script for both my IR remote and surfacedial. I asked google to make a short install instruction so for any of you wanting to have a volume wheel.., have a look at the pdf. The surfacedial have an issue that it goes into deep sleep after a while so in that case you just tap once on the dial and it is online in a couple of seconds..

Great! It is a bit late for me because my dial died some time ago but it is still the best feel remote knob I have ever seen

 

[phofman]

I like how the AI is helping with DIY, projects that would otherwise never arise. Learning how to use it (efficiently) is inevitable, IMO. That why some comments in https://www.diyaudio.com/community/threads/new-site-policy-on-ai-generated-content.431397/ surprise me, IME AI is a catalyst of DIY, not its inhibitor.

 

[paalj]

Thanks for the link @phofman . I did not know it was forbidden. I might have posted some content that is not allowed over there. I am also trying to get the dust off some other projects that I do not have the knowledge to do on my own so in that case you are right . The project would have stayed in the bin. The nice thing about AI is that it never get bored of stupid questions from a person without python knowledge. It just ask for more money when the time is out ;-)

 

[testp]

This is my experience as well, AI can be very very helpful to start things or small projects.

and continues to be helpful even in more complicated projects, as long as the scope of AI help is controlled and minimum (business reasons/logic behind existing code is more difficult to prompt to it).

of courese there is the maintaining issue, i think i saw one, it's okey but little quirky

"if dial_device and device == dial_device:" # then do something..

if dial_device itself is boolean, then -> "if dialdevice and device:" # should do the same thing..

if dial_device is not boolean, then dial_device doesn't need to be there, so -> "if device == dial_device:" # should do the same thing..

actually i stand corrected, it say's be truthy and equal at the same, so it's good... Impressive again, AI.

 

[pike]

If someone else is curious about the Pinout on Raspiaudio's 8xIn 8xOut hat, they published this info yesterday (FINALLY).
I made this guide to easier see which header pins are not in use :=)

 

[Jukka]

Hi @HenrikEnquist. This is a minor thing, but bother me each time I see it. "Bypassed" is a double-negative setting value, which is confusing and considered bad in UX design. It's recommended to use "enabled" instead and having "yes" as default value. You could also just drop the "default". Default is currently same as "yes" and you're never going to switch it to "no", are you?

 

[melomane13]

a new interest interface for camilladsp:

https://store.sure-electronics.com/product/854

usb 8 ch, pcm5122, 105 snr, 0,007 % thd+noise 24bit/48khz , 50$

 

[HenrikEnquist]

"Bypassed" is a double-negative setting value, which is confusing and considered bad in UX design.

I agree, and it's an easy thing to fix. There just tends to always be something more important to work on . I'll get to it, promise!

 

[Bwaslo]

a new interest interface for camilladsp:

https://store.sure-electronics.com/product/854

usb 8 ch, pcm5122, 105 snr, 0,007 % thd+noise 24bit/48khz , 50$

Looks pretty nice. Way cheaper (and less soldering) than using MCHstreamer+DAC boards.

 

[HenrikEnquist]

I agree, and it's an easy thing to fix. There just tends to always be something more important to work on . I'll get to it, promise!

I have updated this for the v4 gui. Instead of the dropdown it will be a button, saying ether Active with a bright green border, or Bypassed with a grey border (same colors and styling as the channel selectors)

 

[Yems]

I need help, i tried to adapt Michael's brilliant step by step guide to the current 4.xx release of camilladsp. I mainly updated the 3.x links to the 4.x ones. Everything seems to work, but... the camilla frontend is the old one. Can sombody help?

 

[Yems]

... i don't know what i did different, but now it works!