Le 2 août 2013 à 18:28, Anssi Hannula a écrit :
02.08.2013 19:14, Ashecrow kirjoitti:
Le 2 août 2013 à 15:42, Anssi Hannula a écrit :
02.08.2013 16:11, Ashecrow kirjoitti:
Hi Anssi, Thanks for your answer
Test on kernel 3.8 + non-pcm bit in AES0: aplay -D hdmi:CARD=PCH,DEV=0,AES0=0x06 -c8 -fs16_le -r192000 dts.spdif => same result: no signal
Hmh, OK.
With kernel upgrade to 3.9: same result
Note that I have tested with alsa* 1.025 and intel-hda driver included in kernel
Do you have any other idea?
You could try DEV=1 instead of DEV=0 (according to your log DEV=0 is correct, though), and truehd (thd.spdif from ffmpeg samples).
If neither of those work, could you provide another alsa-info while playing back using AES0=0x06 (with alsa debug enabled again)?
I have already tried DEV=1 but it does the same. Moreover, let me note that I play DTS and dolby fine with DEV=0 in xbmc. So I guess it is the right device.
OK. Note that in some cases you can hear stereo audio or AC-3/DTS even when using wrong DEV=x (but HBR or multichannel audio would not work).
ok but it works for neither hdmi:...DEV=0 nor hdmi:... DEV=1
see attached alsa-info.txt_dev0_kernel-3.8_aes0_dts-hd which is result of playing dts-hd spdif encapsulated with kernel 3.8 in debug mode and AES0=0x06 through command bellow
aplay -D hdmi:CARD=PCH,DEV=0,AES0=0x06 -c8 -fs16_le -r192000 dts.spdif
see attached alsa-info.txt_dev0_kernel-3.8_aes0_true-hd which is result of playing dts-hd spdif encapsulated with kernel 3.8 in debug mode and AES0=0x06 through command bellow
aplay -D hdmi:CARD=PCH,DEV=0,AES0=0x06 -c8 -fs16_le -r192000 thd.spdif
Looks like your kernel is definitely too old to have working HBR on Intel (the "ASP channel x => slot y" messages should have x=y), so you'll need 3.9+.
Ok but I did the test with kernel 3.9.3 and it doesn't work
Unfortunately I don't see anything else wrong (and HBR+intel works for me), so I don't have anything else to suggest at the moment. Sorry.
Ok I know it works for many people who have intel hardware but not for my hardware. I've been struggling with this for 6 months and still no clue. How can I start a debug process?
Thanks for your help
Thanks
Le 1 août 2013 à 18:37, Anssi Hannula a écrit :
01.08.2013 19:29, ashecrow42@free.fr kirjoitti:
Hi there,
Hi!
I have troubles using HBR audio (DTS-HD and Dolby TrueHD). With every test, I get no signal in the AV receiver. I have tested using a dts-hd encapsulated in spdif sample file (found there http://samples.mplayerhq.hu/hdmi/) and commands bellow
- aplay -D hdmi devices
- aplay -D hw devices
- aplay -D plughw devices
You need to set the non-pcm bit in AES0. Use e.g. "-D hdmi:AES0=0x06".
Note that I use ubuntu raring with 3.8 kernel that includes Xingchao's HBR kernel patches.
A. Configurations I have tested:
hda driver upgrade (alsa devel ubuntu team daily builds)
upgrade alsa-lib & alsa-utils (alsa-testing launchpad)
kernel upgrade to 3.9
IIRC 3.9 (or newer) may indeed be needed since you have both hdmi and spdif.
- snd_hda_codec_realtek module backlist (to try to disable SPDIF)
/etc/modprobe.d/blacklist.conf
snd_hda_codec_realtek index = -2 in /etc/modprobe.d/alsa-base.conf
fresh new ubuntu raring install with no modifications at all: still
no signal
B. Info:
cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC892 Codec: Intel CougarPoint HDMI
I use zotac ZBOX ID82 (intel HM65 chipset with hdmi and spdif)
with alsa debug and alsa debug verbose enabled in kernel I got the alsa-info.txt attached file produced on raring with no modification while playing dts-hd sample file with command:
aplay -D hdmi:CARD=PCH,DEV=0 -c8 -fs16_le -r192000 dts.spdif
As per above you need to use aplay -D hdmi:CARD=PCH,DEV=0,AES0=0x06 -c8 -fs16_le -r192000 dts.spdif
C. I add that:
- In every test I have non HD audio protocols (DTS and dolby) working
well in the same configuration
- I have tried with windows just to see if my hardware is broken and I
get DTS-HD audio with no problem
- Takashi, I've read your HD-Audio.txt file and as far as I see, I have
no known error message in kernel log
=> I and Wingchao Wang have conclued that it is driver or codec related. Can you help me please?
Thanks a lot PS: sorry if you receive this email twice, I have sent it again as I was not member of the list the first time.
-- Anssi Hannula
-- Anssi Hannula
-- Anssi Hannula