INTERACT FORUM
More => Old Versions => JRiver Media Center 24 for Linux => Topic started by: percy on May 27, 2018, 09:30:15 am
-
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
-
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?
-
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.
-
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...
-
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
-
Sorry forgot your request for the df command
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
-
Thanks, how about the output of the
mount
command?
-
No the disk is statically mounted at startup in the /etc/fstab (see its content hereafter)
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
-
No the disk is statically mounted at startup in the /etc/fstab (see its content hereafter)
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.
-
sorry for my misunderstanding. Here is the output from the mount command
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)
-
From a terminal as the user running MC,
please do
/usr/lib/jriver/Media\ Center\ 24/alsacap
and post the results.
-
/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'
-
/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.
-
Yes thats because mc23 is playing internet radio over it.
-
I started MC24 and did as you requested.
I selected a Xonar output (bureau) and requested a FLAC 44.1 file to play
-
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.
-
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.
-
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
/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?
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.
-
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.
-
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.
-
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?
-
Yes MC23 and MC24 are installed on the same machine with the same Master licence.
Yes I am in the audio group
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
-
Yes MC23 and MC24 are installed on the same machine with the same Master licence.
Yes I am in the audio group
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:
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).
-
No i installed the latest version ( not the beta) and i checked it an hour ago again and it was still 24.0.28
-
As the output is rather large I saved it in a file which is attached
-
Oeps that was too fast. The previous one was while MC23 was running.
This is the one while MC24 is running
.
-
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?
-
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
-
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
-
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.
-
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.
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.
-
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?
-
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.
-
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.
/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
-
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.
/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.
-
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.
-
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.
-
This morning I completely removed mediacenter24 as explained on your forum with
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
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)
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.
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.
-
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)
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.
Segmentation fault (core dumped)
-
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.
-
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.
-
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.
-
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.
-
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.
-
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!)
-
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).
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.
-
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).
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.
-
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.
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.
options snd slots=snd-hda-intel,snd-hda-intel,snd-virtuoso
to have always the save order of in "/proc/asound/cards"
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
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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)
-
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
(https://www.alsa-project.org/main/index.php/Asoundrc)
-
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.
-
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.
-
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)
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?
-
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
-
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"
snd_pcm_hw_params_any() to initialize the hardware parameters
snd_pcm_hw_params_set_rate_resample() to disable alsa sample rate manipulation
snd_pcm_hw_params_set_access() to set access type SND_PCM_ACCESS_RW_INTERLEAVED)
Then:
snd_pcm_hw_params_test_channels() is where yours fails when 2 channels are requested.
-
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
-
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
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
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
aplay -D xonar_brown_black -vv JustUs.wav
which outputted
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.
-
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
-
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...
-
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.
-
Sadly enough it didn't change anything.
I have attached the logfile.
-
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
-
I attached the /usr/lib/jriver/Media\ Center\ 24/alsacap as (renamed to alsacap.txt) and also the log.txt
-
You were supposd to run alsacap and attach the output. ;D
-
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
*** 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'
-
I wonder if the device identifier we're using is just tripping up ALSA somehow.
-
Is there something I can provide as additional info to elude de inigma?
-
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.
-
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)
-
Are you specifying dmix: devices in MC23? (in MC's audio config)
NVM, I see those hints aren't used.
-
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).
-
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.
-
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.
-
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.
-
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.
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"
}
-
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.
:D