I am hoping someone can help -- I may just be a bit crazy here: Am
running Debain w/alsa 1.0.16, kernel 2.6.26 on a latitude D630 - Intel
ICH8. I've got the snd_hda_intel driver to load and I can get some
sound, but alsamixer shows only a single channel: master, pcm, and front
-- no left/right,
=== On Sunday 07 May 2006 17:11, Christoph Anton Mitterer wrote: ===
Hi.
Additionally to my problems with the onboard sound chip that I've reported in
another post,.. I'm think about buying a 2nd soundcard for my computer an afaik
the TerraTec Aureon 7.1 soundcards are very good cards.
Ac
On Sun, 2006-05-07 at 14:44 +0200, Christoph Anton Mitterer wrote:
> pcm.dsp0
> {
> type plug
> slave.pcm "output"
> }
Recording via the OSS API with aoss will not work in full duplex as you
have set the slave PCM to "output". Try changing that to "duplex".
Also try removing the .asoundrc e
On Sun, 2006-05-07 at 14:44 +0200, Christoph Anton Mitterer wrote:
> Hi.
>
> My mainboard is a Tyan Thunder K8WE (S2895) (details can be found here
> http://tyan.com/products/html/thunderk8we.html and here
> http://tyan.com/products/html/thunderk8we_spec.html).
>
> It uses Nvidia nForce Professio
Hi.
My mainboard is a Tyan Thunder K8WE (S2895) (details can be found here
http://tyan.com/products/html/thunderk8we.html and here
http://tyan.com/products/html/thunderk8we_spec.html).
It uses Nvidia nForce Professional 2200 chipset which includes an AC97 compliant
soundchip.
My distribution is
Hi.
Additionally to my problems with the onboard sound chip that I've reported in
another post,.. I'm think about buying a 2nd soundcard for my computer an afaik
the TerraTec Aureon 7.1 soundcards are very good cards.
According to the kernel-docs I assume that at least the following two should be
Hi.
It works!
It was my fault ( of course ;-).
I was using the wrong syntax for the mencoder call.
With this call (and so nothing about my tv-cards within /etc/asound.conf) it
works:
/usr/bin/mencoder tv://E5 -tv
driver=v4l2:device=/dev/v4l/video0:width=640:height=480:chanlist=europe-west:a
On Tue, 2006-02-28 at 15:11 +0100, [EMAIL PROTECTED] wrote:
> The /etc/asound.conf is "a book with seven seals" to me.
> And the (for me) cryptical error messages from alsa (via mencoder) are
> not very helpfull to me too.
Exactly - you're not supposed to use it. It's only for advanced
functiona
[EMAIL PROTECTED] wrote:
> Q.1. What kernel-module parameter do I need?
None.
> Q.1.a How should be the output via dmesg?
> Q.1.b I don't know if it normal, but I got NO dmesg-output for loading
> snd_bt87x (as I was used to with btaudio)?!
ALSA drivers usually don't output anything to the syste
Hi.
I am quiet desperate...
'cause every HOWTO I found so far:
...unfortunatly covers only recording using btaudio / OSS!
...but as I heard that the OSS-sound-drivers (DEPRICATED) will be removed in
one of the next kernel releases, I am trying to use the new snd_bt87x /
saa7134_alsa ALSA-modu
Op woensdag 11 februari 2004 17:36, schreef Florian Schmidt:
> On Wed, 11 Feb 2004 16:51:19 +0100
>
> Florian Schmidt <[EMAIL PROTECTED]> wrote:
> > > it probably won't be possible to mix the sound of the second device
> > > seperatly of the first device?
> >
> > sure, start alsamixer with the appr
On Wed, 11 Feb 2004 16:51:19 +0100
Florian Schmidt <[EMAIL PROTECTED]> wrote:
> >
> > it probably won't be possible to mix the sound of the second device
> > seperatly of the first device?
>
> sure, start alsamixer with the appropriate command line switch [i'm
> too lazy to read the manpage now]
On Wed, 11 Feb 2004 15:50:26 +0100
Alien9 <[EMAIL PROTECTED]> wrote:
> at home I have 2 cards, a via82xx and a ens1371.
>
> the via82xx onboard has 2 devices, I'd like to know if it is possible
> to split that card in 2 seperated cards, each stereo instead of one
> surround card.
http://
at home I have 2 cards, a via82xx and a ens1371.
the via82xx onboard has 2 devices, I'd like to know if it is possible to split
that card in 2 seperated cards, each stereo instead of one surround card.
it does not have to be split exactly, but I wonder if I could set the asoundrc
file so that I
Hi,
In the process of debuging the problems some hdsp users are
experiencing, I reviewed almost every single line of code in the hdsp
driver, and there are things in there that were inherited from the old
rme9652 driver and that don't seem relevant anymore for the hdsp
(particularly now that h
On Mon, 24 Nov 2003 04:46:13 +0100
David Garcia Garzon <[EMAIL PROTECTED]> wrote:
> Thanks, any help wil be wellcome. And, yes, i am convinced: a basic
> treatment of the vertical view of the architecture will be present,
> but not as the key structure of the document, i prefer an horizontal
> div
David Garcia Garzon wrote:
> - Which is the use that can have rawmidi that sequencer don't?
> It is only a backward compatibility interface?
In most cases, yes.
It comes in handy if you have a bunch of MIDI bytes and don't want to
manage the complexity of parsing them and/or creating sequencer
ev
> I will be glad to read it then. I would also like, if my aruments
> convinced you that at least a basic treatment of the architecture of
> alsa is necessary, assist you in writing something up.
Thanks, any help wil be wellcome. And, yes, i am convinced: a basic treatment
of the vertical view of
A Diumenge 23 Novembre 2003 20:02, Frank Barknecht va escriure:
> Hallo,
>
> David Garcia Garzon hat gesagt: // David Garcia Garzon wrote:
> > - Which is the use that can have rawmidi that sequencer don't? It is only
> > a backward compatibility interface?
>
> Rawmidi devices ("/dev/snd/midiCxCx")
On Mon, 24 Nov 2003 02:06:20 +0100
David Garcia Garzon <[EMAIL PROTECTED]> wrote:
> The architectural division you did (the same one that appears in all
> existing documentation) is very useful (in fact, vital) for
> programmers but only annecdotal for final users (or it should be in
> the future)
Hallo,
David Garcia Garzon hat gesagt: // David Garcia Garzon wrote:
> - Which is the use that can have rawmidi that sequencer don't? It is only a
> backward compatibility interface?
Rawmidi devices ("/dev/snd/midiCxCx") are compatibility interfaces,
but still in wide use even with "modern" softw
On Sun, 23 Nov 2003 18:08:02 +0100
David Garcia Garzon <[EMAIL PROTECTED]> wrote:
> http://www.salleurl.edu/~is04069/Modders/Docs/alsadoc.html
Hi, i followed your link and althogh i'm not capable of speaking spanish
i did look at the "Arquitectura general" section and you dive right into
the diff
As i posted before i am on a user manual[1] (by now in spanish) about sound
infraestructure in Linux. I need some answers in order to fill some dark
zones on the manual. I was unable to post the first block of questions on
devel list so i post them here. Web references or code references may suf
Hi there, I recently picked up an Extigy and built
alsa for it (before i had alsa built for an intel810 and a Midisport 2x2
midiman, now i just have the extigy and that's it)
After building it, I got sound, and the midi input
was working great, but I couldn't play 2 things at the same time.
At Mon, 9 Sep 2002 19:23:20 -0400 (EDT),
Igor Gueths wrote:
>
> Hi all. I've noticed some peculiarities with my driver that I'm hoping to
> clear up here. Whenever I use arecord to record a wav, I always try to use
> the following sample format: 16-bit unsigned 44100 hz. However, when I try
> usi
Hi all. I've noticed some peculiarities with my driver that I'm hoping to
clear up here. Whenever I use arecord to record a wav, I always try to use
the following sample format: 16-bit unsigned 44100 hz. However, when I try
using this format, arecord outputs something similar to: xrun: at least
0.
I have a question pertaining to my Avance Logic ALS4000. I have tried
using the Alsa drivers to no avail. I have not been able to get it
configured properly. I am not sure what I am doing wrong. I do the
./configure, make, and make install for the drivers, utils, and libs.
then I do the modpro
27 matches
Mail list logo
