Hi Takashi,
Please commit this to reenable usx2yloader hotplugging:
Index: alsa-tools/usx2yloader/tascam_fw
===
RCS file: /cvsroot/alsa/alsa-tools/usx2yloader/tascam_fw,v
retrieving revision 1.1
diff -u -r1.1 tascam_fw
---
At Tue, 2 Dec 2003 09:31:32 +0100,
Karsten Wiese wrote:
Hi Takashi,
Please commit this to reenable usx2yloader hotplugging:
Index: alsa-tools/usx2yloader/tascam_fw
===
RCS file:
I found that if I forced the aRtsd use 48000 sample rate then there is no the static
problem, I guess there is a problem in SW sample rate converter.
Sincerely,
ChenLi Tien
-Original Message-
From: C.L. Tien -
Sent: 2003/12/2 [] 03:51
To: Takashi Iwai; [EMAIL PROTECTED]
Cc:
Takashi Iwai wrote:
Karsten Wiese wrote:
Later there should also be some magic to (not) include the /local substring,
I don't know yet how to do that; anybody?
fixed on cvs.
tascam_fw and tascam_fpga will be generated via configure script now.
Such scripts should not be generated by
Jonathan Woithe wrote:
Under Jazz++, any hold on controller event which occurs within the first
bar played gets turned off too quickly (assuming playback starts at beat one
of a bar). In fact, even if there are no subsequent hold off events
within the entire midi file the hold on is still
At Tue, 2 Dec 2003 17:36:41 +0800,
C.L. Tien - [EMAIL PROTECTED] wrote:
I found that if I forced the aRtsd use 48000 sample rate then there
is no the static problem, I guess there is a problem in SW sample rate
converter.
ok, at least, a step forward :)
could you tell me whether it runs on
On Tue, Dec 02, 2003 at 11:47:16AM +0100, Takashi Iwai wrote:
At Tue, 2 Dec 2003 17:36:41 +0800,
C.L. Tien - ? [EMAIL PROTECTED] wrote:
I found that if I forced the aRtsd use 48000 sample rate then there
is no the static problem, I guess there is a problem in SW sample rate
The artmessage display open in OSS mode.
The codec I use is cmedia's cmi9739, it doesn't support variable rate (VRA).
Sincerely,
ChenLi Tien
-Original Message-
From: Takashi Iwai [mailto:[EMAIL PROTECTED]
Sent: 2003/12/2 [] 06:47
To: C.L. Tien -
Cc: [EMAIL PROTECTED]
Am Dienstag, 2. Dezember 2003 11:05 schrieb Takashi Iwai:
At Tue, 2 Dec 2003 09:31:32 +0100,
fixed on cvs.
tascam_fw and tascam_fpga will be generated via configure script now.
the diff is attached below. please give a try.
Tried succesfully!
Thanks,
Karsten
hello,
i don't have the up to date patch for acpi and had the same problem even
without the low latency patch. i'm going to hold out upgrading until 2.6...
right now, i'm having too much fun with the hdsp ;) - for two months it sat
idle... dust (yes dust!) collected on it!
big thanks for all
Takashi Iwai wrote :
At Mon, 01 Dec 2003 19:30:07 +0100,
I wrote:
At Mon, 01 Dec 2003 19:15:59 +0100,
Thomas Charbonnel wrote:
Hi,
I'm testing rc1, and I have problems with my laptop's internal intel8x0
soundcard :
* Using OSS emulation, after between 19 and 20 seconds of playing the
sound gets
Takashi Iwai wrote :
ok, then please check /proc/asound/card0/codec97#0/* files whether VRA
is properly set to 44100Hz during the playback.
Takashi
Bingo, it seems it's not, indeed :
[EMAIL PROTECTED] thomas $ cat /proc/asound/card0/codec97#0/*
0-0/0: Cirrus Logic CS4299 rev 4
Capabilities
At Tue, 02 Dec 2003 14:57:29 +0100,
Thomas Charbonnel wrote:
Takashi Iwai wrote :
ok, then please check /proc/asound/card0/codec97#0/* files whether VRA
is properly set to 44100Hz during the playback.
Takashi
Bingo, it seems it's not, indeed :
please try the attached
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking
At Tue, 2 Dec 2003 17:04:03 +0100,
Martin Holzer wrote:
(snip)
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /bin/install -c
checking whether
Hi Takashi,
Two Segmentation fault spots cleared.
Please commit. Thanks,
Karsten
Index: alsa-tools/us428control/Cus428State.cc
===
RCS file: /cvsroot/alsa/alsa-tools/us428control/Cus428State.cc,v
retrieving revision 1.2
diff -u
Hi,
I want to report that I've built alsa-1.0.0rc1 under Gentoo with q
2.4.20-r7 kernel. Thanks to Thomas Charbonnel for the help with the
ebuilds. If any other Gentoo users need the ebuilds, then contact me off
list.
Unfortunately this release does not impact my loud glitch/pop noise
on
We went ahead and added code to our alsa client software to cleanly
return to a PCM value of 0 and then stuffed a full buffer worth of 0s
into the buffer before closeing the PCM in order to solve our pop
problem. I'm not sure how the OSS emulation stuff works since we don't
use it, but maybe
On Dec 2, Martin Holzer wrote:
Subject: [Alsa-devel] alsa-tools-1.0.0_rc1 has broken gcc 2.9x support
I compiled it yesterday and with gcc-2.95.3 I had no problem...
tom.
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does
Takashi Iwai wrote :
please try the attached patch.
possibly this isn't a fix, but it will print debug messages while
probing and opening the pcm.
Takashi
Takashi, I applied your patch but nothings shows up in my logs.
I even replaced all the KERN_DEBUG by KERN_EMERG, and still nothing.
The only
make[1]: Entering directory
`/var/tmp/portage/alsa-tools-1.0.0_rc1/work/alsa-tools-1.0.0rc1/hdspmixer/sr
c'
if g++ -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\
-DPACKAGE_VERSION=\\ -DPACKAGE_STRING=\\
-DPACKAGE_BUGREPORT=\\
-DPACKAGE=\hdspmixer\ -DVERSION=\1.6\ -DSTDC_HEADERS=1
-DHAVE_LIBASOUND=1
Takashi,
I've completed my changes on the serial-u16550 driver. I have
implemented most of your suggestions to my previous patch. Now:
* There is a user selectable flag droponfull. Set to 1 and
any new bytes delivered to the driver after the buffer fills
up will be discarded until the
Hi,
The alsa keeps state of all mixer levels in alsa's internal format
which has min,max info. So, for example if alsa has 0-31 levels,
converting that to the OSS 0-100 range is easy with a simple
calculation, but if an OSS app just does Volume++, the change will be
lost in the conversion
On Tue, 2003-12-02 at 10:16, Steve deRosier wrote:
We went ahead and added code to our alsa client software to cleanly
return to a PCM value of 0 and then stuffed a full buffer worth of 0s
into the buffer before closeing the PCM in order to solve our pop
problem. I'm not sure how the OSS
24 matches
Mail list logo
