On Tue, 10 Jun 2003, Paul Davis wrote:
> >Like you I think the HDSP driver understands my firmware revision. I have
> >also downgraded and upgraded my firmware without success.
> >
> >This whole Alsa/HDSP thing is amazingly weird...
>
> at the moment, i regret that we made the move to user-space l
The error is as follows; I've tried to move a couple locks around but I
can't figure it out.
-->8
bad: scheduling while atomic!
Call Trace:
[] schedule+0x3a6/0x3b0
[] schedule_timeout+0x5a/0xb0
[] process_timeout+0x0/0x10
[] usb_start_wait_urb+0xaf/0x190
Dear ALSA developers,
Here is a message from ESS regarding getting some information for the
ESS1988/Allegro-1 series cards in order to get better support for them in
linux. I hope that some others will help me badger the ESS people in order to
(A) release info needed to make the Linux driver or
>Anyone care to shed the light on the math for what totalmix does
>regarding fader-to-mixer, fader-to-db and mixer-to-fader values? What I
>have works, but it's UGLY. (well just the constants... I like things to
>be simple.)
you could use the settings in ardour, which has relatively
sophisticated
Anyone care to shed the light on the math for what totalmix does
regarding fader-to-mixer, fader-to-db and mixer-to-fader values? What I
have works, but it's UGLY. (well just the constants... I like things to
be simple.)
d!
On Wed, 2003-06-11 at 00:48, tom burkart wrote:
> Today, Paul Davis wrote
Hi all,
I modified the code in amixer.c for my own use. Instead of being a command
line utility that ends after every mixer access, I have it as a function
call from a larger program. I also cut it down quite a bit so that I am
only using sset for Master and PCM.
The problem that I am runnin
My card which can enter a low power state. It turns
off some components but it leaves the PCI bus interface
active. To bring the card back to life it has to be
reinitialized from scratch. What "D" state is it ? PCI
power management papers say that already in D1 state
i/o space is disabled. I'm a
On 11-Jun-2003 Sundaranathan S wrote:
> Hi All,
>
> Can anyone tell me how to test alsa-lib APIs. If there is any
> documentation available please let me know.
Yes, the official documentation is here:
http://www.alsa-project.org/documentation.php3
Bye.
--
On Wednesday 11 June 2003 16.03, Gorm David Lai wrote:
> Thanks for the advice, though it still doesn't work.
> It seems to play, and sets the right sync on the mixing console. The
> console just doesn't get any input.
> Do I have to unmute the card anywhere?
Note that my example uses /dev/zero (z
> > so I think
> > I'm almost set to be able to try this stuff out again.
>
> For what it's worth, i had problems with alsa 0.9.4 & SMP. i think
> there are some spinlock changes that aren't very well debugged yet.
> On the other hand, alsa 0.9rc7 seems fairly stable. i've gotten
> some lockups,
Thanks for the advice, though it still doesn't work.
It seems to play, and sets the right sync on the mixing console. The
console just doesn't get any input.
Do I have to unmute the card anywhere?
/Gorm
On Wed, 2003-06-11 at 15:48, Anders Torger wrote:
>
> Test this:
>
> aplay -D hw:0,1 -r 44
Test this:
aplay -D hw:0,1 -r 44100 -f S16_LE -c 8 /dev/zero
it should work. It works on my card.
The problem in your
aplay -D hw:0,1 -c 8 ~/cavi/sound/01/01\ Track\ \ 1.wav
is that aplay seems to ignore your -c 8, and reads the wav header
instead, and sets it to stereo, as you can see in t
Ok. Sorry for spamming the list, but I got a hint that may point to
somewhere where someone can help me.
If I use aplay with plughw:0,1 as opposed to hw:0,1 aplay acts as if it
is playing, but no sound reaches the digital mixing console, though it
still seems to sync to the signal. This seems to b
I also have problems with aplay. Maybe this is related?
The following command:
aplay -D hw:0,1 -c 8 ~/cavi/sound/01/01\ Track\ \ 1.wav
Which gives the following output:
Playing WAVE '/users/lai/cavi/sound/01/01 Track 1.wav' : Signed 16 bit
Little Endian, Rate 44100 Hz, Stereo
aplay: set_params
Today, Clemens Ladisch wrote:
> What, exactly, does "doesn't work properly" mean? It doesn't compile?
> "modprobe snd-ymfpci" fails? Error messages in /var/log/messages?
> "aplay something.wav" crashes? The computer explodes? Green demons
> coming out of your speakers?
:-) oops. Sorry about the
On Mon, 2003-06-09 at 19:23, Martin Langer wrote:
> On Fri, Jun 06, 2003 at 12:06:33PM +0200, Gorm David Lai wrote:
> > On Thu, 2003-06-05 at 21:03, Martin Langer wrote:
> > > On Thu, Jun 05, 2003 at 12:17:32PM +0200, Gorm David Lai wrote:
> > > >
> > > > We have recently bought a RME Digi96/8 car
Hi All,
Can anyone tell me how to
test alsa-lib APIs. If there is any documentation available please let
me know.
thanks,
-Sundaranathan
SIP Technologies & Exports Ltd
--
"Live as if to die tomorrow. Learn as if to live forever."
tom burkart wrote:
> Today, Clemens Ladisch wrote:
> > > My Toshiba Tecra (uses YMF-744B) still does not work under 0.9.4(rel)
> > Is there still an oops?
> Sorry, no oops, but doesn't work properly either.
What, exactly, does "doesn't work properly" mean? It doesn't compile?
"modprobe snd-ymfpci"
On 10 Jun 2003, Ray Heasman wrote:
> Hi,
>
> The ALSA YMF-754 SPDIF support is incomplete in a way that ensures that
> AC-3 streams can not be decoded by standards compliant receivers. Very
> forgiving receivers will render the AC-3, but they are being kind.
> According to the standard, they shou
Today, Clemens Ladisch wrote:
> > My Toshiba Tecra (uses YMF-744B) still does not work under 0.9.4(rel)
> Is there still an oops?
Sorry, no oops, but doesn't work properly either.
tom.
Consultant
AUSSECPhone: 61 4 1768 2202
339 Blaxland Rd., Ryde NSW 2112
Email: [EMAIL PROTECTED]
20 matches
Mail list logo
