Both are supported!will it allow me to import a REW CDSP filter output to a current config somehow - or is it for importing only full config files?
I have both streaming and analog input, analog into a Motu M4 connected via usb to the RPi 5 running CamillaDSP.I just started messing with CamillaDSP with MoodeAudio and an 8ch HDMI extractor (Very nice so far). I also have in my posession, the DAC8x and I'm waiting for my Pi 5 to arrive in the mail. I'm looking forward to trying this out. Are you doing streaming only or have you incorporated some sort of ADC (or digital)
input?
That parameter needs to be a device name, as recognized by the respective audio backend. hw:xxx is naming of linux alsa. You need to use WASAPI naming. IIRC if you run camilladsp with parameter -v (verbose), it will list all available devices including their string names to use in the config file.
Well, software audio loopback is not simple on any OS. Linux has a built-in loopback device, very flexible, and most tutorials focus on that one. Windows has third-party loopback softwares - see https://www.google.com/search?client=firefox-b-lm&q=audio+loopback+software+for+windows . Each gets setup differently, likely each has issues.The step by step guide also says "Here let's assume we already figured out all the Loopbacks etc and already know the devices to use." which is not helpful.
See e.g. https://www.diyaudio.com/community/...-interfaces-are-actually-multichannel.395126/However, this method only allows me to utilize two of the stereo input/output channels, for example Line Out 1-2,Line Out 3-4, Line Out 5-6, etc. And it doesn't appear to allow me to input multiple playback devices.
See https://www.diyaudio.com/community/...re-actually-multichannel.395126/#post-7252339 . Your device is multichannel, therefore it works as multichannel in linux. But your device vendor decided to split it into multiple pairs by its windows driver. You paid (big) money to Motu, they should be the ones receiving your complaintWhat I was hoping for was to recognize the entire device at once and use all 16 inputs and 18 outputs at once, and apparently the tutorials using the Raspberry Pi do this in the form of hw:Ultralitemk5.
I am afraid that's quite typical on windows where you are stuck with choices done by the vendors. Sorry for being honest, it's just the way it is.so I'm stuck again
They probably implement merging the stereo devices into one multichannel. Doing that in linux would be trivial as its audio layer offers tools for that (and much more). No such features built in windows. But IIRC people use tools like https://vb-audio.com/Matrix/ . It was thoroughly discussed e.g. here https://www.audiosciencereview.com/forum/index.php?threads/vb-matrix.48989/I still don't understand why DAWs like Cubase can do that though
Cool. Wouldn't it be easier to just use a tablet and html into Camilla instead? Even if local........
The CamillaDSP is working fine, the touchscreen doesn't work properly - no touch - on the RPi 5 .
Pavel, I welcome your constructive feedback. I will apply the changes immediately. In my defense I am a 76 year old long retired IBM 360/370 assembler programmer who is still learning, but with CamillaDSP and advice from people like you I have made my Klipschorns (patented in the year I was born - 1947) sound superb and coherent - no longer the smeared sounds from the wildly different length horns.@Wirrunna : IIUC your setup uses a USB soundcard on capture and an I2S device on playback. You have rate-adjust enabled, and it correctly measures the clock difference (at 1.0075). Yet your resampler is synchronous which will eventually result in xruns. IMO the asynchronous resampler is required in your setup.
CDSP v.2 changed buffer size to 4x chunksize. Optimal target level would be 75% of the buffer filled, i.e. 3 chunk sizes. Due to https://github.com/HEnquist/camilladsp/issues/335 only 2 chunksizes max can be set in the target level parameter, yet your config sets only 1 chunksize (target-level=2048). IMO setting target-level to 4096 (with the async resampler, of course) would make the setup more robust. In the upcoming CDSP v.3 (which has the max value of the parameter raised to full buffer size) I would recommend to set the target level to 3 x 2048 = 6144. To minimize latency, if needed you could lower the chunksize e.g. to 1024 in CDSP3.
I do not see any issues in the alsa section of DAC8X_KHorn Sqz.yml, just I would recommend to raise the target level to the two chunksizes mentioned, to give the feedback control more headroom.If you have time, could you have a look at the KHorn configs that are fed from Squeezelite running on the same RPi.
The raised limit will come in v3, it's not available yet.Pavel & Henrik, I have set the target level to 4096 and saved the config but get an error -
4095 will work! The computing effort isn't affected by the target level.Try 4095 - it will take some more computing effort