I could swear that I tried all sampleformat options... It works now with both capture and playback device set to S24LEYour log shows that your playback device supports S16LE and S24LE but you configuration is set to S32LE. I would change your playback format to S24LE.
Michael
Another minor problem that occurred is that I cannot open the GUI from some browsers.
Edge works fine but Chrome and Safari on my iPhone can’t make a ‚secure connection‘ to CamillaDSP.
It’s not blocked by antivirus software so I think it’s an SSL problem. Most common fixes didn’t help though
Hey, I would appreciate if you post how you made those features. I am mostly interested on the volume knob. Do you think it can be done wirelessly with a second pi or something like that? (I believe there is even a pi pico microcontroller with wifi now)mdsimon2, thanks for your tutorial ! I used it as a base for my own project. Some things I've added/did differently: automatic intermittent inaudible low frequency tone to keep my sub powered on when listening to music at low volume (/prevent from going into standby); master volume with a physical knob (rotary encoder with software debouncing); display showing the main volume, CamillaDSP and player (squeezelite) status (playing/stopped/muted/...), switching CamillaDSP configs with a button, mute/play the player and CamillaDSP with another button, and also a bluetooth streamer (currently a "standalone" config that has nothing to do with CamillaDSP but I plan to test CamillaDSP in the signal path some day to add crossfeed). I can post the link to instructions if anyone's interested.
If that wasn't for you I probably wouldn't have started this project (and I wouldn't have spent so many hours on it )
Cheers !
Sure - there's nothing that prevents the volume knob (or whatever that connects to CamillaDSP with pycamilladsp) to be on a remote device.Do you think it can be done wirelessly with a second pi or something like that?
Yes, I guess it makes sense but since I'm using it in another way than that they suggested I thought that someone here might have run into similar problem. Somehow I finally got it to work so I'm happy now.Logs if any may help. IIUC the playback software is proprietary and paid for, perhaps the company who supports the software you paid for would tell you more.
Not to my knowledge....Can the Camilla DSP( Raspberry) be connected to the okto, but also at the same time to a laptop , where is shows up as a soundcard, I can send sound towards to perform REW measurements ?
I read the OP post on Okto Pro8 dac - Camilla DSP, which sound right for my setup, where i run a 2.4 I would like to reuse the system for movies in combination a separate center speaker, So for movies would use more speakers than normal hifi listening and hence have its own DSP configuration for each situation.
My question is if its possible to switch inputs on the okto ( TV, Streamer etc) and the have the camilla DSP apply the corresponding configurations? And if not, how would i swich the configuration the easiest? ( by remote if possible )
Second thing I could not read up on: Can the Camilla DSP( Raspberry) be connected to the okto, but also at the same time to a laptop , where is shows up as a soundcard, I can send sound towards to perform REW measurements ?
Hi thx, didmnt know that it had an analog input without extra boards, il have a tRy once i Can get My hands on a rasberry pi.Not to my knowledge.
But a speaker system whose crossover is implemented via Camilla DSP can be measured using REW. Switch to a Camilla DSP profile which captures input via analog line-in channels rather than a stream. Connect the outputs of a (second) sound device attached to the laptop to the analog line-inputs of the Camilla DSP sound device. Then use REW normally.
My sources would be optical spdif or toslink from both tv and streamer, that would be converted to aes. So only two stereo inputs channels. I did not plan on using the raspberry as a streamer, as I thought it would require a sort of web login to the raspberry every time I would use it, where my current streamer uses airplay - nice and simple. Some googling reveals that raspberry can use AirPlay, but if I did that using okto usb mode would I then still be able to also switch to the tv sound from the aes input ?What specifically are your sources (number of channels, format, etc)? Switching configurations in CamillaDSP is relatively simple via the CamillaDSP GUI. However if you are changing from a streamer configuration (RPi as a source) to an AES input configuration you will need to also change the Okto mode from Pure USB to USB / AES.
Thx, tried to find it without luck, but if it’s possible that’s fine for planning now, then I’ll figure it out when I get the parts.Look in to running the raspberry pi in gadget mode (there is a link in the second post of this tutorial). This would allow a chain of laptop -> usb to rpi running camilladsp -> okto (pure USB mode).
Michael
My sources would be optical spdif or toslink from both tv and streamer, that would be converted to aes. So only two stereo inputs channels. I did not plan on using the raspberry as a streamer, as I thought it would require a sort of web login to the raspberry every time I would use it, where my current streamer uses airplay - nice and simple. Some googling reveals that raspberry can use AirPlay, but if I did that using okto usb mode would I then still be able to also switch to the tv sound from the aes input ?
Thanks for replying. I was looking to replace the minidsp for the okto for one control point. but it seems I need minidsp and the okto and a raspberry. What i was hoping to do, was having one input from the TV, which would have its own routing with 8 speakers and DSP correction/filtering. And then another 2 channel input from streamer ( raspberry if need be or a standalone streamer) which would use fewer speakers and have it own DSP correction/filtering. So in anycase there needs to be the option to switch DSP config and routing easily as inputs are shifted daily.Although the Okto has 4x AES inputs they all need to be clock sync'd. Unless your streamer has the ability to be clocked by your TV (which I highly doubt is possible) this means you effectively only have a single stereo AES input.
There are a few options to use multiple inputs with the Okto. By far the easiest is to use a digital input / output miniDSP (OpenDRC-DI, nanodigi, SHD, Flex digital) upstream of the Okto. You can change sources on the miniDSP and the output will always be at a constant sample rate so no need to switch CamillaDSP configurations or input mode on the Okto. Such a setup is described in detail in Part 3 of the tutorial.
You could also use a simple TOSLINK switcher but unless your TV and streamer are outputting at the same sample rate you will need to switch CamillaDSP configurations to accommodate the rate changes.
As mentioned in my initial reply you can also use the RPi as a streamer but that will require you to switch not only CamillaDSP configurations but also the Okto input mode (between Pure USB and USB / AES). This is probably the most complicated way of doing it but requires the least amount of additional gear.
There is no right answer here, just whatever works best for you from a usability standpoint. Personally I use an OpenDRC-DI upstream of my Okto with three sources: 1) Apple TV 2) Raspberry Pi streamer with an Allo digione HAT and 3) Mac mini. 99% of the time I just use the Apple TV for audio/video source and airplay but changing sources is relatively easy.
Michael