usb quattro

usb quattro

[Patrick Shirkey]

I have just found that the quattro will not output an audible stream 
from the external input channels until it has been made to output a 
stream through the internal i/o first.

This means that the direct monitor switch does not work until a file is 
played internally through the card.

After that everything works as expected.

Is this a fixable bug or should I make a note in the online docs about it?


-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: usb quattro

[Takashi Iwai]

At Wed, 04 Sep 2002 23:32:25 +0900,
Patrick Shirkey wrote:
> 
> I have just found that the quattro will not output an audible stream 
> from the external input channels until it has been made to output a 
> stream through the internal i/o first.
> 
> This means that the direct monitor switch does not work until a file is 
> played internally through the card.
> 
> After that everything works as expected.
> 
> Is this a fixable bug or should I make a note in the online docs about it?

could you check whether only hw_params() (prepare()) sets up enough,
or do you really need to feed data to the output?

(although i'm not sure, too, what is missing there...)


Takashi


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: usb quattro

[Patrick Shirkey]

Takashi Iwai wrote:
> At Wed, 04 Sep 2002 23:32:25 +0900,
> Patrick Shirkey wrote:
> 
>>I have just found that the quattro will not output an audible stream 
>>from the external input channels until it has been made to output a 
>>stream through the internal i/o first.
>>
>>This means that the direct monitor switch does not work until a file is 
>>played internally through the card.
>>
>>After that everything works as expected.
>>
>>Is this a fixable bug or should I make a note in the online docs about it?
> 
> 
> could you check whether only hw_params() (prepare()) sets up enough,
> or do you really need to feed data to the output?
> 

I can, how should I go about doing so?

> (although i'm not sure, too, what is missing there...)
> 
> 
> Takashi
> 
> 



-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: usb quattro

[Takashi Iwai]

At Wed, 04 Sep 2002 23:51:25 +0900,
Patrick Shirkey wrote:
> 
> Takashi Iwai wrote:
> > At Wed, 04 Sep 2002 23:32:25 +0900,
> > Patrick Shirkey wrote:
> > 
> >>I have just found that the quattro will not output an audible stream 
> >>from the external input channels until it has been made to output a 
> >>stream through the internal i/o first.
> >>
> >>This means that the direct monitor switch does not work until a file is 
> >>played internally through the card.
> >>
> >>After that everything works as expected.
> >>
> >>Is this a fixable bug or should I make a note in the online docs about it?
> > 
> > 
> > could you check whether only hw_params() (prepare()) sets up enough,
> > or do you really need to feed data to the output?
> > 
> 
> I can, how should I go about doing so?

well, just write a few codes...

#include <alsa/asoundlib.h>

int main()
{
	snd_pcm_t *pcm;
	int err;
	snd_pcm_hw_params_t hw;

	err = snd_pcm_open(&pcm, "hw:0,0", SND_PCM_STREAM_PLAYBACK, 0);
	snd_pcm_hw_params_alloca(&hw);
	err = snd_pcm_hw_params_any(pcm, hw);
	err = snd_pcm_hw_params_set_access(pcm, hw, SND_PCM_ACCESS_RW_INTERLEAVED);
	err = snd_pcm_hw_params_set_format(pcm, hw, SND_PCM_FORMAT_S16_LE);
	err = snd_pcm_hw_params_set_rate(pcm, hw, 48000, 0);
	err = snd_pcm_hw_params_set_channels(pcm, hw, 2);
	err = snd_pcm_hw_params_set_period_size(pcm, hw, 512, 0);
	err = snd_pcm_hw_params_set_buffer_size(pcm, hw, 1024, 0);
	err = snd_pcm_hw_params(pcm, hw);
	return err;
}


(not tested at all ;)


Takashi


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: usb quattro

[Patrick Shirkey]

Takashi Iwai wrote:

I changed it to this (very small change).

> 
> well, just write a few codes...
> 
> #include <alsa/asoundlib.h>
> 
> int main()
> {
> 	snd_pcm_t *pcm;
> 	int err;
> 	snd_pcm_hw_params_t hw; <<<<----
> 
> 	err = snd_pcm_open(&pcm, "hw:2,1", SND_PCM_STREAM_PLAYBACK, 0);
> 	snd_pcm_hw_params_alloca(&hw);
> 	err = snd_pcm_hw_params_any(pcm, hw);
> 	err = snd_pcm_hw_params_set_access(pcm, hw, SND_PCM_ACCESS_RW_INTERLEAVED);
> 	err = snd_pcm_hw_params_set_format(pcm, hw, SND_PCM_FORMAT_S16_LE);
> 	err = snd_pcm_hw_params_set_rate(pcm, hw, 48000, 0);
> 	err = snd_pcm_hw_params_set_channels(pcm, hw, 2);
> 	err = snd_pcm_hw_params_set_period_size(pcm, hw, 512, 0);
> 	err = snd_pcm_hw_params_set_buffer_size(pcm, hw, 1024, 0); <<<<----
> 	err = snd_pcm_hw_params(pcm, hw);
> 	return err;
> }
> 
> 
> (not tested at all ;)
> 
> 
> Takashi
> 
> 

It doesn't quite compile.

----
#gcc -c -o qinit qinit.c
qinit.c: In function `main':
qinit.c:7: storage size of `hw' isn't known
qinit.c:17: too many arguments to function 
`snd_pcm_hw_params_set_buffer_size'
----

-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: usb quattro

[Takashi Iwai]

At Thu, 05 Sep 2002 00:26:37 +0900,
Patrick Shirkey wrote:
> 
> Takashi Iwai wrote:
> 
> I changed it to this (very small change).
> 
> > 
> > well, just write a few codes...
> > 
> > #include <alsa/asoundlib.h>
> > 
> > int main()
> > {
> > 	snd_pcm_t *pcm;
> > 	int err;
> > 	snd_pcm_hw_params_t hw; <<<<----

oops,

        snd_pcm_hw_params_t *hw;

and...

> > 
> > 	err = snd_pcm_open(&pcm, "hw:2,1", SND_PCM_STREAM_PLAYBACK, 0);
> > 	snd_pcm_hw_params_alloca(&hw);
> > 	err = snd_pcm_hw_params_any(pcm, hw);
> > 	err = snd_pcm_hw_params_set_access(pcm, hw, SND_PCM_ACCESS_RW_INTERLEAVED);
> > 	err = snd_pcm_hw_params_set_format(pcm, hw, SND_PCM_FORMAT_S16_LE);
> > 	err = snd_pcm_hw_params_set_rate(pcm, hw, 48000, 0);
> > 	err = snd_pcm_hw_params_set_channels(pcm, hw, 2);
> > 	err = snd_pcm_hw_params_set_period_size(pcm, hw, 512, 0);
> > 	err = snd_pcm_hw_params_set_buffer_size(pcm, hw, 1024, 0); <<<<----

 	err = snd_pcm_hw_params_set_buffer_size(pcm, hw, 1024);

> > 	err = snd_pcm_hw_params(pcm, hw);
> > 	return err;
> > }


Takashi


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: usb quattro

[Patrick Shirkey]

Sorry if this is stupid, I'm not a trained programmer. I get this now.

Do you know how to fix it?

# gcc qinit.c
/tmp/cco2X9S0.o: In function `main':
/tmp/cco2X9S0.o(.text+0x17): undefined reference to `snd_pcm_open'
/tmp/cco2X9S0.o(.text+0x22): undefined reference to 
`snd_pcm_hw_params_sizeof'
/tmp/cco2X9S0.o(.text+0x3d): undefined reference to 
`snd_pcm_hw_params_sizeof'
/tmp/cco2X9S0.o(.text+0x5c): undefined reference to `snd_pcm_hw_params_any'
/tmp/cco2X9S0.o(.text+0x72): undefined reference to 
`snd_pcm_hw_params_set_access'
/tmp/cco2X9S0.o(.text+0x88): undefined reference to 
`snd_pcm_hw_params_set_format'
/tmp/cco2X9S0.o(.text+0xa0): undefined reference to 
`snd_pcm_hw_params_set_rate'
/tmp/cco2X9S0.o(.text+0xb6): undefined reference to 
`snd_pcm_hw_params_set_channels'
/tmp/cco2X9S0.o(.text+0xce): undefined reference to 
`snd_pcm_hw_params_set_period_size'
/tmp/cco2X9S0.o(.text+0xe7): undefined reference to 
`snd_pcm_hw_params_set_buffer_size'
/tmp/cco2X9S0.o(.text+0xfb): undefined reference to `snd_pcm_hw_params'
collect2: ld returned 1 exit status


-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: usb quattro

[Takashi Iwai]

At Thu, 05 Sep 2002 01:35:39 +0900,
Patrick Shirkey wrote:
> 
> Sorry if this is stupid, I'm not a trained programmer. I get this now.
> 
> Do you know how to fix it?

	% gcc -l qinit qinit.c -lasound -ldl -lm


Takashi


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: usb quattro

[Tim Goetze]

Takashi Iwai wrote:

>At Thu, 05 Sep 2002 01:35:39 +0900,
>Patrick Shirkey wrote:
>> 
>> Sorry if this is stupid, I'm not a trained programmer. I get this now.
>> 
>> Do you know how to fix it?
>
>	% gcc -l qinit qinit.c -lasound -ldl -lm

rather

$ gcc -o qinit qinit.c -lasound -ldl -lm
       ^
i think.

tim



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: usb quattro

[Patrick Shirkey]

Tim Goetze wrote:
> Takashi Iwai wrote:
> 
> 
>>At Thu, 05 Sep 2002 01:35:39 +0900,
>>Patrick Shirkey wrote:
>>
>>>Sorry if this is stupid, I'm not a trained programmer. I get this now.
>>>
>>>Do you know how to fix it?
>>
>>	% gcc -l qinit qinit.c -lasound -ldl -lm
> 
> 
> rather
> 
> $ gcc -o qinit qinit.c -lasound -ldl -lm
>        ^
> i think.
>

That was it. Thanks.

Yes this code works. I don't know what that means though?

I have also found a serious kernel oops which is caused when starting 
jack with this card. It also fscked my user profile in mozilla so I have 
lost all my emails from teh past 6 months.




-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: usb quattro

[Takashi Iwai]

At Thu, 05 Sep 2002 23:02:14 +0900,
Patrick Shirkey wrote:
> 
> Tim Goetze wrote:
> > Takashi Iwai wrote:
> > 
> > 
> >>At Thu, 05 Sep 2002 01:35:39 +0900,
> >>Patrick Shirkey wrote:
> >>
> >>>Sorry if this is stupid, I'm not a trained programmer. I get this now.
> >>>
> >>>Do you know how to fix it?
> >>
> >>	% gcc -l qinit qinit.c -lasound -ldl -lm
> > 
> > 
> > rather
> > 
> > $ gcc -o qinit qinit.c -lasound -ldl -lm
> >        ^
> > i think.

errm..

> >
> 
> That was it. Thanks.
> 
> Yes this code works. I don't know what that means though?

ok, then it means that something in prepare() does initialize
something (hmm, too ambiguous :), not the fact that you send the data
to the device.

but please make sure that this trick works after fresh reboot, too
(and/or after the usb device power-off).  it's just to be sure...


> I have also found a serious kernel oops which is caused when starting 
> jack with this card. It also fscked my user profile in mozilla so I have 
> lost all my emails from teh past 6 months.

oh, that's too bad.

please let me know if you catch an oops trace.


Takashi


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: usb quattro

[Patrick Shirkey]

Takashi Iwai wrote:

>>That was it. Thanks.
>>
>>Yes this code works. I don't know what that means though?
> 
> 
> ok, then it means that something in prepare() does initialize
> something (hmm, too ambiguous :), not the fact that you send the data
> to the device.
> 
> but please make sure that this trick works after fresh reboot, too
> (and/or after the usb device power-off).  it's just to be sure...
> 

Yes to both

> 
> 
>>I have also found a serious kernel oops which is caused when starting 
>>jack with this card. It also fscked my user profile in mozilla so I have 
>>lost all my emails from teh past 6 months.
> 
> 
> oh, that's too bad.
> 
> please let me know if you catch an oops trace.
> 

Here's what I get from ksymoops

----
Warning (compare_maps): ksyms_base symbol 
vmalloc_to_page_R__ver_vmalloc_to_page not found in System.map. 
Ignoring ksyms_base entry
Unable to handle kernel NULL pointer dereference at virtual address 00000020
c01e52e4
*pde = 00000000
CPU:    0
EIP:    0010:[<c01e52e4>]  Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010097
eax: cf21cc84   ebx: cf21c480    ecx: d7efd3fc      edx: cf21c484
esi: 00000000   ed1: 00000097     ebp: cf21cc84       esp: c0287f38
Warning (Oops_set_regs): garbage 'ed1: 00000097     ebp: cf21cc84 
esp: c0287f38' at end of register line ignored
ds: 0018        es: 0018       ss:0018
Process swapper (pid: 0, stackpage=c0287000)
Stack:  00000292 d7efd3fc 00000000 0000cc00 d7efd380 c0287fac c01e535b5 
d7efd380
         d7efd380 d7eede80 04000001 0000000b c0109e8a 0000000b d7efd380 
c0287fac
         c0287fac 0000000b c02bee80 d7eede80 c010a018 0000000b c0287fac 
d7eede80
Call Trace: [<c01e53b5>] [<c0109e8a>] [<c010a018>] [<c0106f10>] [<c0106f10>]
    [<c010c108>] [<c0106f10>] [<c0106f36>] {<c0106fc2>] [<c0105000>]
Code: c7 46 20 98 ff ff ff 8b 43 10 8b 1b 80 b8 00 00 00 8b 48


 >>EIP; c01e52e4 <uhci_remove_pending_qhs+44/90>   <=====

 >>eax; cf21cc84 <_end+ef35f08/187112e4>
 >>ebx; cf21c480 <_end+ef35704/187112e4>
 >>ecx; d7efd3fc <_end+17c16680/187112e4>
 >>edx; cf21c484 <_end+ef35708/187112e4>

Trace; c01e53b5 <uhci_interrupt+85/f0>
Trace; c0109e8a <handle_IRQ_event+3a/80>
Trace; c010a018 <do_IRQ+58/b0>
Trace; c0106f10 <default_idle+0/30>
Trace; c0106f10 <default_idle+0/30>
Trace; c010c108 <call_do_IRQ+5/d>
Trace; c0106f10 <default_idle+0/30>
Trace; c0106f36 <default_idle+26/30>

Code;  c01e52e4 <uhci_remove_pending_qhs+44/90>
00000000 <_EIP>:
Code;  c01e52e4 <uhci_remove_pending_qhs+44/90>   <=====
    0:   c7 46 20 98 ff ff ff      movl   $0xffffff98,0x20(%esi)   <=====
Code;  c01e52eb <uhci_remove_pending_qhs+4b/90>
    7:   8b 43 10                  mov    0x10(%ebx),%eax
Code;  c01e52ee <uhci_remove_pending_qhs+4e/90>
    a:   8b 1b                     mov    (%ebx),%ebx
Code;  c01e52f0 <uhci_remove_pending_qhs+50/90>
    c:   80 b8 00 00 00 8b 48      cmpb   $0x48,0x8b000000(%eax)

  <0>Kernel panic:Aiee, killing interrupt handler!

3 warnings issued.  Results may not be reliable.
----

Interestingly I have just seen a thread on usb-devel about various 
lockups in the usb  code so it might be related.



-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

AW: usb quattro

[Karsten Wiese]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="US-ASCII", Size: 2046 bytes --]

> Here's what I get from ksymoops
>
> ----
> Warning (compare_maps): ksyms_base symbol
> vmalloc_to_page_R__ver_vmalloc_to_page not found in System.map.
> Ignoring ksyms_base entry
> Unable to handle kernel NULL pointer dereference at virtual
> address 00000020
> c01e52e4
> *pde = 00000000
> CPU:    0
> EIP:    0010:[<c01e52e4>]  Not tainted
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010097
> eax: cf21cc84   ebx: cf21c480    ecx: d7efd3fc      edx: cf21c484
> esi: 00000000   ed1: 00000097     ebp: cf21cc84       esp: c0287f38
> Warning (Oops_set_regs): garbage 'ed1: 00000097     ebp: cf21cc84
> esp: c0287f38' at end of register line ignored
> ds: 0018        es: 0018       ss:0018
> Process swapper (pid: 0, stackpage=c0287000)
> Stack:  00000292 d7efd3fc 00000000 0000cc00 d7efd380 c0287fac c01e535b5
> d7efd380
>          d7efd380 d7eede80 04000001 0000000b c0109e8a 0000000b d7efd380
> c0287fac
>          c0287fac 0000000b c02bee80 d7eede80 c010a018 0000000b c0287fac
> d7eede80
> Call Trace: [<c01e53b5>] [<c0109e8a>] [<c010a018>] [<c0106f10>]
> [<c0106f10>]
>     [<c010c108>] [<c0106f10>] [<c0106f36>] {<c0106fc2>] [<c0105000>]
> Code: c7 46 20 98 ff ff ff 8b 43 10 8b 1b 80 b8 00 00 00 8b 48
>
>
>  >>EIP; c01e52e4 <uhci_remove_pending_qhs+44/90>   <=====
>

the Tascam US-428 driver (copied / changed from snd-usb-audio ) showed a
similar problem.
I worked around it by not using ASYNC_UNLINKing of the urbs.

uhci_remove_pending_qhs is called to unlink urbs in ASYNC mode.
seems as if uhci has a bug ? or may we asyncly unlink only 1 urb at a time?
any experiences with kernels > 2.4.18 ?

Karsten


__________________________________________________________________

Gesendet von Yahoo! Mail - http://mail.yahoo.de
Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: AW: usb quattro

[Patrick Shirkey]

Karsten Wiese wrote:

>> >>EIP; c01e52e4 <uhci_remove_pending_qhs+44/90>   <=====
>>
> 
> 
> the Tascam US-428 driver (copied / changed from snd-usb-audio ) showed a
> similar problem.
> I worked around it by not using ASYNC_UNLINKing of the urbs.
> 
> uhci_remove_pending_qhs is called to unlink urbs in ASYNC mode.
> seems as if uhci has a bug ? or may we asyncly unlink only 1 urb at a time?
> any experiences with kernels > 2.4.18 ?
> 

This is with kernel 2.4.19pre10

It may be that the code is fixed for the 2.5.x series. there seems to be 
a few different versions of the uhci code floating around.



-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: AW: usb quattro

[Takashi Iwai]

At Thu, 5 Sep 2002 21:02:00 +0200,
Karsten Wiese wrote:
> 
> > Here's what I get from ksymoops
> >
> > ----
> > Warning (compare_maps): ksyms_base symbol
> > vmalloc_to_page_R__ver_vmalloc_to_page not found in System.map.
> > Ignoring ksyms_base entry
> > Unable to handle kernel NULL pointer dereference at virtual
> > address 00000020
> > c01e52e4
> > *pde = 00000000
> > CPU:    0
> > EIP:    0010:[<c01e52e4>]  Not tainted
> > Using defaults from ksymoops -t elf32-i386 -a i386
> > EFLAGS: 00010097
> > eax: cf21cc84   ebx: cf21c480    ecx: d7efd3fc      edx: cf21c484
> > esi: 00000000   ed1: 00000097     ebp: cf21cc84       esp: c0287f38
> > Warning (Oops_set_regs): garbage 'ed1: 00000097     ebp: cf21cc84
> > esp: c0287f38' at end of register line ignored
> > ds: 0018        es: 0018       ss:0018
> > Process swapper (pid: 0, stackpage=c0287000)
> > Stack:  00000292 d7efd3fc 00000000 0000cc00 d7efd380 c0287fac c01e535b5
> > d7efd380
> >          d7efd380 d7eede80 04000001 0000000b c0109e8a 0000000b d7efd380
> > c0287fac
> >          c0287fac 0000000b c02bee80 d7eede80 c010a018 0000000b c0287fac
> > d7eede80
> > Call Trace: [<c01e53b5>] [<c0109e8a>] [<c010a018>] [<c0106f10>]
> > [<c0106f10>]
> >     [<c010c108>] [<c0106f10>] [<c0106f36>] {<c0106fc2>] [<c0105000>]
> > Code: c7 46 20 98 ff ff ff 8b 43 10 8b 1b 80 b8 00 00 00 8b 48
> >
> >
> >  >>EIP; c01e52e4 <uhci_remove_pending_qhs+44/90>   <=====
> >
> 
> the Tascam US-428 driver (copied / changed from snd-usb-audio ) showed a
> similar problem.
> I worked around it by not using ASYNC_UNLINKing of the urbs.
 
yes, this could be the problem.
this happend once and i thought it fixed on the alsa side, but it
seems that there is something wrong on usb driver itself.
why it happened on jack is because jack caused xrun - and the driver
tries to stop the stream and unlinks urbs with ASYNC_UNLINK flag.

anyway, i changed the code on cvs to use SYNC unlink mode as default.
this may have a drawback that the urbs still exist even if the driver
stops the stream after detection of xrun.  but usually this doesn't
matter so much.

i've tested normal playbacks and it seems working.


Takashi


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: usb quattro

[Takashi Iwai]

At Fri, 06 Sep 2002 03:31:53 +0900,
Patrick Shirkey wrote:
> 
> Takashi Iwai wrote:
> 
> >>That was it. Thanks.
> >>
> >>Yes this code works. I don't know what that means though?
> > 
> > 
> > ok, then it means that something in prepare() does initialize
> > something (hmm, too ambiguous :), not the fact that you send the data
> > to the device.
> > 
> > but please make sure that this trick works after fresh reboot, too
> > (and/or after the usb device power-off).  it's just to be sure...
> > 
> 
> Yes to both

thanks.


Takashi


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: AW: usb quattro

[Patrick Shirkey]

Takashi Iwai wrote:

>>the Tascam US-428 driver (copied / changed from snd-usb-audio ) showed a
>>similar problem.
>>I worked around it by not using ASYNC_UNLINKing of the urbs.
> 
>  
> yes, this could be the problem.
> this happend once and i thought it fixed on the alsa side, but it
> seems that there is something wrong on usb driver itself.
> why it happened on jack is because jack caused xrun - and the driver
> tries to stop the stream and unlinks urbs with ASYNC_UNLINK flag.
> 
> anyway, i changed the code on cvs to use SYNC unlink mode as default.
> this may have a drawback that the urbs still exist even if the driver
> stops the stream after detection of xrun.  but usually this doesn't
> matter so much.
> 
> i've tested normal playbacks and it seems working.
> 
> 

I have actually managed to get a stream from alsaplayer through without 
a hang but the sound is choppy.

I will make a test signal  so you can hear what I am getting. It's 
similar to what was happening before the driver was fixed last time.

I got this output from jackd. this happened after I started jack and 
didn't connect any other apps. Maybe it timed out but I don't think it 
is supposed to.

----
$ jackd -v -d alsa -d q4
jackd 0.37.1
Copyright 2001-2002 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

512 waiting for signals
creating alsa driver ... q4|1024|2|48000|swmon
You appear to be using the ALSA software "plug" layer, probably
a result of using the "default" ALSA device. This is less
efficient than it could be. Consider using a ~/.asoundrc file
to define a hardware audio device rather than using the plug layer

You appear to be using the ALSA software "plug" layer, probably
a result of using the "default" ALSA device. This is less
efficient than it could be. Consider using a ~/.asoundrc file
to define a hardware audio device rather than using the plug layer

new client: alsa_pcm, id = 1 type 1 @ 0x8067e38 fd = 14
port alsa_pcm:in_1 buf shm key 0x7598eff0 at offset 4096 bi = 0x8067208
registered port alsa_pcm:in_1, offset = 4096
port alsa_pcm:in_2 buf shm key 0x7598eff0 at offset 8192 bi = 0x8067218
registered port alsa_pcm:in_2, offset = 8192
registered port alsa_pcm:out_1, offset = 0
registered port alsa_pcm:out_2, offset = 0
-- jack_rechain_graph():
client alsa_pcm: inprocess client, execution_order=0.


**** alsa_pcm: xrun of at least 0.044 msecs



**** alsa_pcm: xrun of at least 0.024 msecs



**** alsa_pcm: xrun of at least 0.024 msecs



**** alsa_pcm: xrun of at least 0.028 msecs



**** alsa_pcm: xrun of at least 0.027 msecs



**** alsa_pcm: xrun of at least 0.029 msecs



**** alsa_pcm: xrun of at least 0.044 msecs



**** alsa_pcm: xrun of at least 0.035 msecs



**** alsa_pcm: xrun of at least 0.043 msecs



**** alsa_pcm: xrun of at least 0.043 msecs



**** alsa_pcm: xrun of at least 0.024 msecs



**** alsa_pcm: xrun of at least 0.025 msecs



**** alsa_pcm: xrun of at least 0.025 msecs



**** alsa_pcm: xrun of at least 0.026 msecs



**** alsa_pcm: xrun of at least 0.028 msecs



**** alsa_pcm: xrun of at least 0.027 msecs



**** alsa_pcm: xrun of at least 0.035 msecs



**** alsa_pcm: xrun of at least 0.034 msecs



**** alsa_pcm: xrun of at least 0.044 msecs



**** alsa_pcm: xrun of at least 0.292 msecs



**** alsa_pcm: xrun of at least 0.025 msecs



**** alsa_pcm: xrun of at least 0.025 msecs



**** alsa_pcm: xrun of at least 0.026 msecs



**** alsa_pcm: xrun of at least 0.028 msecs

load = 40.1330 max usecs: 17123.160, spare = 4209.840


**** alsa_pcm: xrun of at least 0.028 msecs



**** alsa_pcm: xrun of at least 0.036 msecs



**** alsa_pcm: xrun of at least 0.044 msecs



**** alsa_pcm: xrun of at least 0.044 msecs



**** alsa_pcm: xrun of at least 0.043 msecs



**** alsa_pcm: xrun of at least 0.025 msecs



**** alsa_pcm: xrun of at least 0.025 msecs



**** alsa_pcm: xrun of at least 0.025 msecs



**** alsa_pcm: xrun of at least 0.023 msecs

load = 56.6747 max usecs: 15619.234, spare = 5713.766
load = 28.5257 max usecs: 80.377, spare = 21252.623
load = 14.4081 max usecs: 61.988, spare = 21271.012
load = 7.3838 max usecs: 76.672, spare = 21256.328
load = 3.8441 max usecs: 64.923, spare = 21268.076
load = 2.0735 max usecs: 64.639, spare = 21268.361


**** alsa_pcm: xrun of at least 19.643 msecs

delay of 29276.168 usecs exceeds estimated spare time of 21268.361; 
restart ...
load = 1.1959 max usecs: 67.880, spare = 21265.121
load = 0.7490 max usecs: 64.444, spare = 21268.557
load = 0.5604 max usecs: 79.328, spare = 21253.672


**** alsa_pcm: xrun of at least 25.716 msecs

delay of 39187.176 usecs exceeds estimated spare time of 21253.672; 
restart ...
load = 0.4574 max usecs: 75.620, spare = 21257.381
load = 0.3795 max usecs: 64.340, spare = 21268.660
load = 0.3446 max usecs: 66.060, spare = 21266.939
load = 0.3312 max usecs: 67.805, spare = 21265.195
load = 0.3430 max usecs: 75.690, spare = 21257.311
load = 0.3253 max usecs: 65.600, spare = 21267.400
load = 0.3170 max usecs: 65.860, spare = 21267.141


**** alsa_pcm: xrun of at least 0.348 msecs

ALSA lib pcm_hw.c:398:(snd_pcm_hw_prepare) SNDRV_PCM_IOCTL_PREPARE 
failed: Input/output error
ALSA-HW: prepare error for playback on "q4" (Input/output error)
driver wait function failed, exiting
telling signal thread that the engine is done
jack main caught signal 1


----

-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: AW: usb quattro

[Patrick Shirkey]

Patrick Shirkey wrote:

> 
> I have actually managed to get a stream from alsaplayer through without 
> a hang but the sound is choppy.
> 
> I will make a test signal  so you can hear what I am getting. It's 
> similar to what was happening before the driver was fixed last time.
> 

Well I just noticed that the sound from native alsa apps is fscked to.

Here is a sample for you, it should be a pure sine wav but it's not quite.

http://www.boosthardware.com/audio/sine-0907.wav

I spose that fixing this might help jack or maybe not :)

-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

usb-midi

[Patrick Shirkey]

I missed the merge of the drivers.

Do we still have a usb-midi module or is everything usb-audio now?

I will have to change the matrix to show this.


-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: AW: usb quattro

[Takashi Iwai]

At Sat, 07 Sep 2002 05:40:02 +0900,
Patrick Shirkey wrote:
> 
> Takashi Iwai wrote:
> 
> >>the Tascam US-428 driver (copied / changed from snd-usb-audio ) showed a
> >>similar problem.
> >>I worked around it by not using ASYNC_UNLINKing of the urbs.
> > 
> >  
> > yes, this could be the problem.
> > this happend once and i thought it fixed on the alsa side, but it
> > seems that there is something wrong on usb driver itself.
> > why it happened on jack is because jack caused xrun - and the driver
> > tries to stop the stream and unlinks urbs with ASYNC_UNLINK flag.
> > 
> > anyway, i changed the code on cvs to use SYNC unlink mode as default.
> > this may have a drawback that the urbs still exist even if the driver
> > stops the stream after detection of xrun.  but usually this doesn't
> > matter so much.
> > 
> > i've tested normal playbacks and it seems working.
> > 
> > 
> 
> I have actually managed to get a stream from alsaplayer through without 
> a hang but the sound is choppy.
> 
> I will make a test signal  so you can hear what I am getting. It's 
> similar to what was happening before the driver was fixed last time.
> 
> I got this output from jackd. this happened after I started jack and 
> didn't connect any other apps. Maybe it timed out but I don't think it 
> is supposed to.
> 
> ----
> $ jackd -v -d alsa -d q4
> jackd 0.37.1
> Copyright 2001-2002 Paul Davis and others.
> jackd comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details
> 
> 512 waiting for signals
> creating alsa driver ... q4|1024|2|48000|swmon

the resolution of usb-audio device is 1ms.  this value is fixed.
thus you need to adjust the period size according to the sample rate
if you want to achieve the real-time response with a small period
size.

that means:
- the sample rate should be 48kHz (or 32kHz), which can be divided by
  1000, and should not be 44.1kHz.
- the period size should be aligned to (rate / 1000).
  in the case of 48kHz, the period size should be 48, 96, 192, ...

please try this combination.


Takashi


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: usb-midi

[Clemens Ladisch]

Patrick Shirkey wrote:
> I missed the merge of the drivers.
> 
> Do we still have a usb-midi module or is everything usb-audio now?

Both. :-)

All USB devices are handled by snd-usb-audio.
The snd-usb-midi module still exists, but is loaded automatically
by snd-usb-audio. For the user, only snd-usb-audio matters.


HTH
Clemens


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: AW: usb quattro

[Patrick Shirkey]

Takashi Iwai wrote:
> At Sat, 07 Sep 2002 05:40:02 +0900,
> Patrick Shirkey wrote:
> 
>>Takashi Iwai wrote:
>>
>>
>>>>the Tascam US-428 driver (copied / changed from snd-usb-audio ) showed a
>>>>similar problem.
>>>>I worked around it by not using ASYNC_UNLINKing of the urbs.
>>>
>>> 
>>>yes, this could be the problem.
>>>this happend once and i thought it fixed on the alsa side, but it
>>>seems that there is something wrong on usb driver itself.
>>>why it happened on jack is because jack caused xrun - and the driver
>>>tries to stop the stream and unlinks urbs with ASYNC_UNLINK flag.
>>>
>>>anyway, i changed the code on cvs to use SYNC unlink mode as default.
>>>this may have a drawback that the urbs still exist even if the driver
>>>stops the stream after detection of xrun.  but usually this doesn't
>>>matter so much.
>>>
>>>i've tested normal playbacks and it seems working.
>>>
>>>
>>
>>I have actually managed to get a stream from alsaplayer through without 
>>a hang but the sound is choppy.
>>
>>I will make a test signal  so you can hear what I am getting. It's 
>>similar to what was happening before the driver was fixed last time.
>>
>>I got this output from jackd. this happened after I started jack and 
>>didn't connect any other apps. Maybe it timed out but I don't think it 
>>is supposed to.
>>
>>----
>>$ jackd -v -d alsa -d q4
>>jackd 0.37.1
>>Copyright 2001-2002 Paul Davis and others.
>>jackd comes with ABSOLUTELY NO WARRANTY
>>This is free software, and you are welcome to redistribute it
>>under certain conditions; see the file COPYING for details
>>
>>512 waiting for signals
>>creating alsa driver ... q4|1024|2|48000|swmon
> 
> 
> the resolution of usb-audio device is 1ms.  this value is fixed.
> thus you need to adjust the period size according to the sample rate
> if you want to achieve the real-time response with a small period
> size.
> 
> that means:
> - the sample rate should be 48kHz (or 32kHz), which can be divided by
>   1000, and should not be 44.1kHz.
> - the period size should be aligned to (rate / 1000).
>   in the case of 48kHz, the period size should be 48, 96, 192, ...
> 
> please try this combination.
> 
> 

Takashi you little beauty :)

The sound is infinitely better.

I'll add a note to the docs.

Hmm. Now I have no excuses when people ask to hear my music though ;)

-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: AW: usb quattro

[Patrick Shirkey]

Patrick Shirkey wrote:

>>
>> the resolution of usb-audio device is 1ms.  this value is fixed.
>> thus you need to adjust the period size according to the sample rate
>> if you want to achieve the real-time response with a small period
>> size.
>>
>> that means:
>> - the sample rate should be 48kHz (or 32kHz), which can be divided by
>>   1000, and should not be 44.1kHz.
>> - the period size should be aligned to (rate / 1000).
>>   in the case of 48kHz, the period size should be 48, 96, 192, ...
>>
>> please try this combination.
>>
>>
> 
> Takashi you little beauty :)
> 
> The sound is infinitely better.
> 
> I'll add a note to the docs.
> 
> Hmm. Now I have no excuses when people ask to hear my music though ;)
> 

Blah. I spoke too soon. I should have been worried when it was so easy.

I can get much better sound quality using this:

jackd -v -R -d alsa -d q4 -p 1152

which is through the plug layer. Currently the hw layer produces white 
noise.

I will have to track down the correct settings.



-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: AW: usb quattro

[Patrick Shirkey]

Patrick Shirkey wrote:

>  Currently the hw layer produces white
> noise.
> 

What is odd about this is that the noise only comes from the internal 
i/o. If I play through an external and use the direct monitor switch the 
  sound is perfect.

I get the most stable jack with these settings:

- using the hw layer.

jackd -v -R -d alsa -d quattro2 -p 4608

- using the plug layer.

jackd -v -R -d alsa -d q4 -p 1017

I have tested (using ardour) a 48khz stereo sine wave. For the first 
example I get white noise and for the second I get an almost clean 
signal which sounds slightly higher pitched than it should.

Note that using the previous version of the driver I could get a clean 
signal from all native alsa apps.

-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

Re: AW: usb quattro

[Patrick Shirkey]

Takashi Iwai wrote:

> the resolution of usb-audio device is 1ms.  this value is fixed.
> thus you need to adjust the period size according to the sample rate
> if you want to achieve the real-time response with a small period
> size.
> 
> that means:
> - the sample rate should be 48kHz (or 32kHz), which can be divided by
>   1000, and should not be 44.1kHz.
> - the period size should be aligned to (rate / 1000).
>   in the case of 48kHz, the period size should be 48, 96, 192, ...
> 
> please try this combination.
> 

This is not working properly here.

Using 48khz with the above or higher sample rates I get many xruns from 
jackd and it is impossible to connect ardour.

However if I use 44100/48000 with the default period size of 1024 then 
it takes jack a while to warm the card up (about 5-10 seconds) and then 
I get no xruns. However the sound quality is scratchy.


-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: AW: usb quattro

[Patrick Shirkey]

Patrick Shirkey wrote:
> Takashi Iwai wrote:
> 
>> the resolution of usb-audio device is 1ms.  this value is fixed.
>> thus you need to adjust the period size according to the sample rate
>> if you want to achieve the real-time response with a small period
>> size.
>>
>> that means:
>> - the sample rate should be 48kHz (or 32kHz), which can be divided by
>>   1000, and should not be 44.1kHz.
>> - the period size should be aligned to (rate / 1000).
>>   in the case of 48kHz, the period size should be 48, 96, 192, ...
>>
>> please try this combination.
>>
> 
> This is not working properly here.
> 
> Using 48khz with the above or higher sample rates I get many xruns from 
> jackd and it is impossible to connect ardour.
> 
> However if I use 44100/48000 with the default period size of 1024 then 
> it takes jack a while to warm the card up (about 5-10 seconds) and then 
> I get no xruns. However the sound quality is scratchy.
> 
> 

I was thinking about why the sound has been degraded again. It sounds 
the same as what was happening a couple of months back. Is it possible 
that when you added the code for merging multiple endpoints that you 
didn't take into account that fix again?

It seems odd that by changing the endpoint code the audio quality (which 
was perfect) has been degraded to what we were hearing a couple of 
months back.


-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

usb quattro

[Patrick Shirkey]

I just updated using cvs from a couple of hours ago and I can get 
perfect quality audio with multiple channels through jack.

I need to figure out why the audio gets playback on all channels but I 
am using some asoundrc magic to do that so it probably needs fine tuning.

Thanks Takashi and Clemens.


-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: usb quattro

[Patrick Shirkey]

Patrick Shirkey wrote:
> I just updated using cvs from a couple of hours ago and I can get 
> perfect quality audio with multiple channels through jack.
> 

Further testing reveals that jack cannot capture audio from the pcm ins. 
arecord works however. I have tested using jackrec and ardour but 
neither will capture audio. Instead they write a soundless file to disk 
  without complaint.




-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

control info.

[Patrick Shirkey]

Where can I get a list of the available controls for each module?

I would like to add this to the online docs.

-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: usb quattro

[Takashi Iwai]

At Thu, 26 Sep 2002 09:56:15 +0900,
Patrick Shirkey wrote:
> 
> Patrick Shirkey wrote:
> > I just updated using cvs from a couple of hours ago and I can get 
> > perfect quality audio with multiple channels through jack.
> > 
> 
> Further testing reveals that jack cannot capture audio from the pcm ins. 
> arecord works however. I have tested using jackrec and ardour but 
> neither will capture audio. Instead they write a soundless file to disk 
>   without complaint.

in the next week (perhaps), i'll get a quattro, so i can test ardour
on it, too.
i've been trying to get contact about the technical issues with
m-audio.  they are quite friendly.  let's see what happens in near
future... 


Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf