Thank you for your donation!


Solved: CamillaDSP - MPD unable to play flat.yml
#1
Hi,

Struggling to get CamillaDSP working in Moode - I'm hoping someone may be able to advise on what is going wrong.

Long term the goal is to get to a 6 output active crossover, but struggling with some of the baby steps first.


Hardware:
  • RPi 3B, running a fresh install of Moode 7.1
  • MiniDSP UDIO-8  which is basically a USBStreamer module (that then outputs up to 8 channels of AES/EBU to downstream DACs).


Working:
  • Fresh install of Moode 7.1 and play 2 channel audio to the USBStreamer ALSA.  Local file or SOMA radio works fine. 
  • aplay via the command line, playing of a local wav file to 2 channels 
  • aplay via the command line, playing of a local wav file to 4, 6, 8 channels using a local wav file as a test  
  • alsa speaker test to all or individual channels.


Not Working:
  • Turn CamillaDSP on and try to play 2 channel to the default output. "MPD error: failed to open audio output"
  • Turn CamillaDSP on and try to play 2 channel to the non-default output.  "MPD error: failed to open audio output". whether I use "hw:2,0" or "USBStreamer" as the name of the output.
  • Tried various buffer sizes (as suggested in another thread) - no change
When I go into the Camilla GUI, it always flashes a change in the status box on the right, starting with "State: backend offline", then after a second it changes to "State:offline".  This is with everything set to on, configurations set and saved and the rpi restarted. 

The mpd log file has the following:   (/var/log/mpd/log)
Code:
Apr 20 00:57:11.737 ERRO Playback error: ALSA function 'snd_pcm_hw_params_set_channels' failed with error 'EINVAL: Invalid argument', module: camilladsp
Apr 20 00:57 : exception: Failed to play on "ALSA CamillaDSP" (alsa): snd_pcm_poll_descriptors_revents() failed: No such device
Apr 20 00:57 : exception: Failed to open audio output
Apr 20 01:13 : player: played "http://ice1.somafm.com/beatblender-128-aac"
Apr 20 01:13 : player: played "http://ice1.somafm.com/beatblender-128-aac"


moodeutl -F
Code:
*** Scanning for playback devices ***
Card 0, ID `b1', name `bcm2835 HDMI 1'
 Device 0, ID `bcm2835 HDMI 1', name `bcm2835 HDMI 1', 4 subdevices (4 available)
   1..8 channels, sampling rate 8000..192000 Hz
   Sample formats: U8, S16_LE
   Buffer size range from 80 to 131072
   Period size range from 80 to 131072

     Subdevice 0, name `subdevice #0'
     Subdevice 1, name `subdevice #1'
     Subdevice 2, name `subdevice #2'
     Subdevice 3, name `subdevice #3'
Card 1, ID `Headphones', name `bcm2835 Headphones'
 Device 0, ID `bcm2835 Headphones', name `bcm2835 Headphones', 4 subdevices (4 available)
   1..8 channels, sampling rate 8000..192000 Hz
   Sample formats: U8, S16_LE
   Buffer size range from 80 to 131072
   Period size range from 80 to 131072

     Subdevice 0, name `subdevice #0'
     Subdevice 1, name `subdevice #1'
     Subdevice 2, name `subdevice #2'
     Subdevice 3, name `subdevice #3'
Card 2, ID `USBStreamer', name `USBStreamer'
 Device 0, ID `USB Audio', name `USB Audio', 1 subdevices (1 available)
   8 channels, sampling rate 44100..192000 Hz
   Sample formats: S16_LE, S32_LE
   Buffer size range from 12 to 65536
   Period size range from 6 to 32768

     Subdevice 0, name `subdevice #0'

moodeutl -l
Code:
moodeutl -l
20210420 021849 worker: -- Start
20210420 021849 worker: Successfully daemonized
20210420 021849 worker: Integrity check (passed)
20210420 021850 worker: File check (OK)
20210420 021850 worker: Session vacuumed
20210420 021850 worker: Session loaded
20210420 021850 worker: Debug logging (OFF)
20210420 021850 worker: -- Device
20210420 021850 worker: ALSA cards: (0:b1 | 1:Headphones | 2:USBStreamer | 3:empty
20210420 021850 worker: MPD config: (2:USBStreamer | mixer:(USBStreamer ) | card:2)
20210420 021850 worker: ALSA mixer actual (USBStreamer )
20210420 021850 worker: ALSA USBStreamer volume set to (0%)
20210420 021850 worker: -- System
20210420 021851 worker: Host     (moode)
20210420 021851 worker: moOde    (7.1.0 2021-03-15)
20210420 021851 worker: RaspiOS  (10.6)
20210420 021851 worker: Kernel   (5.4.77-v7+ #1371)
20210420 021851 worker: Platform (Pi-3B+ 1.3 1GB)
20210420 021851 worker: ARM arch (armv7l, 32-bit kernel)
20210420 021851 worker: MPD ver  (0.22.6_p0x3)
20210420 021851 worker: CPU gov  (ondemand)
20210420 021851 worker: USB boot enabled
20210420 021851 worker: File system not expanded yet
20210420 021851 worker: HDMI port on
20210420 021851 worker: -- Network
20210420 021851 worker: eth0 exists
20210420 021851 worker: IP addr (192.168.1.170)
20210420 021852 worker: Netmask (255.255.255.0)
20210420 021852 worker: Gateway (192.168.1.1)
20210420 021852 worker: Pri DNS (192.168.1.1)
20210420 021852 worker: Domain  (localdomain)
20210420 021852 worker: wlan0 exists
20210420 021852 worker: Pi integrated wlan0 power save disabled
20210420 021852 worker: wifi country (AU)
20210420 021852 worker: wlan0 SSID is blank
20210420 021852 worker: eth0 addr exists, AP mode not started
20210420 021852 worker: wlan0 address not assigned
20210420 021852 worker: -- Audio
20210420 021852 worker: ALSA card number (2)
20210420 021852 worker: MPD audio output (USBStreamer)
20210420 021852 worker: Audio formats (S16_LE, S32_LE)
20210420 021852 worker: ALSA mixer name (USBStreamer )
20210420 021852 worker: MPD volume control (software)
20210420 021852 worker: Hdwr volume controller exists
20210420 021852 worker: Max ALSA volume (100%)
20210420 021852 worker: Reset renderer active flags
20210420 021852 worker: CamillaDSP (flat.yml)
20210420 021852 worker: -- MPD
20210420 021852 worker: MPD started
20210420 021853 worker: MPD accepting connections
20210420 021853 worker: MPD output 1 ALSA Default (off)
20210420 021853 worker: MPD output 2 ALSA Crossfeed (off)
20210420 021853 worker: MPD output 3 ALSA Parametric EQ (off)
20210420 021853 worker: MPD output 4 ALSA Graphic EQ (off)
20210420 021853 worker: MPD output 5 ALSA Polarity Inv (off)
20210420 021853 worker: MPD output 6 ALSA CamillaDSP (on)
20210420 021853 worker: MPD output 7 ALSA Bluetooth (off)
20210420 021853 worker: MPD output 8 HTTP Server (off)
20210420 021853 worker: MPD crossfade (off)
20210420 021853 worker: MPD ignore CUE files (yes)
20210420 021853 worker: -- Feature availability
20210420 021853 worker: Source select (available)
20210420 021853 worker: Source select (source: MPD)
20210420 021853 worker: Source select (output: USBStreamer)
20210420 021853 worker: Bluetooth (available)
20210420 021853 worker: Airplay renderer (available)
20210420 021853 worker: Spotify renderer (available)
20210420 021853 worker: Squeezelite (available)
20210420 021853 worker: RoonBridge renderer (not installed)
20210420 021853 worker: UPnP renderer (available)
20210420 021853 worker: DLNA server (available)
20210420 021853 worker: UPnP browser (available)
20210420 021853 worker: GPIO button handler (available)
20210420 021853 worker: Stream recorder (n/a)
20210420 021853 worker: -- Music sources
20210420 021853 worker: USB source (383D-6A65)
20210420 021853 worker: NAS and UPnP sources (none configured)
20210420 021853 worker: -- Miscellaneous
20210420 021853 worker: USB volume knob (Off)
20210420 021853 worker: USB auto-mounter (udisks-glue)
20210420 021853 worker: LED0 (On)
20210420 021853 worker: LED1 (On)
20210420 021853 worker: Saved MPD vol level (0)
20210420 021853 worker: Preamp volume level (0)
20210420 021853 worker: MPD volume level (31) restored
20210420 021853 worker: ALSA USBStreamer volume (100%)
20210420 021853 worker: Auto-play (Off)
20210420 021853 worker: Maintenance interval (3 hrs)
20210420 021853 worker: Screen saver activation (Never)
20210420 021854 worker: Session permissions (OK)
20210420 021854 worker: Watchdog started
20210420 021854 worker: Ready
20210420 022030 worker: Job mpdrestart
Reply
#2
Some additional diagnostics

alsa speaker test for all 8 channels, when sent direct to the USBStreamer works fine

Code:
speaker-test -Ddefault:USBStreamer -c8  

speaker-test 1.1.8

Playback device is default:USBStreamer
Stream parameters are 48000Hz, S16_LE, 8 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 2048 to 16384
Period size range from 1024 to 1024
Using max buffer size 16384
Periods = 4
was set period_size = 1024
was set buffer_size = 16384
0 - Front Left
6 - Front Left Center
2 - Front Center
7 - Front Right Center
1 - Front Right
5 - Rear Right
4 - Rear Left
3 - LFE
Time per period = 23.571733


But the same when sent to the camilladsp alsa pipe gives the following error
Code:
speaker-test -Dcamilladsp -c2

speaker-test 1.1.8

Playback device is camilladsp
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 7680 to 32768
Period size range from 3840 to 4096
Using max buffer size 32768
Periods = 4
was set period_size = 4096
was set buffer_size = 32768
0 - Front Left
Apr 20 23:50:30.483 ERROthread '<unnamed>' panicked at 'slog-scope: No logger set. Use `slog_scope::set_global_logger` or `slog_scope::scope`.', /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/slog-scope-4.4.0/lib.rs:125:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Playback error: ALSA function 'snd_pcm_hw_params_set_channels' failed with error 'EINVAL: Invalid argument', module: camilladsp
Write error: -19,No such device
xrun_recovery failed: -19,No such device
Transfer failed: No such device
Reply
#3
I've done some more troubleshooting using bitlab's guide pt1- no progress but hopefully this helps someone more knowledgable than me!

The camillagui service wasn't running, when I did

Code:
systemctl list-unit-files

I've now made that start, using the following and confirmed it is enabled when the rpi is rebooted.  

Code:
sudo systemctl enable camillagui.service

Unfortunately, Moode config for CamillaDSP still is unchanged, with the backend offline (same as before, it changes after a second or so).

I've then tried to run CamillaDSP directly, using the v0.5 beta 6 download from github.  I've also checked all the dependencies and they are all there (as expected).

I've then checked the capabilities under alsa for my device (USBStreamer).Max sample rate is 192000

Code:
alsacap
*** Scanning for playback devices ***
Card 0, ID `b1', name `bcm2835 HDMI 1'
 Device 0, ID `bcm2835 HDMI 1', name `bcm2835 HDMI 1', 4 subdevices (4 available)
   1..8 channels, sampling rate 8000..192000 Hz
   Sample formats: U8, S16_LE
   Buffer size range from 80 to 131072
   Period size range from 80 to 131072

     Subdevice 0, name `subdevice #0'
     Subdevice 1, name `subdevice #1'
     Subdevice 2, name `subdevice #2'
     Subdevice 3, name `subdevice #3'
Card 1, ID `Headphones', name `bcm2835 Headphones'
 Device 0, ID `bcm2835 Headphones', name `bcm2835 Headphones', 4 subdevices (4 available)
   1..8 channels, sampling rate 8000..192000 Hz
   Sample formats: U8, S16_LE
   Buffer size range from 80 to 131072
   Period size range from 80 to 131072

     Subdevice 0, name `subdevice #0'
     Subdevice 1, name `subdevice #1'
     Subdevice 2, name `subdevice #2'
     Subdevice 3, name `subdevice #3'
Card 2, ID `USBStreamer', name `USBStreamer'
 Device 0, ID `USB Audio', name `USB Audio', 1 subdevices (1 available)
   8 channels, sampling rate 44100..192000 Hz
   Sample formats: S16_LE, S32_LE
   Buffer size range from 12 to 65536
   Period size range from 6 to 32768

However, the camilladsp config file has a max sample rate of 384000, so i've commented those out of the config file.


Code:
cat /etc/alsa/conf.d/camilladsp.conf
# For more info about this configuration file see: https://github.com/scripple/alsa_cdsp
pcm.camilladsp {
   type cdsp
   cpath "/usr/local/bin/camilladsp"
   config_out "/usr/share/camilladsp/working_config.yml"

   # config_cdsp says to use the new CamillaDSP internal substitutions.
   # When config_cdsp is set to an integer != 0 the hw_params and
   # extra samples are passed to CamillaDSP on the command line as
   # -f format -r samplerate -n channels -e extra_samples
   config_cdsp 1

####################################
# Set the values for your DAC here #
####################################
   min_channels 1
   max_channels 8
   rates = [
       44100
       48000
       88200
       96000
       176400
       192000
       #352800
       #384000
   ]

###############################################
# Uncomment the following lines,              #
# if you want more detailed logging output in #
# /var/log/mpd/log                            #
###############################################
  cargs [
#        -v
       -p "1234"
       -a "0.0.0.0"
  ]

Despite all this, when i run the (downloaded 0.5 beta 6) camilla DSP, it still gives the same error when i point it to flat.yml, irrespective of whether I limit the same rate and channels, or just go with the defaults.


Code:
camilladsp /usr/share/camilladsp/working_config.yml
Apr 21 04:57:27.482 ERRO Playback error: ALSA function 'snd_pcm_hw_params_set_channels' failed with error 'EINVAL: Invalid argument', module: camilladsp
Apr 21 04:57:27.483 INFO Playback thread has already stopped., module: camillalib::processing

Code:
#Verbose Mode, with 2 channels and limited to 44100 sample rate
~/camdsp $ camilladsp -v -n 2 -r 44100 /usr/share/camilladsp/working_config.yml
Apr 21 04:59:02.351 DEBG Read config file Some("/usr/share/camilladsp/working_config.yml"), module: camilladsp
Apr 21 04:59:02.352 DEBG Apply override for samplerate: 44100, module: camillalib::config
Apr 21 04:59:02.353 DEBG Samplerate changed, adjusting chunksize: 4096 -> 4096, module: camillalib::config
Apr 21 04:59:02.354 DEBG Scale extra samples: 0 -> 0, module: camillalib::config
Apr 21 04:59:02.354 DEBG Apply override for capture channels: 2, module: camillalib::config
Apr 21 04:59:02.354 DEBG Config is valid, module: camilladsp
Apr 21 04:59:02.355 DEBG Wait for config, module: camilladsp
Apr 21 04:59:02.355 DEBG Config ready, module: camilladsp
Apr 21 04:59:02.356 DEBG Using channels [true, true], module: camilladsp
Apr 21 04:59:02.357 DEBG Build new pipeline, module: camillalib::filters
Apr 21 04:59:02.357 DEBG build filters, waiting to start processing loop, module: camillalib::processing
Apr 21 04:59:02.358 DEBG Capture thread ready to start, module: camilladsp
Apr 21 04:59:02.359 ERRO Playback error: ALSA function 'snd_pcm_hw_params_set_channels' failed with error 'EINVAL: Invalid argument', module: camilladsp
Apr 21 04:59:02.360 DEBG Error while starting, release barrier, module: camilladsp
Apr 21 04:59:02.360 DEBG Wait for capture thread to exit.., module: camilladsp
Apr 21 04:59:02.361 DEBG starting captureloop, module: camillalib::filedevice
Apr 21 04:59:02.362 DEBG starting captureloop, module: camillalib::filedevice
Apr 21 04:59:02.363 DEBG Exit message received, sending EndOfStream, module: camillalib::filedevice
Apr 21 04:59:02.363 INFO Playback thread has already stopped., module: camillalib::processing
Apr 21 04:59:02.364 DEBG Restarting with new config, module: camilladsp
Apr 21 04:59:02.364 DEBG Wait for config, module: camilladsp
Apr 21 04:59:02.365 DEBG No config and not in wait mode, exiting!, module: camilladsp


Hope someone can assist, as I'm runnng out of ideas!
Reply
#4
I won't pretend to understand Camilla well at all, but I would make two observations.
  1. You should not need to mess about with starting bits on the command line.  I'd try doing a fresh installation and see if that helps.
  2. There is a bug with simple configurations like the flat.yml that is addressed in the next patch release.
Reply
#5
(04-21-2021, 10:29 AM)the_bertrum Wrote: I won't pretend to understand Camilla well at all, but I would make two observations.
  1. You should not need to mess about with starting bits on the command line.  I'd try doing a fresh installation and see if that helps.
  2. There is a bug with simple configurations like the flat.yml that is addressed in the next patch release.

Thanks for the good news on #2!  Any details or link to a github issue for this one, as I've got a bit of spare time, so happy to see if i can manually progress before 7.2 is released.  

In terms of not #1 needing the command line, I agree and it was only after the GUI didn't want to behave that I flashed a new image, tried the GUI again and then started tinkering via command line. GUI certainly looks great in terms of graphics and functionality (aside from the minor issue of no sound for the moment!) Smile
Reply
#6
@gingerbeer

First things first:
1. No need to run:
Code:
sudo systemctl enable camillagui.service

On the moOde camilladsp config page at the bottom there is a section called Pipeline Editor. It status is off flip the toggle switch to turn it on.

2. Also no need to comment out the 384 in the alsa_cdsp config.

3. CamillaDSP 5 beta 6 doesn't have fixes that would fixes the indicated problems. The changes with with preinstalled version are mostly related to using an alsa a capture devide (which isn't the case when use moOde out of the box).

4. The offline states in the camillagui is normal when no music is playing. moOde uses the alsa_cdsp device to automatic start camilladsp when music plays and stop camilladsp when the music plays. So if you don't have sound for any reason camilladsp will also be offline.  The camillagui will start in that case its own copy only for edit purpose (not for playback).

5. Because the configuration how moode deals with audio devices selection is changed in moode 7.2, I would not recommand to just 'pull' in the git repo. Just a little more patience until 7.2 is released. Which indeed fixes some camilladsp configuration issues (see change log on 7.2 thread), but probably not your current issue.

Now lets see if we can find a reason of the issues, but lets first go back to the beginning:
  • turnof camilladsp.
  • select headphone or hdmi as playdevice from the moode interface, hooking up to a headphone/speaker whatever you have available.
  • verify if you have sound by using the default supplied test file.
if succesfull:
  • at moode camilladsp config page make sure the default device option in 
  • select the flat configuration
  • press save
  • play again the test file
  •  if the first try isn't successfull select annother default available config press save and after that switch back to flat and press save.
  • play again the test file
Let us know what the results are?
Reply
#7
Quote:Now lets see if we can find a reason of the issues, but lets first go back to the beginning:
  • turnof camilladsp.
  • select headphone or hdmi as playdevice from the moode interface, hooking up to a headphone/speaker whatever you have available.
  • verify if you have sound by using the default supplied test file.
if successful:
  • at moode camilladsp config page make sure the default device option in 
  • select the flat configuration
  • press save
  • play again the test file
  •  if the first try isn't successfull select annother default available config press save and after that switch back to flat and press save.
  • play again the test file
Let us know what the results are?

Hi @bitlab 

Thank you for the very detailed response above.  

I started with a freshly flashed image of Moode 7.1 and I was able to get CamillaDSP working for both flat.yml and quick_convolution.yml, for both the HDMI and the headphone jack output. I noticed that when I change the device under the MPD settings GUI, then I would need to change-and-change-back the file in the CamillaDSP GUI, so that it would get the right hardware output device.  But great news being that there is sound coming through when Camilla is enabled, and it sounds different.

But then when I do exactly the same for the USBStreamer under the MPD settings GUI (and toggle/save the Camilla profiles) it goes back to "mpd playback error".  It does appear to be pointing to the right spot in hw:2,0 and all the settings look otherwise the same as for when it goes to the headphone jack (hw:1,0).  

So it would suggest the MiniDSP USBStreamer module is the culprit. In terms of Alsa everything else looks same as before (aplay -l; aplay -L etc.)

If you have any further test suggestions they would be greatly appreciated.

Code:
cat /var/log/mpd/log

Apr 22 10:23:57.307 INFO Starting playback from Prepared state, module: camillalib::alsadevice
[color=#000000][font=Menlo]Apr 22 10:24 : player: played "http://ice1.somafm.com/beatblender-128-aac"[/font][/color]
[color=#000000][font=Menlo]Apr 22 10:24:19.839 INFO Capture finished, module: camilladsp[/font][/color]
[color=#000000][font=Menlo]Apr 22 10:24:19.909 INFO Playback finished, module: camilladsp[/font][/color]
[color=#000000][font=Menlo]Apr 22 10:24:28.799 INFO Starting playback from Prepared state, module: camillalib::alsadevice[/font][/color]
[color=#000000][font=Menlo]Apr 22 10:24:46.710 ERRO Playback error: ALSA function 'snd_pcm_hw_params_set_channels' failed with error 'EINVAL: Invalid argument', module: camilladsp[/font][/color]
[color=#000000][font=Menlo]Apr 22 10:24:46.712 INFO Playback thread has already stopped., module: camillalib::processing[/font][/color]
[color=#000000][font=Menlo]Apr 22 10:24 : exception: Failed to play on "ALSA CamillaDSP" (alsa): snd_pcm_poll_descriptors_revents() failed: No such device[/font][/color]
[color=#000000][font=Menlo]Apr 22 10:24 : exception: Failed to open audio output[/font][/color]
Reply
#8
@gingerbeer

Quote:I noticed that when I change the device under the MPD settings GUI, then I would need to change-and-change-back the file in the CamillaDSP GUI, so that it would get the right hardware output device.
Yes that is normal after changing device the camilladsp config needs to be updated. WIth version 7.2 the general handling of output devicesis improved and doesn't require that step anymore.

I think that maybe the cause is in message below:
Code:
Apr 20 00:57:11.737 ERRO Playback error: ALSA function 'snd_pcm_hw_params_set_channels' failed with error 'EINVAL: Invalid argument', module: camilladsp
Which suggest that the set number of channels isn't correct (prob 2 in this case).
Alsacap shows indeed that this device only supports 8 channels:
Code:
8 channels, sampling rate 44100..192000 Hz

And not like the HDMI which acccept 1 to 8 channels:
Code:
 1..8 channels, sampling rate 8000..192000 Hz

Lets see what happens if we force CamillaDSP to use 8 channel output:
Because the regular setup of moOde with camilladsp covers only 2 channel devices, we need to disable the Default Device patch:
  • At the moOde camilladsp config scree toggle the Default Device option to OFF.
Create a new config to expriment with:
  • At the moOde camilladsp config screen select the flat config from the Pipeline configuration section
  • Press the copy button just below it and set the name to flat8ch:
Open the pipeline editor (=camillagui):
  • At the moOde camilladsp config screen go to the pipeline editor section
  • Set the Status to On
  • Set the Expert Mode to On
  • Press the open button
Within the camillagui change the playback device (bottom option at the devices tab):
  • Set the channels to 8
  • Check if the hardware device is correct
This will not be enough you need to change the mixer to map the input against the outputs:
  • In camillagui select the mixer tab
  • In the default present mixer set the number of outputs to 8
  • Map the inputs against the outputs (even if you don't need those, for example left to 4 and right to 4 channels)
  • Use the green plus at the bottom to add more output mappings.
  • When done press the Applto to CDSP (at the left side).

Try some music and let us know.
Reply
#9
Quote:@bitlab
Lets see what happens if we force CamillaDSP to use 8 channel output:

Smile Smile 

That worked perfectly - thank you for the amount of time and detailed instructions you've given.

8 channels of "flat" sounds pretty good already; next step room correction.
Reply
#10
Hi bitlab, looking for your help as well. Got the reference from gingerbeer, i am having similar issues and have tried to follow most of the recommendations but still cant seem to make moOde / Camilladsp to work.

my current step up - rasp pi, flashed the current moOde version (7.1) , creative xi fi 5.1 sound card. The intent is to create a 6 channel crossover + parametric eq etc

My past efforts to use camilladsp have been mixed...but they have been on another SBC (Rock64) with my creative sound card. I was able to make it work but with pulse and never using alsa.

This is what i did and still getting error message
- flashed the latest moOde 7.1
- set the MPD to Pi HDMI, the Mpd restarted
- went to audio settings, copied flat and renamed ....and when i click on check...it says its not a valid yml file
- went to the pipeline editor...made some changes
. . . . .went to capture device section, changed sample format to S16LE and get an error message that "500 Internal Server Error Server got itself in trouble"
can post logs record, playback details...

would greatly appreciate your help and guidance. Best
Reply


Forum Jump: