elupus Wrote:now it only applies the AESX=XX options if your devicestring is iec958, (since that is probably the only one that can take those options)
on my ubuntu the iec958 pcm device is defined in /usr/share/alsa/pcm/iec958.conf
Thrashing around in Ubuntu 10.10 trying to get HDMI passthru. Looking up some of the error messages I'm getting while using custom hardware devices I found this old thread. Above it's stated that the AESX=XX options will only be applied when the device string is iec958 which I don't believe I'm using. The error I receive is as follows:
Code:
ALSA lib conf.c:4500:(parse_args) Unknown parameter AES0
ALSA lib conf.c:4633:(snd_config_expand) Parse arguments error: No such file or directory
ALSA lib pcm.c:2208:(snd_pcm_open_noupdate) Unknown PCM plughw:NVidia,3,AES0=0x6,AES1=0x82,AES2=0x0,AES3=0x2
Not sure but it looks like something may be having issues parsing? I am attempting to use "plughw:NVidia,3" as my custom device string FWIW. I get a red X message and a failure to initialize the audio device error.
Is it possible this bug has come back? It seems to tack on AES0= stuff onto the string I feed it for a custom device.
More info: speaker-test works using plughw:0,3 or hw=0,3 or plughw:NVidia,3 I am using the 6 channel switch with speaker-test like so:
Code:
speaker-test -D plughw:NVidia,3 -c 6
Channels do not appear to be mapped right but w/e - the hardware I'm choosing appears correct but parsed badly. This is pre-11.0 Git:844c6c7
XBMC log here ->
http://pastebin.com/NMhyjatj
Note these lines in the log:
Code:
15:19:02 T:140492188669696 M:1080512512 DEBUG: Initialize - using alsa device hw:0,3,AES0=0x6,AES1=0x82,AES2=0x0,AES3=0x2
15:19:02 T:140492188669696 M:1080385536 ERROR: Initialize - failed to open custom device hw:0,3,AES0=0x6,AES1=0x82,AES2=0x0,AES3=0x2 (error:No such file or directory), retry with default hw:0,3
15:19:02 T:140492188669696 M:1080385536 ERROR: Initialize - pcm_open_lconf, alsa error: -16 - Device or resource busy
I think it's clear XBMC is not sending the custom hardware string to ALSA. Old bug is back?
One last tidbit - Movie plays in Ubuntu including sound although the CPU chokes BAD