help upgraded to lucid and now no sound in xbmc
#1
I just upgraded to lucid from karmic and now I cant play my movies with audio. I had it working perfectly on karmic. Any help please.

Here is my my xbmc log
http://pastebin.com/8XTEDbC8
  • Acer Revo 3610

  • I am now running xbmc 9.11 (camelot) on ubuntu lucid full ubuntu desktop
  • kernel 2.6.32-26-generic

  • alsa version - Advanced Linux Sound Architecture Driver Version 1.0.21.
  • Running HDMI to receiver Onkyo TX606

I get sound in xbmc menus however when I try to put a movie on it gives me a fail to initialize audio message.
my xbmc settings are below

audio output digitial
dolby digital ac3 on
dts capable receiver on
audio out device custom
custom audio device hdmi
passthrough output device custom
custom passthrough device plughw:0,3
downmix multichannel audio to stereo off

I checked alsamixer and its unmuted.

Any help.
Nvidia Shield with Kodi 18
Reply
#2
I currently have my /etc/asound.conf as below

pcm.!hdmi-remap {
type asym
playback.pcm {
type plug
slave.pcm "remap-surround71"
}
}

pcm.!remap-surround71 {
type route
slave.pcm "hw:0,3"
ttable {
0.0= 1
1.1= 1
2.4= 1
3.5= 1
4.2= 1
5.3= 1
6.6= 1
7.7= 1
}
}

does not look right as I have read in other post another asound.conf file going to try to change this to see if it works.

Code:
# ~/.asoundrc or /etc/asound.conf
# ALSA configuration file

##### USAGE #####
# Save this file as "~/.asoundrc" (for user-specific sound configuration) or
# "/etc/asound.conf" (for system-wide sound configuration) and specify ALSA
# device names ad described in the next section.


##### DEVICE NAMES #####
# This configuration file defines four devices for use by the user.  Those
# devices are "analog", "mixed-analog", "digital", and "mixed-digital".  The
# user may also re-define "default" to be identical to one of the above-named
# devices (i.e. to send all sound output to the digital output unless otherwise
# specified).  Use the device names as described below:
#  - "analog" outputs to the analog output directly and (at least on software
#  sound cards) blocks other audio output.  After playback completes, "queued"
#  sounds are output in sequence.
#  - "mixed-analog" mixes audio output from multiple programs into the analog
#  output (so you can hear beeps, alerts, and other noises while playing back
#  an audio stream).
#  - "digital" outputs to the digital output directly.  Since most (all?)
#  digital outputs expect 48kHz PCM audio, this may not work for some playback
#  (i.e. CD's--which are 44.1kHz PCM audio--or 32kHz audio streams from TV
#  recordings, etc.).
#  - "mixed-digital"

# All other devices created within this file are used only by the configuration
# file itself and should /not/ be used directly.  In other words, do not use
# the devices "analog-hw", "dmix-analog", "digital-hw", or "dmix-digital".


##### IMPORTANT #####
# To make this ALSA configuration file work with your sound card, you will need
# to define the appropriate card and device information for the "analog-hw" and
# "digital-hw" devices below.  You can find the card and device information
# using "aplay -l".


##### Configuration File #####

# Override the default output used by ALSA.  If you do not override the
# default, your default device is identical to the (unmixed) "analog" device
# shown below.  If you prefer mixed and/or digital output, uncomment the
# appropriate four lines below (only one slave.pcm line).
#
# Note, also, that as of ALSA 1.0.9, "software" sound cards have been modified
# such that their default "default" device is identical to the "mixed-analog"
# device.  Whether using an ALSA version before or after 1.0.9, it does no harm
# and has no affect on performance to redefine the device (even if the
# redefinition does not change anything).  Also, by using this ALSA
# configuration file, you once again have access to unmixed analog output using
# the "analog" device.
pcm.!default {
  type plug
## Uncomment the following to use (unmixed) "analog" by default
#  slave.pcm "analog-hw"
## Uncomment the following to use "mixed-analog" by default
#  slave.pcm "dmix-analog"
## Uncomment the following to use (unmixed) "digital" by default
#  slave.pcm "digital-hw"
## Uncomment the following to use "mixed-digital" by default
  slave.pcm "dmix-digital"
}

# Control device (mixer, etc.) for the card
ctl.!default {
  type hw
  card 0
}

# Alias for (converted) analog output on the card
# - This is identical to the device named "default"--which always exists and
# refers to hw:0,0 (unless overridden)
# - Therefore, we can specify "hw:0,0", "default", or "analog" to access analog
# output on the card
# - Note that as of ALSA 1.0.9, "software" sound card definitions redefine
# "default" to do mixing, meaning this device is different from "default" and
# allows playback while blocking other sound sources (until playback
# completes).
pcm.analog {
  type plug
  slave.pcm "analog-hw"
}

# Control device (mixer, etc.) for the card
ctl.analog {
  type hw
  card 0
}

# Alias for (converted) mixed analog output on the card
# - This will accept audio input--regardless of rate--and convert to the rate
# required for the dmix plugin (in this case 48000Hz)
# - Note that as of ALSA 1.0.9, "software" sound card definitions redefine
# "default" to do mixing, meaning this device is identical to "default" for
# "software" sound cards.
pcm.mixed-analog {
  type plug
  slave.pcm "dmix-analog"
}

# Control device (mixer, etc.) for the card
ctl.mixed-analog {
  type hw
  card 0
}

# Alias for (converted) digital (S/PDIF) output on the card
# - This will accept audio input--regardless of rate--and convert to the rate
# required for the S/PDIF hardware (in this case 48000Hz)
pcm.digital {
  type plug
  slave.pcm "digital-hw"
}

# Control device (mixer, etc.) for the card
ctl.digital {
  type hw
  card 0
}

# Alias for mixed (converted) digital (S/PDIF) output on the card
#  - This will accept audio input--regardless of rate--and convert to the rate
#  required for the S/PDIF hardware (in this case 48000Hz)
pcm.mixed-digital {
  type plug
  slave.pcm "dmix-digital"
}

# Control device (mixer, etc.) for the card
ctl.mixed-digital {
  type hw
  card 0
}

# The following devices are not useful by themselves.  They require specific
# rates, channels, and formats.  Therefore, you probably do not want to use
# them directly.  Instead use of of the devices defined above.

# Alias for analog output on the card
# Do not use this directly--it requires specific rate, channels, and format
pcm.analog-hw {
  type hw
  card 0
  # The default value for device is 0, so no need to specify
#  - Uncomment one of the below or create a new "device N" line as appropriate
#    for your sound card or
#  device 1
#  device 4
}

# Control device (mixer, etc.) for the card
ctl.analog-hw {
  type hw
  card 0
}

# Alias for digital (S/PDIF) output on the card
# Do not use this directly--it requires specific rate, channels, and format
pcm.digital-hw {
  type hw
  card 0
  device 3
#  - Comment out "device 1" above and uncomment one of the below or create a
#    new "device N" line as appropriate for your sound card or
#  device 2
#  device 4
}

# Control device (mixer, etc.) for the card
ctl.digital-hw {
  type hw
  card 0
}

# Direct software mixing plugin for analog output on the card
# Do not use this directly--it requires specific rate, channels, and format
pcm.dmix-analog {
  type dmix
  ipc_key 1234
  slave {
    pcm "analog-hw"
    period_time 0
    period_size 1024
    buffer_size 4096
    rate 48000
    }
}

# Control device (mixer, etc.) for the card
ctl.dmix-analog {
  type hw
  card 0
}

# Direct software mixing plugin for digital (S/PDIF) output on the card
# Do not use this directly--it requires specific rate, channels, and format
pcm.dmix-digital {
  type dmix
  ipc_key 1235
  slave {
    pcm "digital-hw"
    period_time 0
    period_size 2048
    buffer_size 32768
    rate 48000
    }
}

# Control device (mixer, etc.) for the card
ctl.dmix-digital {
  type hw
  card 0
}
Nvidia Shield with Kodi 18
Reply
#3
still not working. what settings should I have in xbmc?

check my nvidia drivers and I currently have 195.36.24

I read in a post that all 190 and 195 drivers are broken. Do I need to go back to aprevious version or a newer version?

ok I updated my drivers now to 260.19.26 via xswat .

lets see if that does anything.
Nvidia Shield with Kodi 18
Reply
#4
ok got it working halfway. The xbmc menus do not work anymore however audio for the movies work. this is my settings in xbmc below

audio output digitial
dolby digital ac3 on
dts capable receiver on
audio out device default

passthrough output device custom
custom passthrough device plughw:0,3
downmix multichannel audio to stereo off

anybody know how to get the menu audio working?
Nvidia Shield with Kodi 18
Reply
#5
menu audio requires a SPECIAL /etc/asound.conf

its documented to death and the above one is NOT it.

so that I litter the forums with crap that as been posted a million times, here it is again

pcm.!default {
type plug
slave {
pcm "hdmi"
}
}

BTW Im not surprised you xbmc 9.11 is having problem on lucid, simply cause IT old, the way it handles audio is NO longer how lucid handles it...

just cause thers a package for xbmc for a particular distro it does not mean its working 100% with all setups and all hardware...

at best 40% to 60%
Reply
#6
X3lectric Wrote:menu audio requires a /etc/asound.conf

its documented to death and the above one is NOT it.

correct and I have one that is below. is this a correct asound.conf file or do I need to change something on it? I just copied it from another post here


Code:
# ~/.asoundrc or /etc/asound.conf
# ALSA configuration file

##### USAGE #####
# Save this file as "~/.asoundrc" (for user-specific sound configuration) or
# "/etc/asound.conf" (for system-wide sound configuration) and specify ALSA
# device names ad described in the next section.


##### DEVICE NAMES #####
# This configuration file defines four devices for use by the user.  Those
# devices are "analog", "mixed-analog", "digital", and "mixed-digital".  The
# user may also re-define "default" to be identical to one of the above-named
# devices (i.e. to send all sound output to the digital output unless otherwise
# specified).  Use the device names as described below:
#  - "analog" outputs to the analog output directly and (at least on software
#  sound cards) blocks other audio output.  After playback completes, "queued"
#  sounds are output in sequence.
#  - "mixed-analog" mixes audio output from multiple programs into the analog
#  output (so you can hear beeps, alerts, and other noises while playing back
#  an audio stream).
#  - "digital" outputs to the digital output directly.  Since most (all?)
#  digital outputs expect 48kHz PCM audio, this may not work for some playback
#  (i.e. CD's--which are 44.1kHz PCM audio--or 32kHz audio streams from TV
#  recordings, etc.).
#  - "mixed-digital"

# All other devices created within this file are used only by the configuration
# file itself and should /not/ be used directly.  In other words, do not use
# the devices "analog-hw", "dmix-analog", "digital-hw", or "dmix-digital".


##### IMPORTANT #####
# To make this ALSA configuration file work with your sound card, you will need
# to define the appropriate card and device information for the "analog-hw" and
# "digital-hw" devices below.  You can find the card and device information
# using "aplay -l".


##### Configuration File #####

# Override the default output used by ALSA.  If you do not override the
# default, your default device is identical to the (unmixed) "analog" device
# shown below.  If you prefer mixed and/or digital output, uncomment the
# appropriate four lines below (only one slave.pcm line).
#
# Note, also, that as of ALSA 1.0.9, "software" sound cards have been modified
# such that their default "default" device is identical to the "mixed-analog"
# device.  Whether using an ALSA version before or after 1.0.9, it does no harm
# and has no affect on performance to redefine the device (even if the
# redefinition does not change anything).  Also, by using this ALSA
# configuration file, you once again have access to unmixed analog output using
# the "analog" device.
pcm.!default {
  type plug
## Uncomment the following to use (unmixed) "analog" by default
#  slave.pcm "analog-hw"
## Uncomment the following to use "mixed-analog" by default
#  slave.pcm "dmix-analog"
## Uncomment the following to use (unmixed) "digital" by default
#  slave.pcm "digital-hw"
## Uncomment the following to use "mixed-digital" by default
  slave.pcm "dmix-digital"
}

# Control device (mixer, etc.) for the card
ctl.!default {
  type hw
  card 0
}

# Alias for (converted) analog output on the card
# - This is identical to the device named "default"--which always exists and
# refers to hw:0,0 (unless overridden)
# - Therefore, we can specify "hw:0,0", "default", or "analog" to access analog
# output on the card
# - Note that as of ALSA 1.0.9, "software" sound card definitions redefine
# "default" to do mixing, meaning this device is different from "default" and
# allows playback while blocking other sound sources (until playback
# completes).
pcm.analog {
  type plug
  slave.pcm "analog-hw"
}

# Control device (mixer, etc.) for the card
ctl.analog {
  type hw
  card 0
}

# Alias for (converted) mixed analog output on the card
# - This will accept audio input--regardless of rate--and convert to the rate
# required for the dmix plugin (in this case 48000Hz)
# - Note that as of ALSA 1.0.9, "software" sound card definitions redefine
# "default" to do mixing, meaning this device is identical to "default" for
# "software" sound cards.
pcm.mixed-analog {
  type plug
  slave.pcm "dmix-analog"
}

# Control device (mixer, etc.) for the card
ctl.mixed-analog {
  type hw
  card 0
}

# Alias for (converted) digital (S/PDIF) output on the card
# - This will accept audio input--regardless of rate--and convert to the rate
# required for the S/PDIF hardware (in this case 48000Hz)
pcm.digital {
  type plug
  slave.pcm "digital-hw"
}

# Control device (mixer, etc.) for the card
ctl.digital {
  type hw
  card 0
}

# Alias for mixed (converted) digital (S/PDIF) output on the card
#  - This will accept audio input--regardless of rate--and convert to the rate
#  required for the S/PDIF hardware (in this case 48000Hz)
pcm.mixed-digital {
  type plug
  slave.pcm "dmix-digital"
}

# Control device (mixer, etc.) for the card
ctl.mixed-digital {
  type hw
  card 0
}

# The following devices are not useful by themselves.  They require specific
# rates, channels, and formats.  Therefore, you probably do not want to use
# them directly.  Instead use of of the devices defined above.

# Alias for analog output on the card
# Do not use this directly--it requires specific rate, channels, and format
pcm.analog-hw {
  type hw
  card 0
  # The default value for device is 0, so no need to specify
#  - Uncomment one of the below or create a new "device N" line as appropriate
#    for your sound card or
#  device 1
#  device 4
}

# Control device (mixer, etc.) for the card
ctl.analog-hw {
  type hw
  card 0
}

# Alias for digital (S/PDIF) output on the card
# Do not use this directly--it requires specific rate, channels, and format
pcm.digital-hw {
  type hw
  card 0
  device 3
#  - Comment out "device 1" above and uncomment one of the below or create a
#    new "device N" line as appropriate for your sound card or
#  device 2
#  device 4
}

# Control device (mixer, etc.) for the card
ctl.digital-hw {
  type hw
  card 0
}

# Direct software mixing plugin for analog output on the card
# Do not use this directly--it requires specific rate, channels, and format
pcm.dmix-analog {
  type dmix
  ipc_key 1234
  slave {
    pcm "analog-hw"
    period_time 0
    period_size 1024
    buffer_size 4096
    rate 48000
    }
}

# Control device (mixer, etc.) for the card
ctl.dmix-analog {
  type hw
  card 0
}

# Direct software mixing plugin for digital (S/PDIF) output on the card
# Do not use this directly--it requires specific rate, channels, and format
pcm.dmix-digital {
  type dmix
  ipc_key 1235
  slave {
    pcm "digital-hw"
    period_time 0
    period_size 2048
    buffer_size 32768
    rate 48000
    }
}

# Control device (mixer, etc.) for the card
ctl.dmix-digital {
  type hw
  card 0
}
Nvidia Shield with Kodi 18
Reply
#7
X3lectric Wrote:menu audio requires a SPECIAL /etc/asound.conf

its documented to death and the above one is NOT it.

so that I litter the forums with crap that as been posted a million times, here it is again

pcm.!default {
type plug
slave {
pcm "hdmi"
}
}


Do I just add that to the bottom of my current one or do I make a new one with only that information above? also would be xbmc audio settings be the same as I have above?
Nvidia Shield with Kodi 18
Reply
#8
backup ur current and add what I posted, DONT MIX and MATCH, also I edited my previous post pls read it again.
Reply
#9
X3lectric Wrote:backup ur current and add what I posted, DONT MIX and MATCH, also I edited my previous post pls read it again.

thanks. I want to upgrade to dharma however the HTE script is not being put into it and that is my main reason not to upgrade yet. plus I rather wait until the final release it out.

Thanks for the help. going to do it right now to see if it works.
Nvidia Shield with Kodi 18
Reply
#10
well I put in the asound.conf that you advised and it didnt work. I tried to play some movies in ac3 and it gave me the fail to initialize audio error. and the menu settings did not work either.

This is the asound.conf that I currently have.

Code:
pcm.!hdmi-remap {

type asym

playback.pcm {

type plug

slave.pcm "remap-surround71"

}

}



pcm.!remap-surround71 {

  type route

  slave.pcm "hw:0,3"

  ttable {

    0.0= 1

    1.1= 1

    2.4= 1

    3.5= 1

    4.2= 1

    5.3= 1

    6.6= 1

    7.7= 1

  }

}
Nvidia Shield with Kodi 18
Reply
#11
you did reboot xbmc after putting the setting I said right?

also your xbmc settings on sound need to be correct.

I think its time u upgraded xbmc its not final or stable release but the again stable doesnt equal bug free and in that respect the current RC1 is better in EVERY way then 9.11.

I cant tell you what setting for xbmc are best for you, since I dont have same setup.
Reply
#12
X3lectric Wrote:you did reboot xbmc after putting the setting I said right?

also your xbmc settings on sound need to be correct.

I think its time u upgraded xbmc its not final or stable release but the again stable doesnt equal bug free and in that respect the current RC1 is better in EVERY way then 9.11.

I cant tell you what setting for xbmc are best for you, since I dont have same setup.

thanks for the help. the menu sounds are no biggie. I can live without it. as long as the movies are playing sound like they are suppose to.

One of the main reason I dont upgrade yet is becuase the home theater experience script does not work in dharma. hoping that someone can pickit up and make it for dharma. thanks for your help.
Nvidia Shield with Kodi 18
Reply
#13
what script you talking about?
Reply
#14
X3lectric Wrote:what script you talking about?

This one here nuka made it however he is no longer working on it.

Alot of people are not upgrading yet because of this. This script gives you a custom home theater experience if you have made some custom intros etc..

Check it out. I know you are capable of doing it and I am sure that alot of poeple would be VERY grateful aswell.

Also hope you feel better. Big Grin Big Grin
Nvidia Shield with Kodi 18
Reply
#15
You are aware that the addons available for dharma do all this theres tons of stuff, you cant possibly not have a better HTPC exp with this script then with the current dharma...

btw if you read the bottom link on my signature, you'll understand a bit why Im not able to do more or what I would like or even what I enjoy....

Thx, but Im not feeling better, Im in excrciating pain 24/7 over 3 years now... when I get a bit frustrated peeps moan Im harsh, but though I try not to make it personal, they dont get how my shite circumstances are...

I dont want anyones pitty either, just peace and quiet... I'd kill for some relief.

I doubt anyone is gonna pick that script up,cause theres so many addons that do that and more and better. Even if I was tip top, I dont do python.... I learned linux and bash only... and I cant concentrate to save my life.
Reply

Logout Mark Read Team Forum Stats Members Help
help upgraded to lucid and now no sound in xbmc0