>Admittedly, it's quite old but that, if anything speaks only in Linux's
>favor in terms of its pro-audio readiness. At any rate, I was checking
>out the benchmark data and was wondering as to how did this
>person/software app get to the 0.73ms buffer fragment that is equal to
>128bytes? In other w
Hi all,
I've had an interesting discussion with a professor and a distinguished
member of the electroacoustic music community regarding audio latencies
which made me realize that I did not understand the issue in its
entirety. Hence, I looked around the net in order to educate myself.
I soon stum
I can't work out how to get the entries in /dev/snd to have the correct
permissions.
Starting with no modules.
Modprobe snd- results in the files in /dev/snd having only root rw
permissions. They are created with the correct group "audio"
At the moment every time I reload my driver I need to
On Monday 06 October, 2003 � 03:36:32PM +0200, Jaroslav Kysela wrote:
> We added these sanity checks for debugging purposes, but if they occur too
> much, there's something bad with driver or hardware.
>
> Basically, we have only information from last interrupt position and the
> actual position i
Hi,
I have a pretty frustrating problem with my Alsa setup. Right now I'm
just looking for guidance about what's messed up and how I might get it
fixed. I'm not sure if it's a driver issue, an Alsa issue, or a hardware
issue. I have not yet found anyone else that has this exact set of
problems,
James Courtier-Dutton <[EMAIL PROTECTED]> writes:
> 2) For alsa to work in kernel 2.6, the first item in the OSS menu has
> to be set to M, otherwise module soundcore does not seem to
> exist. (This is unconfirmed, so might just be user error)
That is not the case. It works fine here, without an
Hi,
I have been helping a few people on #alsa on freenode.net.
Some points to note: -
1) It seems that alsa does not work when compiled into the kernel, but
does work as modules.
2) For alsa to work in kernel 2.6, the first item in the OSS menu has to
be set to M, otherwise module soundcore does
At Mon, 06 Oct 2003 19:19:08 +0200 (CEST),
[EMAIL PROTECTED] wrote:
>
> Thanx that cleared a lot.
>
> I thought so,
>
> since I want to allocate once and then leave it, (because I dont want an exlusiv
> use of capture and playback ...)
>
> Please three more questions:
>
> 1) I found also the
Thanx that cleared a lot.
I thought so,
since I want to allocate once and then leave it, (because I dont want an exlusiv
use of capture and playback ...)
Please three more questions:
1) I found also the function:
snd_malloc_sgbuf_pages(hdspm->pci, wanted, dmab)
Can I allocate memory with th
This adds support for the timer on ymfpci chips.
Index: alsa-kernel/include/ymfpci.h
===
RCS file: /cvsroot/alsa/alsa-kernel/include/ymfpci.h,v
retrieving revision 1.10
diff -u -r1.10 ymfpci.h
--- alsa-kernel/include/ymfpci.h
Some functions assumed that timer->hw.resolution is in Hz, while it's
actually in ns/tick.
Index: alsa-kernel/core/timer.c
===
RCS file: /cvsroot/alsa/alsa-kernel/core/timer.c,v
retrieving revision 1.47
diff -u -r1.47 timer.c
--- al
At 2 Oct 2003 20:15:04 -0400,
Arcady Genkin wrote:
>
> The code for sscape_ctl from the 0.9.7 tarball of alsa-tools does not
> compile. The problem is on line 208 in sscape_ctl.c:
>
> microcode.code = &_microcode;
>
> This produces the following (fatal) error message:
>
> source='sscape_
Hi there,
I'm trying to route spdif signal from my dvb card through my soundcard,
a sb live 5.1, to my amplifier. My amplifier states that it's 48kHz
spdif signal. I connected the spdif out of the dvb card to the "CD
SPDIF" connector of the sb live card. Is this the proper way to do it,
ie, should
At Thu, 02 Oct 2003 00:16:57 -0400,
Manuel Jander wrote:
>
> Hello,
>
> Below is a link to a patch (a big one) which adds support for the Aureal
> Vortex and Advantage family of soundcards. This driver is believed to be
> stable, but its development will continue, to add and extend features.
>
>
At Sun, 5 Oct 2003 21:01:58 +0200 (CEST),
Jaroslav wrote:
>
> On Sat, 4 Oct 2003, Winfried Ritsch wrote:
>
> >
> > Hello !
> >
> > (A question from an newbie-developer to make it perfect ;-)
> >
> > I am writing an ALSA-lowleveldriver for the RME HDSP-MADI card.
> > (which have 64Audion in and ou
On Sun, 5 Oct 2003, Giuliano Pochini wrote:
> On Sat, 4 Oct 2003 16:58:12 -0500
> Ryan Underwood <[EMAIL PROTECTED]> wrote:
>
> > > i have an ES1983S Maestro-3i on a c600 dell laptop
> > > i got this message in syslog :
> > >
> > > ALSA sound/core/pcm_lib.c:214: Unexpected hw_pointer value (stream
At Sun, 5 Oct 2003 21:25:27 +0200,
Karsten Wiese wrote:
>
> [1 ]
> Hi Takashi,
>
> this enables DRAINING.
> Here it is a really bugfix for using us428 with snd & alsaplayer.
> Please commit.
thanks, applied now.
> What do you think about the us428control stuffs I sent you last week?
it looks
At Sat, 04 Oct 2003 15:39:52 +0100,
James Courtier-Dutton wrote:
>
> Hi,
>
> With 5.1 channel sound being used quite a lot now, I was wondering what
> to do about volume controls.
> For example, I have: -
> Front speakers controlled by PCM and Master slider.
> Rear speakers controlled by Surround
At Sat, 4 Oct 2003 16:58:12 -0500,
Ryan Underwood wrote:
>
>
> Hi,
>
> On Sat, Oct 04, 2003 at 11:12:00PM +0200, Jon wrote:
> > hello,
> >
> > i have an ES1983S Maestro-3i on a c600 dell laptop
> > i got this message in syslog :
> >
> > ALSA sound/core/pcm_lib.c:214: Unexpected hw_pointer valu
At Mon, 6 Oct 2003 03:46:05 -0700 (PDT),
Daniel MacDonald wrote:
> Also, I would recommend that:
>
> options snd-intel8x0 mpu_port=0x330
>
> be added to modules.conf by alsaconf by default (if it
> doesn't already- I haven't run the 0.9.7a version as
> everything is working fine now) as MIDI doe
At Fri, 03 Oct 2003 17:00:42 +0100,
James Courtier-Dutton wrote:
>
> [1 ]
> This patch fixes the display of revision number for ALC650 AC97 chip.
> "alsamixer"
> displayed the correct revision, but
> "cat /proc/asound/card0/ac97#0"
> did not.
thanks, now committed to cvs together with your patch
At Fri, 3 Oct 2003 17:10:42 -0500,
Ryan Underwood wrote:
>
>
> Ok, I fixed this, and then discover that a Makefile is not generated in
> /hal2 directory, so the build dies at that point. What should I use for
> a Makefile template for this directory? Has anyone built this successfully?
are you
Doh!
Thanks to Jaroslav for the very speedy reply, but it
turns out that BOTH mic. in and line in recording work
fine under ALSA 0.9.7a / NFORCE2. I THOUGHT I had the
capture level up- it would've helped if I had actually
used my eyes and what little brain I have to realise
it was at 0. Sorry abou
23 matches
Mail list logo
