At Thu, 23 Jan 2003 01:35:53 +0100,
Tais M. Hansen <[EMAIL PROTECTED]> wrote:
>
> On Wednesday 22 January 2003 17:23, Takashi Iwai wrote:
> > could you test the following two patches?
> > with the first one, the driver will calculate the current pointer like
> > VIA686 does. if this is ok, no mes
At Tue, 21 Jan 2003 10:37:45 -,
Merrony, Stephen (London) <[EMAIL PROTECTED]> wrote:
>
> Sorry if this is a FAQ, but is there any way I can control reverb from my
> ALSA application?
not yet. the emu10k1 dsp code was not implemented fully yet...
ciao,
Takashi
---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 23 January 2003 11:03, Takashi Iwai wrote:
> ok, the attached is the third trial.
> please appply it solely without the preivous patches.
I'm assuming the very first via8233a-fix.dif is still supposed to be applied.
(won't work without it
At Thu, 23 Jan 2003 12:15:26 +0100,
Tais M. Hansen <[EMAIL PROTECTED]> wrote:
>
> On Thursday 23 January 2003 11:03, Takashi Iwai wrote:
> > ok, the attached is the third trial.
> > please appply it solely without the preivous patches.
>
> I'm assuming the very first via8233a-fix.dif is still sup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 23 January 2003 12:46, Takashi Iwai wrote:
> > I'm assuming the very first via8233a-fix.dif is still supposed to be
> > applied. (won't work without it anyway)
> yes. the patch had been already applied to cvs.
Ok, I'll just do a cvs updat
(moved to alsa-devel up to now...)
At Thu, 23 Jan 2003 11:33:50 +0100,
I wrote:
>
> At Thu, 23 Jan 2003 11:26:02 +0100 (MET),
> Clemens Ladisch wrote:
> >
> > The default output device used by aplay is "hw:0", which doesn't
> > automatically convert sample rates. Try "aplay -D plughw:0 something
At Thu, 23 Jan 2003 13:36:53 +0100,
Tais M. Hansen <[EMAIL PROTECTED]> wrote:
>
> > > Well... Ogg123 freezes the same way as with test1. Artsd no longer fails
> > > with "cpu overload", but it's constantly busy and can't play sound.
> > > ...
> > hmm, it'd better to start from the beginning.
> > p
At Wed, 22 Jan 2003 12:38:31 -0500,
Paul Davis wrote:
>
> if you try to play a 22.05kHz stream on hardware that supports 32kHz
> and 44.1kHz but not 22.05kHz, alsa-lib's plughw layer chooses to use
> 32kHz and resamples. this seems like an error to me: it would be much
> better to choose 44.1kHz a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 23 January 2003 16:08, Takashi Iwai wrote:
> > Okay, fresh cvs checkout. Enabled POINTER_DEBUG and applied the
> > via-pointer-debug.dif.
> > Ogg123 freezes/stalls without ever making a sound, like with the previous
> > test and test3 patch
This finally adds support for capturing.
Contrary to what I've written earlier, the mixer controls (capture
selection etc.) *are* supported, because they're on the device's front
panel, not in software. :-)
--- alsa-kernel/usb/usbquirks.h.orig2003-01-23 18:22:44.78570 +0100
+++ alsa-ker
At Thu, 23 Jan 2003 18:50:38 +0100,
Tais M. Hansen <[EMAIL PROTECTED]> wrote:
>
> On Thursday 23 January 2003 16:08, Takashi Iwai wrote:
> > > Okay, fresh cvs checkout. Enabled POINTER_DEBUG and applied the
> > > via-pointer-debug.dif.
> > > Ogg123 freezes/stalls without ever making a sound, like
Hi Mark and Jack,
regarding to the alsaplayer problem:
could you try the attached patch (to cvs version) ?
hope this fixes the nasty bug...
ciao,
Takashi
pcm-unlink-fix.dif
Description: Binary data
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 23 January 2003 19:07, Takashi Iwai wrote:
> > > thanks.
> > > it seems really the index value was not updated correctly by the
> > > chip.
> > > ok, take 4: please try the new one...
> > Same as before, log output attached. :)
> the next
Paul, Takashi-san and Clemens,
Hi. A couple of days ago Fernando got a new RPM built for Alsa which
includes the recent HDSP 9652 MIDI timing fix that you worked together
on and supplied about 10 days ago. I wanted to report back that the
timing is now much improved. I haven't used it a lot yet,
14 matches
Mail list logo