More > JRiver Media Center 24 for Linux
No Sound on any zone (except the default player) from MC24 Ubuntu 16 & 18
percy:
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
bob:
--- Quote from: 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
--- End quote ---
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?
percy:
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.
bob:
--- Quote from: percy on May 30, 2018, 12:23:44 am ---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.
--- End quote ---
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...
percy:
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
Navigation
[0] Message Index
[#] Next page
Go to full version