[Alsa-devel] [Patch]snd-usb-us428.patch.0.2
Hi Takashi,
This is a Bugfix (sporadic hangups solved), cosmetical treatment and
feature-enhancement (Setting of PCM-Out Volume according to
Mastervolume-Slider at device start).
Please commit.
tnx,
Karsten
Index: alsa-driver/usb/us428/usX2Yhwdep.c
===
RCS file: /cvsroot/alsa/alsa-driver/usb/us428/usX2Yhwdep.c,v
retrieving revision 1.2
diff -u -r1.2 usX2Yhwdep.c
--- alsa-driver/usb/us428/usX2Yhwdep.c 24 Sep 2003 16:45:10 - 1.2
+++ alsa-driver/usb/us428/usX2Yhwdep.c 23 Oct 2003 17:01:39 -
@@ -93,7 +93,7 @@
return -EBUSY;
/* if userspace tries to mmap beyond end of our buffer, fail */
-if (size ((PAGE_SIZE - 1 + sizeof(us428ctls_sharedmem_t)) / PAGE_SIZE) * PAGE_SIZE){
+if (size ((PAGE_SIZE - 1 + sizeof(us428ctls_sharedmem_t)) / PAGE_SIZE) * PAGE_SIZE) {
snd_printd( %i %i\n, size,sizeof(us428ctls_sharedmem_t));
return -EINVAL;
}
@@ -103,6 +103,7 @@
if(!(us428-us428ctls_sharedmem = snd_malloc_pages(sizeof(us428ctls_sharedmem_t), GFP_KERNEL)))
return -ENOMEM;
memset(us428-us428ctls_sharedmem, -1, sizeof(us428ctls_sharedmem_t));
+ us428-us428ctls_sharedmem-CtlSnapShotLast = -2;
}
area-vm_ops = us428ctls_vm_ops;
#ifdef VM_RESERVED
@@ -174,11 +175,11 @@
i;
us428-Seq04 = 0;
- if (NULL == (us428-AS04.buffer = kmalloc(URB_DataLen_AsyncSeq*URBS_AsyncSeq, GFP_KERNEL))){
+ if (NULL == (us428-AS04.buffer = kmalloc(URB_DataLen_AsyncSeq*URBS_AsyncSeq, GFP_KERNEL))) {
err = -ENOMEM;
}else
- for (i = 0; i URBS_AsyncSeq; ++i){
- if (NULL == (us428-AS04.urb[i] = usb_alloc_urb(0, GFP_KERNEL))){
+ for (i = 0; i URBS_AsyncSeq; ++i) {
+ if (NULL == (us428-AS04.urb[i] = usb_alloc_urb(0, GFP_KERNEL))) {
err = -ENOMEM;
break;
}
@@ -219,7 +220,7 @@
int err;
do {
- if ((err = snd_us428_create_usbmidi(card)) 0){
+ if ((err = snd_us428_create_usbmidi(card)) 0) {
snd_printk(snd_us428_create_alsa_devices: snd_us428_create_usbmidi error %i \n, err);
break;
}
@@ -238,7 +239,7 @@
if (! (us428-In04urb = usb_alloc_urb(0, GFP_KERNEL)))
return -ENOMEM;
- if (! (us428-In04Buf = kmalloc(21, GFP_KERNEL))){
+ if (! (us428-In04Buf = kmalloc(21, GFP_KERNEL))) {
usb_free_urb(us428-In04urb);
return -ENOMEM;
}
@@ -276,15 +277,15 @@
}
if (!err1 == dsp-index)
do {
- if ((err = snd_us428_AsyncSeq04_init((us428dev_t*)hw-private_data))){
+ if ((err = snd_us428_AsyncSeq04_init((us428dev_t*)hw-private_data))) {
snd_printk(snd_us428_AsyncSeq04_init error \n);
break;
}
- if ((err = snd_us428_In04_init((us428dev_t*)hw-private_data))){
+ if ((err = snd_us428_In04_init((us428dev_t*)hw-private_data))) {
snd_printk(snd_us428_In04_init error \n);
break;
}
- if ((err = snd_us428_create_alsa_devices(hw-card))){
+ if ((err = snd_us428_create_alsa_devices(hw-card))) {
snd_printk(snd_us428_create_alsa_devices error %i \n, err);
snd_card_free(hw-card);
break;
Index: alsa-driver/usb/us428/usbus428.c
===
RCS file: /cvsroot/alsa/alsa-driver/usb/us428/usbus428.c,v
retrieving revision 1.5
diff -u -r1.5 usbus428.c
--- alsa-driver/usb/us428/usbus428.c 6 Oct 2003 13:15:17 - 1.5
+++ alsa-driver/usb/us428/usbus428.c 23 Oct 2003 17:01:39 -
@@ -75,7 +75,7 @@
MODULE_AUTHOR(Karsten Wiese [EMAIL PROTECTED]);
-MODULE_DESCRIPTION(TASCAM NAME_ALLCAPS Version 0.1);
+MODULE_DESCRIPTION(TASCAM NAME_ALLCAPS Version 0.2);
MODULE_LICENSE(GPL);
MODULE_CLASSES({sound});
MODULE_DEVICES({{TASCAM(0x1604), NAME_ALLCAPS(0x8001) }});
@@ -131,22 +131,29 @@
us428-In04IntCalls++;
- if (urb-status){
+ if (urb-status) {
snd_printk( Interrupt Pipe 4 came back with status=%i\n, urb-status);
return;
}
-{
- int diff = -1, i;
// printk(%i:0x%02X , 8, (int)((unsigned char*)us428-In04Buf)[8]); Master volume shows 0 here if fader is at max during boot ?!?
- for (i = 0; i 21; i++) {
- if (us428-In04Last[i] != ((char*)us428-In04Buf)[i]) {
-if (diff 0)
- diff = i;
-us428-In04Last[i] = ((char*)us428-In04Buf)[i];
+ if (us428ctls) {
+ int diff = -1;
+ if (-2 == us428ctls-CtlSnapShotLast) {
+ diff = 0;
+ memcpy(us428-In04Last, us428-In04Buf, sizeof(us428-In04Last));
+ us428ctls-CtlSnapShotLast = -1;
+ } else {
+ int i;
+ for (i = 0; i 21; i++) {
+if (us428-In04Last[i] != ((char*)us428-In04Buf)[i]) {
+ if (diff 0)
+ diff = i;
+ us428-In04Last[i] = ((char*)us428-In04Buf)[i];
+}
}
}
- if (diff = 0us428ctls) {
+ if (0 = diff) {
int n = us428ctls-CtlSnapShotLast + 1;
if (n = N_us428_ctl_BUFS || n 0)
n = 0;
@@ -186,7 +193,7 @@
}
}
- if (err){
+ if (err) {
snd_printk(In04Int() usb_submit_urb err=%i\n, err);
}
}
Index: alsa-driver/usb/us428/usbus428audio.c
===
RCS file:
Re: [Alsa-devel] Oops on resume, X crashes
At Thu, 23 Oct 2003 17:12:08 +0800, Gou Zhuang wrote: I turned on OSS_DEBUG in pcm_oss.c. I did not start X this time, I only started artsd from console to reproduce the oops. Below is the messages after resume, my comments are marked with - - MYDEBUG intel8x0.c:2141: Entering intel8x0_suspend() MYDEBUG intel8x0.c:2149: Call snd_pcm_suspend_all() on Intel 82801CA-ICH3 MYDEBUG intel8x0.c:2149: Call snd_pcm_suspend_all() on Intel 82801CA-ICH3 - MIC ADC MYDEBUG intel8x0.c:2152: Call snd_power_change_state(card, SNDRV_CTL_POWER_D3hot) MYDEBUG intel8x0.c:2154: Return from snd_power_change_state() pcm_oss: ioctl = 0x8010500c pcm_oss: space: bytes = 7168, fragments = 7, fragstotal = 7, fragsize = 1024 pcm_oss: write: recovering from SUSPEND ALSA pcm_oss.c:552: snd_pcm_oss_prepare: SNDRV_PCM_IOCTL_PREPARE failed pcm_oss: write 1024 bytes (wrote -11 bytes) --- IT SEEMS THE WRITE FAILED! that's ok, because it's opened with non-block mode. MYDEBUG intel8x0.c:2162: Entering intel8x0_resume() MYDEBUG intel8x0.c:2167: Call pci_enable_device(chip-pci) PCI: Found IRQ 11 for device 00:1f.5 PCI: Sharing IRQ 11 with 00:1f.6 MYDEBUG intel8x0.c:2169: Call pci_set_master(chip-pci) PCI: Setting latency timer of device 00:1f.5 to 64 MYDEBUG intel8x0.c:2067: Entering snd_intel8x0_chip_init() MYDEBUG ../../alsa-kernel/pci/ac97/ac97_codec.c:2148: Entering snd_ac97_resume() MYDEBUG ../../alsa-kernel/pci/ac97/ac97_codec.c:2148: Entering snd_ac97_resume() MYDEBUG intel8x0.c:2177: Call snd_power_change_state(card, SNDRV_CTL_POWER_D0) ok, i think i found a bug. please try the attached patch. Takashi pm-oops-fix.dif Description: Binary data
Re: [Alsa-devel] bug in ens1371/ens1370 joystick driver
At Thu, 23 Oct 2003 16:23:26 -0300,
Juan Linietsky wrote:
On Thursday 23 October 2003 04:14, you wrote:
Juan Linietsky wrote:
The ens1371 driver takes a joystick_port parameter with range 1..8
but that same parameter is them put into a switch to detect io port
values like 0x200, 0x208, etc. so the joystick will never be detected.
ens1370.c says:
MODULE_PARM(joystick_port, 1- __MODULE_STRING(SNDRV_CARDS) i);
MODULE_PARM_DESC(joystick_port, Joystick port address.);
MODULE_PARM_SYNTAX(joystick_port, SNDRV_ENABLED
,allows:{{0},{0x200},{0x208},{0x210},{0x218}},dialog:list);
The range 1..8 means that it's possible to specify a parameter value
for each of the up to 8 cards (SNDRV_CARDS is defined as 8). The
parameter itself takes the correct values.
Regards,
Clemens
this is still not very helpful, as modinfo -p only returns:
joystick_port int array (min = 1, max = 8), description Joystick port
address.
how are you supposed to know that you can only enter 0x200,0x208,etc?
RTFM :)
alsa-kernel/Documentation/Joystick.txt.
Specially when in the OSS driver you do:
modprobe es1371 joystick=1
and it works flawlessly
ok, i'll add more code...
Takashi
---
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] [PATCH]us428control.patch.0.3
Hi Takashi,
This has more features:
- PCM-Volume adjusted to MasteVolumeSlider setting at device start.
- Direct Monitoring Functions adjustable directly on the US428
- Alsa Sequencer Output port for applications to receive the US428 sliders
etc.
please add the missing files attached + commit the patch.
Danke,
Karsten
Index: alsa-tools/us428control/Cus428State.cc
===
RCS file: /cvsroot/alsa/alsa-tools/us428control/Cus428State.cc,v
retrieving revision 1.1
diff -u -r1.1 Cus428State.cc
--- alsa-tools/us428control/Cus428State.cc 6 Oct 2003 15:57:24 - 1.1
+++ alsa-tools/us428control/Cus428State.cc 23 Oct 2003 17:01:45 -
@@ -20,12 +20,14 @@
#include stdio.h
#include string.h
-#include Cus428State.h
+#include alsa/asoundlib.h
+#include Cus428Midi.h
extern int verbose;
-void
-us428_lights::init_us428_lights()
+
+
+void us428_lights::init_us428_lights()
{
int i = 0;
memset(this, 0, sizeof(*this));
@@ -33,8 +35,14 @@
Light[ i].Offset = i + 0x19;
}
-int
-Cus428State::LightSend()
+
+void Cus428State::InitDevice(void)
+{
+ SliderChangedTo(eFaderM, ((unsigned char*)(us428ctls_sharedmem-CtlSnapShot + us428ctls_sharedmem-CtlSnapShotLast))[eFaderM]);
+}
+
+
+int Cus428State::LightSend()
{
int Next = us428ctls_sharedmem-p4outLast + 1;
if(Next 0 || Next = N_us428_p4out_BUFS)
@@ -44,14 +52,8 @@
return us428ctls_sharedmem-p4outLast = Next;
}
-void
-Cus428State::SliderChangedTo(int S, unsigned char New)
+void Cus428State::SendVolume(usX2Y_volume V)
{
- if ((S = eFader4 || S 0) S != eFaderM)
- return;
-
- usX2Y_volume V;
- V.SetTo(S, New);
int Next = us428ctls_sharedmem-p4outLast + 1;
if (Next 0 || Next = N_us428_p4out_BUFS)
Next = 0;
@@ -60,24 +62,107 @@
us428ctls_sharedmem-p4outLast = Next;
}
+void Cus428State::SliderChangedTo(int S, unsigned char New)
+{
+ if (StateInputMonitor() S = eFader3
+ || S == eFaderM) {
+ usX2Y_volume V = Volume[S = eFader4 ? eFader4 : S];
+ V.SetTo(S, New);
+ if (S == eFaderM || !LightIs(eL_Mute0 + S))
+ SendVolume(V);
+ } else
+ Midi.SendMidiControl(0x40 + S, ((unsigned char*)us428_ctls)[S] / 2);
+
+}
-void
-Cus428State::KnobChangedTo(eKnobs K, bool V)
+
+void Cus428State::KnobChangedTo(eKnobs K, bool V)
{
- switch (K) {
- case eK_InputMonitor:
- if (verbose 1)
- printf(Knob InputMonitor now %i, V);
+ switch (K ~(StateInputMonitor() ? 3 : -1)) {
+ case eK_Select0:
if (V) {
- LightSet(eL_InputMonitor, ! LightIs(eL_InputMonitor));
+ int S = eL_Select0 + (K 7);
+ Light[eL_Select0 / 8].Value = 0;
+ LightSet(S, !LightIs(S));
LightSend();
}
- if (verbose 1)
- printf( Light is %i\n, LightIs(eL_InputMonitor));
+ break;
+ case eK_Mute0:
+ if (V) {
+ int M = eL_Mute0 + (K 7);
+ LightSet(M, !LightIs(M));
+ LightSend();
+ if (StateInputMonitor()) {
+usX2Y_volume V = Volume[M - eL_Mute0];
+if (LightIs(M))
+ V.LH = V.LL = V.RL = V.RH = 0;
+SendVolume(V);
+ }
+ }
break;
default:
- if (verbose 1)
- printf(Knob %i now %i\n, K, V);
+ switch (K) {
+ case eK_InputMonitor:
+ if (verbose 1)
+printf(Knob InputMonitor now %i, V);
+ if (V) {
+if (StateInputMonitor()) {
+ SelectInputMonitor = Light[0].Value;
+ MuteInputMonitor = Light[2].Value;
+} else {
+ Select = Light[0].Value;
+ Mute = Light[2].Value;
+}
+LightSet(eL_InputMonitor, ! StateInputMonitor());
+Light[0].Value = StateInputMonitor() ? SelectInputMonitor : Select;
+Light[2].Value = StateInputMonitor() ? MuteInputMonitor : Mute;
+LightSend();
+ }
+ if (verbose 1)
+printf( Light is %i\n, LightIs(eL_InputMonitor));
+ break;
+ default:
+ if (verbose 1)
+printf(Knob %i now %i\n, K, V);
+ Midi.SendMidiControl(K, V);
+ }
}
}
+
+void Cus428State::WheelChangedTo(E_In84 W, char Diff)
+{
+ char Param;
+ switch (W) {
+ case eWheelPan:
+ if (StateInputMonitor() Light[0].Value) {
+ int index = 0;
+
+ while( index 4 (1 index) != Light[0].Value)
+index++;
+
+ if (index = 4)
+return;
+
+ Volume[index].PanTo(Diff, us428_ctls-Knob(eK_SET));
+ if (!LightIs(eL_Mute0 + index))
+SendVolume(Volume[index]);
+ return;
+ }
+ Param = 0x4D;
+ break;
+ case eWheelGain:
+ Param = 0x48;
+ break;
+ case eWheelFreq:
+ Param = 0x49;
+ break;
+ case eWheelQ:
+ Param = 0x4A;
+ break;
+ case eWheel:
+ Param = 0x60;
+ break;
+ }
+ Midi.SendMidiControl(Param, ((unsigned char*)us428_ctls)[W]);
+}
Index: alsa-tools/us428control/Cus428State.h
===
RCS file: /cvsroot/alsa/alsa-tools/us428control/Cus428State.h,v
retrieving revision 1.1
diff -u -r1.1 Cus428State.h
--- alsa-tools/us428control/Cus428State.h 6 Oct 2003 15:57:24 - 1.1
+++ alsa-tools/us428control/Cus428State.h 23 Oct 2003 17:01:45 -
@@ -23,24 +23,79 @@
#include Cus428_ctls.h
-class Cus428State: public us428_lights, public Cus428_ctls{
Re: [Alsa-devel] Oops on resume, X crashes
Takashi Iwai wrote: At Thu, 23 Oct 2003 17:12:08 +0800, Gou Zhuang wrote: I turned on OSS_DEBUG in pcm_oss.c. I did not start X this time, I only started artsd from console to reproduce the oops. Below is the messages after resume, my comments are marked with - - MYDEBUG intel8x0.c:2141: Entering intel8x0_suspend() MYDEBUG intel8x0.c:2149: Call snd_pcm_suspend_all() on Intel 82801CA-ICH3 MYDEBUG intel8x0.c:2149: Call snd_pcm_suspend_all() on Intel 82801CA-ICH3 - MIC ADC MYDEBUG intel8x0.c:2152: Call snd_power_change_state(card, SNDRV_CTL_POWER_D3hot) MYDEBUG intel8x0.c:2154: Return from snd_power_change_state() pcm_oss: ioctl = 0x8010500c pcm_oss: space: bytes = 7168, fragments = 7, fragstotal = 7, fragsize = 1024 pcm_oss: write: recovering from SUSPEND ALSA pcm_oss.c:552: snd_pcm_oss_prepare: SNDRV_PCM_IOCTL_PREPARE failed pcm_oss: write 1024 bytes (wrote -11 bytes) --- IT SEEMS THE WRITE FAILED! that's ok, because it's opened with non-block mode. MYDEBUG intel8x0.c:2162: Entering intel8x0_resume() MYDEBUG intel8x0.c:2167: Call pci_enable_device(chip-pci) PCI: Found IRQ 11 for device 00:1f.5 PCI: Sharing IRQ 11 with 00:1f.6 MYDEBUG intel8x0.c:2169: Call pci_set_master(chip-pci) PCI: Setting latency timer of device 00:1f.5 to 64 MYDEBUG intel8x0.c:2067: Entering snd_intel8x0_chip_init() MYDEBUG ../../alsa-kernel/pci/ac97/ac97_codec.c:2148: Entering snd_ac97_resume() MYDEBUG ../../alsa-kernel/pci/ac97/ac97_codec.c:2148: Entering snd_ac97_resume() MYDEBUG intel8x0.c:2177: Call snd_power_change_state(card, SNDRV_CTL_POWER_D0) ok, i think i found a bug. please try the attached patch. Takashi I applied the patch, the oops went away :) But I still get a lot of ALSA pcm_oss.c:552: snd_pcm_oss_prepare: SNDRV_PCM_IOCTL_PREPARE failed. And the artsd crashed after resume with the following errmsg: Sound Server fatal error: AudioSubSystem::handleIO: write failed len = 16, can_write = 24, errno = 4 (interrupted system call) Do you have any clue on this? gouzhuang --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] OSS emulation delays (?)
I've had similar problems with mplayer and my Terratec DMX 6fire (also ice1712) MPlayer isn't quite so slow, but there is a decent pause while seeking in movies. I've had this problem with mplayer and oss emulation since alsa 0.9.3 i think (not quite sure). In older versions it worked fine, but in newer versions and the current cvs it takes about a second for mplayer to skip anywhere. I didn't have this problem with any other app than mplayer though. With the xmms ALSA driver, this is not a problem. Unfortunately mplayer and ALSA don't seem to get along with my card (ice1712... maudio delta-44), but with audio disabled seek times are fine. Same problem here again, mplayer's alsa-output has been broken for me since I have that card (1.5 years). Audio seems to be running fine, but video plays at about one fps, and after few seconds the buggy-audio-driver message pops up. Because mplayer is the only app having problem with the alsa-driver, I always thought it was mplayer's bug, but I didn't dare to post on their mailinglists :o). I ended up using arts, because it works perfectly with the ice1712 drivers and both xmms and mplayer. gruss Steffen --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] Re: [PATCH]us428control.patch.0.3
At Thu, 23 Oct 2003 19:30:35 +0200, Karsten Wiese wrote: [1 text/plain; us-ascii (7bit)] Hi Takashi, This has more features: - PCM-Volume adjusted to MasteVolumeSlider setting at device start. - Direct Monitoring Functions adjustable directly on the US428 - Alsa Sequencer Output port for applications to receive the US428 sliders etc. please add the missing files attached + commit the patch. thanks! applied both patches. Takashi --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] bug in ens1371/ens1370 joystick driver
At Fri, 24 Oct 2003 12:53:36 +0200, I wrote: Specially when in the OSS driver you do: modprobe es1371 joystick=1 and it works flawlessly ok, i'll add more code... committed to cvs now. the new version accepts like modprobe snd-ens1371 joystick_port=1 for auto-detection of the joystick port. Takashi --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] patch, and other via82xx (VT8235) capture problems
At Wed, 22 Oct 2003 23:48:43 -0500, Zinx Verituse wrote: [1 text/plain; us-ascii (7bit)] I've attached a patch to fix a bug in the via82xx driver, but I suspect the register is wrong for the VT8235 because when I set the Input Source to 'Mic', no interrupts seem to be getting triggered: arecord: pcm_read:1110: read error: Input/output error But as 'Line', it works (albeit with significantly reduced voltage and volume) thanks for the patch. now applied to cvs. Are the specs for the VT8235 available anywhere? not in public i know of... Takashi --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] patch, and other via82xx (VT8235) capture problems
At Thu, 23 Oct 2003 20:05:02 -0500, Zinx Verituse wrote: On Thu, Oct 23, 2003 at 06:47:35PM +0200, Takashi Iwai wrote: thanks for the patch. now applied to cvs. Are the specs for the VT8235 available anywhere? not in public i know of... Ah, too bad. Takashi Any ideas on the problem with me not being able to record if the Input Source is set to Mic? arecord records when it's set to Line (as it was forced, before), and does playback as well.. When it's set to Mic, I get no playback from a Mic (and I'm not wanting to hook up powered output in to the jack when it's set to Mic), but I suspect it's still Line-in, and the register being twiddled isn't right, or needs some more setup. arecord waits a bit, then gives the error I mentioned: arecord: pcm_read:1110: read error: Input/output error dmesg says nothing :/ If nothing else, the settings do have to do with the actual capture sources (idx 0 vs. idx 1), because when I set idx 0 to mic, it can't record, but idx 1 can, and when I set idx 1 to mic, it can't record, but idx 0 can. When both are set to mic, neither can record. sorry, could you elaborate this? i'm confused. did you try hw:0,0 and hw:0,1, right? Takashi --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] patch, and other via82xx (VT8235) capture problems
On Fri, Oct 24, 2003 at 03:14:44PM +0200, Takashi Iwai wrote: At Thu, 23 Oct 2003 20:05:02 -0500, Zinx Verituse wrote: Any ideas on the problem with me not being able to record if the Input Source is set to Mic? arecord records when it's set to Line (as it was forced, before), and does playback as well.. When it's set to Mic, I get no playback from a Mic (and I'm not wanting to hook up powered output in to the jack when it's set to Mic), but I suspect it's still Line-in, and the register being twiddled isn't right, or needs some more setup. arecord waits a bit, then gives the error I mentioned: arecord: pcm_read:1110: read error: Input/output error dmesg says nothing :/ If nothing else, the settings do have to do with the actual capture sources (idx 0 vs. idx 1), because when I set idx 0 to mic, it can't record, but idx 1 can, and when I set idx 1 to mic, it can't record, but idx 0 can. When both are set to mic, neither can record. sorry, could you elaborate this? i'm confused. did you try hw:0,0 and hw:0,1, right? Yeah, hw:0,0 fails when Input Source idx 0 is set to Mic, and hw:0,1 fails when Input Source idx 1 is set to Mic. Takashi -- Zinx Verituse --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] Relative positioning.
Hi! I make a Layer and I put into a sublayer with relative positioning, the layers added to absolute 0,0 coordinate. Cow --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] Please remove us from your list
Please remove [EMAIL PROTECTED] from the alsa-devel mailing list Thank you Jerry and Deborah Stevens --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] question about libalsaplayer's functionality (and its possible incorporation in my app)
Hi all, I've tried contacting the maintainer of the project (Andy), but he never bothered to reply, so now I am taking this question to all of you out there that might have had exposure to this interesting library. Does anyone know what is the current status of the whole project anyhow? Any help on this matter is greatly appreciated! When answering any of the given questions, please include the question in your reply. Thank you very much! So here's the excerpt from the letter: I've recently decided to incorporate libalsaplayer-like functionality the upcoming version of my app RTMix. However, with having a particular feature in mind I am wondering whether libalsaplayer provides that and if not, whether you'd be willing to add it (or let me add it, although that might get messy since I am not too familiar with the inner workings of the lib). So, here it goes: Apart from all the wonderful features libalsaplayer offers, I am looking for some additional ones: I would like to be able to indefinitely loop specific ranges of a particular soundfile (i.e. 2.2secs-4.12secs or whatever). 1. Is it possible to do this and have music continually loop even if one changes the direction of playing so that when the alsaplayer runs out of the looping material in each direction that it just jumps back onto the other end of the loop and contiues on (kind of like a ring-buffer)? 2. Is it also possible to do this kind of looping on the whole soundfile (the gui version of alsaplayer always stops if I let it play 'til the end or the beginning, depending in which direction I am going). 3. Is it possible to define loop points by addressing a particular sample number rather than giving time in seconds? 4. How stable is alsaplayer when looping really small chunks of sound (i.e. like 5 sample loop)? 5. Is alsaplayer capable of ramping such loop points by attenuating let's say ending 20 samples (it would be cool if this number could be user-selectable) and then ramping up the beginning 20 samples in order to alleviate the pop that happens when looping a sound where waveforms at the beginning and the end do not align? 6. If the feature in question 5 does not exist is there a way to control output level of a player on a per-sample basis via callback so that one can implement that outside of the lib? 7. If neither 5 or 6 are possible, would you be willing to implement such functionality (i.e. a toggle_ramp( bool ); and set_ramp_length( int ); callbacks or something similar. I would greatly appreciate your feedback on this matter as that will greatly assist me in determining how to go about implementing such functionality in my app. Thank you very much! Looking forward to hearing from you. Sincerely, Ivica Ico Bukvic, composer multimedia sculptor http://meowing.ccm.uc.edu/~ico P.S. How do you implement reading of a sound faster and slower than it sounds in such a gradual fashion? Do you adjust the sampling rate of the DSP and if so does that affect other streams coming from the libalsaplayer, or is this something that is sound-specific (and if so, how)? --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
