Thank you for your donation!


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


Problem: Camilladsp "failed to open audio output"
#1
I've been trying to set up quick convolution on Moode 8.3.6.  I'm using convolution files created in Cavern, because I wanted to start with something simple.  I've set up what I think is a faithful copy of the included convolution filters.  I've  set the sample rate to 48KHz to match the IR files.  

When I try to play a file I get an mpd error whose short text is "exception: Failed to open audio output."  The ALSA output is the HAT I'm using configured specifically as the default output.  It's shown correctly (dev 0,0) in the Camilladsp configuration.   I can supply the complete configuration if it would help.   Log file extract below.

Code:
Oct 19 08:06 : exception: Failed to open audio output
2023-10-19 15:06:42.205081 INFO [src/bin.rs:711] CamillaDSP version 1.0.3
2023-10-19 15:06:42.205436 INFO [src/bin.rs:712] Running on linux, aarch64
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Imaginary parts of both first and last values were non-zero.', src/fftconv.rs:150:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2023-10-19 15:06:42.289176 ERROR [src/alsadevice.rs:553] Message channel error: receiving on a closed channel
2023-10-19 15:06:42.289440 INFO [src/filedevice.rs:497] Processing thread has already stopped.
2023-10-19 15:06:42.289590 ERROR [src/bin.rs:344] Playback error: receiving on a closed channel
Oct 19 08:06 : output: Failed to play on "ALSA Default" (alsa): snd_pcm_poll_descriptors_revents() failed: No such device
no pid file present!
ALSA lib libasound_module_pcm_cdsp.c:869:(cdsp_hw_free) Error executing camilla_exit_cmd /usr/local/bin/cdspstorevolume

Oct 19 08:06 : exception: Failed to open audio output
Reply
#2
"dev 0,0" is not an ALSA device name.

In the CamillaDSP Pipeline editor under the Playback section, the device setting should be something like hw:0,0 or plughw:0,0
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#3
(10-19-2023, 03:34 PM)My mistake.  The device is listed as plughw:0,0 Tim Curtis Wrote: "dev 0,0" is not an ALSA device name.

In the CamillaDSP Pipeline editor under the Playback section, the device setting should be something like hw:0,0 or plughw:0,0
Reply
#4
In the main CamillaDSP Config screen the setting "Default device" ON uses the Output device and mode in Audio Config. If "Default device" is set to OFF the "device" setting in the Pipeline editor is used.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#5
(10-19-2023, 07:20 PM)I gave that a try but no luck.  I\m wondering if it's something about the files Cavern creates.  I've tried convolution files that come with the Camilla installation and they seem to work in quick convolution.  Tim Curtis Wrote: In the main CamillaDSP Config screen the setting "Default device" ON uses the Output device and mode in Audio Config. If "Default device" is set to OFF the "device" setting in the Pipeline editor is used.
Reply
#6
I tried creating a convolution setup using the Sennheiser headphone files that come with Camilladsp. It works just fine, or at least it plays audio. I'm pretty sure it's the files generated by Cavern. Is it true that convolution file formats, within WAV or RAW, can differ?
Reply
#7
@nosferatu_cat 

Did you notice this message in the midst of your log output?


Code:
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Imaginary parts of both first and last values were non-zero.', src/fftconv.rs:150:14


"fft" is a typical shortform for fast Fourier transform and the error message suggests to me that your convolution file contains data unacceptable to CamillaDSP.

It seems to me, though, that this is an issue to bring up to the Cavern devs to see what they may have to say since it's their output.

Regards,
Kent
Reply
#8
Also try posting in the main CamillaDSP thread at diyAudio.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#9
It was the file.  I created a quick and dirty IR file in REW and had no problem creating a quick convolution setup.  Now I have to learn how to create a good IR file.   Big Grin
Reply
#10
(10-21-2023, 04:55 PM)nosferatu_cat Wrote: It was the file.  I created a quick and dirty IR file in REW and had no problem creating a quick convolution setup.  Now I have to learn how to create a good IR file.   Big Grin

Nice :-)
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply


Forum Jump: