On Saturday 20 September 2008 12:56:31 pm Tyler Aviss wrote:
> Normally if I'm on a list and send an email, it goes to everyone on
> the list including myself (aka I get my own email back).
> The last one I sent out didn't come to my inbox, though it does appear
> on the archives. Is that normal fo
On Friday 13 June 2008, Grant wrote:
> I don't get sound from usb-audio, making sure the name matches.
> Could the .asoundrc syntax be wrong there?
I doubt the following could be wrong:
pcm.usb-audio {
type hw
card 0
}
Unless usb-audio is not your device. I would tend
On Friday 13 June 2008, Grant wrote:
> I changed my config like so and restarted alsasound with the same
> results:
>
> .asoundrc:
>
> pcm.usb-audio {
> type hw
> card 0
> }
> pcm.usb-audio_44 {
> type plug
> slave {
> pcm usb-audio
>
On Friday 13 June 2008, Grant wrote:
> pcm.my_device
Sorry, thought it would be understood that 'my_device' is the alsa alias
(in my case the the name of the kernel module without the
leading "snd-") for the hardware device in question (see your
modules.conf file or whatever is proper for your
On Thursday 12 June 2008, Florian Faber wrote:
> So, please tell me - how should a 'pro audio chain' look like?
I'm not saying one should never work with floats - I'm sure there's a
very good reason for it, but the chain should still be able to
support "digital wire" capability if desired. You m
On Thursday 12 June 2008, Florian Faber wrote:
> On IEEE 32 bit floats the mantissa is 23 bit, so there might be
> situations where you loose the LSB.
And that was the only point - a "pro audio chain" should be able to
support "digital wire" capability.
> And as long as it doesn't support the sa
On Thursday 12 June 2008, Florian Faber wrote:
> What makes you think converting a 16 bit unsigned integer to a IEEE
> 32 bit float and back would change the value?
Should have used a 24 bit example. I'm of the opinion that with it the
process is not always a bit perfect translation. But I'm open
On Thursday 12 June 2008, Grant wrote:
> I'm trying to get music from mpd to my USB DAC in 100% untouched
> form. My mpd.conf is as follows:
>
> audio_output {
> type "alsa"
> name "USB Monica"
> device "hw:0,0"
> format "44100:16:2"
> }
Don't know anything about mpd but you can set up an asoundrc
On Monday 09 June 2008, Bill Unruh wrote:
> That will at most give you digitization noise which at 16 bit is 96dB
> below full signal. Ie, it is much less than the tape hiss from a tape
> recorder for example.
Not that tape hiss should be a standard we compare everything to :)
A little peeve with
Use fixed font, no word wrap and wide window to view properly:
┌[AlsaMixer v1.0.16rc1
(Press Escape to quit)]┐
│ Card: HDA Intel
On Saturday 26 April 2008, Andy Teijelo Pérez wrote:
> I'm attaching a screen hardcopy of my alsamixer in All View (run with
> "-V all") There you can see that I only have 16 controls and there's
> no Analog Loopback and that the top of the window shows it's
> alsamixer 1.0.16 running, just like al
On Saturday 26 April 2008, Andy Teijelo Pérez wrote:
> sadly, my alsamixer
> doesn't show that switch.
Use the tab key to toggle between playback/capture/all view modes. Or
start alsamixer with a view switch: "alsamixer -V capture"
or "alsamixer -V all".
--
Chris
-
On Wednesday 23 April 2008, Mark Knecht wrote:
> Florian,
>Great info and thanks for all the help.
>
>If you get to a place where you want another tester, in my case
> and HDSP 9652 running under Gentoo, drop me a note.
Ditto that.
--
Chris
--
On Saturday 28 July 2007, Uli wrote:
> I wanna get rid of my 10 year old crappy speakers and I'm looking for some
> really high class speakers and sound card.
http://www.hometheaterblog.com/hometheater/2006/03/what_about_bose.html
Sound Card Suggestions...
PCI:
http://www.rme-audio.de/en_products
On Sunday 01 July 2007, Andrew Gaydenko wrote:
> For me the driver works for the same card on amd64 platform (Core 2 Duo).
> The card (hex) firmware revision is:
>
> lspci | grep RME
> 05:04.0 Multimedia audio controller: Xilinx Corporation RME Hammerfall DSP
> (rev 98)
>
> '(re)store' commands do
On Wednesday 02 May 2007, Andrew Gaydenko wrote:
> What is the current state of 'hdsp' alsa driver? Does it still require
> to downgrade RME HDSP 9632 firmware to v.1.51 (as I have found while
> googling)?
Interested in this answer as well. RME seems to only offer 1.52.
On top of that I don't hav
On Sunday 01 July 2007, Andrew Gaydenko wrote:
> For me the driver works for the same card on amd64 platform (Core 2 Duo).
> The card (hex) firmware revision is:
Core 2 Duo x86_64 here as well, on Intel 975BX board.
> lspci | grep RME
> 05:04.0 Multimedia audio controller: Xilinx Corporation RME
Changes in alsa-kernel/pci/rme9652/hdsp.c for the 1.0.14 release break the RME
HDSP 9632 (and alsa all together once the module loads).
An attempt to to do "alsactl restore" results in:
===
alsactl: set_control:991: warning: name mismatc
On Friday 29 June 2007, Chris Smith wrote:
> Recently updated alsa (drivers, libs, utils, etc.) from 1.0.14-rc3 to
> 1.0.14 and snd_hdsp does not work any longer. In fact if I allow the
> snd_hdsp module to load alsa will not work at all even with the default
> snd_hda_intel device.
&g
Hello,
Recently updated alsa (drivers, libs, utils, etc.) from 1.0.14-rc3 to 1.0.14
and snd_hdsp does not work any longer. In fact if I allow the snd_hdsp module
to load alsa will not work at all even with the default snd_hda_intel device.
An attempt to to do "alsactl restore" results in:
=
On Friday 19 January 2007 17:07, Ronny Standtke wrote:
> -
> alias snd-card-0 snd-intel8x0
> options snd-intel8x0 index=0
> alias snd-card-1 snd-usb-audio
> options snd-usb-audio index=1
> alias snd-card-2 snd-usb-audio
> options snd-usb-audio index=2
> -
Just curious, have you tri
Hello,
I'm trying to get Mplayer and Xine to talk natively to the Also driver for the
RME HDSP 9632 with little success. I'm using the following in my asoundrc for
direct analog output:
pcm.hdsp_analog {
type plug
ttable.0.10 1
ttable.1.11 1
slave.pcm hdsp
Doh!
Needed to install alsa-lib first.
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: h
I'm getting this error:
==
Making all in aplay
make[1]: Entering directory `/usr/local/src/alsa-utils-1.0.0rc1/aplay'
if gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include-O2
-fomit-frame-pointer -s -pipe -mcpu=pentium4 -march=pentium4 -mm
What are the PCM and Master level settings when using the intel8x0 driver for
unity gain, that which causes no volume processing to be done?
Thanks.
Chris
---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts ov
On Monday 13 October 2003 10:39, Takashi Iwai wrote:
> nope, it's not a right fix.
> "ifdef CONFIG_HAVE_PDE" means what "if >= 2.4.23" does.
> it should have been fixed on the cvs now.
>
> 0.9.7c is already out. please give a try.
Tried it but make fails:
In file included from
/usr/local/src/a
On Monday 13 October 2003 03:04, Jaroslav Kysela wrote:
> You have to rerun autoconf and configure.
I hadn't previously run autoconf as this wasn't a CVS version but running it
after applying the patch didn't help any.
Bernard Rosenkraenzer posted another patch on the alsa-devel and it is work
On Sunday 12 October 2003 12:40, Jaroslav Kysela wrote:
>
> Bellow patch will solve your problem for 0.9.7b.
>
Thanks much, but I now get a similar error:
In file included from
/usr/local/src/alsa-driver-0.9.7b/include/sound/driver.h:42,
from hwdep.c:22:
/usr/local/src/alsa-d
Using a previously working simple configure:
./configure --with-cards=hdsp,intel8x0 --with-sequencer=yes --with-oss=yes
--with-isapnp=no
With alsa-driver 0.9.6 I get this error during make:
In file included from
/usr/local/src/alsa-driver-0.9.6/include/sound/driver.h:42,
from
29 matches
Mail list logo
