[pulseaudio-tickets] [Bug 39664] New: Kinect USB Audio device and module-alsa-card.c: Failed to find a working profile.
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Jul 29 04:14:42 PDT 2011
https://bugs.freedesktop.org/show_bug.cgi?id=39664
Summary: Kinect USB Audio device and module-alsa-card.c: Failed
to find a working profile.
Product: PulseAudio
Version: unspecified
Platform: All
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: alsa
AssignedTo: pulseaudio-bugs at lists.freedesktop.org
ReportedBy: ospite at studenti.unina.it
QAContact: pulseaudio-bugs at lists.freedesktop.org
CC: lennart at poettering.net
Created an attachment (id=49710)
--> (https://bugs.freedesktop.org/attachment.cgi?id=49710)
Kinect, module-alsa-card.c: Failed to find a working profile.
Hi,
the Microsoft Kinect sensor device comes with array of four microphones on it
and it shows up as a USB Audio Class device after uploading a firmware to it,
but the Linux audio stack still needs some touches before the device works out
of the box.
This report starts from pulseaudio to track what the missing pieces are, I
suspect snd-usb-audio is involved too.
This is a timeline of what happens:
1. the sensor device is connected;
2. a udev rule detects the audio part of the device (idVendor=045e,
idProduct=02ad, Product: Xbox NUI Audio) and uploads the firmware to it;
3. the device is re-enumerated and shows up as a proper USB Audio Class
device (idVendor=045e, idProduct=02bb, Product: Kinect USB Audio).
At this point pulseaudio fails to detect it (full log in the attachments):
pulseaudio[1643]: module-alsa-card.c: Failed to find a working profile.
pulseaudio[1643]: module.c: Failed to load module "module-alsa-card"
(argument: "device_id="1"
name="usb-Microsoft_Kinect_USB_Audio_A44884D23275040A-01-Audio"
card_name="alsa_card.usb-Microsoft_Kinect_USB_Audio_A44884D23275040A-01-Audio"
tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1""):
initialization failed.
I noticed that alsamixer tells "This sound device does not have any controls.",
I don't know if this is the cause of the message above.
However if I kill and restart pulseaudio the device gets detected and can be
used mostly OK, even if the names of the Microphones are not right yet (see the
attached screenshot), I imagined this happened because udev is not involved
when restarting the audio server with the device connected already, but I am
not sure of this.
About alsamixer not showing any controls, by looking at the USB descriptor
(attached as well) I thought it was because snd-usb-audio does not support the
microphones arrays yet (wTerminalType 0x0205 Microphone Array), a quick
"grep -r 205 sound/usb" seems to confirm this but again I am not 100% sure.
I am looking into this but I wanted to ask for advice here too, and keep
history of the pulseaudio point of view of the issue anyways.
Thanks,
Antonio Ospite
http://ao2.it
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the pulseaudio-bugs
mailing list