[SomeoneWhoIsntMe]

Quote:

Originally Posted by Weedy Kamo-chan ~ # cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.11rc5.

If you can, try downgrading to 1.0.10, and locking it there for now. Not sure how that works in portage, but you catch my drift.

 

[CousCous]

Quote:

Originally Posted by Weedy It's broken again. Kamo-chan ~ # cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.11rc5.

Weedy, same thing happened to me. Downgrading to 1.0.11rc4 fixed it.

 

[Weedy]

i know i can downgrade and i have, but i want a fix not a work around

Ps. Thank god i could downgrade cause im was killing my self for the 30mins i had to use the normal DAC

 

[Weedy]

anyone tested with 1.0.11? (ie final)

 

[Weedy]

Code:

[left]Kamo-chan ~ # cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.11. Compiled on May 13 2006 for kernel 2.6.16-gentoo-r7 (SMP).[/left]

very broken does anyone have a fix?

 

[wallstreet]

I just upgraded to Ubuntu Dapper from Breezy and haven't been able to get the hi-res output to work yet. Here is the output I get w/ the previous asound.state
Quote:

sudo alsactl restore alsactl: set_control:888: warning: iface mismatch (2/3) for control #53 alsactl: set_control:890: warning: device mismatch (1/1) for control #53 alsactl: set_control:892: warning: subdevice mismatch (0/0) for control #53 alsactl: set_control:894: warning: name mismatch (IEC958 Playback Con Mask/IEC958 Playback Con Mask) for control #53 alsactl: set_control:896: warning: index mismatch (0/0) for control #53 alsactl: set_control:888: warning: iface mismatch (2/3) for control #54 alsactl: set_control:890: warning: device mismatch (1/1) for control #54 alsactl: set_control:892: warning: subdevice mismatch (0/0) for control #54 alsactl: set_control:894: warning: name mismatch (IEC958 Playback Pro Mask/IEC958 Playback Pro Mask) for control #54 alsactl: set_control:896: warning: index mismatch (0/0) for control #54

This is with Advanced Linux Sound Architecture Driver Version 1.0.10rc3, not with the 1.0.11 that other people have been having problems with. Any suggestions?

 

[sabotaged]

I've got alsa 1.0.10rc3, and I can't seem to get it to work through the high res jack. I've set it as my default card, and checked Alternate Level to Surround Out.

Some weird things: playing a song in banshee, a music player which uses esd, results in the song playing really fast (not that I can hear it, but the song time moves very fast). This doesn't seem to change if I alter the sampling rate in alsamixer.

Also if I try and play an mp3 in mplayer, I get this:

alsa-init: 1 soundcard found, using: default
alsa-init: format s16le are not supported by hardware, trying default
alsa-init: unable to set format: Invalid argument
Could not open/initialize audio device -> no sound.
Audio: no sound
Video: no video

Anyone have any ideas?

Edit: alstactl restore gives no errors

 

[sgprater]

Quote:

Originally Posted by sabotaged I've got alsa 1.0.10rc3, and I can't seem to get it to work through the high res jack. I've set it as my default card, and checked Alternate Level to Surround Out. Some weird things: playing a song in banshee, a music player which uses esd, results in the song playing really fast (not that I can hear it, but the song time moves very fast). This doesn't seem to change if I alter the sampling rate in alsamixer. Also if I try and play an mp3 in mplayer, I get this: alsa-init: 1 soundcard found, using: default alsa-init: format s16le are not supported by hardware, trying default alsa-init: unable to set format: Invalid argument Could not open/initialize audio device -> no sound. Audio: no sound Video: no video Anyone have any ideas? Edit: alstactl restore gives no errors

1) Can you copy and paste your .asoundrc file here?
2) What's the output of "aplay -L"?

The error message "alsa-init: unable to set format: Invalid argument" is deceptive -- it can indicate all kinds of problems, not just format problems. I was getting that error message when it couldn't find the card I referred to in my (erroneous) commandline argument.

 

[sabotaged]

jzablot@venice:~$ cat /proc/asound/cards

0 [CK804 ]: NFORCE - NVidia CK804
NVidia CK804 with ALC850 at 0xfebfd000, irq 58
1 [AV710 ]: ICE1724 - Chaintech AV-710
Chaintech AV-710 at 0xdf00, irq 66

/etc/asound.conf:

pcm.!default {
type hw
card 1

}

ctl.!default {
type hw
card 1
}

And here's my output from aplay -L: http://pastebin.com/747131

 

[sgprater]

Okay, what happens when you execute "aplay -D default <somefile.wav>"?

Also, what is the output of "aplay -l"?

Looks like your Alsa sees your card, which is a step in the right direction.

Feel free to PM me if you'd like to continue this offline.

 

[Weedy]

what about final

 

[Weedy]

BUMPING A BOOKMARKED THREAD!

 

[darklegion]

The asound.state is still broken with alsa 1.0.12-rc1.

EDIT : I posted a bug report to the ALSA developers:
https://bugtrack.alsa-project.org/al...ew.php?id=2348

 

[darklegion]

Attached is a working asound.state for 1.0.11 and up.

Also it seems that envy24control was ported to ice1274, which seems to support changing a number of advanced settings; notably it seems to support sample rates higher than 48000, although who knows if it will actually work with the AV710.
You can get it here:
https://bugtrack.alsa-project.org/al...ew.php?id=1831

You'll need to select "guest login" in order to access it.

 

[Weedy]

Quote:

Originally Posted by darklegion /img/forum/go_quote.gif Attached is a working asound.state for 1.0.11 and up. Also it seems that envy24control was ported to ice1274, which seems to support changing a number of advanced settings; notably it seems to support sample rates higher than 48000, although who knows if it will actually work with the AV710. You can get it here: https://bugtrack.alsa-project.org/al...ew.php?id=1831 You'll need to select "guest login" in order to access it.

i want your babies