Nigel,
Thanks again. I wasn't trying to imply that you weren't helping, just
asking whether people who really know what's going on inside Alsa look at
the messages.
Anyway, I tried your suggestion and it recreated asound.state. Exactly the
same as the previous one (diff gives no changes), and als
At Mon, 03 Mar 2008 22:03:13 +0100,
Ferry Toth wrote:
>
> Hi Takashi,
>
> I'm sorry, please explain what is the HG version.
See download page of www.alsa-project.org. You can pick up a daily
snapshot tarball instead.
Takashi
---
At Mon, 3 Mar 2008 12:48:11 -0600 (CST),
Stephen Stocker wrote:
>
> On Mon, 3 Mar 2008, Takashi Iwai wrote:
>
> > At Sat, 1 Mar 2008 03:58:16 -0600 (CST),
> > Stephen Stocker wrote:
> >>
> >> Hi.
> >>
> >> I'm running kernel 2.4.24-ck1, gcc 3.3.4. Trying to compile the
> >> alsa-lib-1.0.16,
> Anyway, I tried your suggestion and it
> recreated asound.state. Exactly the same
> as the previous one (diff gives no changes),
> and alsamixer gives the same error message.
> By the way, the USB sound card is disconnected,
> so that's not what's messing things up.
Some distros do the alsactl s
James Courtier-Dutton wrote:
> John Sigler wrote:
>
>> I have an RME AES-32 PCI board.
>> http://www.rme-audio.de/en_products_hdsp_aes32.php
>>
>> When I boot, every channel has its volume set to 0.
>>
>> http://lxr.linux.no/linux/sound/pci/rme9652/hdspm.c#L3396
>> http://lxr.linux.no/linux/sou
On 04/03/2008, John Sigler <[EMAIL PROTECTED]> wrote:
> James Courtier-Dutton wrote:
>
> > John Sigler wrote:
> >
> >> I have an RME AES-32 PCI board.
> >> http://www.rme-audio.de/en_products_hdsp_aes32.php
> >>
> >> When I boot, every channel has its volume set to 0.
> >>
>
> >> http://lxr.
Hello,
I have a 64bit machine with a 64bit OS. I am trying to run a java
program using the 32bit java (the real time version).
Mostly it works fine, I get wonderful low latency audio, but opening a
midi device input crashes the program with an assertion error in
rawmidi.c (line 264)
I am gue
At Tue, 4 Mar 2008 15:03:15 +,
James Courtier-Dutton wrote:
>
> > > Now that we have these dB gain levels, we could potentially set all
> > > mixer controls to 0dB, i.e. not gain and not attenuation, with only
> > > the master output control being set to a lower value so as to avoid
> > >
James Courtier-Dutton wrote:
> Some time ago, there was no way to tell, from user space, if 100%
> or 50% was 0db, -50dB or +50dB. As a result, the safest value to
> use was the minimum value being either 0% or mute. That has changed
> with alsa 1.0.16, as dB gain information is now available.
I'
Takashi Iwai wrote:
> hdspm driver still doesn't support TLV dB information.
> In addition, rme9652/hdsp/hdspm drivers use control elements in a
> non-standard way for indirect accessing, so each mixer value isn't
> visible in amixer or alsactl.
Hello Takashi,
Can you tell whether the hdspm driv
hello,
im using debian with kernel 2.6.18 and alsa 1.0.16 and when i start the pc i
have that message :
"AC'97 0 does not respond - RESET"
i need to run alsaconf after every reboot...
i have a SIS soundcard and always runs under linux
--
Takashi Iwai wrote:
> At Tue, 4 Mar 2008 15:03:15 +,
> James Courtier-Dutton wrote:
>>> > Now that we have these dB gain levels, we could potentially set all
>>> > mixer controls to 0dB, i.e. not gain and not attenuation, with only
>>> > the master output control being set to a lower value s
James,
Thanks. My comments are below.
Best regards,
Peter
mailto:[EMAIL PROTECTED]
www.ptoye.com
-
Sunday, March 2, 2008, 11:52:57 PM, you wrote:
>> I'm a bit confused about the rest of your comment. The only file called
>> devfs is a directory which has two subdirector
On Tuesday 04 March 2008 11:40, Peter Toye wrote:
> Nigel,
>
> Thanks again. I wasn't trying to imply that you weren't helping, just
> asking whether people who really know what's going on inside Alsa look at
> the messages.
>
> Anyway, I tried your suggestion and it recreated asound.state. Exactly
On Tue, 4 Mar 2008, Takashi Iwai wrote:
>>
>>Hi,
>>I'm still getting an error, but slightly different after applying the
>> patch. I'm not sure how to shorten it here without losing some vital
>> message, so here's the complete error:
>
> Looks like your glibc has no CLOCK_MONOTONIC defini
Hello,
I am a PARDUS LINUX user. I upgraded latest 1.0.16 alsa-driver. But, my sound
card seems still unsupported by alsa. In the alsa-project web page ıt is said
that support for this model is under development.
After upgrade, I wrote in console "#alsaconf" but still it comes the same
error m
Hi!
WHICH is your soundcard?
Kindest regards
Julien
Music was my first love and it will be my last (John Miles)
FIND MY WEB-PROJECT AT:
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
=== AND MY PERSONAL PAGES AT: ===
http://www.julie
On Tue, Mar 4, 2008 at 6:07 PM, Julien Claassen <[EMAIL PROTECTED]> wrote:
> Hi!
> WHICH is your soundcard?
> Kindest regards
>Julien
Maya44 PCI. It was described in a PNG attachment clipped from an ALSA
web screenshot ;-)
Here's the latest, from a recent alsa ML posting:
> Can'
At Tue, 04 Mar 2008 17:57:15 +,
James Courtier-Dutton wrote:
>
> Takashi Iwai wrote:
> > At Tue, 4 Mar 2008 15:03:15 +,
> > James Courtier-Dutton wrote:
> >>> > Now that we have these dB gain levels, we could potentially set all
> >>> > mixer controls to 0dB, i.e. not gain and not attenu
19 matches
Mail list logo
