[pulseaudio-tickets] [Bug 39664] Kinect USB Audio device and module-alsa-card.c: Failed to find a working profile.

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=39664

--- Comment #4 from Antonio Ospite <ospite at studenti.unina.it> 2011-08-04 04:49:07 PDT ---
(In reply to comment #3)

> Hi Antonio,
> 
> Thanks for the bug report.
> 
> Would it be possible to get us a better log from PA. The details in the syslog
> are pretty sparse, so if you could disable autospawning via: "echo autospawn=no
> >>~/.pulse/client.conf" and then run PA manually on the command line via
> "pulseaudio -vvvvv" then it should give you a lot more info which could help.
> 

OK, full log attached in 'pulseaudio_verbose_kinect_NOT_detected.txt' 
you can skip to when I plug in the device by going to line 1018 "ABOUT 
TO PLUG IN THE Kinect", and the tentative detection is until line 4223 
"NOT DETECTED" 

I noticed that if the device is _already_ plugged in when pulseaudio 
starts, then it gets recognized automatically, it looks like this 
happens because the Kinect is detected _before_ the other soundcard in 
the system, this seems to be confirmed by the "pacmd ls" output from 
below. I am attaching also the log for this case, see 
'pulseaudio_verbose_kinect_detected_first.txt'.
I tried to compare the failure with the success to narrow down the cause 
but I can't figure it out yet.

> I suspect that the trick here will be to write a specific profile for this
> device (it's quite specialised after all) which will then be able to give the
> right names to the devices. Note however, that our channel names are relatively
> fixed (they have to be so that sounds can be mapped to channels properly) and
> thus you may not be able to get the perfect names here.
> 
> 
> http://pulseaudio.org/wiki/WritingProfiles
>

OK, I can look into this later can't I? The misnaming is not related to 
the failed detection I suppose.

> In addition to the the debug output please also supply:
> 
>  1. amixer -c1 (where 1 is the card number - cat /proc/adound/cards)
>  2. pacmd ls (when the device is working properly - perhaps after restarting
> PA)

1. amixer shows nothing, no controls at all:
    $ cat /proc/asound/cards
     0 [NVidia         ]: HDA-Intel - HDA NVidia
                          HDA NVidia at 0xfcf78000 irq 20
     1 [Audio          ]: USB-Audio - Kinect USB Audio
                             Microsoft Kinect USB Audio at
usb-0000:00:02.1-5.1, high speed
    $ amixer -c1
    $

2. output from "pacmd ls" is attached, when the Kinect is recognized it 
   shows up as the first sourdcard to pulseaudio, see from line 525.


> Note that even when PA is restarted, udev is used to detect things. I suspect
> the problem of it not showing up is related to some kind of race condition.
>

Thanks,
   Antonio

-- 
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.