Hello, I will keep this as short as possible. I have been using Ubuntu since 8.x, I am not an expert with Linux but I have learned quite a bit over the years. I am a retired Broadcast Engineer mainly in hardware not software or coding. As of the release of 13.10 the ongoing audio issues have gotten worse. Especially with the use of HDMI audio, 5.1 and above surround sound. Earlier versions of this distribution had it's issues between ALSA and Pulseaudio, but nothing as bad as the loss of HDMI audio output and 5.1 surround sound. After working with two knowledgeable gentlemen I have regained the HDMI audio output but still do not have access to 5.1 surround sound, but only stereo. As I stated above, I will keep this short. All references to this issue will now point to the ongoing bug report at this URL. https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1249705 Thank you for your time, GEE
Please describe concisely here exactly what problem you have, instead of pasting a URL. List up your hardware showing the bug, and describe how to reproduce the bug, at best, independently from Ubuntu.
Hello and thank you for the quick response. Sorry if I did not post all the information here, I thought it may be a bit redundant to repost everything since there is another ongoing bug report. It was suggested that I start one here. To start, here is my system information. Description: Ubuntu 13.10 Release: 13.10 Kernel-release version 3.11.0-13-generic uname -a string Linux HTPC 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linuxx86_64 x86_64 GNU/Linux HTPC System Info: Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ × 2 Memory: 4GiB Graphics: GeForce 7050 PV / nForce 630a/integrated/SSE2 OS Type: Ubuntu 13.10 64-bit Disk: 320 GB DVB: AVerTVHD MCE A180 Remote: ATI USB RF wireless remote ( Remote Wonder) Keyboard/Mouse: Wireless System formerly a Captiveworks 3000/4000 ATSC and DVB-S Satellite HTPC, Distro used, Susse
Here is the link to the ALSA information http://www.alsa-project.org/db/?f=f9ee0512e733d5ef27b233589b333b8bc329edb8 With weeks of suggested testing and changing around scripts I removed the install of 13.10 and started fresh due to more issues then I started with. This fresh install took me back to the original issue of no HDMI output, it was non existent until I replaced the original HDA-Intel.conf with this script suggested to me on the other bug report. This URL is for the HDA-Intel.conf that I am now using. http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/alsa-lib/saucy-proposed/view/head:/src/conf/cards/HDA-Intel.conf I hope this information is useful to you so you can investigate this HDMI issue. If you need anything further please let me know. Also, please remember that I am a hardware person not a scripting/coding person, so you may have to be a bit more detailed for me if you need a specific testing result. Here are yesterday tests I have done after replacing the originaly installed HDA-Intel.conf This is a C/P of those tests --------------------------------------------------- I replaced the HDA-Intel.conf with the above(see #45 in above Bug URL posting). My results are the same. Audio-test -c 6 -t wav results in audio out via the HDMI, stereo only. Left-Right reversed and Left-Right Rear, Center and LFE barely audible and probably due to the rear, center and LFE being mixed down to stereo.. The audio test videos that I used can be obtained at http://www.dolby.com/us/en/consumer/technology/home-theater/dolby-digital-plus-download.html I have also been using some test DVDs I purchased while working in the production studios. The DVD set is called "Video Essentials NTSC" test dvds by JKP. Running a test using XBMC settings as follows: Top selection: Audio Output --> HDMI Speaker Configuation --> 5.1 Lower Section: Audio Output Device --> HDA NVidia, HDMI Passthrough Device --> HDA Nvidia, HDMI These settings result in only digital data in the audio output (Buzz or Hiss). Top section (as above) Lower Section: Audio Output Device --> HDA Nvidia, ALC888 Digital S/PDIF Passthrough Device --> HDA Nvidia,ALC888 Digital S/PDIF These settings result in decoded audio playback of 5.1 surround sound using these encoded test videos. Video: 1920x1080 H.264 @ 24 fps (all test videos) Test video #1: Audio Codec: E-AC-3 (ATSC A/52B) Channels: Surround 5.1 Sample Rate: 48000 Hz Bitrate 640 kbps Test video #2: Audio Codec: DolbyTrueHD Channels: Surround 7.1 Sample Rate: 48000 Bitrate N/A Using the surround sound test video "channelcheck-large.mp4" or "channelcheck-small.mp4". File with extention .m2ts produces digital noise output in VLC. VLC media player version "2.0.9 Twoflower" settings: HDA Nvidia, HDMI 0 Audio out selected produces only 5.1 downmixed to stereo. There is no option for surround sound with this selection. The 5.1 downmix to stereo is also not properly a mapped L-R it is reversed as R-L. All HDMI 0 selections available to play through HDMI is only Stereo, there are no 5.1 surround sound options under Audio Channels dropdown or Audio Device dropdown except analog. HDA Nvidia, ALC888 Digital IEC958 (S/PDIF) Digital Audio Output only produces Stereo only. Using the Audio Selection of: Playback/recording Through Pulseaudio Sound Server, produces audio out receiver selected input S/PDIF or HDMI with Pulseaudio selections (IEC958) or (HDMI) in Stereo only. Here is a summery of my findings with both ALSA and Pulseaudio, with the original HDA-Intel.conf replaced. This also includes my findings with the original script are as follows: 1. The original script was limited to selections for audio output which included no HDMI output. With the replacement of the original HDA-Intel.conf there is now HDMI with an additional output of "Playback/recording Through Pulseaudio sound server", something I have never noticed before. 2. All output selections only produce Stereo output. There is no selection for 5.1 surround either S/PDIF, IEC958 or HDMI. There is only Analog 5.1 and above available. Earlier releases of Ubuntu before 13.10 had options for 5.1 surround S/PDIF, IEC958 or HDMI in the Audio Output selection and Audio Channels of VLC. I have not tested with earlier versions of VLC. 3. When testing under the media package XBMC version Frodo 12.2, I have full Digital 5.1 surround sound via S/PDIF receiver selection. When selecting direct HDMI on the receiver, not HDMI-auto which will default to S/PDIF, some of the video's audio track did not play through HDMI or if an encoded 5.1 track were to play the audio there is only digital buzz or hiss. 4. Here is something to look at. Why is XBMC producing 5.1 surround sound via S/PDIF when VLC or other media players do not? Most all experienced users of XBMC state; turn off or completely remove Pulseaudio. I feel that it is not Pulseaudio and or ALSA that is thes issues since there is no 5.1surround in the standard media players and there is 5.1 surround in XBMC but only via S/PDIF.
MCP67 is an old chip and it's supposed to provide only 2ch PCM. You can send compressed streams like 5.1 Dolby, but the payload is still 2ch, i.e. different from 8ch LPCM on many other codecs. Also, 2ch payload doesn't support HBR, by obvious reason. Of course, you may test whether MCP67 can do more than expected. Replace patch_nvhdmi_2ch with patch_nvhdmi for the entry of "MCP67 HDMI" in snd_hda_preset_hdmi[] array in sound/pci/hda/patch_hdmi.c. This will set up the controller as well as recent Nvidia controllers. Or, you can even try patch_generic_hdmi instead. This works for Intel and others (not for AMD). Though, I don't think this would work. But still worth to try, if you are sure that the chip is capable of multi-channel LPCM and HBR. Speaking SPDIF: SPDIF is always only 2ch-stereo. It's so per definition. You can get 5.1 or such outputs only by the compressed stream sent over 2ch payload. But for sending such non-PCM data, you have to set up IEC958 status bits to indicate the data being non-PCM. Otherwise the receiver won't accept such streams. The same is true of HDMI in case you send a compressed stream. This is the likely reason why some player works while other doesn't. It's a matter of application, whether it sets up the proper data. The application should open the stream via spdif:xxx or data:xxx PCM name *and* with proper AES bits. The default AES parameters (= IEC958 status bits) are for raw PCM streams, not for non-PCM data streams.
http://cgit.freedesktop.org/pulseaudio/pulseaudio/log/?qt=grep&q=passthrough when one pulseaudio client use 5.1 passthrough over SPDIF/HDMI , pulseaudio need to prevent mixing of audio with other pulseaudio client if it allow multiple clients playing 5.1 AC3 and stereo at the same time, it need to decode 5.1 and perform mixing with other stereo audio and perform encode to 5.1
Thank you for your taking an intrest in this matter an for the explanation of how the audio stream should be working. What I can not understand that when I purchased this system some time ago there was 5.1 surround via the S/PDIF and HDMI up to 13.04 Ubuntu. This system ran under a custom version of Suse and what I understood it still used the ALSA but I am not sure if Pulseaudio was being used. Below is a history on this HTPC system. The reason why I abandoned Suse was due to the loss of support from the manufacture of this $450-US HTPC. This HTPC was capable of ATSC and Satellite DVB-S reception. The abandonment of this system was not due to the age of the hardware but due to lack of profit which was lost by the changes in the Satellite broadcasting industry. I had two Terrestrial tuners installed in my system and for my work I had a custom USB controlled commercial satellite receiver used for monitoring our satellite broadcast trucks. After the loss of support I had stored away the PC until I decided to remove the custom Suse distro and tried Windows 7 with WMC. That was a nightmare and was very short lived. Surprisingly though, it had 5.1 output at that time and that was only via S/PDIF and it worked fine. Until there were the usual many updates I finally had HDMI audio. The video was horrible so I tabled the project again. Now enter Ubuntu 8.x. Video and audio outperformed Microsoft's OS. HDMI was still a bit unreliable until the release of 12.04 LTS. Mind you, I was only using 32 bit versions of Ubuntu until I installed a 64 bit later version of 12.04. I eventually went to 13.04 64 bit and the HDMI then worked fine. I had access to 5.1 and not only via S/PDIF, but I had 5.1 surround with the proper mapping via HDMI. At that time I was using VLC and I had quite a few output selections of digital 5.1 surround sound and not just only 5.1 analog surround which is now limited to all but one media package XBMC. Now we come to the release of Ubuntu 13.10. I usually do not jump right into a new release of any OS, but what I read about the various improvements I thought would give it a try. That was a big mistake on my part. There were many improvements to this new release; I can see some of the differences, but again, something has happened to the audio. I still can't completely grasp why Linux has to use two audio packages to produce an audio output. Is this due to the various codecs and various media players? I just don't see why this is not being done under one package and the foucus can be then narrowed down to one package and not having to troubleshoot two packages to see which one is broken or conflicting with the other. This shows my lack of knowledge in the coding, but I still have my logical thoughts. At first with a fresh 13.10 install and with the help of Raymond and a bit of direction from David Henningsson, I finally have the HDMI output selections showing again. Until this help there was no selections or working output for HDMI either via ALSA or Pulseaudio. Presently I do not have access to what was once working. I somewhat agree this is old hardware. Again, without the media package XBMC I cannot produce 5.1 surround sound output , With the exception of XBMC, VLC and other media players which once had Digital 5.1 output now only have Digital Stereo output via either S/PDIF or HDMI and only 5.1 and above surround sound output via Analog. I have not rewired my system to test if the 5.1 analog output is working due to not being able to move the rack around to access the back of receiver. Is there a reason why the developers may have dropped support for MCP67 chip set in 13.10 or is there something broken in the code? I feel that it is the latter, something is broken. It would not be advantageous for the developers to stop supporting hardware that is roughly 5 years old; especially for audio, without some sort of advanced warning. I can see other pieces of hardware not being supported due to the manufacture's lack of support, but not a complete motherboard. Remember this is not Microsoft; a company that removes hardware support as fast as they keep sending out updates. Not to go off subject with this audio issue, but I would just like to mention that I have three other pieces of hardware that has stopped working since the releases of 13.04, 32 or 64bit. Two ATSC TV tuner cards lacking system firmware drivers and a USB RF remote control which is apparently not plug-in and run. Both Tuners use the dvb-fe-nxt2004.fw driver and I discovered in the early hours of this morning that the firmware drivers can not be found anywhere. Perl get command cannot find the firmware. Apparently even with the latest version of Ubuntu this older driver would have both of these cards running. This hardware is still being sold and maybe not the same hardware package, but they are still using the same chip sets and in some cases the same firmware. Now I have a crippled HTPC. I can do without this older hardware for now. As for the audio aspects of this system, there are many systems still using this chip set. There should be no reason that it is now broken or possibly not supported with this latest release.
Well, all I can say is that the problem is likely in the user-space side. PulseAudio can handle the compress audio passthru, but you need use it in some explicit manner. At best, consult Ubuntu guys instead of kernel bugzilla. So, please describe here concisely if you have any *kernel* bugs to fix. The rest would be better asked in Ubuntu-specific places, I guess.
I just tried something different here with my system. I turned off the Onkyo receiver which routed the HDMI directly to my TV from the PC. I tried all sorts of settings within ALSA and Pulseaudio to hear the sound on my TV. Nothing passes through from the media players except this in the terminal, " speaker-test -d -c 2 -t wav -Dhw:0,3 " With this I get the audio pass through of Left and Right audio to the TV's speakers but as usual mapped wrong as Right / Left. In addition, the speaker test within the Sound panel does not pass the audio either from HDMI. So this above test may point to the issue. I am now pretty sure it is not my hardware MCP67 audio chip-set that is too old. Why do I make this statement; I tried a completely new computer with HDMI output and still the same issues. Also, as I stated time and again my audio worked properly before the release of 13.10. My next test which my neighbor was gracious enough to let me experiment with his new laptop. The test subject was a new HP ENVY Laptop, Intel 2.4GHz i7 core, 8GB ram, 1TB drive, Intel HD graphics and HDMI out. We set the laptop up as a dual boot with Ubuntu 13.10 64Bit with all the latest updates. This is a major issue which I now know it is not an issue with my system but with Ubuntu 13.10; ALSA, Pulseaudio,the Kernel or all three.
http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=814c0371a493cf47df4e6e27253cfd5ec3cef783 pulseaudio only set nonaudio bit in the above patch , the other possible way is when pulseaudio using a52 plugin which set nonaudio bit
http://cgit.freedesktop.org/pulseaudio/pulseaudio/plain/src/modules/alsa/mixer/profile-sets/extra-hdmi.conf did pulseaudio allow you to select those mapping using a52 ?
Hi Raymond, See the launchpad report for answers to ytour last two posts.
Node 0x05 [Pin Complex] wcaps 0x400381: Stereo Digital Control: name="HDMI/DP,pcm=3 Phantom Jack", index=0, device=0 Pincap 0x00000014: OUT Detect Pin Default 0x185601f0: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0xf, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Connection: 1 0x04 if pincap does not support DETECT or MISC=NO_PRESNCE https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_hdmi.c?id=30efd8debd1ef30be342d374f01e993509f5b76b it should fall back to codec default if PD and ELD are not supported unless you can provide emulated ELD info https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_hdmi.c?id=bbbe33900d1f3c4402148ccb85234a741a6606a3 does chmap return correct channel map ? chmap -D iec958:0 query chmap -D hdmi:0 query chmap -D a52:0 query
some codecs have formats [0x5]: PCM AC3 but your codec Node 0x04 [Audio Output] wcaps 0x211: Stereo Digital Control: name="IEC958 Playback Con Mask", index=1, device=0 Control: name="IEC958 Playback Pro Mask", index=1, device=0 Control: name="IEC958 Playback Default", index=1, device=0 Control: name="IEC958 Playback Switch", index=1, device=0 Device: name="HDMI 0", type="HDMI", device=3 Converter: stream=0, channel=0 Digital: Enabled Digital category: 0x0 IEC Coding Type: 0x0 PCM: rates [0x40]: 48000 bits [0x2]: 16 formats [0x1]: PCM
No such command in 13.10, chmap. I also looked up channel map query. Please excuse my ignorance, but am I missing something here? channel map query in linux
http://git.alsa-project.org/?p=alsa-lib.git;a=blob_plain;f=test/chmap.c;hb=HEAD pulseaudio seem can differentiate dts or ac3 pactl list Ports: hdmi-output-0: HDMI / DisplayPort (priority: 5900, available) Active Port: hdmi-output-0 Formats: ac3-iec61937, format.rate = "[ 32000, 44100, 48000, 88200, 96000, 176400, 192000 ]" dts-iec61937, format.rate = "[ 32000, 44100, 48000, 88200, 96000, 176400, 192000 ]" pcm
" David Henningsson, 22 Oct 2013 22:13 " http://comments.gmane.org/gmane.comp.audio.pulseaudio.general/18678 If this is releated?
But then again, maybe not.
Can't seem to get the script in #15 running. Here is some other information from running "pactl list" http://pastebin.com/bXyQx2yL
Here is another piece of information using " bash alsa-info.sh --stdout " http://pastebin.com/Ps67Avpy These are my latest since I have been tweaking aroung with the audio aspects of this system again.
Another run.... http://www.alsa-project.org/db/?f=0fa3fc4747efc89389c552a7f7019b08699806a3
I guess you misunderstand the concept of "passthrough" mode. It's to pass through a compressed stream (e.g. AC3 or DTS) as is to the receiver by packing into a 2-channel stereo PCM stream. Thus, it won't appear in the hardware profile in the kernel driver. From the hardware POV, it's nothing but a normal 2-channel stereo PCM stream. This is why alsa-info nor codec show any piece information for AC3 or whatever. It doesn't matter. (HBR mode is a bit different story, but it's not possible on your device, in anyway.) And, note that the compressed stream setup is done in user-space. More exactly, the user app needs to pass certain AES status bits at opening the ALSA HDMI device via hdmi:CARD=XXX,AES0=XXXX,AES1=XXX,...., and needs to prepare the compressed stream packed in PCM. Here is the reason why speaker-test doesn't work for testing it. speaker-test is only for testing multi-channel (L)PCM streams. The newer graphics chip may support it, but yours doesn't.
Hi I do understand the concept. This system here for some odd reason did have the HDMI working before this release, but there may be a reason behind this too. Something that I may have neglected to mentiion. I don't know how they did it with this MB but they had it working under Suse. The BIOS had been modified to do something with the audio. Also 12.04 to 13.04 with a bit of tweaking did work here. Today I was messing around with this page and now I have audio through to the TV minus the receiver. https://help.ubuntu.com/community/SoundTroubleshootingProcedure All media players pass through the HDMI to the TV now. Still in stereo which I know that is what I am going to be stuck wth. But for a pass through for TV, I don't need Surround. I have no clue what had been changed but from the start I had no HDMI available not alone HDMI output. With a few things Raymond suggested I finally have HDMI out. Today's adventure now gaind HDMI audio passthrough to the TV. Now that is one thing I did not have after scraping Suse (custom for this system). Something I have not had answered yet and maybe because it is a sore a subject. Why two programs for audio when one should only be needed? And now for the possible sore point. With all the audio issues with ALSA and Pulseaudio over all these years, why was these projects not scrapped and a new single audio package been developed. Not trying to ruffle any feathers I am just showing my ignorance again when it comes to Linux in general. What this all boils down to and from the original start of my reports is that I had no issues here and the way things worked I expected them to work that way with Suse to the release of Ubuntu 13.10. So apparently there has been some tinkering with something in the Audio paths or in the Kernel. I will keep testing here until I get this back to exactly what I had before this release. I will keep things posted on my findings in the launchpad report. If I find that it is Kernel related from some other posts or tests I will report them here.
do alsa need to set AES3=2 for 48000Hz for AC3 passthrough since a52 plugin did this but pulseaudio only set AES0=6 (non audio bit) ? your mcp67 does not support more than 2 channels https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_nvhdmi.c?id=a3d6ab9723060e8d67e28a8d9142e6d08953d07b - { .id = 0x10de0067, .name = "MCP67 HDMI", .patch = patch_nvhdmi }, + { .id = 0x10de0002, .name = "MCP78 HDMI", .patch = patch_nvhdmi_8ch }, + { .id = 0x10de0006, .name = "MCP78 HDMI", .patch = patch_nvhdmi_8ch }, + { .id = 0x10de0007, .name = "MCP7A HDMI", .patch = patch_nvhdmi_8ch }, + { .id = 0x10de0067, .name = "MCP67 HDMI", .patch = patch_nvhdmi_2ch }, + { .id = 0x10de8001, .name = "MCP73 HDMI", .patch = patch_nvhdmi_2ch },
Please see the following sections 10.4 to 10.9, >10.12< ftp://download.nvidia.com/XFree86/gpu-hdmi-audio-document/gpu-hdmi-audio.html ------ ftp://download.nvidia.com/XFree86/gpu-hdmi-audio-document/gpu-hdmi-audio.html#_4_6_channel_support_on_some_older_chipsets I now understand about the passing of two channels only, and are we still missing the passthrough of AC3 and the somewhat under SD DTS not 720/1080P? Leading back to the begining; 13.10, lets call it out of the box or fresh install. There was no output what so ever from the HDMI. It took many of Raymond's suggestions and weeks of digging through forum after forum to even get HDMI to work. Yes it may be MCP67 related, but that was never an issue here before this release. That was the point of both bug reports, No HDMI audio. Sorry that I may have gone off the mark bringing up the 5.1 surround issue since I equaited it to the HDMI. So lets now stay on track with the HDMI "13.10 Out of box Fresh install" issue. HDMI in general did not work. And as of today there will be a possible addition of another person with the same issues as I have. I met this person at a Office supply store here in the states called Staples. He has had the same issue with 13.10 that I have been having with HDMI. All other releases up to 13.10 worked for him with HDMI audio output. As soon as he installed 13.10 HDMI was gone. Apparently he went back to an earlier version.
Sorry, I have no idea what got me off track with the 5.1 surround. I am not going to worry about surround sound, that is already covered here via S/PDIF. AC3 and DTS are fine. Now I would like back to the existing issue that this was first issued as a bug. aplay -D plughw:0,3 /usr/share/sounds/alsa/Noise.wav plays white noise to the TV via HDMI without any issues. No audio from FireFox v25 playing a YouTube video or via XBMC through the HDMI. Now that the HDMI has output with one test. If I am using this term right, what is not getting pined correctly or selected correctly? Apparently something is not stable between ALSA and or Pulseaudio since earlier I was watching a video stream with audio via the HDMI. YouTube and XBMC. Something is not consistant in 13.10 after a reboot or a relog. This is not a hardware or chip issue since I hve spoken to someone earlier with a completely different system and they arfe having the same issues. Remember, much earlier in my rants, I mentioned the laptop test with a new HP laptop. Same issues with HDMI out under 13.10. So now that is three seperate systems. I have also been in an IRC and I was told to dump 13.10 since it is buggy and go back to XBMCUbuntu 12.2. There are issues all over the net when searching for 13.10 HDMI output issues. There is no more detail I can give you here except if you ask me to run a test, and remember if you want me to patch something, you may have to walk me through it or write something that I can just drop in to the terminal or make a executeable . Again, I am a hardware person not software.
pulseaudio treat the headphone is not available when your headphone is not plugged control.39 { iface CARD name 'Line Out Front Jack' value false comment { access read type BOOLEAN count 1 } } pulseaudio did not check whether line out front is not plugged and treat it as not available analog output has higher priority than hdmi or spdif analog-output: Analog Output (priority: 9900, latency offset: 0 usec) Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo, output:analog-surround-40, output:analog-surround-40+input:analog-stereo, output:analog-surround-41, output:analog-surround-41+input:analog-stereo, output:analog-surround-50, output:analog-surround-50+input:analog-stereo, output:analog-surround-51, output:analog-surround-51+input:analog-stereo, output:analog-surround-71, output:analog-surround-71+input:analog-stereo analog-output-headphones: Headphones (priority: 9000, latency offset: 0 usec, not available) Properties: device.icon_name = "audio-headphones" Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo iec958-stereo-output: Digital Output (S/PDIF) (priority: 0, latency offset: 0 usec) Part of profile(s): output:iec958-stereo, output:iec958-stereo+input:analog-stereo hdmi-output-0: HDMI / DisplayPort (priority: 5900, latency offset: 0 usec) Properties: device.icon_name = "video-display" Part of profile(s): output:hdmi-stereo, output:hdmi-stereo+input:analog-stereo
Well, I would say that that is an issue since I am not using a headphone.
All of you have been a great help, but you may forget one thing, I may be able to understand some of this jargon posted being that I am a former Broadcast Engineer, but as to the end user, this is all meaningless if they are trying to follow. You all seem to be very intelligent when it comes to an issue like this but the average user wants “Plug `n Play”. If my situation can ever be solved with this two package audio system, there needs to be clarity on a fix. Apparently in my case it is not fixed yet and maybe this issue will not even be solved. Just chalk it up to the countless growing complaints and frustration that the end users are having with the audio. I understand the main issues for Linux developers is the hardware manufacture. Apparently they do not consider Linux a viable operating system thus the lack of support. Now with that said, think of yourself as the end user when it comes to developing code for a specific device that needs drivers or input from the manufacture, now that is what the actual end user is feeling. I spent well over a month with this issue. I understand that as the saying goes, "Rome was not built in a day". Well, Ancient Rome is long gone and so should be these two audio packages. Users should not have to keep patching, updating and tweaking every time they use a different type of media and or media player. This is just getting old. As for these two audio packages. Think of it as a car, what would that look like if you had to replace a bad tire with a skateboard so you can travel down the road. Or when a headlamp goes, you tape or tie on a bunch of torches (flashlights) across the grill so you can see ahead of you at night. Well now apply that poor analogy to that of ALSA and Pulseaudio, From what I see as a somewhat educated Linux user, these packages are a total nightmare of a kludge just to make audio. Please look into abandoning these two old and at one time usable audio projects and look to the future of a “single” audio package. Maybe add a user friendly GUI with a drag and drop patch bay if needed. Something on the order of the jack/patching packages already in use. Place that all into one “single “ package not as a add this and add that system like has been around for ages of these audio packages for the various Linux distributions. Eventually, I will fade into the sunset as most end users do that have to deal with these ALSA and Pulseaudio long running issues, thus leading them to revert to an older version or abandoning Linux all together. This frustration is usually due to all the patches, tweaks, work-arounds and not to forget saying ones hardware is old, the chip set does not support this or that and as in my case, being told that it can't work when one knows it once worked and did not stop working due to an aging chip set. As you can see, I may ramble, but I am a very detailed person when it comes to this type of situation and I am and have been on your end of a situation like this. I feel that my notes and comments may help others that encounter something like this and I am not doing all this just for myself. In addition, just a yes, no and a cut and paste does not always answer a question. I did have a thought during the last couple of days, maybe if you can find the time and if this will work within Linux, lets try a remote access to this system. This way you can have access to this now kludged audio system and see what the issue is. As for you hearing any audio changes, I can be your ears and report back what is and is not working. I do not mind having my system being the Frankenstein of experiments as long as we all can learn what the cause and effect is and the end user can then profit from the fix. So maybe we can get this issue taken care of so we can both move on to something else. Again, Thank You for your patience with all my ramblings and going off the main subject which was No HDMI with Ubuntu 13.10output and dragging the 5. surround issue in which just confused things. GEE
All of you have been a great help, but you may forget one thing, I may be able to understand some of this jargon posted being that I am a former Broadcast Engineer, but as to the end user, this is all meaningless if they are trying to follow. You all seem to be very intelligent when it comes to an issue like this but the average user wants “Plug `n Play”. If my situation can ever be solved with this two package audio system, there needs to be clarity on a fix. Apparently in my case it is not fixed yet and maybe this issue will not even be solved. Just chalk it up to the countless growing complaints and frustration that the end users are having with the audio. I understand the main issues for Linux developers is the hardware manufacture. Apparently they do not consider Linux a viable operating system thus the lack of support. Now with that said, think of yourself as the end user when it comes to developing code for a specific device that needs drivers or input from the manufacture, now that is what the actual end user is feeling. I spent well over a month with this issue. I understand that as the saying goes, "Rome was not built in a day". Well, Ancient Rome is long gone and so should be these two audio packages. Users should not have to keep patching, updating and tweaking every time they use a different type of media and or media player. This is just getting old. As for these two audio packages. Think of it as a car, what would that look like if you had to replace a bad tire with a skateboard so you can travel down the road. Or when a headlamp goes, you tape or tie on a bunch of torches (flashlights) across the grill so you can see ahead of you at night. Well now apply that poor analogy to that of ALSA and Pulseaudio, From what I see as a somewhat educated Linux user, these packages are a total nightmare of a kludge just to make audio. Please look into abandoning these two old and at one time usable audio projects and look to the future of a “single” audio package. Maybe add a user friendly GUI with a drag and drop patch bay if needed. Something on the order of the jack/patching packages already in use. Place that all into one “single “ package not as a add this and add that system like has been around for ages of these audio packages for the various Linux distributions. Eventually, I will fade into the sunset as most end users do that have to deal with these ALSA and Pulseaudio long running issues, thus leading them to revert to an older version or abandoning Linux all together. This frustration is usually due to all the patches, tweaks, work-arounds and not to forget saying ones hardware is old, the chip set does not support this or that and as in my case, being told that it can't work when one knows it once worked and did not stop working due to an aging chip set. As you can see, I may ramble, but I am a very detailed person when it comes to this type of situation and I am and have been on your end of a situation like this. I feel that my notes and comments may help others that encounter something like this and I am not doing all this just for myself. In addition, just a yes, no and a cut and paste does not always answer a question. I did have a thought during the last couple of days, maybe if you can find the time and if this will work within Linux, lets try a remote access to this system. This way you can have access to this now kludged audio system and see what the issue is. As for you hearing any audio changes, I can be your ears and report back what is and is not working. I do not mind having my system being the Frankenstein of experiments as long as we all can learn what the cause and effect is and the end user can then profit from the fix. So maybe we can get this issue taken care of so we can both move on to something else. Again, Thank You for your patience with all my ramblings and going off the main subject which was No HDMI with Ubuntu 13.10 output and dragging the 5.1 surround issue in which just confused things. GEE
Sorry about the double post. The browser crashed and apparently when I restarted it it double posted. Apparently bugzilla has no access to edit to delete a doubl post
do this proposed patch fix your problem ? http://mailman.alsa-project.org/pipermail/alsa-devel/2013-December/070023.html
Hello Raymond, What I read makes sense in reference to my issue. Not sure on how to apply that patch though, remember I am mostly a hardware person. Thanks
Hello again, I have been inthe hospital since the 20th and now jack on line. Apparently everyone is on holiday or this issue is not going to be officially resolved. I appreciate the information that was posted in Comment 31, but I am still at a loss on how to apply this patch. If I am having this issue and can grasp most what has been given me to try, how is the usual end user going to understand this? I greatly appreciate the help, but as stated in Comment 32 I do not know how to apply the patch in Comment 31. Thanks G
There is still the issue here with no HDMI output with 13.10 after a new install. I am now having the issue on a different MB with onboard audio. This would make three different systems now with this issue and one being a high end laptop with HDMI. Please do not tell me that my system could not have worked with the chipset that is in my system as mentioned many times above. The HDMI output worked with no issues before 13.10 release. I had more HDMI options to select from in the Sound and Pulseaudio config settings for stereo and surround sound. Now it is very limited to what can be used. S/PDIF is even limited in reference to the surround sound options. Mainly, there is only various Analog options referencing surround sound. Please take my word for this. I would not have spent all this time between two bug reports if I did not see an issue here from a once fully functioning system. This would have been a total waste of my time and anyone involved with these reports. With the release of 13.10 the audio issues have gotten worse since some developers decided to remove support for older chipsets which now has crippled quite a few of the once working older HTPCs. Why remove support for older systems forcing the end user to have to replace a once working system? If it is due to removing drivers to cut down the size/bloat of the newer releases then at least give a simple option to add the older drivers and code back in for the older systems. My many installs of 13.10 have been tweaked, edited and re-edited lines of code, added and removed config files, install and reinstall of 13.10 multiple times due to all the changes being tried that eventually caused the audio to completely fail and lastly, information about patches without explanation on how to apply these patches. It has been over three months since the release of 13.10 and yet no resolution to this issue. The release of 13.10 has been a disaster in reference to the audio portion of its release. Still no one can understand here that the regular user of these distros using this archaic method of audio control is not going to understand any of what has transpired over these past three months. The end user needs something as simple as other operating systems such as Mac and forgive me, Windows to set up their audio. The end user should not have to spend hours trying to configure the audio which then leads to total frustration. This type of situation such as I have endured would force any regular user to just go back to a different OS and then end up complaining how complicated Ubuntu or other distros are. Maybe a developer or advanced user of these distros containing Alsa and Pulseaudio can understand these issues but the end user, the plug`n play end user is just getting left with these various audio issues leading to a once working and expensive HTPC. How much longer is this going to go on before someone decides to place a few people on this issue and redevelop the audio portion as one single package for Ubuntu and Linux in general? Please stop waisting time with tweaks and patches and look into a single, more user friendly and productive audio package. Maybe develop a one package replacement that can be easly be installed into Ubuntu 13.10 and the latest distros using 13.10
there are case which digital stop working too https://bugzilla.kernel.org/show_bug.cgi?id=68611 could it be pulseaudio misuse a52 plugin since a52 plugin require fix rate and hardcoded slave pcm ? it expect a52:x to acccess iec958 of card x
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1242390 there are bug in a52 plugin https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247160 Dell Studio Hybrid 140g use both primary and second digital outputs but one is HDMI and the other SPDIF SPDIF is no longer working on ubuntu 13.10 but still work with 13.04 Live CD should the driver create device 1 and device 3 ? Node 0x11 [Pin Complex] wcaps 0x400780: Mono Digital Control: name="HDMI Phantom Jack", index=0, device=0 Pincap 0x00000014: OUT Detect Pin Default 0x18561130: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Black DefAssociation = 0x3, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 1 0x10 Node 0x1e [Pin Complex] wcaps 0x400780: Mono Digital Control: name="SPDIF Phantom Jack", index=0, device=0 Pincap 0x00000014: OUT Detect Pin Default 0x01451120: [Jack] SPDIF Out at Ext Rear Conn = Optical, Color = Black DefAssociation = 0x2, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 1 0x06
I have this problem on my high-end Sony laptop. Was working fine in earlier releases of 13.04, but broke somewhere in the last updates to 13.04 and 13.10. Not kernel events appear when pulling HDMI cable in/out. And xrandr says HDMI is "disconnected". Please fix ASAP!
I have been ill for some time here, this is why there has been no follow up from me. Yes Darren there is an issue that apparently won't get placed in the Things To Do to get fixed. I am thinking after all these months, fixing the audio is not a priority for any of the devs. While I was in the hospital a friend reinstalled an older version of 12.04 Quantal for me and it has worked great until I Foolishly (underline Foolishly) upgraded my system via the proper steps to Trusty 14.04 this past weekend (2014-05-17) Now my system is down again in reference to the HDMI and S/PDIF. No 5.1 Surround sound (DTS). It is all gone again. I do not want to hear that my chipset in this computer is old and can't possible work with 5.1 surround. It worked, Believe me it worked all these months even under the original Suse linux package it came with. I had all forms of Surround, minus THX and EAC3. I may not be a developer but I am not stupid when it comes to following directions for upgrading my system. I am Foolish for trusting that the development team had fixed this issue after all these months, especially for 14.04 Trusty. So the way things look now I have to lose all my nice settings for my HTPC (Ascetics), and installed features to go back to 12.04 Quantal. This is the most ridiculous thing any person has to do to enjoy their entertainment because there is No Interest in fixing the audio.
P.S. While I was ill, I was given a new laptop so I had a way of keeping in touch with friends and family. In addition, I do volunteer support for Second Life, Linden Labs of San Diego CA. Even in my hospital bed I took care of support issues. I don't like leaving users hanging with issues. This laptop has HDMI in it and I am sure as heck not going to tie up a Windows based laptop with XBMC for surround sound. I have XBMC here on this Linux system and the audio issues just Needs to be Fixed once and for all.
(In reply to darren from comment #37) > I have this problem on my high-end Sony laptop. Was working fine in earlier > releases of 13.04, but broke somewhere in the last updates to 13.04 and > 13.10. > > Not kernel events appear when pulling HDMI cable in/out. > And xrandr says HDMI is "disconnected". > > Please fix ASAP! If xrandr doesn't show any HDMI connection, the primary problem is rather the video driver. For HDMI, audio driver is merely a subdevice although there's a dedicated PCI device. In anyway, check whether the xrandr problem persists with the latest upstream kernel (3.14.x). If it still happens, better to open another bug report and assign to the video component (and don't forget to attach the detailed hardware info). Your problem is definitely different. The only same factor is that it's a regression on Ubuntu.