My previous post was sent before I remembered my msi85 machine has two TW installations, one with "normal" KF5, the other with zypper locks set to block replacing KDE4 functionality with KF5's feature losses and crashing. The one with KF5 continues to have audio trouble. The one without KF5 works as well as 13.1, 13.2 and 42.1. Only two locks are responsible for the KDE4 retention: breez* kde-oxygen-fonts Takashi Iwai composed on 2015-12-24 09:59 (UTC+0100):
On Thu, 24 Dec 2015 09:16:25 +0100 Felix Miata wrote:
Takashi Iwai composed on 2015-12-21 09:31 (UTC+0100):
Based upon your direction, mostly having to do with including 'options snd-hda-intel index=1,0' in /etc/modprobe.d/, setting set_default_volume -f 0, and adjusting alsamixer in multi-user.target, I have sound of all types tried on host msi85 in the following:
13.1/TDE and KDE4 13.2/KDE4 42.1/KDE3
In TW/KF5 I get sound from aplay, YaST2 play test sound and Firefox/YoutubeHTML5, but not SMPlayer or KF5.
Check which sound backend your SMPlayer is using. If it's a direct ALSA-API usage, this should work as long as the backend mplayer can interpret.
Changing between pure alsa and alsa (0.0 - HDA Intel PCH) produces no apparent difference. It's set to simply alsa on the working SMPlayer in the KDE4 TW installation.
In K5 systemsettings multimedia, no sound devices are found or listed on either device preference or backend tab, even though phonon-backend-vlc-0.8.2-1.1 from OSS is installed, and content from /proc/asound/devices and /proc/asound/cards matches that in the other installations. SMPlayer-15.11.0-1.1 from OSS exits with code 2 and reports "Failed to recognize file format" trying to load any audio or video file, even after explicitly setting its sound preference to the same alsa HDA Intel PCH device that works elsewhere.
Well, it doesn't mean anything about the sound device failure directly. It rather suggests that your SMPlayer can't play the given file format. What file did you try to play?
Several audio and video types. Can't say exactly which, because the failure causes the selections not to be remembered in player history.
Doesn't it work even with a normal WAV file?
Doesn't work even with /usr/share/sounds/alsa/test.wav.
If playing a normal WAV file still doesn't work, report it to Bugzilla, likely KDE category or such, as it's either an application itself or KF5-specific problem.
That's the question, against what? Is the KDE failure likely the same failure as smplayer's? [broken KF5]
# rpm -qa | sort | egrep 'alsa|arts|mix|kspace|imedia|pavucontrol|phono|pulse' alsa-1.1.0-1.1.x86_64 alsa-firmware-1.0.29-1.1.noarch alsa-oss-1.0.28-3.3.x86_64 alsa-plugins-1.1.0-2.1.x86_64 alsa-utils-1.1.0-1.2.x86_64 kmix-15.08.3-1.1.x86_64 libQt5Multimedia5-5.5.1-1.1.x86_64 libphonon4-4.8.1-1.3.x86_64 libphonon4qt5-4.8.3-3.1.x86_64 libpulse-mainloop-glib0-7.1-1.1.x86_64 libpulse0-7.1-1.1.x86_64 phonon-backend-vlc-0.8.2-1.1.x86_64 plasma5-workspace-5.4.2-2.1.x86_64
[OK KDE4] # rpm -qa | sort | egrep 'alsa|arts|mix|kspace|imedia|pavucontrol|phono|pulse' alsa-1.1.0-1.1.x86_64 alsa-oss-1.0.28-3.3.x86_64 alsa-plugins-1.1.0-2.1.x86_64 alsa-utils-1.1.0-1.2.x86_64 kdebase4-workspace-4.11.22-4.1.x86_64 kmix-15.08.3-1.1.x86_64 libQt5Multimedia5-5.5.1-1.1.x86_64 libphonon4-4.8.1-1.3.x86_64 libphonon4qt5-4.8.3-3.1.x86_64 libpulse-mainloop-glib0-7.1-1.1.x86_64 libpulse0-7.1-1.1.x86_64 phonon-backend-vlc-0.8.2-16.4.x86_64 0.8.2-16.4 came from Packman in June. Everything else in KDE4 seems to have come from OSS. Even though the two installations run the same kernel and use the same content in /etc/moduprobe.d/, the snd modules loaded in the two different TW installations differ: --- 1 2015-12-24 05:51:02.095724644 -0500 (broken KF5) +++ 2 2015-12-24 05:51:09.245708595 -0500 (working KDE4) @@ -1,11 +1,13 @@ -snd 90112 16 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel +snd 90112 14 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_seq_device snd_hda_codec 147456 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel snd_hda_codec_generic 81920 1 snd_hda_codec_realtek snd_hda_codec_hdmi 53248 1 snd_hda_codec_realtek 86016 1 snd_hda_core 73728 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel -snd_hda_intel 40960 4 +snd_hda_intel 40960 2 snd_hwdep 16384 1 snd_hda_codec snd_pcm 135168 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core -snd_timer 36864 1 snd_pcm +snd_seq 77824 0 +snd_seq_device 16384 1 snd_seq +snd_timer 36864 2 snd_pcm,snd_seq soundcore 16384 1 snd How can it be determined why the differences? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org