Topic: No Sound on any zone (except the default player) from MC24 Ubuntu 16 & 18 (Read 8106 times)

bob · « **Reply #50 on:** June 21, 2018, 08:55:27 am »

Quote from: percy on June 20, 2018, 09:15:51 am

But if i open that same device with the linux ALSA aplay it plays the music file on the requested 2 channels without any problem. And so does MC23! That is the reason which make me belive that the problem is somewhere in MC24. If you provide me with cat /proc/asound/cards output. Then i can provide you with the corresponding /etc/asound.conf file so jou can try it out on your system. Then maybe we can get a more detailed error info.

Why are you modifying the conf file in the first place? I've never had to do that.

percy · « **Reply #51 on:** June 21, 2018, 09:29:21 am »

Finally an easy one. As you could have guessed by looking at the "asound.conf" my system has the 7.1 channels audio from the motherboard as well as a Xonar ST plus the H6 extension board delivering another 7.1 channels. Now my home has speakers all around the house. 2 channels (stereo) in the bedroom, the bureau, the work room and the dining room. Then there are 1 channel (mono) speakers in the bathroom the terrace the kitchen and the WC. Everything was wired in when the house was build. In the storage room, where all the wiring comes together the Ubuntu 18.04 PC with JRiver MC24 is connected to a 12 channel amplifier plus a stereo amplifier powering all these speakers. On to of this there is, over the network using DLNA, the PS Audio Direct Stream DAC for the living room.
So I need to separate all these stereo and mono channels out of the two 7.1 channels provided by the on board an additional sound card.
That is what the ALSA configuration (in /etc/asound.conf) is all about. By the way this same configuration file could have been located in the home directory of the user running MC24 but then it would have been called "~/.asoundrc" and would have been user specific there where the one in /etc is system wide. The content would have been exactly the same.

Awesome Donkey · « **Reply #52 on:** June 21, 2018, 09:49:48 am »

Personally, I've only ever edited /usr/share/alsa/alsa.conf and /etc/modprobe.d/alsa-base.conf on Arch Linux/Antergos to get the hw: outputs working.

percy · « **Reply #53 on:** June 21, 2018, 10:02:43 am »

If you look at /usr/share/alsa/alsa.conf you will see that it includes both /etc/asound.conf and the .asoundrc from the home directory of the user (and in that sequence).
So what is in my asound.conf could have been in /usr/share/alsa/alsa.conf but is it preferred to leave that file untouched and put the specific configuration settings in the two (asound.conf, .asoundrc)

percy · « **Reply #54 on:** June 21, 2018, 10:08:36 am »

I forgot to add the URL of the explanation of the ALSA asound configuration for easy reference

https://www.alsa-project.org/main/index.php/Asoundrc

Awesome Donkey · « **Reply #55 on:** June 21, 2018, 10:10:34 am »

Quote from: percy on June 21, 2018, 10:02:43 am

If you look at /usr/share/alsa/alsa.conf you will see that it includes both /etc/asound.conf and the .asoundrc from the home directory of the user (and in that sequence).

Yep, it does. I just prefer going right to the root (bad pun, I know) of the "problem" and dealing with it that way. Always works fine for me.

bob · « **Reply #56 on:** June 21, 2018, 10:37:30 am »

Quote from: percy on June 21, 2018, 09:29:21 am

Finally an easy one. As you could have guessed by looking at the "asound.conf" my system has the 7.1 channels audio from the motherboard as well as a Xonar ST plus the H6 extension board delivering another 7.1 channels. Now my home has speakers all around the house. 2 channels (stereo) in the bedroom, the bureau, the work room and the dining room. Then there are 1 channel (mono) speakers in the bathroom the terrace the kitchen and the WC. Everything was wired in when the house was build. In the storage room, where all the wiring comes together the Ubuntu 18.04 PC with JRiver MC24 is connected to a 12 channel amplifier plus a stereo amplifier powering all these speakers. On to of this there is, over the network using DLNA, the PS Audio Direct Stream DAC for the living room.
So I need to separate all these stereo and mono channels out of the two 7.1 channels provided by the on board an additional sound card.
That is what the ALSA configuration (in /etc/asound.conf) is all about. By the way this same configuration file could have been located in the home directory of the user running MC24 but then it would have been called "~/.asoundrc" and would have been user specific there where the one in /etc is system wide. The content would have been exactly the same.

Ok I see what you are doing but you understand that it's failing a totally generic call.
The source material is 2 channels so when we open the output we set the hardware parameters to 2 channels. That is being rejected by alsa.
It really doesn't help to refer to MC23 as if it's "right" and MC24 is "wrong". The difference is that MC24 can't open the device as you have it configured.
It works on every hardware device I've tested on Ubuntu 18 and I'm seeing nothing odd about the way we are opening the device.

percy · « **Reply #57 on:** June 21, 2018, 10:49:56 am »

How do you suggest that I change the configuration to achieve my goal of separating the different hardware output channels?
By the way it is not only in MC23 that it works OK but also in the ALSA aplay tool (as I posted before)

Code: [Select]

aplay -D xonar_brown_black /home/percy/JustUs.wav
Playing WAVE '/home/percy/JustUs.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo

Where I select that xonar_brown_black device which I defined in asound.conf and asked ALSA to play a 2 channel file on it. No problem at all it played flawlessly.
So clearly the ALSA library can handle that configuration.

I have no problem at all changing the configuration if I only new what to change in it to accomplish the channel rearrangement.
Is it possible for you to tell me what primitive you call with which parameters? Maybe then I can search the reason. Also how did MC23 called the ALSA library?

percy · « **Reply #58 on:** June 21, 2018, 11:13:07 am »

Maybe MC24 now uses a native call that invokes below the ALSA sound library but then I cannot understand why the output devices which I configured in the ALSA configuration do show up in the "MC24 -> Tools -> Audio -> Audio Device" list, unless that list is build from the ALSA library devices and the actual library call to start the output is not.
Note, I am only guessing in the hope to hit the target as a blind guy

bob · « **Reply #59 on:** June 21, 2018, 02:02:36 pm »

Quote from: percy on June 21, 2018, 11:13:07 am

Maybe MC24 now uses a native call that invokes below the ALSA sound library but then I cannot understand why the output devices which I configured in the ALSA configuration do show up in the "MC24 -> Tools -> Audio -> Audio Device" list, unless that list is build from the ALSA library devices and the actual library call to start the output is not.
Note, I am only guessing in the hope to hit the target as a blind guy

MC asks alsa for the device hints then opens the device using the hinted choice that you select. For example, hw:CARD=PCH,DEV=0 [ALSA] long boring description here
is opened as "hw:CARD=PCH,DEV=0"

Code: [Select]

snd_pcm_hw_params_any() to initialize the hardware parameters

Code: [Select]

snd_pcm_hw_params_set_rate_resample() to disable alsa sample rate manipulation

Code: [Select]

snd_pcm_hw_params_set_access() to set access type SND_PCM_ACCESS_RW_INTERLEAVED)
Then:

Code: [Select]

snd_pcm_hw_params_test_channels() is where yours fails when 2 channels are requested.

percy · « **Reply #60 on:** June 21, 2018, 02:55:02 pm »

Thanks very mutch. Its late now. I will analyse all this info tommorow. Thanks a lot. I am not a linux specialist a not absolutely not in linux audio stuff but i will try to search if i. An find any corrolation that could help us solve this problem

percy · « **Reply #61 on:** June 24, 2018, 04:41:33 am »

I did another test to output with the "aplay" (and the "flac" program) to play first a FLAC 96Khz/24 bit file and afterwards a standard WAV 44.1/16 bit file both outputted via ALSA. I tried to play each of the music files through each of the speakers defined in my "/etc/asound.conf" ALSA configuration file. Each test went flawlessly and the sound emerged through the right speakers.
Here are the output from the test to one set of speakers. I used the -vv option on the aplay command because it gives a very detailed explanation on how the "aplay" command performs.
The FLAC file was played with

Code: [Select]

flac -d '/mediapool/Music/PercyLibrary/FLAC/Jazz/Bobby Hutcherson/Enjoy The View/05-Montara.flac' -o - | aplay  -vv -D xonar_brown_black

the output of this command

Code: [Select]

flac 1.3.2
Copyright (C) 2000-2009  Josh Coalson, 2011-2016  Xiph.Org Foundation
flac comes with ABSOLUTELY NO WARRANTY.  This is free software, and you are
welcome to redistribute it under certain conditions.  Type `flac' for details.

Playing WAVE 'stdin' : Signed 24 bit Little Endian in 3bytes, Rate 96000 Hz, Stereo
Plug PCM: Rate conversion PCM (192000, sformat=S24_3LE)
Converter: libspeex (external)
Protocol version: 10002
Its setup is:
  stream       : PLAYBACK
  access       : RW_INTERLEAVED
  format       : S24_3LE
  subformat    : STD
  channels     : 2
  rate         : 96000
  exact rate   : 96000 (96000/1)
  msbits       : 24
  buffer_size  : 4096
  period_size  : 512
  period_time  : 5333
  tstamp_mode  : NONE
  tstamp_type  : MONOTONIC
  period_step  : 1
  avail_min    : 512
  period_event : 0
  start_threshold  : 4096
  stop_threshold   : 4096
  silence_threshold: 0
  silence_size : 0
  boundary     : 2305843009213693952
Slave: Route conversion PCM (sformat=S32_LE)
  Transformation table:
    0 <- none
    1 <- none
    2 <- 0
    3 <- 1
    4 <- none
    5 <- none
    6 <- none
    7 <- none
Its setup is:
  stream       : PLAYBACK
  access       : MMAP_INTERLEAVED
  format       : S24_3LE
  subformat    : STD
  channels     : 2
  rate         : 192000
  exact rate   : 192000 (192000/1)
  msbits       : 24
  buffer_size  : 8192
  period_size  : 1024
  period_time  : 5333
  tstamp_mode  : NONE
  tstamp_type  : MONOTONIC
  period_step  : 1
  avail_min    : 1024
  period_event : 0
  start_threshold  : 8192
  stop_threshold   : 8192
  silence_threshold: 0
  silence_size : 0
  boundary     : 4611686018427387904
Slave: Direct Stream Mixing PCM
Its setup is:
  stream       : PLAYBACK
  access       : MMAP_INTERLEAVED
  format       : S32_LE
  subformat    : STD
  channels     : 8
  rate         : 192000
  exact rate   : 192000 (192000/1)
  msbits       : 24
  buffer_size  : 8192
  period_size  : 1024
  period_time  : 5333
  tstamp_mode  : NONE
  tstamp_type  : MONOTONIC
  period_step  : 1
  avail_min    : 1024
  period_event : 0
  start_threshold  : 8192
  stop_threshold   : 8192
  silence_threshold: 0
  silence_size : 0
  boundary     : 4611686018427387904
Hardware PCM card 2 'Xonar ST+H6' device 0 subdevice 0
Its setup is:
  stream       : PLAYBACK
  access       : MMAP_INTERLEAVED
  format       : S32_LE
  subformat    : STD
  channels     : 8
  rate         : 192000
  exact rate   : 192000 (192000/1)
  msbits       : 24
  buffer_size  : 8192
  period_size  : 1024
  period_time  : 5333
  tstamp_mode  : ENABLE
  tstamp_type  : MONOTONIC
  period_step  : 1
  avail_min    : 1024
  period_event : 0
  start_threshold  : 1
  stop_threshold   : 4611686018427387904
  silence_threshold: 0
  silence_size : 4611686018427387904
  boundary     : 4611686018427387904
  appl_ptr     : 0
  hw_ptr       : 4098
########################            +              | 70%^C-Montara.flac: 2% complete

The WAV file was started with

Code: [Select]

aplay -D xonar_brown_black -vv JustUs.wav

which outputted

Code: [Select]

Playing WAVE 'JustUs.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Plug PCM: Rate conversion PCM (192000, sformat=S16_LE)
Converter: libspeex (external)
Protocol version: 10002
Its setup is:
  stream       : PLAYBACK
  access       : RW_INTERLEAVED
  format       : S16_LE
  subformat    : STD
  channels     : 2
  rate         : 44100
  exact rate   : 44100 (44100/1)
  msbits       : 16
  buffer_size  : 1881
  period_size  : 235
  period_time  : 5333
  tstamp_mode  : NONE
  tstamp_type  : MONOTONIC
  period_step  : 1
  avail_min    : 235
  period_event : 0
  start_threshold  : 1881
  stop_threshold   : 1881
  silence_threshold: 0
  silence_size : 0
  boundary     : 1058908862385487872
Slave: Route conversion PCM (sformat=S32_LE)
  Transformation table:
    0 <- none
    1 <- none
    2 <- 0
    3 <- 1
    4 <- none
    5 <- none
    6 <- none
    7 <- none
Its setup is:
  stream       : PLAYBACK
  access       : MMAP_INTERLEAVED
  format       : S16_LE
  subformat    : STD
  channels     : 2
  rate         : 192000
  exact rate   : 192000 (192000/1)
  msbits       : 16
  buffer_size  : 8192
  period_size  : 1024
  period_time  : 5333
  tstamp_mode  : NONE
  tstamp_type  : MONOTONIC
  period_step  : 1
  avail_min    : 1024
  period_event : 0
  start_threshold  : 8192
  stop_threshold   : 8192
  silence_threshold: 0
  silence_size : 0
  boundary     : 4611686018427387904
Slave: Direct Stream Mixing PCM
Its setup is:
  stream       : PLAYBACK
  access       : MMAP_INTERLEAVED
  format       : S32_LE
  subformat    : STD
  channels     : 8
  rate         : 192000
  exact rate   : 192000 (192000/1)
  msbits       : 24
  buffer_size  : 8192
  period_size  : 1024
  period_time  : 5333
  tstamp_mode  : NONE
  tstamp_type  : MONOTONIC
  period_step  : 1
  avail_min    : 1024
  period_event : 0
  start_threshold  : 8192
  stop_threshold   : 8192
  silence_threshold: 0
  silence_size : 0
  boundary     : 4611686018427387904
Hardware PCM card 2 'Xonar ST+H6' device 0 subdevice 0
Its setup is:
  stream       : PLAYBACK
  access       : MMAP_INTERLEAVED
  format       : S32_LE
  subformat    : STD
  channels     : 8
  rate         : 192000
  exact rate   : 192000 (192000/1)
  msbits       : 24
  buffer_size  : 8192
  period_size  : 1024
  period_time  : 5333
  tstamp_mode  : ENABLE
  tstamp_type  : MONOTONIC
  period_step  : 1
  avail_min    : 1024
  period_event : 0
  start_threshold  : 1
  stop_threshold   : 4611686018427387904
  silence_threshold: 0
  silence_size : 4611686018427387904
  boundary     : 4611686018427387904
  appl_ptr     : 0
  hw_ptr       : 4098

I sadly have little time the next month as there are some workings in the house (new windows and floors so I have to clear out my bureau and its equipment) So my idea to write some program myself (although I think it won't bring any solution because if "aplay" works fine?) but it will have to wait till the end of July.

Meanwhile this information may shed some light on the matter.
I cannot thank you guys enough for spending all that effort in helping me out with this problem.
Luckily MC23 still function flawlessly on that same system so I am currently still enjoying the music throughout my home thanks to it.

Hendrik · « **Reply #62 on:** June 24, 2018, 05:06:54 am »

From what I can tell, we should probably be setting the sample format before setting the channels. At least thats the big difference to every other ALSA example or comparable use-case that I could spot.
Its typically create -> access/disablehwresampling -> format -> channel -> sample rate -> everything else

bob · « **Reply #63 on:** June 25, 2018, 10:00:02 am »

Quote from: Hendrik on June 24, 2018, 05:06:54 am

From what I can tell, we should probably be setting the sample format before setting the channels. At least thats the big difference to every other ALSA example or comparable use-case that I could spot.
Its typically create -> access/disablehwresampling -> format -> channel -> sample rate -> everything else

I'll check and see if that changed.
I couldn't find anything about order in any of documentation I looked at...

bob · « **Reply #64 on:** June 25, 2018, 11:15:54 am »

Try this build:
http://files.jriver.com/mediacenter/test/MediaCenter-24.0.37-amd64.deb

And see if it does anything different.
If not, attach a log.

percy · « **Reply #65 on:** June 25, 2018, 11:32:52 am »

Sadly enough it didn't change anything.
I have attached the logfile.

bob · « **Reply #66 on:** June 25, 2018, 11:57:02 am »

Ok try this:
http://files.jriver.com/mediacenter/test/MediaCenter-24.0.37-2-amd64.deb

I still think your problem is your configuration.
MC's configuration sequence just sets parameters until the actual call to set the hardware params is done and the error is that 2 channel mode isn't available.

If it fails attach the log.
Also attach the results of
/usr/lib/jriver/Media\ Center\ 24/alsacap

percy · « **Reply #67 on:** June 25, 2018, 12:50:38 pm »

I attached the /usr/lib/jriver/Media\ Center\ 24/alsacap as (renamed to alsacap.txt) and also the log.txt

Hendrik · « **Reply #68 on:** June 25, 2018, 12:55:26 pm »

You were supposd to run alsacap and attach the output.

percy · « **Reply #69 on:** June 25, 2018, 12:58:39 pm »

Sorry about that, my fault, I am completely stupid. I already asked myself what the heck does he want with an executable?
Anyway, Here is the output

Code: [Select]

*** Scanning for playback devices ***
Card 0, ID `HDMI', name `HDA Intel HDMI'
  Device 3, ID `HDMI 0', name `HDMI 0', 1 subdevices (1 available)
    2 channels, sampling rates 32000, 44100, 48000 Hz
    Sample formats: S16_LE, S32_LE
      Subdevice 0, name `subdevice #0'
  Device 7, ID `HDMI 1', name `HDMI 1', 1 subdevices (1 available)
    2..8 channels, sampling rates 32000, 44100, 48000, 88200, 96000, 176400, 192000 Hz
    Sample formats: S16_LE, S32_LE, IEC958_SUBFRAME_LE
      Subdevice 0, name `subdevice #0'
  Device 8, ID `HDMI 2', name `HDMI 2', 1 subdevices (1 available)
    2..8 channels, sampling rates 32000, 44100, 48000, 88200, 96000, 176400, 192000 Hz
    Sample formats: S16_LE, S32_LE, IEC958_SUBFRAME_LE
      Subdevice 0, name `subdevice #0'
Card 1, ID `PCH', name `HDA Intel PCH'
  Device 0, ID `ALC1150 Analog', name `ALC1150 Analog', 1 subdevices (1 available)
    2..8 channels, sampling rates 44100, 48000, 96000, 192000 Hz
    Sample formats: S16_LE, S32_LE
      Subdevice 0, name `subdevice #0'
  Device 1, ID `ALC1150 Digital', name `ALC1150 Digital', 1 subdevices (1 available)
    2 channels, sampling rates 32000, 44100, 48000, 88200, 96000, 192000 Hz
    Sample formats: S16_LE, S32_LE
      Subdevice 0, name `subdevice #0'
Card 2, ID `STH6', name `Xonar ST+H6'
  Device 0, ID `Multichannel', name `Multichannel', 1 subdevices (1 available)
    2..8 channels, sampling rates 32000, 44100, 48000, 88200, 96000, 176400, 192000 Hz
    Sample formats: S16_LE, S32_LE
      Subdevice 0, name `subdevice #0'
  Device 1, ID `Digital', name `Digital', 1 subdevices (1 available)
    2 channels, sampling rates 32000, 44100, 48000, 88200, 96000, 176400, 192000 Hz
    Sample formats: S16_LE, S32_LE
      Subdevice 0, name `subdevice #0'

Hendrik · « **Reply #70 on:** June 25, 2018, 01:00:54 pm »

I wonder if the device identifier we're using is just tripping up ALSA somehow.

percy · « **Reply #71 on:** June 25, 2018, 01:03:39 pm »

Is there something I can provide as additional info to elude de inigma?

bob · « **Reply #72 on:** June 25, 2018, 01:26:15 pm »

Looking back at the stuff you posted earlier, it seems all of your intel devices work, only the xonar device you've split from multichannel to single or double channel won't open.
Since I moved the number of channels in the last build to under the sample rate, it's now the sample rate set that's not working.
I don't see in your config files where the discrete devices like xonar_brown_black is defined but I suspect you aren't specifying the possible sample rates and channels in that definition.

percy · « **Reply #73 on:** June 25, 2018, 01:44:37 pm »

No the intel devices do not work either. Only the unsplit device work (whatever is defined as 5.1 7.1 4.0 etc) plays , but nor as specified either as all channels play the same (cant say it is stereo or mono) but the all play the same via MC24 (net via aplay or MC23). In my config I define the cards as 8 channel (7.1) with sample rate that is compatible (192000) then the “dmix” is used to provide the necessary bindings for the “plug” type definitions where the channels are split into the sets (pairs for the rooms with stereo (2) speakers and 1 channel for the mono rooms) that I have in the “ttable” channel repartitions. The alsacap program only list the basic device capabilities. It does (apparently) not inform about the definitions descriped in the "/etc/asound.conf (which I reattach for your easy access)

bob · « **Reply #74 on:** June 25, 2018, 01:54:36 pm »

Are you specifying dmix: devices in MC23? (in MC's audio config)
NVM, I see those hints aren't used.

percy · « **Reply #75 on:** June 25, 2018, 02:06:32 pm »

Yes the configuration (both in Unix (Ubuntu both 16 & 18)) AND mc (BOTH 23 & 24) is exactly the same (identical). For Ubuntu this is obvious as I run MC23 & MC24 on the dame PC (and of course OS. I either start MC23 where everything works as expected or MC24) The configuration of MC24 is the restore from the backup which runs under MC23. So you may assume that the only difference is the MC23 to MC24 software. Where MC23 just as aplay work perfectly as expected on every device defined in /etc/asound.conf (sadly enough not yet on MC24).

bob · « **Reply #76 on:** June 25, 2018, 03:13:56 pm »

Quote from: percy on June 25, 2018, 02:06:32 pm

Yes the configuration (both in Unix (Ubuntu both 16 & 18)) AND mc (BOTH 23 & 24) is exactly the same (identical). For Ubuntu this is obvious as I run MC23 & MC24 on the dame PC (and of course OS. I either start MC23 where everything works as expected or MC24) The configuration of MC24 is the restore from the backup which runs under MC23. So you may assume that the only difference is the MC23 to MC24 software. Where MC23 just as aplay work perfectly as expected on every device defined in /etc/asound.conf (sadly enough not yet on MC24).

Like I said before, it's not useful to compare to MC23.

Try this:
http://files.jriver.com/mediacenter/test/MediaCenter-24.0.37-3-amd64.deb

There is more debugging info in the log.

percy · « **Reply #77 on:** June 26, 2018, 04:51:06 am »

I Solved the problem. I attached the log from the successful run.

The solution is to set in the MC24 Tools -> Options-> Audio -> DSP & Output Format -> Output Format device of the "Zone to Configure" to either 7.1 (2 channels in 7.1 also works)
From what I see in the log it is not the bitrate that causes the problem (the 19200 in the MC24 configuration is consistent with the 19200 in the /etc/asound.conf configuration for the DMIX plugin of the XONAR card/device.

The problem is that it refuses to set the device to 2 channels (thinking only exactly 8 channels is possible Min & Max are both 8 ).
Although I select 7.1 channels in MC24 it only play sound through the 1 or 2 channels split out from that device in defined in my /etc/asound.conf.
So that solved the problem, simply set the output format in MC24 to the total number of channels the specific sound card device possesses and not the number of channels required.

bob · « **Reply #78 on:** June 26, 2018, 08:49:17 am »

Quote from: percy on June 26, 2018, 04:51:06 am

I Solved the problem. I attached the log from the successful run.

The solution is to set in the MC24 Tools -> Options-> Audio -> DSP & Output Format -> Output Format device of the "Zone to Configure" to either 7.1 (2 channels in 7.1 also works)
From what I see in the log it is not the bitrate that causes the problem (the 19200 in the MC24 configuration is consistent with the 19200 in the /etc/asound.conf configuration for the DMIX plugin of the XONAR card/device.

The problem is that it refuses to set the device to 2 channels (thinking only exactly 8 channels is possible Min & Max are both 8 ).
Although I select 7.1 channels in MC24 it only play sound through the 1 or 2 channels split out from that device in defined in my /etc/asound.conf.
So that solved the problem, simply set the output format in MC24 to the total number of channels the specific sound card device possesses and not the number of channels required.

That makes sense, the last change I made was to look and display in the log the number of channels that are allowed by ALSA.
I think that if you define your pseudo devices specifying 2 channels (or 1 in the cases they are mono) you could get it to work as well.

percy · « **Reply #79 on:** June 26, 2018, 09:32:13 am »

The pseudo device "xonar_brown_black" is defined as having 2 channels (ttable parameter defines which 2 channels from the "xonar_dmix" plug in)
If I change the "channels 8" in the slave definition of the "plug" type "xonar_brown_black" pseudo device then it doesn't function again.

Code: [Select]

pcm.xonar_brown_black {
        type plug
        slave {
                pcm "xonar_dmix"
                channels 8
        }
        ttable.0.2 1    # in-channel 0, out-channel 2, 100% volume
        ttable.1.3 1    # in-channel 1, out-channel 3, 100% volume
        hint.description "Bureau 2 Channels Stereo Amp Ch 2"
}

percy · « **Reply #80 on:** June 26, 2018, 09:50:40 am »

In any case I want to thank you for the incredible patience and sustained help you provided for solving my problem. Thanks very much.
The fact that I have to set the number of channels to 7.1 in MC24 does not bother me at all.
Should you need any help in collecting information to research any further this issue feel free to call on me. If I can provide any help I will gladly be of assistance.

INTERACT FORUM

Author Topic: No Sound on any zone (except the default player) from MC24 Ubuntu 16 & 18 (Read 8106 times)