Posts: 7,650
Joined: Jun 2011
Reputation:
287
can you give the nightly PPA a try, those udev-trigger or sleep workarounds should not be necessary anymore. Xbmc now waits for audio devices to come up.
Posts: 34
Joined: Dec 2012
Reputation:
0
i am using the latest frodo release of buntu and it required a work around as of January
Posts: 15
Joined: Oct 2009
Reputation:
0
nermal
Junior Member
Posts: 15
I just installed the latest nightly package (2:13.0~git20130427.0200-44f0991-0raring) and I can confirm that the issue is still present. My Nvidia HDMI audio device is not detected, unless I delay the start of XBMC by 10 seconds (sleep 10).
The udevtrigger solution did not work for me. "aplay -l" lists the Nvidia HDMI device, but XBMC can't see it unless I wait 10 seconds after LXDE comes up.
It would be great if XBMC either waited for previously seen audio devices to show up or rescan the ALSA devices periodically after startup.
Posts: 19,982
Joined: May 2009
Reputation:
451
nickr
Retired Team-Kodi Member
Posts: 19,982
Not strictly an xbmc issue, the problem is a system config issue - xbmc starting too soon.
Posts: 15
Joined: Oct 2009
Reputation:
0
nermal
Junior Member
Posts: 15
"aplay -l" detects the device 10 seconds before XBMC detects it though, so I think it is an XBMC issue.
Posts: 7,135
Joined: Oct 2012
un1versal
Out of Memory (1939–2016)
Posts: 7,135
Since delaying lightdm fixes the problem it cant be a XBMC problem, it were a XBMC problem it wouldn't be solved in such way would it? (That's not really a question)
uNi
Posts: 15
Joined: Oct 2009
Reputation:
0
nermal
Junior Member
Posts: 15
Agreed. But why is it that other programs (like aplay) can use the HDMI audio immediately, without any delay of lightdm? I think that is a XBMC problem.
Posts: 7,135
Joined: Oct 2012
un1versal
Out of Memory (1939–2016)
Posts: 7,135
2013-05-03, 15:16
(This post was last modified: 2013-05-03, 15:19 by un1versal.)
I dont know the intricacies of aplay in relation to alsa other than its a command line player for alsa, and XBMC is totally unrelated to aplay, perhpas you would like to go ask alsa forums that.
that said if this was a device blocking issue it would block any devices trying to use the soundcard, while xbmc has been known to block devices due to AE bugs, this doesnt appear to be the case, so ergo, not xbmc problem, you can determine this easily by bypassing lightdm as a xbmc laucher and lauch xbmc via xinit on system boot see
HOW-TO:Install_XBMC_for_Linux#Upstart_init_script (wiki) and disable lightdm for a boot or two, if it cures it you will know for sure.
But Im not a developer or going to be arguing the finer points of madness with you. I will defer to a developer like fritsch or wsnipx who know better whats going on.
uNi