Linux AudioEngine testers - Linux only - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Development (https://forum.kodi.tv/forumdisplay.php?fid=32) +--- Forum: Kodi Application (https://forum.kodi.tv/forumdisplay.php?fid=93) +--- Thread: Linux AudioEngine testers - Linux only (/showthread.php?tid=128298) |
RE: AudioEngine testers - Linux only - zombor - 2012-12-19 So I compiled the latest git version of XBMC, and now I can't do any passthrough audio. Under "Passthrough output device" my HDMI isn't even an option. It shows up under "Audio output device" though. I'm running on a Core i3 with built in HDMI on the motherboard on Linux 3.2.1. RE: AudioEngine testers - Linux only - zombor - 2012-12-19 (2012-12-19, 03:50)zombor Wrote: So I compiled the latest git version of XBMC, and now I can't do any passthrough audio. Under "Passthrough output device" my HDMI isn't even an option. It shows up under "Audio output device" though. So I upgraded my kernel version to 3.6 (was running 3.2) and now basic passthrough works. I still don't get TrueHD or the dolby HD audio via passthrough. My receiver supports it (Onkyo TX-SR607) but I just get silence unless I turn off TrueHD in the system settings. Here's some logs if it will help: Quote:21:24:33 T:2703215424 INFO: CAEStreamInfo::SyncDTS - dtsHD stream detected (8 channels, 48000Hz, 16bit BE, period: 8192) [28/1986] RE: AudioEngine testers - Linux only - tudstudent - 2012-12-19 What are your settings -> screenshot Furthermore, did you read recent posts concerning no ruehd en truedts? Try kernel 3.7 RE: AudioEngine testers - Linux only - zombor - 2012-12-20 (2012-12-19, 20:27)tudstudent Wrote: What are your settings -> screenshot I just upgraded to 3.7, no differences. Here's some pictures of my settings (Output stereo to all speakers is actually off): Both TrueHD and DTS-HD fail to bitstream. RE: AudioEngine testers - Linux only - furii - 2012-12-20 did you apply the intel patches? http://forum.xbmc.org/showthread.php?tid=128298&pid=1184055#pid1184055 RE: AudioEngine testers - Linux only - zombor - 2012-12-20 I checked those patches, and they are already in the mainline 3.7 release it seems. RE: AudioEngine testers - Linux only - tudstudent - 2012-12-20 Turn LPCM off. True HD DTS on DTS AC3 on aac off hdmi out And be sure you have an XORG.conf before you boot RE: AudioEngine testers - Linux only - vicbitter - 2012-12-20 (2012-12-20, 17:43)zombor Wrote: I checked those patches, and they are already in the mainline 3.7 release it seems. Have you applied the alsa-lib patch? See post #612 for further details... RE: AudioEngine testers - Linux only - tudstudent - 2012-12-21 What I am wondering lately and have no idea how to figure out is why my sound sometimes after restart from suspend is just gone. No link to the receiver, however there is a image signal to my television (just no sound anymore). Back to sleep and wake-up again is no help, also restart of the receiver same problem... Can I change this is someway or understand where this problem comes from? RE: AudioEngine testers - Linux only - bradman334 - 2012-12-22 I am not sure if this is the correct place for me to be posting this, I apologise if it is not. I recently updated my XBMC to Frodo, 12.0-RC1 Git:49b2d1f to be precise. I am trying to use HDMI from my HTPC (running Linux Mint 13) to my TV for audio. When I start XBMC manually the audio option "HDA ATI, HDMI" exists and with it audio works perfectly. When XBMC auto starts there is no HDMI option. This includes initial boot of the HTPC as well as exiting XBMC, logging out of the Mint session and allowing XBMC to auto start from there (it automatically logs in as the XBMC user and runs XBMC). What would be different between a manual and auto start of XBMC such that the auto start does not have the HDMI option? Could it be a timing issue? I can turn on debugging and post logs if that is helpful. RE: AudioEngine testers - Linux only - bradman334 - 2012-12-22 I just updated to RC2 and even though I still don't have the "HDA ATI, HDMI" audio device when auto starting (it default to Playback through PulseAudio) my audio is working! It seems a little strange to me but its working so I am not complaining. RE: AudioEngine testers - Linux only - wileyc - 2012-12-24 (long time xbmc user, first time poster) Pardon me if this has been asked/answered before ... but it doesn't appear possible to specify a custom audio output device anymore. Am I missing something obvious? RE: AudioEngine testers - Linux only - un1versal - 2012-12-24 Welcome to forums. No, you cant and there is absolutely no need to specify custom audio device uNi RE: AudioEngine testers - Linux only - vijayrv - 2012-12-24 Been breaking my head on issues around audio over HDMI. uNiversal had helped me to the maximum in this thread: http://forum.xbmc.org/showthread.php?tid=149424. However, the issue has not been resolved. It has been identified as a ALSA related problem. Would be a great help if someone could help looking into it. Thanks in advance Apologies for cross linking another thread here. I have plain run out of ideas :-) RE: AudioEngine testers - Linux only - wileyc - 2012-12-25 (2012-12-24, 20:25)uNiversal Wrote: Welcome to forums. With all due respect, there is at least one use case for custom audio devices: using ALSA plugins. Consider this case: I've got a tiny AMD E350-based HTPC. It doesn't have a physical IEC958 port. I want to output stereo sound on all speakers on my 5.1 surround sound system; this unit doesn't have HDMI inputs (which wouldn't help anyway, because fglrx apparently doesn't support this functionality) nor discrete six-channel analog input. The solution here was to use a USB-to-SPDIF converter, which presents two devices to the kernel: one IEC958 (taking care of a52 passthrough) and one PCM. That PCM device, unfortunately, is only two channels. The solution here would be to use the a52 ALSA plugin to upmix stereo output to a52, pass it through the dongle's IEC958 interface, and all is good. This worked on previous xbmc releases. If, as you say, there is absolutely no reason to support custom audio devices, then what is the recommended method for addressing this particular need? |