INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1] 2   Go Down

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

percy

  • Junior Woodchuck
  • **
  • Posts: 70

Cannot play on any zone (except the default player) from MC24 stable (24.0.28) on either Ubuntu 16.04 (fully updated 4.4.0-127-generic) or Ubuntu 18.04 (Linux 4.15.0-22-generic).  Not from the onboard Intel Audio device neither from the Xonar ST+H6 nor from the DLNA DAC’s. Only the player zone using the default [ALSA] through the PulseAudio sound server works
The MC23 (latest 23.0.102) works perfectly.
I did the installation (exactly as described) and the restore (File -> Library -> Restore Library) where I restored the backup I created from the MC23 version (using File -> Library > Backup Library)
So On both OSes (16 & 18) I have the MC23 working perfectly and the MC24 which when selecting a zone just pops up a window with “Nothing to play” and when I then select a track or Radio Station URL pops up with  Something went wrong with playback. Playback could not be started on the output ALSA using the format 192 Khz 2 Ch (or by the way any other format).
I also tried to configure MC24 (after the complete removal and reinstallation installation of MC24) without restoring the library but that resulted in exactly the same behavior.
I remember that when I first installed the MC24 on Ubuntu 16 it did work (although had some hiccups, which was to be expected by an early version) somewhere on the line after an update it stopped functioning (sadly I don’t remember from which version transition this occurred).
So I presume the problem resides in the configuration or program of MC24 (as MC23 can run on the same machine with the same configuration perfectly.
I added some text files with configuration details
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

Cannot play on any zone (except the default player) from MC24 stable (24.0.28) on either Ubuntu 16.04 (fully updated 4.4.0-127-generic) or Ubuntu 18.04 (Linux 4.15.0-22-generic).  Not from the onboard Intel Audio device neither from the Xonar ST+H6 nor from the DLNA DAC’s. Only the player zone using the default [ALSA] through the PulseAudio sound server works
The MC23 (latest 23.0.102) works perfectly.
I did the installation (exactly as described) and the restore (File -> Library -> Restore Library) where I restored the backup I created from the MC23 version (using File -> Library > Backup Library)
So On both OSes (16 & 18) I have the MC23 working perfectly and the MC24 which when selecting a zone just pops up a window with “Nothing to play” and when I then select a track or Radio Station URL pops up with  Something went wrong with playback. Playback could not be started on the output ALSA using the format 192 Khz 2 Ch (or by the way any other format).
I also tried to configure MC24 (after the complete removal and reinstallation installation of MC24) without restoring the library but that resulted in exactly the same behavior.
I remember that when I first installed the MC24 on Ubuntu 16 it did work (although had some hiccups, which was to be expected by an early version) somewhere on the line after an update it stopped functioning (sadly I don’t remember from which version transition this occurred).
So I presume the problem resides in the configuration or program of MC24 (as MC23 can run on the same machine with the same configuration perfectly.
I added some text files with configuration details
I"ll take a look here. The ALSA configuration changed recently. Perhaps there is an issue there?
What are your device settings (in MC audio configuration) for using the internal INTEL hardware?
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

I have included (attached) the MC “Machine Settings” and “User Settings”.
I Hope that you can find the necessary info in there.
I also enable the logging in MC but the only error I can detect there is “Cannot Play” without exact reason. I added also an excerpt of the MC24 log file

The fact that the MC23 installation works perfectly on both Ubuntu 16 & 18 on the same hardware and configuration then the MC24 installation seems for me to point to some configuration or software problem in MC24. Of course if the layout of (for example) the asound.conf file changed (or any other MC external configuration) and is interpreted  differently in MC23 & MC24 then it could even be that an configuration file external to MC must be modified. That would probably mean the MC23 and MC24 cannot run on the same machine configuration without modifying these config files in between runs.

Thanks very much for any help or info. Of course I am available for any more information that could solve my enigma.
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

I have included (attached) the MC “Machine Settings” and “User Settings”.
I Hope that you can find the necessary info in there.
I also enable the logging in MC but the only error I can detect there is “Cannot Play” without exact reason. I added also an excerpt of the MC24 log file

The fact that the MC23 installation works perfectly on both Ubuntu 16 & 18 on the same hardware and configuration then the MC24 installation seems for me to point to some configuration or software problem in MC24. Of course if the layout of (for example) the asound.conf file changed (or any other MC external configuration) and is interpreted  differently in MC23 & MC24 then it could even be that an configuration file external to MC must be modified. That would probably mean the MC23 and MC24 cannot run on the same machine configuration without modifying these config files in between runs.

Thanks very much for any help or info. Of course I am available for any more information that could solve my enigma.
What is
/mediapool
?
A locally connected drive or a share?

From a prompt, can you do a
df -k
 and
mount
and attach the responses...

Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

That is the 8TB WD RED mounted in that directory of the OS SSD drive. So it is a local drive not a network attached system
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

Sorry forgot your request for the df command
Code: [Select]
df -k
Filesystem      1K-blocks       Used  Available Use% Mounted on
udev              3895864          0    3895864   0% /dev
tmpfs              785052       3156     781896   1% /run
/dev/sda2       244568380    7998488  224076836   4% /
tmpfs             3925244         48    3925196   1% /dev/shm
tmpfs                5120          4       5116   1% /run/lock
tmpfs             3925244          0    3925244   0% /sys/fs/cgroup
/dev/loop0          21504      21504          0 100% /snap/gnome-logs/25
/dev/loop1           1664       1664          0 100% /snap/gnome-calculator/154
/dev/loop3          22144      22144          0 100% /snap/gnome-logs/31
/dev/loop2          88704      88704          0 100% /snap/core/4486
/dev/loop4          12544      12544          0 100% /snap/gnome-characters/69
/dev/loop5         143488     143488          0 100% /snap/gnome-3-26-1604/59
/dev/loop6         142848     142848          0 100% /snap/gnome-3-26-1604/64
/dev/loop7          88704      88704          0 100% /snap/core/4650
/dev/loop8           3840       3840          0 100% /snap/gnome-system-monitor/39
/dev/loop9           2432       2432          0 100% /snap/gnome-calculator/167
/dev/loop10          3456       3456          0 100% /snap/gnome-system-monitor/36
/dev/loop11         13312      13312          0 100% /snap/gnome-characters/86
/dev/sdb       7752327804 3649863980 3711746112  50% /mediapool
/dev/sda1          523248       4744     518504   1% /boot/efi
tmpfs              785048         24     785024   1% /run/user/1000
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

Thanks, how about the output of the
mount
command?
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

No the disk is statically mounted at startup in the /etc/fstab (see its content hereafter)
Code: [Select]
cat /etc/fstab

UUID=4d7295b6-e3d3-425a-9555-f1838b8bdde3 /               ext4    defaults,noatime,nodiratime,discard,errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=0504-3D1E  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0
UUID=045b0af4-acef-4a59-b920-14c430c75271 /mediapool      ext4    defaults 0 0
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

No the disk is statically mounted at startup in the /etc/fstab (see its content hereafter)
Code: [Select]
cat /etc/fstab

UUID=4d7295b6-e3d3-425a-9555-f1838b8bdde3 /               ext4    defaults,noatime,nodiratime,discard,errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=0504-3D1E  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0
UUID=045b0af4-acef-4a59-b920-14c430c75271 /mediapool      ext4    defaults 0 0
The mount command with no args gives details of the filesystems currently mounted.
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

sorry for my misunderstanding. Here is the output from the mount command
Code: [Select]
mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=3895864k,nr_inodes=973966,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=785052k,mode=755)
/dev/sda2 on / type ext4 (rw,noatime,nodiratime,discard,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16539)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
/var/lib/snapd/snaps/gnome-logs_25.snap on /snap/gnome-logs/25 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-calculator_154.snap on /snap/gnome-calculator/154 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-logs_31.snap on /snap/gnome-logs/31 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core_4486.snap on /snap/core/4486 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-characters_69.snap on /snap/gnome-characters/69 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-3-26-1604_59.snap on /snap/gnome-3-26-1604/59 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-3-26-1604_64.snap on /snap/gnome-3-26-1604/64 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core_4650.snap on /snap/core/4650 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-system-monitor_39.snap on /snap/gnome-system-monitor/39 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-calculator_167.snap on /snap/gnome-calculator/167 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-system-monitor_36.snap on /snap/gnome-system-monitor/36 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-characters_86.snap on /snap/gnome-characters/86 type squashfs (ro,nodev,relatime,x-gdu.hide)
/dev/sdb on /mediapool type ext4 (rw,relatime,data=ordered)
/dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=785048k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/var/lib/snapd/snaps/gnome-logs_34.snap on /snap/gnome-logs/34 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-calculator_170.snap on /snap/gnome-calculator/170 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-system-monitor_41.snap on /snap/gnome-system-monitor/41 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-characters_96.snap on /snap/gnome-characters/96 type squashfs (ro,nodev,relatime,x-gdu.hide)
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

From a terminal as the user running MC,
please do
/usr/lib/jriver/Media\ Center\ 24/alsacap
and post the results.
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

Code: [Select]
/usr/lib/jriver/Media\ Center\ 24/alsacap
*** 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..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 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 (0 available)
Error opening sound device for card 1, device 0: Device or resource busy.  Skipping.
  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'
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

Code: [Select]
/usr/lib/jriver/Media\ Center\ 24/alsacap
*** 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..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 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 (0 available)
Error opening sound device for card 1, device 0: Device or resource busy.  Skipping.
  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'
Interesting that it says that the Intel analog device is busy.
Can you try the xonar device on the analog output and turn on logging? If it doesn't work, please attach the log.
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

Yes thats because mc23 is playing internet radio over it.
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

I started MC24 and did as you requested.
I selected a Xonar output (bureau) and requested a FLAC 44.1 file to play
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

I started MC24 and did as you requested.
I selected a Xonar output (bureau) and requested a FLAC 44.1 file to play
Interesting, it's failing because the device says the number of channels (2) isn't available.
Logged

BryanC

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 2663

ALSA does not have a mixer. It's very likely something else is playing to your devices. Try shutting down browsers, old versions of MC, or any other program that could possibly be using your sound devices. If you have Pulse installed, check its mixer after you've done this to see if anything else is using it.

Using the alsa plugin for pulseaudio may allow you to switch outputs via MC zones as opposed to using the built-in mixer.
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

There are no browsers running at all (as far as I know).
I never run MC23 when I start MC24. (At first MC23 was not even installed on this version of Ubuntu, only MC24).
As you can see, when MC24 is not running all audio devices are available
Code: [Select]
/usr/lib/jriver/Media\ Center\ 24/alsacap
*** 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..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 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'
Can I uninstall pulseaudio from the system, does MC not need it? 
Code: [Select]
sudo apt remove --purge pulseaudio(MC is the only thing I use this server for. It is the dedicated music server of my home. It delivers music through his onboard soundcard (Motherboard + Asus Xonar) via a 12 channel amplifier and some DLNA DAC's (which do not function either with MC24).

"pavucontrol"  is not installed on my system.

Logged

BryanC

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 2663

Some programs depend on it so I wouldn't uninstall it. And in all honesty it's transcended its reputation at this point and works pretty well as a set-it-and-forget-it daemon. Not sure what your issue could be unfortunately.
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

Yes it is extremely strange as MC 23 works perfectly on the same PC with the same OS and the same configuration.
also (as mentioned before) when selecting "player" as zone (the only one I do never use ), the one that uses default [ALSA] through pulse audio server, that seems to work. Of course no sound is emerging from anywhere but MC does not report any error and the information in the MC indicates the track (or Internet Radio station) is playing normally.
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

I just tried this on 16.04 AMD64 without any issues.

You are running 23 and 24 under the same user account?

If not, is the 24 user a member of the audio group?
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

Yes MC23 and MC24 are installed on the same machine with the same Master licence.
Yes I am in the audio group
Code: [Select]
sudo getent group audio
audio:x:29:pulse,percy
As mentioned in a PM to you I can give you access to the Ubuntu machine via Teamviewer. I can forward you the ID and password via PM if that can help you.
I extremely appreciate your help. Thanks a lot
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

Yes MC23 and MC24 are installed on the same machine with the same Master licence.
Yes I am in the audio group
Code: [Select]
sudo getent group audio
audio:x:29:pulse,percy
As mentioned in a PM to you I can give you access to the Ubuntu machine via Teamviewer. I can forward you the ID and password via PM if that can help you.
I extremely appreciate your help. Thanks a lot
Since I can't reproduce this it appears to be something specific to your setup.

You could try:
Code: [Select]
sudo lsof | grep dev | grep -v null | grep -v pts | grep -v urandom | grep -v dri | grep -v udev | grep -v ptm | grep -v tty | grep -v event | grep -v console | grep -v log | grep -v zero | grep -v imobile | grep -v rfkillto see what has the sound devices open.
You said you were running 24.0.28. If you have installed 24.0.31 since then there could be an issue with your gstreamer setup (but not if you are still running 24.0.28).

Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

No i installed the latest version ( not the beta) and i checked it an hour ago again and it was still 24.0.28
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

As the output is rather large I saved it in a file which is attached
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

Oeps that was too fast. The previous one was while MC23 was running.
This is the one while MC24 is running
.
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

Oeps that was too fast. The previous one was while MC23 was running.
This is the one while MC24 is running
.
Is this ubuntu 16 or 18?
You are not using the default player zone from what you said previously, correct?
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

This is ubuntu 18. I do not use the default player. There is no actual phisical output from this default output, but i see the buffering and then the play time running when i select that zone
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

Is teamviewer acces not an option. It would allow to check directly. I have no problems with that. If at the end I have to reinstall from scratch, that would not be a problem. I have backups from everything no worries
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

By the way I also mentioned in my first entry that not even the DLNA (network DAC's) work.
This is not true. All the DLNA devices work perfectly, even DSF files in DoP to my PS Audio Direct Stream DAC.
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

I installed the beta version MediaCenter-24.0.32-amd64.deb but that did not change anything.
To provide the most detailed information I tried out all the selectable output available under the  MC24 Tools -> Options -> Audio -> Device settings (and there are a lot)
(I also attached this data together with the screen shots of the MC24 selectable output devices.
 
Code: [Select]
default [ALSA] playback/ recording through the PulseAudio sound server | (XONAR Front channels play, These are the ones configured in the Ubuntu System Sound Settings)
front:CARD=PCH,DEV=0 [ALSA] HDA Intel PCH, ALC1150 Analog Front Speakers | (All Intel channels play simultaniously)
front:CARD=STH6,DEV=0 [ALSA] Xonar ST+H6, Multi channel. Front Speakers | (Reports "Playback Problem")
hdaintel_dshare [ALSA] | (Reports "Playback Problem")
hdmi:CARD=HDMI,DEV=0 [ALSA] [ALSA] HDA Intel HDMI, HDMI 0, HDMI Audio Output | (Functions as expected but nothings is connected to the HDMI )
hdmi:CARD=HDMI,DEV=1 [ALSA] [ALSA] HDA Intel HDMI, HDMI 1, HDMI Audio Output | (Functions as expected but nothings is connected to the HDMI )
hdmi:CARD=HDMI,DEV=2 [ALSA] [ALSA] HDA Intel HDMI, HDMI 2, HDMI Audio Output | (Functions as expected but nothings is connected to the HDMI )
hw:CARD=HDMI,DEV=3 [ALSA] HDA Intel HDMI, HDMI 0 Direct hardware device without any conversion | (Functions as expected but nothings is connected to the HDMI )
hw:CARD=HDMI,DEV=7 [ALSA] HDA Intel HDMI, HDMI 1 Direct hardware device without any conversion | (Functions as expected but nothings is connected to the HDMI )
hw:CARD=HDMI,DEV=8 [ALSA] HDA Intel HDMI, HDMI 3 Direct hardware device without any conversion | (Functions as expected but nothings is connected to the HDMI )
hw:CARD=PCH,DEV=0 [ALSA] HDA Intel PCH, ALC1150 Analog Direct hardware device without any conversion | (All Intel channels play)
hw:CARD=PCH,DEV=1 [ALSA] HDA Intel PCH, ALC1150 Digital Direct hardware device without any conversion | (Functions as expected but nothings is connected to the digital )
hw:CARD=STH6,DEV=0 [ALSA] Xonar ST+H6, Multi channel. Direct hardware device without any conversion | (Reports "Playback Problem")
hw:CARD=STH6,DEV=1 [ALSA] Xonar ST+H6, Digital. Direct hardware device without any conversion | (Functions as expected but nothings is connected to the digital )
iec958:CARD=PCH,DEV=0 [ALSA] HDA Intel PCH, ACL1150 Digital. IEC958 (S/PDIF) Digital Audio Output | (Functions as expected but nothings is connected to the digital )
iec958:CARD=STH6,DEV=0 [ALSA] Xonar ST+H6, Multichannel. IEC958 (S/PDIF) Digital Audio Output | (Functions as expected but nothings is connected to the digital )
intel_black [ALSA] | (Reports "Playback Problem")
intel_gray_A [ALSA] | (Reports "Playback Problem")
intel_gray_B [ALSA] | (Reports "Playback Problem")
intel_orange_A [ALSA] | (Reports "Playback Problem")
intel_orange_B [ALSA] | (Reports "Playback Problem")
plughw:CARD=HDMI,DEV=3 [ALSA] HDA Intel HDMI, HDMI 0 Direct hardware device with all conversions | (Functions as expected but nothings is connected to the HDMI )
plughw:CARD=HDMI,DEV=7 [ALSA] HDA Intel HDMI, HDMI 1 Direct hardware device with all conversions | (Functions as expected but nothings is connected to the HDMI )
plughw:CARD=HDMI,DEV=8 [ALSA] HDA Intel HDMI, HDMI 2 Direct hardware device with all conversions | (Functions as expected but nothings is connected to the HDMI )
plughw:CARD=PCH,DEV=0 [ALSA] HDA Intel PCH, ALC1150 Analog Direct hardware device with all conversions | (All Intel channels play)
plughw:CARD=PCH,DEV=1 [ALSA] HDA Intel PCH, ALC1150 Digital Direct hardware device without any conversion | (Functions as expected but nothings is connected to the digital )
plughw:CARD=STH6,DEV=0 [ALSA] Xonar ST+H6, Multi channel. Direct hardware device with all conversions | (Reports "Playback Problem")
plughw:CARD=STH6,DEV=1 [ALSA] Xonar ST+H6, Digital. Direct hardware device with all conversions | (Functions as expected but nothings is connected to the digital )
pulse [ALSA] PulseAudio Server | (XONAR Front channels play, These are the ones configured in the Ubuntu System Sound Settings)
surround21:CARD=PCH,DEV=0 [ALSA] HDA Intel PCH, ALC1150 Analog 2.1 Surround output to Front Speakers and Subwoofer | (All Intel channels play simultaniously)
surround21:CARD=STH6,DEV=0 [ALSA] Xonar ST+H6, Multi channel. 2.1 Surround output to Front Speakers and Subwoofer | (Reports "Playback Problem")
surround40:CARD=PCH,DEV=0 [ALSA] HDA Intel PCH, ALC1150 Analog 4.0 Surround output to Front Center and Rear Speakers | (All Intel channels play simultaniously)
surround40:CARD=STH6,DEV=0 [ALSA] Xonar ST+H6, Multi channel. 4.0 Surround output to Front Center and Rear Speakers | (Reports "Playback Problem")
surround41:CARD=PCH,DEV=0 [ALSA] HDA Intel PCH, ALC1150 Analog 2.1 Surround output to Front Center and Rear Speakers and Subwoofer | (All Intel channels play simultaniously)
surround41:CARD=STH6,DEV=0 [ALSA] Xonar ST+H6, Multi channel. 2.1 Surround output to Front Center and Rear Speakers and Subwoofer | (Reports "Playback Problem")
surround50:CARD=PCH,DEV=0 [ALSA] HDA Intel PCH, ALC1150 Analog 4.0 Surround output to Front Center and Rear Speakers | (All Intel channels play simultaniously)
surround50:CARD=STH6,DEV=0 [ALSA] Xonar ST+H6, Multi channel. 4.0 Surround output to Front Center and Rear Speakers | (Reports "Playback Problem")
surround51:CARD=PCH,DEV=0 [ALSA] HDA Intel PCH, ALC1150 Analog 2.1 Surround output to Front Center and Rear Speakers and Subwoofer | (All Intel channels play simultaniously)
surround51:CARD=STH6,DEV=0 [ALSA] Xonar ST+H6, Multi channel. 2.1 Surround output to Front Center and Rear Speakers and Subwoofer | (Reports "Playback Problem")
surround71:CARD=PCH,DEV=0 [ALSA] HDA Intel PCH, ALC1150 Analog 2.1 Surround output to Front Center and Rear Speakers and Subwoofer | (All Intel channels play simultaniously)
surround71:CARD=STH6,DEV=0 [ALSA] Xonar ST+H6, Multi channel. 2.1 Surround output to Front Center and Rear Speakers and Subwoofer | (Reports "Playback Problem")
sysdefault:CARD=PCH,DEV=0 [ALSA] HDA Intel PCH, ALC1150 Analog Default Device | (Reports "Playback Problem")
sysdefault:CARD=STH6,DEV=0 [ALSA] Xonar ST+H6, Multi channel. Default Device | (Reports "Playback Problem")
xonar_blue_gray [ALSA] | (Reports "Playback Problem")
xonar_brown_black [ALSA] | (Reports "Playback Problem")
xonar_dshare [ALSA] | (Reports "Playback Problem")
xonar_purple_green [ALSA] | (Reports "Playback Problem")
xonar_red_white [ALSA] | (Reports "Playback Problem")

The ones with the color in the name are the ones defined by me in “/etc/asound.conf”, (and which work perfectly when MC23 is started on that system) and return the “Playback Problem” Pop-Up in MC24.

The entries which are digital (hdmi, SPDIF) whether from the Intel motherboard ALC1150 or Xonar seem to work (Why do the Xonar digital entries work?) also the Xonar analog front channels that where defined in the Ubuntu System Settings under Sound work when the Default ALSA device through the Pulse Audio Server is selected.

Any of the ALC1150 related entries output on all channels (independently of whether front, 2.1, 4.0, 4.1, 5.0, 5.1, 7.1 is selected).

Can you make up anything more from this Information?

And why does the MC23 on the same system with all the same settings (both on the Ubuntu level as  well as the MC level) work perfectly?

Another annoyance that I noticed (which I remember was also present in one of the early MC22 or MC23 releases) is that when playlists contain radio stations URL’s, the names of the playlist entries keep changing to the currently RDS info (most of the time the name of the song that is played). Maybe there is a good reason for doing this on certain content of the playlist (but I think most of the time this is not the case) Locking the playlist does not help. By the way exporting a playlist in MC23 (maybe also MC24)  under Ubuntu 18 and importing it in MC24 under Windows 10 results in an empty playlist being imported.

Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

What could cause MC24 (the beta 32-4-amd64.deb) only to play with the devices which are per default (not configured in my /etc/asound.conf) and fail on all devices which I defined in that /etc/asound.conf) file, while MC23 on the same machine (hardware and software) plays wonderfully on all these devices’ so the only changed factor is MC23 -> MC24?
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

What could cause MC24 (the beta 32-4-amd64.deb) only to play with the devices which are per default (not configured in my /etc/asound.conf) and fail on all devices which I defined in that /etc/asound.conf) file, while MC23 on the same machine (hardware and software) plays wonderfully on all these devices’ so the only changed factor is MC23 -> MC24?
Post a log from your latest attempt with 24.0.32-4
The changes from that fixed the audio open issues for everybody else. Not sure what your issue is at this point.
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

I attached the logfile from that run as Log.txt

Remark: Although that I installed the MediaCenter-24.0.32-4-amd64.deb When I output the About under the help menu in Mediacenter24 it still displays 24.0.32 (without the -4 at the end)
Also when I start mediacenter24 on the command line of a terminal it dumps an error on the terminal but mediacenter24 still starts up.
Code: [Select]
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: symbol gnutls_pkcs11_privkey_init version GNUTLS_3_4 not defined in file libgnutls.so.30 with link time reference
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so

Also when I try to restore my Mediacenter23 Library backup (File -> Library -> Restore Library) which until now restored correctly (although it most of the time crashed Mediacenter24 at the end of the operation), but now it crashes during the restore action. (On the terminal "Segmentation fault (core dumped)" is outputted.
I attached the logfile from that run as LogSegmentationFault.txt

Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

I attached the logfile from that run as Log.txt

Remark: Although that I installed the MediaCenter-24.0.32-4-amd64.deb When I output the About under the help menu in Mediacenter24 it still displays 24.0.32 (without the -4 at the end)
Also when I start mediacenter24 on the command line of a terminal it dumps an error on the terminal but mediacenter24 still starts up.
Code: [Select]
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: symbol gnutls_pkcs11_privkey_init version GNUTLS_3_4 not defined in file libgnutls.so.30 with link time reference
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so

Also when I try to restore my Mediacenter23 Library backup (File -> Library -> Restore Library) which until now restored correctly (although it most of the time crashed Mediacenter24 at the end of the operation), but now it crashes during the restore action. (On the terminal "Segmentation fault (core dumped)" is outputted.
I attached the logfile from that run as LogSegmentationFault.txt

You won't see the -4 in the version information in MC
The failed to load error message isn't connected to the issue.
Please email a copy of the MC23 library backup that causes MC crashes to me. bob (at) jriver (dot) com. Thanks.
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

I didn't have any issues restoring or loading your your library (in either MC23 or MC24)

Looking at your log file, I see that
/mediapool/Music/MarcLibrary/FLAC/Klassiek/Shostakovich Dmitri/Complete String Quartets - Mandelring Quartet/-01 -01 -01 -01 Volume 5 Nos 11, 15.flac
Is the last file processed and that's a cue/bin file.

I wouldn't expect MC to be analyzing that file if it had worked before.

Perhaps you have a hardware issue? An exhaustive memory scan might be useful.
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

The crash actually occurs before I even can select which Backup Library zip file to restore.
I select File -> Restore Library and then the system crashes away (the splash image of JRiver stays on)

Is there a way that I can remove whatever default remains in the field in which I have to put the backup file name? Maybe there is something in that path (part that does not exist anymore) that make him crash? (I cannot find where that path is stored (if that is the reason of the crash))

My System has a Ubuntu 18.04 Desktop (minimal) clean install on an empty SSD.
There is nothing else installed on that system than MC24 & MC23 & Teamviewer (as the system is stored away).
The Library Backup was taken from MC23 on Ubuntu 16.04.04.
I tried to install MC24 on the  Ubuntu 16.04.04 but it behaved exactly the same as now on Ubuntu 18.04.
The exported library imported without any issues on my MC23 which I installed on the Ubuntu 18.04.
The MC 23 also (luckily) works flawlessly (as before on Ubuntu 16)

I attached the screenshot of the terminal output on which I started mediacenter24 and tried the import.

I think that maybe we could find it if we knew why MC23 works perfectly.
Sorry for all the trouble this seems to be a hard nut to crush.
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

This morning I completely removed mediacenter24 as explained on your forum with
Code: [Select]
sudo apt remove mediacenter24
sudo rm -rf '/usr/lib/jriver/Media Center 24'
sudo rm -rf '/home/percy/.jriver/Media Center 24'

Followed by a clean reinstall
Code: [Select]
sudo apt update
sudo apt upgrade
sudo apt install mediacenter24
mediacenter24 /RestoreFromFile "Media Center24 Master-YYYYYY.mjr"
All that worked without a glitch.
Then I started MC24 (in a terminal)

Code: [Select]
mediacenter24
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: symbol gnutls_pkcs11_privkey_init version GNUTLS_3_4 not defined in file libgnutls.so.30 with link time reference
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so

MC23 does not output this warning when started in the terminal.

When I invoke "File -> Library -> Restore Library..." MC24 crashes just after the restore dialog is displayed but before I can enter anything.
Code: [Select]
Segmentation fault (core dumped)

Question: The warning, has this any influence on the problems:
crash when invoking File -> Library -> Restore Library...
Error popup and no sound output from any of the sound devices defined in /etc/asound.conf

Question: Does a clean install from MC24 tries to recover any settings from the already installed MC23 that could lead to the crash?

Thanks again for your patient and help.
If needed I can provide you with any information that would help in solving these problems.
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

When I tried to configure the library to import
Tools -> import -> Configure auto import.
After this I removed the default (music, video, picture) home folders from the library (this worked).
Then tried to add a my /mediapool/Library folder where my music resides.
When I prese browse a message appears in the terminal (where I started MC24)
Code: [Select]
Gtk-Message: 11:42:47.894: GtkDialog mapped without a transient parent. This is discouraged.

I can select the folder and press open. The MC24 crashes.
Code: [Select]
Segmentation fault (core dumped)
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

mediacenter24
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: symbol gnutls_pkcs11_privkey_init version GNUTLS_3_4 not defined in file libgnutls.so.30 with link time reference
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so


That message has to do with the integrated web browser in MC24 which doesn't exist in MC23.
The browser doesn't work on ubuntu 18 at any rate though that message has nothing to do with the issue and is unrelated to your crash.

Gtk-Message: 11:42:47.894: GtkDialog mapped without a transient parent. This is discouraged.

Is a warning message about the file open dialog. It's not harmful either.

Since your library didn't crash when I loaded it I assume you have a bad file in your /mediapool/Library folder that MC's not handling somehow.
The log SHOULD show the last file parsed before the crash.
After the crash, don't restart MC, instead look at the bottom of the Log.txt and post it.
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

I attached the logfile, but I as explained before the system crashes before I even could enter the name of the Mediacenter Backup ZIP file.
This crash also happens when I try to enter a path to import in the library. There I can enter the path but then the system crashes when I press Open.
Both of these operations (which crash on the beta 32-4) worked before on the latest (28 if I remember well), although the restore crashed the MC24 it still succeeded.
I will remove the beta and try the again the latest to see if that worked for the restore and import. And will report on that as soon as I tested it.

Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

I attached the logfile, but I as explained before the system crashes before I even could enter the name of the Mediacenter Backup ZIP file.
This crash also happens when I try to enter a path to import in the library. There I can enter the path but then the system crashes when I press Open.
Both of these operations (which crash on the beta 32-4) worked before on the latest (28 if I remember well), although the restore crashed the MC24 it still succeeded.
I will remove the beta and try the again the latest to see if that worked for the restore and import. And will report on that as soon as I tested it.
24.0.28 is prior to the integration of the internal browser.
I can load your library fine on 64 bit Debian Jessie and Stretch.
In fact your library loads fine on my ubuntu 18.04 LTS machine as well.
The browser even works there.

Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

The problem with the crashes ONLY occurs when I control Mediacenter24 via TeamViewer (This is independent of 24.0.28 or 24.0.32-4). This does not occur with MC23. That one works perfectly when operated via TeamViewer.
One thing the I noticed is that the restore did not restore any zones (Only playlists and Library paths)
I can live with the fact that I have to go cellar because it only crashes (as far as I know) while setting import paths or restoring libraries.
That fact that it skipped all my zones and there settings is of course cumbersome but the that these zones when reentered manually cannot play music is of course a show stopper.
I attached the log of the Library Restore which worked but did not restore the zones.
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

The problem with the crashes ONLY occurs when I control Mediacenter24 via TeamViewer (This is independent of 24.0.28 or 24.0.32-4). This does not occur with MC23. That one works perfectly when operated via TeamViewer.
One thing the I noticed is that the restore did not restore any zones (Only playlists and Library paths)
I can live with the fact that I have to go cellar because it only crashes (as far as I know) while setting import paths or restoring libraries.
That fact that it skipped all my zones and there settings is of course cumbersome but the that these zones when reentered manually cannot play music is of course a show stopper.
I attached the log of the Library Restore which worked but did not restore the zones.
As far as I'm aware, none of the virtual desktop solutions handle every X call properly and we do some pretty low level calls.
You might try another virtual desktop solution. TigerVNC works pretty well for me.

The zones come from the Settings file, not the library files.
A restore with the settings checkbox checked should pull them in.

Alternately you can copy the MC23 settings files into MC24 (with it not running) and MC24 when it's next run will use those settings file and update them to MC24 settings files.
If you copy both the User and Machine settings files you'll need to re-enter your registration code.
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

The settings checkbox was checked when I invoked the restore (I especially paid attention to that. Both checkboxes (settings & playlists) on that dialog where checked).
I also just tried to run MC23 and MC24 on the same machine.
That works flawless.
Also when using MC24 all the zones from MC23 are displayed and I can control the MC23 zones perfectly in MC24 (and they do play correctly!)
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

Is there any progress on this. Can I try anything to make it work on MC24.
If I invoke a playback on one of the sound devices defined in /etc/asoud.conf it works perfectly proving that on the Ubuntu side all is well (Else MC23 wouldn't work, or would it).

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

The same file works ok in MC23 and pops-up the error message in MC24 (with the same configuration since that was restored from a library backup of the working MC23 on the same machine).

I would be very grateful for any hint or solution.

Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

Is there any progress on this. Can I try anything to make it work on MC24.
If I invoke a playback on one of the sound devices defined in /etc/asoud.conf it works perfectly proving that on the Ubuntu side all is well (Else MC23 wouldn't work, or would it).

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

The same file works ok in MC23 and pops-up the error message in MC24 (with the same configuration since that was restored from a library backup of the working MC23 on the same machine).

I would be very grateful for any hint or solution.

1) In MC's audio device selection, if there is a blank description of the device, MC23's descriptions are OFFSET by the number of those blank entries from the actual device that description is referring to. This means if you are trying to compare MC24 and MC23 device opening you need to use the device name to compare, NOT the description (i.e. hw:CARD=PCH, DEV=0 ....)

2) MC24 has direct DSD support. That required changes in the device handling. There is no going back to MC23's method of opening the device.

3) It WORKS here on MC24 and Ubuntu 18 so there is something about your configuration that slipped by MC23's method of opening the device but doesn't with MC24.

Did you try the latest beta (24.0.35)? If not please do. In any case post a new log since there were some changes made to the device open since your last log.

Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

The version installed is the latest beta (24.0.35)?

I attached the log.txt file (in which I deleted most as it tends to get huge (multi MB) in very short time. I hope I catched the essential bit of which I inserted (as far as I can geuss) the part where it has the problem.

Code: [Select]
0003659: 645908224: Playback: CALSAPlugin::OpenALSA: Opened audio device xonar_brown_black
0003659: 645908224: Playback: CALSAPlugin::OpenALSA: Failed to get desired number of channels (2): Invalid argument
0003659: 645908224: Playback: CALSAPlugin::OpenALSA: Failed to set desired number of channels (2): Invalid argument
0003659: 645908224: Playback: CALSAPlugin::OpenALSA: Finish (23 ms)

When I select the device in MC24 (as in MC23) I select the audio device (Not the description) which I defined in my asound.conf
So for the 2 channels (stereo) in the Bureau I select "xonar_brown_black" from the device list in MC24.
For the speaker in the "Keuken" (Kitchen) I select 1 channel (mono) I select "intel_orange_B" as device in MC24


in "/etc/modprobe.d/alsa-base.conf" I added at the end.
I have also attached the complete "alsa-base.conf" (as "alsa-base.txt") in case you want to investigate something in there.

Code: [Select]
options snd slots=snd-hda-intel,snd-hda-intel,snd-virtuoso

to have always the save order of in "/proc/asound/cards"

Code: [Select]
cat /proc/asound/cards
 0 [HDMI           ]: HDA-Intel - HDA Intel HDMI
                      HDA Intel HDMI at 0xf7c34000 irq 30
 1 [PCH            ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0xf7c30000 irq 29
 2 [STH6           ]: AV200 - Xonar ST+H6

Here is my "/etc/asound.conf" file content
Code: [Select]
pcm_slave.xonar {
pcm "hw:2"
rate 192000
format S32_LE
channels 8
periods 128
period_time 0
period_size 1024
buffer_size 8192
}


pcm.xonar_dshare {
type dmix
ipc_key 2048
slave xonar
bindings {
0 0
1 1
2 2
3 3
4 4
5 5
6 6
7 7
}
}

pcm.xonar_red_white {
type plug
slave {
pcm "xonar_dshare"
channels 8
}
ttable.0.0 1 # in-channel 0, out-channel 0, 100% volume
ttable.1.1 1 # in-channel 1, out-channel 1, 100% volume
hint.description "Slaapkamer 2 Channels Stereo Amp Ch 1"
}

pcm.xonar_brown_black {
type plug
slave {
pcm "xonar_dshare"
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"
}

pcm.xonar_purple_green {
type plug
slave {
pcm "xonar_dshare"
channels 8
}
ttable.0.4 1 # in-channel 0, out-channel 4, 100% volume
ttable.1.5 1 # in-channel 1, out-channel 5, 100% volume
        hint.description "Berging 2 Channels Stereo Amp Ch 3"
}

pcm.xonar_blue_gray {
type plug
slave {
pcm "xonar_dshare"
channels 8
}
ttable.0.6 1 # in-channel 0, out-channel 6, 100% volume
ttable.1.7 1 # in-channel 1, out-channel 7, 100% volume
        hint.description "Living Rear 2 Channels Stereo Sony Amp"
}

pcm_slave.hda_intel {
pcm "hw:1"
rate 44100
channels 8
periods 128
period_time 0
period_size 1024
buffer_size 8192
}


pcm.hdaintel_dshare {
type dmix
ipc_key 4096
slave hda_intel
bindings {
0 0
1 1
2 2
3 3
4 4
5 5
6 6
7 7
}
}

pcm.intel_green {
type plug
slave {
pcm "hdaintel_dshare"
channels 8
}
ttable.0.0 1 # in-channel 0, out-channel 0, 100% volume
ttable.1.1 1 # in-channel 1, out-channel 1, 100% volume
        hint.description "Free Not in Use"
}

pcm.intel_black {
type plug
slave {
pcm "hdaintel_dshare"
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 "Free Not in Use"
}

pcm.intel_orange_A {
type plug
slave {
pcm "hdaintel_dshare"
channels 8
}
ttable.0.5 1 # in-channel 0, out-channel 5, 100% volume
        hint.description "Badkamer 1 Channel Mono Amp Ch 6"
}

pcm.intel_orange_B {
type plug
slave {
pcm "hdaintel_dshare"
channels 8
}
ttable.0.4 1 # in-channel 0, out-channel 4, 100% volume
        hint.description "Keuken 1 Channel Mono Amp Ch 6"
}

pcm.intel_gray_A {
type plug
slave {
pcm "hdaintel_dshare"
channels 8
}
ttable.0.6 1 # in-channel 0, out-channel 6, 100% volume
        hint.description "Terras 1 Channel Mono Amp Ch 5"
}

pcm.intel_gray_B {
type plug
slave {
pcm "hdaintel_dshare"
channels 8
}
ttable.0.7 1 # in-channel 1, out-channel 7, 100% volume
        hint.description "Gasten WC 1 Channel Mono Amp Ch 5"
}

The "/etc/asound.conf" is also attached (as asound.txt)

Thanks again for all your effort in trying to help me with this nasty problem.

Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874

I really don't know much of anything about redescribing devices using alsa.conf but it appears like your configuration isn't allowing the device to be opened as a 2 channel device which I assume your source material is or it wouldn't be trying to open it as 2 channels.
You might try testing this by using the output format in DSP studio to set the output to 7.1 for the 8 channel devices and 1 for the mono device.
Logged

percy

  • Junior Woodchuck
  • **
  • Posts: 70

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.
Logged
Pages: [1] 2   Go Up