2010-04-01, 14:17
Makes no difference. Should I report as an alsa bug? :confused2:
snoopy20 Wrote:Makes no difference. Should I report as an alsa bug? :confused2:
paoleary Wrote:Hope it helps. Didn't mean to imply anything, btw.
Now, onward to the report:
Noticing that how well the audio works depends on what video I play. Recorded TV shows work fine, but an episode of Cooking With Dog (mirobridge'd into MythTV), of all things, has tons of audio dropouts and corresponding video slowdown. DVDs also are problematic.
I probably won't be able to get heavily into working through this until this coming weekend, but anyone else is welcome to pick up the torch.
UPDATE: Okay, after some diffing and going back through the git history, it appears that HD_AUDIO-9.10.tar.gz is indeed written against an older release of ALSA. I'm not surprised, but there was no way to be sure if Wei Ni had completely rewritten it and just not posted it upstream yet. Notably, my patch wipes out this commit. I think we're going to need to figure out how to forward port this. My naive first attempt just updated the PCI IDs, but that didn't really work. Gonna try something like that again, and make sure I do it correctly. Will keep you posted.
UPDATE 2: Didn't work (device appears and is unmuted but no sound), which is what I expected. What appears to have happened is nVidia's development (in HD_AUDIO-9.10.tar.gz) diverged from ALSA mainline. Now it's a matter of figuring out how.
UPDATE 3: Found a bug that's probably holding up the GT240 people. New patch; I've already fixed the wiki.
rodercot Wrote:Hey All,
I tried again this morning with My GT240 and adding the msi option in sound.conf with the last nvhdmi patch only. and still no go for audio. It works and the video portion seems fine again just no passthrough to the rcvr.
How do I check the actual id's of the card. if i run lspci the output is
audio device 0be4 I believe and is not listed as GT240 as some report with their GT220's but I do see GT240 HDMI in Alsamixer.
What manufactured cards are people using, I am trying Asus GT240 1Gb GDDR5, I notice that some of the cards still have the spdif input on them including the Gt-220 and I thought that all the 220's on had on-board audio codec it is somewhat confusing to say the least. I was gonna pick up the Asus GT-220 1Gb and try it out as well I would love to see a passive cooled model. I gotta get this to work the smoothness is amazing. panning shots are perfectly smooth as well even with animated stuff like Family Guy etc..
It would be great if we could actually come up with a smooth how-to for this.
**Note that link that kjetil posted to the ALSA upgrade page gave me a resident shield trojan error when I opened it with a downloader problem. I virus vaulted and and ran another avg scan to dump it, I have not seen any issues since I got the message***
Regards.
Dave
snoopy20 Wrote:Same problem with mine (Palet GTX240) which doesn't seem to be passing spdif over. I've reported as an ALSA bug (see latest bugs it's still at top) and I'll try nvnews.net for some help and report back.
pyite Wrote:i dropped an asus g210 in this afternoon, and got audio pretty much out of the box... but my rear speakers are being mapped as side speakers instead of the rear speakers that they actually are... so 5.1 isn't quite working correctly.
anyone know how to remap to rear?
paoleary Wrote:Wait, I'm reading this again--there's no SPDIF passthrough, or at least there shouldn't be. Some passively-cooled boards left an open header for fan power which uses an identical connector to the SPDIF passthrough, but does not serve the same purpose.
josefwells Wrote:I've got an ASUS GT240 512MB DDR5, installed XBMCFreak Generic 4 yesterday, ran the ALSA update script with snapshot and xbmc no longer complains about the hdmi device.
In my: /etc/modprobe.d/alsa-base.conf
options snd-hda-intel enable_msi=0
(perhaps I should add the probe_mask=0xfff2)
However, it didn't produce sound...
aplay -l shows the devices, alsamixer shows the spdifs are unmuted.
speaker-test -Dhdmi gives nothing.
speaker-test -Dhwplug:0,3 give nothing
Then...
speaker-test -Dhwplug:0,7
works, then, everything else works.
speaker-test -Dhdmi works, speaker-test -Dhwplug:0,3 works...
xbmc works.
I suppose I could just tell xbmc to use hwplug:0,3 directly. Or setup asound.conf to use that as default, but early attempts seemed to result in a syntax error
pcm.!default plughw:0,7
pcm:iec958 plughw:0,7
Any ideas?