* Tascam US-224 support: MIDI OK, Audio KO?
@ 2004-03-29 11:34 Rui Nuno Capela
2004-03-29 19:29 ` Karsten Wiese
2004-03-29 20:00 ` Martin Langer
0 siblings, 2 replies; 18+ messages in thread
From: Rui Nuno Capela @ 2004-03-29 11:34 UTC (permalink / raw)
To: alsa-devel
Hi,
Please note that this is my first time on this list, and this has been
also posted on alsa-user. It's a rather long post, so sorry for the
inconvenience.
I am now just entering the Tascam USx2y arena on Linux and was hoping to
get some help before making any further... mistakes? :) It was just a
couple of days ago that I've got my hands on a US-224 and ran to test it
on my tuxie boxes. I must tell that I'm already committed to Linux audio,
and willing to get the most out of this piece of hardware under it.
On my early tests, which were all under a 2.6.4-ck1 kernel, with stock
ALSA 1.0.3, I could check that the firmware loads and the USB light gets
lit alright as expected. Then I could check on /proc/asound/cards and with
aconnect that the ALSA sequencer interfaces are roughly there. OK.
My first question goes whether us428control's not recognizing any USx2y
hardware dependant stuff (hwdep) either on hw:0 or hw:1. I'm almost sure
that it should be on hw:1 as the US-224 is configured as my second
soundcard under the ALSA configuration (i.e. alias snd-usb-usx2y
snd-card-1). But us428control does not find anything, at least after the
firmware gets loaded.
Strange enough, to me at least, us428control seems to work between the fw
and fpga loading steps. Using lsusb, I've noticed that the USB ids do
change from 1604:8004 to 1604:8005 while plugging in. Guess that's normal,
and it marks the momemt when fw is loaded and fpga is about to.
The second one is about the LEDs on the control surface: besides the USB
light, isn't that supposed to light up anything else? Everything else is
dead dark. Touching the knobs, pushing the buttons or whatever doesn't
make any visible difference. Is that supposed to be normal?
OK. I've tested on two different systems, a Compaq laptop w/Mandrake 10.0
(P4 2.533GHz, OHCI) and on a custom desktop w/SUSE 9.0 (P4 3.333GHz
SMP/HT, UHCI). On both, the firmware seems to get loaded and only visible
thing to note is that the USB light gets lit.
The only thing that i could get to work is the MIDI interface. AFAICT all
faders, buttons and the jog wheel do send MIDI control events, and I could
intercept those on the ALSA sequencer interface. MIDI seems pretty
functional then. I could also test the external raw MIDI interface, by
sending out some notes and it seems to work too.
It's the PCM audio part that gets me worried. ALSA reports both capture
and playback PCM interfaces. But on all my tests I could only ear silence.
Not a sound. Dead silence only. Although it all seems to be OK, at least
as reported by ALSA.
Quite traditionally this symptom is due to initially default muted mixer
channels, but running `alsamixer -c1` reports that there's no mixer elems.
So how can I unmute this beast?
By now, I had already tested on Windows and everything worked and sounded
almost perfectly while on Cubase. So hardware fault is not an issue ;)
I've already tryied the newest firmware (v3.24) as suggested on
"http://www.langerland.de/us122/development.html", but things didn't get
any better. Just an worrifying silent output.
Below you may find all the relevant reports I could gather about my latest
experiments, while on my SUSE 9.0 box, P4 3.333GHz, 1GB DDR400, ASUS
P4P800 Dlx Mobo, running kernel 2.6.4-ck1 and ALSA 1.0.3. BTW, the onboard
sound works flawlessly on snd-intel8x0.
--- `/var/log/messages` (output while the US-224 is being plugged in) Mar
28 23:33:15 gamma-suse1 kernel: usb 2-1: new full speed USB device using
address 2
Mar 28 23:33:18 gamma-suse1 /etc/hotplug/usb.agent[22372]: Bad USB agent
invocation
Mar 28 23:33:22 gamma-suse1 /etc/hotplug/usb.agent[22380]: modules.usbmap
unparsable line:
Mar 28 23:33:22 gamma-suse1 /etc/hotplug/usb.agent[22380]: .
Mar 28 23:33:22 gamma-suse1 /etc/hotplug/usb.agent[22380]: modules.usbmap
unparsable line:
Mar 28 23:33:22 gamma-suse1 /etc/hotplug/usb.agent[22380]: .
Mar 28 23:33:22 gamma-suse1 kernel: usb 2-1: USB disconnect, address 2 Mar
28 23:33:24 gamma-suse1 kernel: usb 2-1: new full speed USB device using
address 3
Mar 28 23:33:24 gamma-suse1 /sbin/hotplug[22469]: no runnable
/etc/hotplug/sound.agent is installed
Mar 28 23:33:24 gamma-suse1 /sbin/hotplug[22467]: no runnable
/etc/hotplug/sound.agent is installed
Mar 28 23:33:25 gamma-suse1 /etc/hotplug/usb.agent[22506]:
/proc/bus/usb/002/002: No such file or directory
Mar 28 23:33:28 gamma-suse1 /etc/hotplug/usb.agent[22528]: Bad USB agent
invocation
Mar 28 23:33:33 gamma-suse1 /etc/hotplug/usb.agent[22536]: Bad USB agent
invocation
Mar 28 23:33:36 gamma-suse1 /etc/hotplug/usb.agent[22544]: modules.usbmap
unparsable line:
Mar 28 23:33:36 gamma-suse1 /etc/hotplug/usb.agent[22544]: .
Mar 28 23:33:36 gamma-suse1 /etc/hotplug/usb.agent[22544]: modules.usbmap
unparsable line:
Mar 28 23:33:36 gamma-suse1 /etc/hotplug/usb.agent[22544]: .
Mar 28 23:33:39 gamma-suse1 /sbin/hotplug[22584]: no runnable
/etc/hotplug/sound.agent is installed
Mar 28 23:33:39 gamma-suse1 /sbin/hotplug[22585]: no runnable
/etc/hotplug/sound.agent is installed
Mar 28 23:33:39 gamma-suse1 /sbin/hotplug[22586]: no runnable
/etc/hotplug/sound.agent is installed
Mar 28 23:33:39 gamma-suse1 /sbin/hotplug[22589]: no runnable
/etc/hotplug/sound.agent is installed
Mar 28 23:33:39 gamma-suse1 /sbin/hotplug[22591]: no runnable
/etc/hotplug/sound.agent is installed
Mar 28 23:33:39 gamma-suse1 kernel: usb 2-1: control timeout on ep0in Mar
28 23:33:39 gamma-suse1 kernel: usbfs: USBDEVFS_CONTROL failed cmd
usbmodules dev 3 rqt 128 rq 6 len 18 ret -110
Mar 28 23:33:40 gamma-suse1 kernel: usb 2-1: control timeout on ep0in Mar
28 23:33:40 gamma-suse1 kernel: usbfs: USBDEVFS_CONTROL failed cmd
usbmodules dev 3 rqt 128 rq 6 len 18 ret -110
Mar 28 23:33:40 gamma-suse1 kernel: usb 2-1: control timeout on ep0in Mar
28 23:33:40 gamma-suse1 kernel: usbfs: USBDEVFS_CONTROL failed cmd
usbmodules dev 3 rqt 128 rq 6 len 18 ret -110
--- `lsusb` (output) -----------------------------------------
Bus 003 Device 002: ID 056a:0011 Wacom Co., Ltd Graphire 2
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 1604:8005 Tascam
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
--- `aadebug.sh` (output) ------------------------------------
ALSA Audio Debug v0.0.7 - Sun Mar 28 23:35:38 WEST 2004
http://alsa.opensrc.org/?aadebug
Kernel ----------------------------------------------------
Linux gamma-suse1 2.6.4-ck1.smp #1 SMP Fri Mar 12 16:01:11 WET 2004 i686
i686 i386 GNU/Linux
Loaded Modules --------------------------------------------
snd_seq 57872 2
snd_usb_usx2y 21700 1
snd_usb_audio 63680 1 snd_usb_usx2y
snd_hwdep 9760 2 snd_usb_usx2y
snd_intel8x0 32040 4
snd_ac97_codec 59268 1 snd_intel8x0
snd_pcm 98976 3 snd_usb_usx2y,snd_usb_audio,snd_intel8x0
snd_timer 25732 2 snd_seq,snd_pcm
snd_page_alloc 11908 3 snd_usb_usx2y,snd_intel8x0,snd_pcm
snd_mpu401_uart 8192 1 snd_intel8x0
snd_rawmidi 24864 2 snd_usb_audio,snd_mpu401_uart
snd_seq_device 8328 2 snd_seq,snd_rawmidi
snd 56420 22
snd_seq,snd_usb_usx2y,snd_usb_audio,snd_hwdep,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
Modprobe Conf ----------------------------------------------
alias char-major-116 snd
alias snd-card-0 snd-intel8x0
alias sound-slot-0 snd-intel8x0
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-11 snd-mixer-oss
alias sound-service-0-12 snd-pcm-oss
alias snd-card-1 snd-usb-usx2y
alias sound-slot-1 snd-usb-usx2y
options snd-intel8x0 ac97_clock=0 enable=1 index=0
options snd-usb-usx2y index=1
#options snd cards_limit=2 major=116
install sound /bin/true
install sound-service-1-0 /bin/true
install sound-service-2-0 /bin/true
install sound-service-3-0 /bin/true
install sound-slot-1 /bin/true
install sound-slot-2 /bin/true
Proc Asound -----------------------------------------------
Advanced Linux Sound Architecture Driver Version 1.0.3.
Compiled on Mar 12 2004 for kernel 2.6.4-ck1.smp (SMP).
0 [ICH5 ]: ICH - Intel ICH5
Intel ICH5 at 0xfebff800, irq 17
1 [USX2Y ]: USB US-X2Y - TASCAM US-X2Y
TASCAM US-X2Y (1604:8005 if 0 at 002/003)
0: [0- 0]: ctl
20: [0- 4]: digital audio playback
27: [0- 3]: digital audio capture
26: [0- 2]: digital audio capture
25: [0- 1]: digital audio capture
16: [0- 0]: digital audio playback
24: [0- 0]: digital audio capture
1: : sequencer
33: : timer
32: [1- 0]: ctl
36: [1- 0]: hardware dependent
48: [1- 0]: digital audio playback
56: [1- 0]: digital audio capture
40: [1- 0]: raw midi
01-00: /proc/bus/usb/002/003
00-00: Intel ICH : Intel ICH5 : playback 1 : capture 1
00-01: Intel ICH - MIC ADC : Intel ICH5 - MIC ADC : capture 1
00-02: Intel ICH - MIC2 ADC : Intel ICH5 - MIC2 ADC : capture 1
00-03: Intel ICH - ADC2 : Intel ICH5 - ADC2 : capture 1
00-04: Intel ICH - IEC958 : Intel ICH5 - IEC958 : playback 1
01-00: US-X2Y Audio : US-X2Y Audio #0 : playback 1 : capture 1
Dev Snd ---------------------------------------------------
controlC0 hwC5D2 midiC2D4 midiC6D2 pcmC1D0c pcmC2D7c pcmC4D6c
pcmC6D5c
controlC1 hwC5D3 midiC2D5 midiC6D3 pcmC1D0p pcmC2D7p pcmC4D6p
pcmC6D5p
controlC2 hwC6D0 midiC2D6 midiC6D4 pcmC1D1c pcmC3D0c pcmC4D7c
pcmC6D6c
controlC3 hwC6D1 midiC2D7 midiC6D5 pcmC1D1p pcmC3D0p pcmC4D7p
pcmC6D6p
controlC4 hwC6D2 midiC3D0 midiC6D6 pcmC1D2c pcmC3D1c pcmC5D0c
pcmC6D7c
controlC5 hwC6D3 midiC3D1 midiC6D7 pcmC1D2p pcmC3D1p pcmC5D0p
pcmC6D7p
controlC6 hwC7D0 midiC3D2 midiC7D0 pcmC1D3c pcmC3D2c pcmC5D1c
pcmC7D0c
controlC7 hwC7D1 midiC3D3 midiC7D1 pcmC1D3p pcmC3D2p pcmC5D1p
pcmC7D0p
hwC0D0 hwC7D2 midiC3D4 midiC7D2 pcmC1D4c pcmC3D3c pcmC5D2c
pcmC7D1c
hwC0D1 hwC7D3 midiC3D5 midiC7D3 pcmC1D4p pcmC3D3p pcmC5D2p
pcmC7D1p
hwC0D2 midiC0D0 midiC3D6 midiC7D4 pcmC1D5c pcmC3D4c pcmC5D3c
pcmC7D2c
hwC0D3 midiC0D1 midiC3D7 midiC7D5 pcmC1D5p pcmC3D4p pcmC5D3p
pcmC7D2p
hwC1D0 midiC0D2 midiC4D0 midiC7D6 pcmC1D6c pcmC3D5c pcmC5D4c
pcmC7D3c
hwC1D1 midiC0D3 midiC4D1 midiC7D7 pcmC1D6p pcmC3D5p pcmC5D4p
pcmC7D3p
hwC1D2 midiC0D4 midiC4D2 pcmC0D0c pcmC1D7c pcmC3D6c pcmC5D5c
pcmC7D4c
hwC1D3 midiC0D5 midiC4D3 pcmC0D0p pcmC1D7p pcmC3D6p pcmC5D5p
pcmC7D4p
hwC2D0 midiC0D6 midiC4D4 pcmC0D1c pcmC2D0c pcmC3D7c pcmC5D6c
pcmC7D5c
hwC2D1 midiC0D7 midiC4D5 pcmC0D1p pcmC2D0p pcmC3D7p pcmC5D6p
pcmC7D5p
hwC2D2 midiC1D0 midiC4D6 pcmC0D2c pcmC2D1c pcmC4D0c pcmC5D7c
pcmC7D6c
hwC2D3 midiC1D1 midiC4D7 pcmC0D2p pcmC2D1p pcmC4D0p pcmC5D7p
pcmC7D6p
hwC3D0 midiC1D2 midiC5D0 pcmC0D3c pcmC2D2c pcmC4D1c pcmC6D0c
pcmC7D7c
hwC3D1 midiC1D3 midiC5D1 pcmC0D3p pcmC2D2p pcmC4D1p pcmC6D0p
pcmC7D7p
hwC3D2 midiC1D4 midiC5D2 pcmC0D4c pcmC2D3c pcmC4D2c pcmC6D1c seq
hwC3D3 midiC1D5 midiC5D3 pcmC0D4p pcmC2D3p pcmC4D2p pcmC6D1p
timer hwC4D0 midiC1D6 midiC5D4 pcmC0D5c pcmC2D4c pcmC4D3c
pcmC6D2c hwC4D1 midiC1D7 midiC5D5 pcmC0D5p pcmC2D4p pcmC4D3p
pcmC6D2p hwC4D2 midiC2D0 midiC5D6 pcmC0D6c pcmC2D5c pcmC4D4c
pcmC6D3c hwC4D3 midiC2D1 midiC5D7 pcmC0D6p pcmC2D5p pcmC4D4p
pcmC6D3p hwC5D0 midiC2D2 midiC6D0 pcmC0D7c pcmC2D6c pcmC4D5c
pcmC6D4c hwC5D1 midiC2D3 midiC6D1 pcmC0D7p pcmC2D6p pcmC4D5p
pcmC6D4p
CPU -------------------------------------------------------
model name : Intel(R) Pentium(R) 4 CPU 2.80GHz
model name : Intel(R) Pentium(R) 4 CPU 2.80GHz
cpu MHz : 3361.785
cpu MHz : 3361.785
RAM -------------------------------------------------------
MemTotal: 1033432 kB
SwapTotal: 1951816 kB
Hardware --------------------------------------------------
00:00.0 Host bridge: Intel Corp. 82865G/PE/P Processor to I/O Controller
(rev 02)
00:1f.5 Multimedia audio controller: Intel Corp. 82801EB AC'97 Audio
Controller (rev 02)
--- `aplay -l` (output) --------------------------------------
**** List of PLAYBACK Hardware Devices ****
card 0: ICH5 [Intel ICH5], device 0: Intel ICH [Intel ICH5]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: ICH5 [Intel ICH5], device 4: Intel ICH - IEC958 [Intel ICH5 - IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
**** List of PLAYBACK Hardware Devices ****
card 1: USX2Y [TASCAM US-X2Y], device 0: US-X2Y Audio [US-X2Y Audio #0]
Subdevices: 1/1
Subdevice #0: subdevice #0
--- `aconnect -li` (output) --------------------------------
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 72: 'TASCAM US-X2Y - Rawmidi 1' [type=kernel]
0 'TASCAM US-X2Y MIDI 1'
client 129: 'US-428' [type=user]
0 'Controls '
--- `aconnect -lo` (output) --------------------------------
client 72: 'TASCAM US-X2Y - Rawmidi 1' [type=kernel]
0 'TASCAM US-X2Y MIDI 1'
client 128: 'KAMix' [type=user]
0 'qamix '
--- `lsusb -v -d 1604:8005` (output) -----------------------
Bus 002 Device 003: ID 1604:8005 Tascam
Language IDs: none (invalid length string descriptor bf; len=0)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 0 Interface
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1604 Tascam
idProduct 0x8005
bcdDevice 0.01
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 169
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 5
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 21
bInterval 10
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 7
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 21
bInterval 10
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 200
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0a EP 10 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 200
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 7
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 21
bInterval 10
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 300
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0a EP 10 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 300
bInterval 1
Language IDs: none (invalid length string descriptor bf; len=0)
--- `aplay -v -D hw:1 "DrumLoopA 01.wav"` ------------------
Playing WAVE 'DrumLoopA 01.wav' : Signed 16 bit Little Endian, Rate 44100
Hz, Stereo
Hardware PCM card 1 'TASCAM US-X2Y' device 0 subdevice 0
Its setup is:
stream : PLAYBACK
access : RW_INTERLEAVED
format : S16_LE
subformat : STD
channels : 2
rate : 44100
exact rate : 44100 (44100/1)
msbits : 16
buffer_size : 16384
period_size : 5513
period_time : 125011
tick_time : 1000
tstamp_mode : NONE
period_step : 1
sleep_min : 0
avail_min : 5513
xfer_align : 5513
start_threshold : 11026
stop_threshold : 16384
silence_threshold: 0
silence_size : 0
boundary : 1073741824
--- No errors, only silence :(
I'm pretty desperate on this. If someone can point out a clue on this
puzzle I'll appreciate very much.
As I said, I'm open to try everything at my reach to make this thing work,
even if that means going deep into driver source code and/or debugging. In
fact, I'm eager to do that, just need some initial pointers and advice.
I'm sure I can help somehow.
Karsten?
Martin?
Pleeeeease?
--
rncbc aka Rui Nuno Capela
rncbc@rncbc.org
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Tascam US-224 support: MIDI OK, Audio KO?
2004-03-29 11:34 Tascam US-224 support: MIDI OK, Audio KO? Rui Nuno Capela
@ 2004-03-29 19:29 ` Karsten Wiese
2004-03-29 21:41 ` Rui Nuno Capela
2004-03-29 20:00 ` Martin Langer
1 sibling, 1 reply; 18+ messages in thread
From: Karsten Wiese @ 2004-03-29 19:29 UTC (permalink / raw)
To: alsa-devel; +Cc: Rui Nuno Capela
Am Montag 29 März 2004 13:34 schrieb Rui Nuno Capela:
>
> My first question goes whether us428control's not recognizing any USx2y
> hardware dependant stuff (hwdep) either on hw:0 or hw:1. I'm almost sure
> that it should be on hw:1 as the US-224 is configured as my second
> soundcard under the ALSA configuration (i.e. alias snd-usb-usx2y
> snd-card-1). But us428control does not find anything, at least after the
> firmware gets loaded.
I only have a us428 here, so I assume us224 behaves the same.
could it be it is already running (started by hotpug scripts which were
installed with alsa)?
Did you try "ps -aux|grep us428control" ?
aconnect -li gave you among others
client 129: 'US-428' [type=user]
0 'Controls '
this usually is due to us428controls activity.
>
> Strange enough, to me at least, us428control seems to work between the fw
> and fpga loading steps. Using lsusb, I've noticed that the USB ids do
> change from 1604:8004 to 1604:8005 while plugging in. Guess that's normal,
> and it marks the momemt when fw is loaded and fpga is about to.
>
> The second one is about the LEDs on the control surface: besides the USB
> light, isn't that supposed to light up anything else? Everything else is
> dead dark. Touching the knobs, pushing the buttons or whatever doesn't
> make any visible difference. Is that supposed to be normal?
if us428control is running ok (AND fits the us224), INPUT MONITOR Led is
functional.
Also if INPUT MONITOR Led is ON, SELECT and MUTE Leds work.
>
> OK. I've tested on two different systems, a Compaq laptop w/Mandrake 10.0
> (P4 2.533GHz, OHCI) and on a custom desktop w/SUSE 9.0 (P4 3.333GHz
> SMP/HT, UHCI). On both, the firmware seems to get loaded and only visible
> thing to note is that the USB light gets lit.
>
> The only thing that i could get to work is the MIDI interface. AFAICT all
> faders, buttons and the jog wheel do send MIDI control events, and I could
> intercept those on the ALSA sequencer interface. MIDI seems pretty
> functional then. I could also test the external raw MIDI interface, by
> sending out some notes and it seems to work too.
faders, buttons and the jog wheel do send MIDI control events are made by
us428control.
>
> It's the PCM audio part that gets me worried. ALSA reports both capture
> and playback PCM interfaces. But on all my tests I could only ear silence.
> Not a sound. Dead silence only. Although it all seems to be OK, at least
> as reported by ALSA.
us428 MASTER Slider behaves funny here:
if it is set to MAXIMUM at Firmware BootUp, it tells us428control that it is
ZEROed!
To hear audio here I have to set MASTER Fader below MAX first.
Later I can put it to MAX and it behaves as expected.
>
> Quite traditionally this symptom is due to initially default muted mixer
> channels, but running `alsamixer -c1` reports that there's no mixer elems.
> So how can I unmute this beast?
>
Hope the above helps. Mixer support isn't yet written, sorry.
To see if capturing works:
can you record a file and it looks like expected in an audio editor?
(UHCI worked more often than OHCI, but also UHCI can be tricky:
on a via mobo one connector does it, but the other not !?!)
Cheers,
Karsten
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Tascam US-224 support: MIDI OK, Audio KO?
2004-03-29 11:34 Tascam US-224 support: MIDI OK, Audio KO? Rui Nuno Capela
2004-03-29 19:29 ` Karsten Wiese
@ 2004-03-29 20:00 ` Martin Langer
1 sibling, 0 replies; 18+ messages in thread
From: Martin Langer @ 2004-03-29 20:00 UTC (permalink / raw)
To: Rui Nuno Capela; +Cc: alsa-devel
On Mon, Mar 29, 2004 at 12:34:25PM +0100, Rui Nuno Capela wrote:
>
> My first question goes whether us428control's not recognizing any USx2y
> hardware dependant stuff (hwdep) either on hw:0 or hw:1. I'm almost sure
> that it should be on hw:1 as the US-224 is configured as my second
> soundcard under the ALSA configuration (i.e. alias snd-usb-usx2y
> snd-card-1). But us428control does not find anything, at least after the
> firmware gets loaded.
>
I remember a hint by Karsten:
try to get us428control running first. if us224 is very similar to 428,
you'll get a printout of lots of control numbers if you use the controls and
have started us428control with option -v2.
> Strange enough, to me at least, us428control seems to work between the fw
> and fpga loading steps. Using lsusb, I've noticed that the USB ids do
> change from 1604:8004 to 1604:8005 while plugging in. Guess that's normal,
> and it marks the momemt when fw is loaded and fpga is about to.
It's normal. If the fw step is ok, a reset of the device will be executed.
Then it says hello with another new ID 8005.
>
> The second one is about the LEDs on the control surface: besides the USB
> light, isn't that supposed to light up anything else? Everything else is
> dead dark. Touching the knobs, pushing the buttons or whatever doesn't
> make any visible difference. Is that supposed to be normal?
No control without us428control.
> OK. I've tested on two different systems, a Compaq laptop w/Mandrake 10.0
> (P4 2.533GHz, OHCI) and on a custom desktop w/SUSE 9.0 (P4 3.333GHz
> SMP/HT, UHCI). On both, the firmware seems to get loaded and only visible
> thing to note is that the USB light gets lit.
BTW: The OHCI bug (pointed out by Clemens) is still in the code.
http://www.mail-archive.com/alsa-devel@lists.sourceforge.net/msg11899.html
> Mar 28 23:33:39 gamma-suse1 kernel: usb 2-1: control timeout on ep0in
Looks like disconnecting the former ID hangs somehow. Or do I misunderstand
this message here.
bye,
martin
--
Living on earth may be expensive,
but it includes an annual free trip around the sun.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Tascam US-224 support: MIDI OK, Audio KO?
2004-03-29 19:29 ` Karsten Wiese
@ 2004-03-29 21:41 ` Rui Nuno Capela
2004-03-29 23:51 ` alsa-driver-1.0.4rc1 missing snd-usb-usx2y ? Rui Nuno Capela
2004-03-29 23:57 ` Tascam US-224 support: MIDI OK, Audio KO? Karsten Wiese
0 siblings, 2 replies; 18+ messages in thread
From: Rui Nuno Capela @ 2004-03-29 21:41 UTC (permalink / raw)
To: alsa-devel
Hi Karsten, Martin,
Karsten wrote:
> I only have a us428 here, so I assume us224 behaves the same.
>
> could it be it is already running (started by hotpug scripts which were
> installed with alsa)?
> Did you try "ps -aux|grep us428control" ?
> aconnect -li gave you among others
> client 129: 'US-428' [type=user]
> 0 'Controls '
> this usually is due to us428controls activity.
>>
Yes us428control is indeed already running, spawned by the hotplug scripts
alright. How could I miss that? :)
OK. The first thing I tried then was killing it and restarting it by hand:
us428control -v2 -D hw:1
By tweaking some knobs and faders it seems that its working. I have the
verbose feedback OK, or so I think. Below, you can find some data that
I've collected here. Please check if it's the same or similar that you
find for the US-428.
>>
>> The second one is about the LEDs on the control surface: besides the
>> USB light, isn't that supposed to light up anything else? Everything
>> else is dead dark. Touching the knobs, pushing the buttons or whatever
>> doesn't make any visible difference. Is that supposed to be normal?
>
> if us428control is running ok (AND fits the us224), INPUT MONITOR Led
> is functional.
Nope. INPUT MONITOR never gets lit, despite the verbose output of
us428control saying otherwise (see below).
> Also if INPUT MONITOR Led is ON, SELECT and MUTE Leds work.
>
Neither of those leds get ON, no matter how much I try to play with them.
Only darkness I see.
> us428 MASTER Slider behaves funny here:
> if it is set to MAXIMUM at Firmware BootUp, it tells us428control
> that it is ZEROed!
> To hear audio here I have to set MASTER Fader below MAX first.
> Later I can put it to MAX and it behaves as expected.
>
Tried several positions. Can't hear a thing. No output, only silence
> Hope the above helps. Mixer support isn't yet written, sorry.
>
Hmmm. Is it planned any time soon? Can I help in any way?
> To see if capturing works:
> can you record a file and it looks like expected in an audio editor?
>
YES. Capture works. I've tested with `arecord -D hw:1 take1.wav` and I can
hear my guitar. Obviously I had to feed the captured file into the onboard
soundcard to get to ear it.
After all, it's only playback that's missing. Oh, and no leds too.
> (UHCI worked more often than OHCI, but also UHCI can be tricky:
> on a via mobo one connector does it, but the other not !?!)
>
As I noted, I'm testing on two quite different machines, a desktop and a
laptop. The desktop one seems to be using UHCI (although ohci, uhci and
ehci modules are all loaded in). The laptop one is OHCI for sure and only.
AFAICT, the behaviour is quite the same on either system. No playback
sound, at least via PHONES output.
Now follows the data I collected while watching `us428control -v2 -D hw:1`
output. Hope it sheds some light.
-- Jog wheel:
poll returned 0x1
Last is 0
00
poll returned 0x1
Last is 1
01
poll returned 0x1
Last is 2
02
. .
. .
. .
poll returned 0x1
Last is 15
xx
-- [INPUT MONITOR] button:
poll returned 0x1
Last is 1
01 00 00 00 06 00 00 00 00 00 xx
Knob InputMonitor now 1 Light is 1
poll returned 0x1
Last is 2
00 00 00 00 06 00 00 00 00 00 xx
Knob InputMonitor now 0 Light is 1
-- [INPUT MONITOR] button (twice):
poll returned 0x1
Last is 4
01 00 00 00 06 00 00 00 00 00 xx
Knob InputMonitor now 1 Light is 0
poll returned 0x1
Last is 5
00 00 00 00 06 00 00 00 00 00 xx
Knob InputMonitor now 0 Light is 0
-- [NULL] button:
poll returned 0x1
Last is 6
80 00 00 00 00 06 00 00 00 00 00 xx
Knob 79 now 1
poll returned 0x1
Last is 7
00 00 00 00 00 06 00 00 00 00 00 xx
Knob 79 now 0
-- [<< LOCATE] button:
poll returned 0x1
Last is 9
08 00 00 00 06 00 00 00 00 00 xx
Knob 83 now 1
poll returned 0x1
Last is 10
00 00 00 00 06 00 00 00 00 00 xx
Knob 83 now 0
-- [LOCATE >>] button:
poll returned 0x1
Last is 1
10 00 00 00 06 00 00 00 00 00 xx
Knob 84 now 1
poll returned 0x1
Last is 2
00 00 00 00 06 00 00 00 00 00 xx
Knob 84 now 0
-- [SET] button:
poll returned 0x1
Last is 3
20 00 00 00 06 00 00 00 00 00 xx
Knob 85 now 1
poll returned 0x1
Last is 4
00 00 00 00 06 00 00 00 00 00 xx
Knob 85 now 0
-- [< BANK] button:
poll returned 0x1
Last is 7
02 00 00 00 06 00 00 00 00 00 xx
Knob 81 now 1
poll returned 0x1
Last is 8
00 00 00 00 06 00 00 00 00 00 xx
Knob 81 now 0
-- [BANK >] button:
poll returned 0x1
Last is 9
04 00 00 00 06 00 00 00 00 00 xx
Knob 82 now 1
poll returned 0x1
Last is 10
00 00 00 00 06 00 00 00 00 00 xx
Knob 82 now 0
-- [REW] button:
poll returned 0x1
Last is 11
10 00 00 00 00 06 00 00 00 00 00 xx
Knob 76 now 1
poll returned 0x1
Last is 12
00 00 00 00 00 06 00 00 00 00 00 xx
Knob 76 now 0
-- [F FWD] button:
poll returned 0x1
Last is 13
08 00 00 00 00 06 00 00 00 00 00 xx
Knob 75 now 1
poll returned 0x1
Last is 14
00 00 00 00 00 06 00 00 00 00 00 xx
Knob 75 now 0
-- [STOP] button:
poll returned 0x1
Last is 15
04 00 00 00 00 06 00 00 00 00 00 xx
Knob 74 now 1
poll returned 0x1
Last is 0
00 00 00 00 00 06 00 00 00 00 00 xx
Knob 74 now 0
-- [PLAY] button:
poll returned 0x1
Last is 1
02 00 00 00 00 06 00 00 00 00 00 xx
Knob 73 now 1
poll returned 0x1
Last is 2
00 00 00 00 00 06 00 00 00 00 00 xx
Knob 73 now 0
-- [RECORD] button:
poll returned 0x1
Last is 3
01 00 00 00 00 06 00 00 00 00 00 xx
Knob 72 now 1
poll returned 0x1
Last is 4
00 00 00 00 00 06 00 00 00 00 00 xx
Knob 72 now 0
-- Channel controls:
poll returned 0x1
Last is 1
f1 f2 f3 f4 fm 00 00 00 00 00 00 00 ss mm 06 00 00 00 00 00 xx
where:
f1..4 - each one of the 4 channel faders
fm - master fader
mm - [MUTE] button (bitflag 00=1,..08=4)
ss - [SELECT] button (bitflag 00=1,..08=4)
-- [SOLO] button:
poll returned 0x1
Last is 2
20 00 00 00 00 06 00 00 00 00 00 xx
Knob 77 now 1
poll returned 0x1
Last is 3
00 00 00 00 00 06 00 00 00 00 00 xx
Knob 77 now 0
-- [REC] button:
poll returned 0x1
Last is 4
40 00 00 00 00 06 00 00 00 00 00 xx
Knob 78 now 1
poll returned 0x1
Last is 5
00 00 00 00 00 06 00 00 00 00 00 xx
Knob 78 now 0
--
OK. That's all for today,
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc@rncbc.org
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
^ permalink raw reply [flat|nested] 18+ messages in thread
* alsa-driver-1.0.4rc1 missing snd-usb-usx2y ?
2004-03-29 21:41 ` Rui Nuno Capela
@ 2004-03-29 23:51 ` Rui Nuno Capela
2004-03-30 7:35 ` [Alsa-user] " Jaroslav Kysela
2004-03-29 23:57 ` Tascam US-224 support: MIDI OK, Audio KO? Karsten Wiese
1 sibling, 1 reply; 18+ messages in thread
From: Rui Nuno Capela @ 2004-03-29 23:51 UTC (permalink / raw)
To: alsa-devel; +Cc: alsa-user
Hi,
Just checked out 1.0.4rc1 a few moments ago and I'm already missing the
snd-usb-usx2y module. AFAICT it's not being included by
./configure --with-cards option, nor it gets built when one sets
--with-cards=all.
I am quite sure this was being built as of 1.0.3 and before. The source
files are in fact on the tarball, but aren't picked up by the build
process, at least as I use to, nor does it appear on ./configure --help
anymore.
Maybe I'm doing something fundamentally wrong. My ol'time build steps used
to be just the following:
./configure --with-isapnp=no --with-sequencer=yes --with-oss=yes
--with-cards=all
make
make install
Am I missing some fine print since 1.0.3 release? The above worked out
simply fine until then.
Now that I'm with a US-224 on my hands for going after some party, this
feels somewhat unconfortable if not disappointing. Is this intentional or
just some mistake?
Bye.
--
rncbc aka Rui Nuno Capela
rncbc@rncbc.org
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Tascam US-224 support: MIDI OK, Audio KO?
2004-03-29 21:41 ` Rui Nuno Capela
2004-03-29 23:51 ` alsa-driver-1.0.4rc1 missing snd-usb-usx2y ? Rui Nuno Capela
@ 2004-03-29 23:57 ` Karsten Wiese
2004-03-30 8:14 ` Rui Nuno Capela
2004-03-30 21:19 ` Rui Nuno Capela
1 sibling, 2 replies; 18+ messages in thread
From: Karsten Wiese @ 2004-03-29 23:57 UTC (permalink / raw)
To: alsa-devel; +Cc: Rui Nuno Capela
Hi Rui,
please try to enable audio out with "us428control -v2 -D hw:1" like this:
- toggle INPUT MONITOR until us428control says "...Light is 1"
- then move Fader3 to max and play some audio.
This is just a guess assuming audio out is mapped on us224 internal mixer 2,
input monitor channel 1 is mapped on us224 internal mixer 0 and input
monitor channel 2 is mapped on us224 internal mixer 1.
- Please also try your guitar on both inputs: move faders 1 & 2 to see if
sound is routed to the outputs.
We have to tweak us428control to add real us224 support.
Above is just to verify that the current us428 internal mixer mechanics is
usable for the us224.
Concerning us224's Lights I'm currently left in the dark....
For us428 I found that a 7Byte long USB-Message on pipe 4 is a Lights set
command, while a 5Byte long is an internal mixer set command.
You could tweak us428control to toggle the 0'th light instead of the 25'th
light, which is InputMonitor Light on us428. the 0th light is Select Channel
1 on the us428.
Exchange Cus428State.cc Line 118 , 119
Light[0].Value = StateInputMonitor() ? SelectInputMonitor : Select;
Light[2].Value = StateInputMonitor() ? MuteInputMonitor : Mute;
for
Light[0].Value = 0x55;
Light[2].Value = 0xAA;
to check light mechanics.
If there's still no lights, some usb snooping on windoz might help.
I've some specially tuned stuff here which I could send you then.
cheers,
Karsten
Am Montag 29 März 2004 23:41 schrieb Rui Nuno Capela:
> Hi Karsten, Martin,
>
> Karsten wrote:
> > I only have a us428 here, so I assume us224 behaves the same.
> >
> > could it be it is already running (started by hotpug scripts which were
> > installed with alsa)?
> > Did you try "ps -aux|grep us428control" ?
> > aconnect -li gave you among others
> > client 129: 'US-428' [type=user]
> > 0 'Controls '
> > this usually is due to us428controls activity.
>
> Yes us428control is indeed already running, spawned by the hotplug scripts
> alright. How could I miss that? :)
>
> OK. The first thing I tried then was killing it and restarting it by hand:
>
> us428control -v2 -D hw:1
>
> By tweaking some knobs and faders it seems that its working. I have the
> verbose feedback OK, or so I think. Below, you can find some data that
> I've collected here. Please check if it's the same or similar that you
> find for the US-428.
>
> >> The second one is about the LEDs on the control surface: besides the
> >> USB light, isn't that supposed to light up anything else? Everything
> >> else is dead dark. Touching the knobs, pushing the buttons or whatever
> >> doesn't make any visible difference. Is that supposed to be normal?
> >
> > if us428control is running ok (AND fits the us224), INPUT MONITOR Led
> > is functional.
>
> Nope. INPUT MONITOR never gets lit, despite the verbose output of
> us428control saying otherwise (see below).
>
> > Also if INPUT MONITOR Led is ON, SELECT and MUTE Leds work.
>
> Neither of those leds get ON, no matter how much I try to play with them.
> Only darkness I see.
>
> > us428 MASTER Slider behaves funny here:
> > if it is set to MAXIMUM at Firmware BootUp, it tells us428control
> > that it is ZEROed!
> > To hear audio here I have to set MASTER Fader below MAX first.
> > Later I can put it to MAX and it behaves as expected.
>
> Tried several positions. Can't hear a thing. No output, only silence
>
> > Hope the above helps. Mixer support isn't yet written, sorry.
>
> Hmmm. Is it planned any time soon? Can I help in any way?
>
> > To see if capturing works:
> > can you record a file and it looks like expected in an audio editor?
>
> YES. Capture works. I've tested with `arecord -D hw:1 take1.wav` and I can
> hear my guitar. Obviously I had to feed the captured file into the onboard
> soundcard to get to ear it.
>
> After all, it's only playback that's missing. Oh, and no leds too.
>
> > (UHCI worked more often than OHCI, but also UHCI can be tricky:
> > on a via mobo one connector does it, but the other not !?!)
>
> As I noted, I'm testing on two quite different machines, a desktop and a
> laptop. The desktop one seems to be using UHCI (although ohci, uhci and
> ehci modules are all loaded in). The laptop one is OHCI for sure and only.
>
> AFAICT, the behaviour is quite the same on either system. No playback
> sound, at least via PHONES output.
>
>
> Now follows the data I collected while watching `us428control -v2 -D hw:1`
> output. Hope it sheds some light.
>
>
> -- Jog wheel:
>
> poll returned 0x1
> Last is 0
> 00
> poll returned 0x1
> Last is 1
> 01
> poll returned 0x1
> Last is 2
> 02
> . .
> . .
> . .
> poll returned 0x1
> Last is 15
> xx
>
> -- [INPUT MONITOR] button:
>
> poll returned 0x1
> Last is 1
> 01 00 00 00 06 00 00 00 00 00 xx
> Knob InputMonitor now 1 Light is 1
> poll returned 0x1
> Last is 2
> 00 00 00 00 06 00 00 00 00 00 xx
> Knob InputMonitor now 0 Light is 1
>
>
> -- [INPUT MONITOR] button (twice):
>
> poll returned 0x1
> Last is 4
> 01 00 00 00 06 00 00 00 00 00 xx
> Knob InputMonitor now 1 Light is 0
> poll returned 0x1
> Last is 5
> 00 00 00 00 06 00 00 00 00 00 xx
> Knob InputMonitor now 0 Light is 0
>
>
> -- [NULL] button:
>
> poll returned 0x1
> Last is 6
> 80 00 00 00 00 06 00 00 00 00 00 xx
> Knob 79 now 1
> poll returned 0x1
> Last is 7
> 00 00 00 00 00 06 00 00 00 00 00 xx
> Knob 79 now 0
>
>
> -- [<< LOCATE] button:
>
> poll returned 0x1
> Last is 9
> 08 00 00 00 06 00 00 00 00 00 xx
> Knob 83 now 1
> poll returned 0x1
> Last is 10
> 00 00 00 00 06 00 00 00 00 00 xx
> Knob 83 now 0
>
>
> -- [LOCATE >>] button:
>
> poll returned 0x1
> Last is 1
> 10 00 00 00 06 00 00 00 00 00 xx
> Knob 84 now 1
> poll returned 0x1
> Last is 2
> 00 00 00 00 06 00 00 00 00 00 xx
> Knob 84 now 0
>
>
> -- [SET] button:
>
> poll returned 0x1
> Last is 3
> 20 00 00 00 06 00 00 00 00 00 xx
> Knob 85 now 1
> poll returned 0x1
> Last is 4
> 00 00 00 00 06 00 00 00 00 00 xx
> Knob 85 now 0
>
>
> -- [< BANK] button:
>
> poll returned 0x1
> Last is 7
> 02 00 00 00 06 00 00 00 00 00 xx
> Knob 81 now 1
> poll returned 0x1
> Last is 8
> 00 00 00 00 06 00 00 00 00 00 xx
> Knob 81 now 0
>
>
> -- [BANK >] button:
>
> poll returned 0x1
> Last is 9
> 04 00 00 00 06 00 00 00 00 00 xx
> Knob 82 now 1
> poll returned 0x1
> Last is 10
> 00 00 00 00 06 00 00 00 00 00 xx
> Knob 82 now 0
>
>
> -- [REW] button:
>
> poll returned 0x1
> Last is 11
> 10 00 00 00 00 06 00 00 00 00 00 xx
> Knob 76 now 1
> poll returned 0x1
> Last is 12
> 00 00 00 00 00 06 00 00 00 00 00 xx
> Knob 76 now 0
>
>
> -- [F FWD] button:
>
> poll returned 0x1
> Last is 13
> 08 00 00 00 00 06 00 00 00 00 00 xx
> Knob 75 now 1
> poll returned 0x1
> Last is 14
> 00 00 00 00 00 06 00 00 00 00 00 xx
> Knob 75 now 0
>
>
> -- [STOP] button:
>
> poll returned 0x1
> Last is 15
> 04 00 00 00 00 06 00 00 00 00 00 xx
> Knob 74 now 1
> poll returned 0x1
> Last is 0
> 00 00 00 00 00 06 00 00 00 00 00 xx
> Knob 74 now 0
>
>
> -- [PLAY] button:
>
> poll returned 0x1
> Last is 1
> 02 00 00 00 00 06 00 00 00 00 00 xx
> Knob 73 now 1
> poll returned 0x1
> Last is 2
> 00 00 00 00 00 06 00 00 00 00 00 xx
> Knob 73 now 0
>
>
> -- [RECORD] button:
>
> poll returned 0x1
> Last is 3
> 01 00 00 00 00 06 00 00 00 00 00 xx
> Knob 72 now 1
> poll returned 0x1
> Last is 4
> 00 00 00 00 00 06 00 00 00 00 00 xx
> Knob 72 now 0
>
>
> -- Channel controls:
>
> poll returned 0x1
> Last is 1
> f1 f2 f3 f4 fm 00 00 00 00 00 00 00 ss mm 06 00 00 00 00 00 xx
>
> where:
>
> f1..4 - each one of the 4 channel faders
> fm - master fader
> mm - [MUTE] button (bitflag 00=1,..08=4)
> ss - [SELECT] button (bitflag 00=1,..08=4)
>
>
> -- [SOLO] button:
>
> poll returned 0x1
> Last is 2
> 20 00 00 00 00 06 00 00 00 00 00 xx
> Knob 77 now 1
> poll returned 0x1
> Last is 3
> 00 00 00 00 00 06 00 00 00 00 00 xx
> Knob 77 now 0
>
>
> -- [REC] button:
>
> poll returned 0x1
> Last is 4
> 40 00 00 00 00 06 00 00 00 00 00 xx
> Knob 78 now 1
> poll returned 0x1
> Last is 5
> 00 00 00 00 00 06 00 00 00 00 00 xx
> Knob 78 now 0
>
>
> --
> OK. That's all for today,
>
>
> Cheers.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Alsa-user] alsa-driver-1.0.4rc1 missing snd-usb-usx2y ?
2004-03-29 23:51 ` alsa-driver-1.0.4rc1 missing snd-usb-usx2y ? Rui Nuno Capela
@ 2004-03-30 7:35 ` Jaroslav Kysela
2004-03-30 7:49 ` Rui Nuno Capela
0 siblings, 1 reply; 18+ messages in thread
From: Jaroslav Kysela @ 2004-03-30 7:35 UTC (permalink / raw)
To: Rui Nuno Capela; +Cc: alsa-devel
On Tue, 30 Mar 2004, Rui Nuno Capela wrote:
> Hi,
>
> Just checked out 1.0.4rc1 a few moments ago and I'm already missing the
> snd-usb-usx2y module. AFAICT it's not being included by
> ./configure --with-cards option, nor it gets built when one sets
> --with-cards=all.
It is fixed in CVS now. Thanks.
Jaroslav
-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Alsa-user] alsa-driver-1.0.4rc1 missing snd-usb-usx2y ?
2004-03-30 7:35 ` [Alsa-user] " Jaroslav Kysela
@ 2004-03-30 7:49 ` Rui Nuno Capela
2004-03-30 20:51 ` Rui Nuno Capela
0 siblings, 1 reply; 18+ messages in thread
From: Rui Nuno Capela @ 2004-03-30 7:49 UTC (permalink / raw)
To: alsa-devel
Jaroslav Kysela wrote:
>>
>> Just checked out 1.0.4rc1 a few moments ago and I'm already missing the
>> snd-usb-usx2y module. AFAICT it's not being included by
>> ./configure --with-cards option, nor it gets built when one sets
>> --with-cards=all.
>
> It is fixed in CVS now. Thanks.
OK. Now my gut feeling went away :)
Thanks.
--
rncbc aka Rui Nuno Capela
rncbc@rncbc.org
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Tascam US-224 support: MIDI OK, Audio KO?
2004-03-29 23:57 ` Tascam US-224 support: MIDI OK, Audio KO? Karsten Wiese
@ 2004-03-30 8:14 ` Rui Nuno Capela
2004-03-30 11:39 ` Karsten Wiese
2004-03-30 21:19 ` Rui Nuno Capela
1 sibling, 1 reply; 18+ messages in thread
From: Rui Nuno Capela @ 2004-03-30 8:14 UTC (permalink / raw)
To: alsa-devel
Karsten,
>
> please try to enable audio out with "us428control -v2 -D hw:1" like this:
>
> - toggle INPUT MONITOR until us428control says "...Light is 1"
>
Yes, it does say "... Light is 1", but NO light on the LED.
> - then move Fader3 to max and play some audio.
> This is just a guess assuming audio out is mapped on us224 internal mixer
> 2, input monitor channel 1 is mapped on us224 internal mixer 0 and input
> monitor channel 2 is mapped on us224 internal mixer 1.
>
Nothing is heard.
> - Please also try your guitar on both inputs: move faders 1 & 2 to see if
> sound is routed to the outputs.
>
Again, nothing seems to be routed. No signal appears on output. Have
tryied on both guitar inputs (A and B), with several combinations and
fader positions, but can hear a thing.
>
> We have to tweak us428control to add real us224 support.
I guess that will be really necessary to have a proper us224control :)
> Above is just to verify that the current us428 internal mixer mechanics is
> usable for the us224.
>
It seems that it is not quite straightforward, isn't it? Is there any
other US-224 user out there to at least confirm all this? It surely ain't
nice this feeling of lonelyness ;) but I will prevail =:O
> Concerning us224's Lights I'm currently left in the dark....
So do the LEDs ;)
> For us428 I found that a 7Byte long USB-Message on pipe 4 is a Lights set
> command, while a 5Byte long is an internal mixer set command.
> You could tweak us428control to toggle the 0'th light instead of the 25'th
> light, which is InputMonitor Light on us428. the 0th light is Select
> Channel 1 on the us428.
> Exchange Cus428State.cc Line 118 , 119
> Light[0].Value = StateInputMonitor() ? SelectInputMonitor : Select;
> Light[2].Value = StateInputMonitor() ? MuteInputMonitor : Mute;
> for
> Light[0].Value = 0x55;
> Light[2].Value = 0xAA;
> to check light mechanics.
>
I'll try this tonight, rest assured.
> If there's still no lights, some usb snooping on windoz might help.
> I've some specially tuned stuff here which I could send you then.
>
That's of course a very good idea. Please do so ASAP.
I'll be very pleased to follow your instructions and get a thorough
profile on this. My laptop has a working winxp partition installed and the
US-224 (audio mixer leds) works there as designed, but that's hardly a
surprise for anyone :)
Cheers,
--
rncbc aka Rui Nuno Capela
rncbc@rncbc.org
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Tascam US-224 support: MIDI OK, Audio KO?
2004-03-30 8:14 ` Rui Nuno Capela
@ 2004-03-30 11:39 ` Karsten Wiese
2004-03-30 12:29 ` Rui Nuno Capela
0 siblings, 1 reply; 18+ messages in thread
From: Karsten Wiese @ 2004-03-30 11:39 UTC (permalink / raw)
To: alsa-devel; +Cc: Rui Nuno Capela
[-- Attachment #1: Type: text/plain, Size: 1869 bytes --]
Am Dienstag 30 März 2004 10:14 schrieb Rui Nuno Capela:
>
> > If there's still no lights, some usb snooping on windoz might help.
> > I've some specially tuned stuff here which I could send you then.
>
> That's of course a very good idea. Please do so ASAP.
>
> I'll be very pleased to follow your instructions and get a thorough
> profile on this. My laptop has a working winxp partition installed and the
> US-224 (audio mixer leds) works there as designed, but that's hardly a
> surprise for anyone :)
>
The real stuff is too big for the list, I'll send it to you seperatly.
It is a modified (changed filter-driver, added ListeningPipe app) usb snooper.
modified so I get (filtered) output consisting of sent/received data in a c
header-file.
It works for me on win2k/vc6 only; haven't tried it on xp yet.
Quick & Dirty Instructions:
Install the filter driver
filter/release2k/usbsnoop.sys
like in standard usb snoopy of that version. (Detailed Instructions somewhere
@ sf.net if not in the zip)
enable filter -driver with standard ui app. see attached jpg.
Switch On us224.
Start ListeningPipe/Release/ListeningPipe.exe.
It will (hopefully) create a BIG file fw.h containing everything it snoops &
dump first occurances of messages to stdout.
Pipe stdout to a file to capture infos, while you do something with the us224.
to get best results, switch off us224 to end "ListeningPipe.exe>somefile".
you can also control-c, but then somefile is not complete. some bugs there
still.
take f1up_m1.h as an example :
preconditions:
us428 switch on, INPUT MONITOR Light activ. Other LEDs OFF.
Fader 1 @ Minimum.
Started ListeningPipe.exe in a shell like this:
ListeningPipe>f1up_m1.h
Moved Fader 1 up (1/5 Full scale).
Switched Mute 1 ON.
Switched off us428. ListeningPipe finished ok.
Cheers,
Karsten
[-- Attachment #2: ui.jpg --]
[-- Type: image/jpeg, Size: 22704 bytes --]
[-- Attachment #3: f1up_m1.h --]
[-- Type: text/x-chdr, Size: 8739 bytes --]
//Pipe Connected!
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@2F090C, len=0x15
{ 0x01, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@2F0BBC, len=0xE
{ 0x19, 0x08, 0x1A, 0x00, 0x1B, 0x00, 0x1C, 0x02, 0x1D, 0x01, 0x1E, 0x00, 0x1F, 0x00,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@43821C, len=0x15
{ 0x03, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@2F0D54, len=0x5
{ 0x00, 0x00, 0x09, 0x00, 0x0A,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@2F0B14, len=0x15
{ 0x05, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@2FEF7C, len=0x5
{ 0x00, 0x00, 0x13, 0x00, 0x14,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@452ECC, len=0x15
{ 0x07, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@452F6C, len=0x5
{ 0x00, 0x00, 0x1D, 0x00, 0x1E,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@449EB4, len=0x15
{ 0x09, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@449F3C, len=0x5
{ 0x00, 0x00, 0x26, 0x00, 0x28,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@449FDC, len=0x15
{ 0x0B, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@43DF04, len=0x5
{ 0x00, 0x00, 0x30, 0x00, 0x32,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@43DFA4, len=0x15
{ 0x0D, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@437EBC, len=0x5
{ 0x00, 0x00, 0x3A, 0x00, 0x3C,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@437F5C, len=0x15
{ 0x0F, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@2F813C, len=0x5
{ 0x00, 0x00, 0x43, 0x00, 0x46,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@4A4E44, len=0x15
{ 0x11, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@2F819C, len=0x5
{ 0x00, 0x00, 0x4D, 0x00, 0x50,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@2F823C, len=0x15
{ 0x13, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@486E84, len=0x5
{ 0x00, 0x00, 0x57, 0x00, 0x5A,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@486EFC, len=0x15
{ 0x15, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@486F7C, len=0x5
{ 0x00, 0x00, 0x61, 0x00, 0x64,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@4B0ECC, len=0x15
{ 0x17, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@4B0F54, len=0x5
{ 0x00, 0x00, 0x6A, 0x00, 0x6E,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@4A5E94, len=0x15
{ 0x19, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@4A5EFC, len=0x5
{ 0x00, 0x00, 0x75, 0x00, 0x78,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@49C244, len=0x15
{ 0x1B, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@4A5FD4, len=0x5
{ 0x00, 0x00, 0x80, 0x00, 0x84,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@449A64, len=0x15
{ 0x1D, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@473F04, len=0x5
{ 0x00, 0x00, 0x8C, 0x00, 0x90,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@473FA4, len=0x15
{ 0x1F, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@430E9C, len=0x5
{ 0x00, 0x00, 0x98, 0x00, 0x9D,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@430F3C, len=0x15
{ 0x21, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@430FDC, len=0x5
{ 0x00, 0x00, 0xB0, 0x00, 0xB6,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@452A64, len=0x15
{ 0x21, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x01, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@2FE3F4, len=0x5
{ 0x00, 0x00, 0x00, 0x00, 0x00,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW Data@2FE484, len=0xE
{ 0x19, 0x08, 0x1A, 0x00, 0x1B, 0x01, 0x1C, 0x02, 0x1D, 0x01, 0x1E, 0x00, 0x1F, 0x00,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW Data@452A3C, len=0x15
{ 0x21, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x06, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 02 URB_FUNCTION_ABORT_PIPE
// _URB_HEADER 1E URB_FUNCTION_RESET_PIPE
// _URB_HEADER 1E URB_FUNCTION_RESET_PIPE
// _URB_HEADER 02 URB_FUNCTION_ABORT_PIPE
// _URB_HEADER 1E URB_FUNCTION_RESET_PIPE
// _URB_HEADER 1E URB_FUNCTION_RESET_PIPE
// _URB_HEADER 02 URB_FUNCTION_ABORT_PIPE
// _URB_HEADER 1E URB_FUNCTION_RESET_PIPE
// _URB_HEADER 1E URB_FUNCTION_RESET_PIPE
// _URB_HEADER 02 URB_FUNCTION_ABORT_PIPE
// _URB_HEADER 1E URB_FUNCTION_RESET_PIPE
// _URB_HEADER 1E URB_FUNCTION_RESET_PIPE
// _URB_HEADER 02 URB_FUNCTION_ABORT_PIPE
// _URB_HEADER 1E URB_FUNCTION_RESET_PIPE
// _URB_HEADER 02 URB_FUNCTION_ABORT_PIPE
// _URB_HEADER 02 URB_FUNCTION_ABORT_PIPE
// _URB_HEADER 02 URB_FUNCTION_ABORT_PIPE
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x86
// NEW Data@509F1C, len=0x40
{ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
};
// _URB_HEADER 02 URB_FUNCTION_ABORT_PIPE
// _URB_HEADER 1E URB_FUNCTION_RESET_PIPE
//Fehler: The pipe has been ended.
exiting
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Tascam US-224 support: MIDI OK, Audio KO?
2004-03-30 11:39 ` Karsten Wiese
@ 2004-03-30 12:29 ` Rui Nuno Capela
2004-03-30 19:14 ` Karsten Wiese
0 siblings, 1 reply; 18+ messages in thread
From: Rui Nuno Capela @ 2004-03-30 12:29 UTC (permalink / raw)
To: alsa-devel
[-- Attachment #1: Type: text/plain, Size: 357 bytes --]
Hi Karsten,
Already grabbed and installed SnoopyPro-0.22 from
http://sourceforge.net/projects/usbsnoop . Guess it's what you mentioned.
See on attachment a screenshot right after sniffer installation. If that's
right, you probably don't need to send everything, just the ListeningPipe
utility. OK?
Cheers,
--
rncbc aka Rui Nuno Capela
rncbc@rncbc.org
[-- Attachment #2: USB224_Snoop1.png --]
[-- Type: image/x-png, Size: 12082 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Tascam US-224 support: MIDI OK, Audio KO?
2004-03-30 12:29 ` Rui Nuno Capela
@ 2004-03-30 19:14 ` Karsten Wiese
2004-03-30 19:32 ` Rui Nuno Capela
0 siblings, 1 reply; 18+ messages in thread
From: Karsten Wiese @ 2004-03-30 19:14 UTC (permalink / raw)
To: alsa-devel
Am Dienstag 30 März 2004 14:29 schrieb Rui Nuno Capela:
> Hi Karsten,
>
> Already grabbed and installed SnoopyPro-0.22 from
> http://sourceforge.net/projects/usbsnoop . Guess it's what you mentioned.
>
> See on attachment a screenshot right after sniffer installation. If that's
> right, you probably don't need to send everything, just the ListeningPipe
> utility. OK?
Hi Rui,
screenshot looks ok. I don't know SnoopyPro-0.22.
I think I took an older version from somewhere on the web & modified it
heavyly.....
maybe SnoopyPro-0.22 can also do what my ListeningPipe app can:
Dump any different telegram only the first time it is being transmitted.
the usb is in constant usage, so if you need to find a special teloegram that
onlyx occurs if you do something, it can be quit hard work to find out the
exact telegram.
If you want ListeningPipe, you have to also use the filter-driver that came
with the zip file. At least so I think...
Cheers,
Karsten
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Tascam US-224 support: MIDI OK, Audio KO?
2004-03-30 19:14 ` Karsten Wiese
@ 2004-03-30 19:32 ` Rui Nuno Capela
2004-03-30 20:15 ` Karsten Wiese
0 siblings, 1 reply; 18+ messages in thread
From: Rui Nuno Capela @ 2004-03-30 19:32 UTC (permalink / raw)
To: Karsten Wiese; +Cc: alsa-devel
> screenshot looks ok. I don't know SnoopyPro-0.22.
I just picked it up from sf.net , as you suggested.
> I think I took an older version from somewhere on the web & modified it
> heavyly.....
> maybe SnoopyPro-0.22 can also do what my ListeningPipe app can:
> Dump any different telegram only the first time it is being transmitted.
> the usb is in constant usage, so if you need to find a special teloegram
> that onlyx occurs if you do something, it can be quit hard work to find
> out the exact telegram.
Hmmm. I think we better stick with your custom binaries and put aside that
SnoopyPro thing. AFAICT there's no filtering feature in it.
We better use the very same tools, otherwise things get weird, and no one
gets the blame ;)
> If you want ListeningPipe, you have to also use the filter-driver that
> came with the zip file. At least so I think...
Of course I do. Please apologize me, but I'm missing the zip file you're
mentioning. Have you sent it already?
Hope to.
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc@rncbc.org
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Tascam US-224 support: MIDI OK, Audio KO?
2004-03-30 19:32 ` Rui Nuno Capela
@ 2004-03-30 20:15 ` Karsten Wiese
0 siblings, 0 replies; 18+ messages in thread
From: Karsten Wiese @ 2004-03-30 20:15 UTC (permalink / raw)
To: alsa-devel; +Cc: Rui Nuno Capela
Am Dienstag 30 März 2004 21:32 schrieb Rui Nuno Capela:
> > screenshot looks ok. I don't know SnoopyPro-0.22.
>
> I just picked it up from sf.net , as you suggested.
>
> > I think I took an older version from somewhere on the web & modified it
> > heavyly.....
> > maybe SnoopyPro-0.22 can also do what my ListeningPipe app can:
> > Dump any different telegram only the first time it is being transmitted.
> > the usb is in constant usage, so if you need to find a special teloegram
> > that onlyx occurs if you do something, it can be quit hard work to find
> > out the exact telegram.
>
> Hmmm. I think we better stick with your custom binaries and put aside that
> SnoopyPro thing. AFAICT there's no filtering feature in it.
>
> We better use the very same tools, otherwise things get weird, and no one
> gets the blame ;)
>
> > If you want ListeningPipe, you have to also use the filter-driver that
> > came with the zip file. At least so I think...
>
> Of course I do. Please apologize me, but I'm missing the zip file you're
> mentioning. Have you sent it already?
i sent it 7 hours ago and now again.
I'd suggest you use my tool if it fits winxp & USB 2 (I mean the latest high
speed USB which your machine is equiped with?) which i don't know as i only
used it with win2k and the slower 10MBit/s USB.
I mean use what fits best ;-)
Just checked: The Mail with the zip is in my inbox again (CCed me), so it
should be in yours too soon:
"Rui Nuno Capela" <rncbc@rncbc.org>
It is 351 kBytes big, so i can't send it to alsa-devel list.
You have it?
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Alsa-user] alsa-driver-1.0.4rc1 missing snd-usb-usx2y ?
2004-03-30 7:49 ` Rui Nuno Capela
@ 2004-03-30 20:51 ` Rui Nuno Capela
2004-04-01 12:57 ` Karsten Wiese
0 siblings, 1 reply; 18+ messages in thread
From: Rui Nuno Capela @ 2004-03-30 20:51 UTC (permalink / raw)
To: alsa-devel
>>> the snd-usb-usx2y module. AFAICT it's not being included by
>>> ./configure --with-cards option, nor it gets built when one sets
>>> --with-cards=all.
>>
>> It is fixed in CVS now. Thanks.
>
Checked out today's alsa-driver-1.0.4rc2 where the missed snd-usb-usx2y
module gets built now.
However, I couldn't get it to load, dmesg gives:
snd_usb_usx2y: Unknown symbol snd_pcm_dma_flags
All other alsa packages are up to 1.0.4rc1 here.
Bye.
--
rncbc aka Rui Nuno Capela
rncbc@rncbc.org
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Tascam US-224 support: MIDI OK, Audio KO?
2004-03-29 23:57 ` Tascam US-224 support: MIDI OK, Audio KO? Karsten Wiese
2004-03-30 8:14 ` Rui Nuno Capela
@ 2004-03-30 21:19 ` Rui Nuno Capela
1 sibling, 0 replies; 18+ messages in thread
From: Rui Nuno Capela @ 2004-03-30 21:19 UTC (permalink / raw)
To: alsa-devel
Karsten,
>
> Concerning us224's Lights I'm currently left in the dark....
> For us428 I found that a 7Byte long USB-Message on pipe 4 is a Lights
> set command, while a 5Byte long is an internal mixer set command.
> You could tweak us428control to toggle the 0'th light instead of the
> 25'th light, which is InputMonitor Light on us428. the 0th light is
> Select Channel 1 on the us428.
> Exchange Cus428State.cc Line 118 , 119
> Light[0].Value = StateInputMonitor() ? SelectInputMonitor : Select;
> Light[2].Value = StateInputMonitor() ? MuteInputMonitor : Mute;
> for
> Light[0].Value = 0x55;
> Light[2].Value = 0xAA;
> to check light mechanics.
>
Made this tweak, and nothing changed. LEDs remain dark.
> If there's still no lights, some usb snooping on windoz might help.
> I've some specially tuned stuff here which I could send you then.
>
Let's go deep :)
--
rncbc aka Rui Nuno Capela
rncbc@rncbc.org
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Alsa-user] alsa-driver-1.0.4rc1 missing snd-usb-usx2y ?
2004-03-30 20:51 ` Rui Nuno Capela
@ 2004-04-01 12:57 ` Karsten Wiese
2004-04-01 15:01 ` Rui Nuno Capela
0 siblings, 1 reply; 18+ messages in thread
From: Karsten Wiese @ 2004-04-01 12:57 UTC (permalink / raw)
To: Rui Nuno Capela; +Cc: alsa-devel
Am Dienstag 30 März 2004 22:51 schrieb Rui Nuno Capela:
> >>> the snd-usb-usx2y module. AFAICT it's not being included by
> >>> ./configure --with-cards option, nor it gets built when one sets
> >>> --with-cards=all.
> >>
> >> It is fixed in CVS now. Thanks.
>
> Checked out today's alsa-driver-1.0.4rc2 where the missed snd-usb-usx2y
> module gets built now.
>
> However, I couldn't get it to load, dmesg gives:
>
> snd_usb_usx2y: Unknown symbol snd_pcm_dma_flags
>
> All other alsa packages are up to 1.0.4rc1 here.
>
CVS today: OK here with 2.4 and 2.6.5-rc3. Have you tried a fresh checkout?
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Alsa-user] alsa-driver-1.0.4rc1 missing snd-usb-usx2y ?
2004-04-01 12:57 ` Karsten Wiese
@ 2004-04-01 15:01 ` Rui Nuno Capela
0 siblings, 0 replies; 18+ messages in thread
From: Rui Nuno Capela @ 2004-04-01 15:01 UTC (permalink / raw)
To: alsa-devel
Karsten Wiese wrote:
>> >>> the snd-usb-usx2y module. AFAICT it's not being included by
>> >>> ./configure --with-cards option, nor it gets built when one sets
>> >>> --with-cards=all.
>> >>
>> >> It is fixed in CVS now. Thanks.
>>
>> Checked out today's alsa-driver-1.0.4rc2 where the missed snd-usb-usx2y
>> module gets built now.
>>
>> However, I couldn't get it to load, dmesg gives:
>>
>> snd_usb_usx2y: Unknown symbol snd_pcm_dma_flags
>>
>> All other alsa packages are up to 1.0.4rc1 here.
>>
> CVS today: OK here with 2.4 and 2.6.5-rc3. Have you tried a fresh
> checkout?
No I didn't, I was with the stock source tarballs. Haven't the time to
checkout from CVS, yet.
BTW, Karsten,
Haven't you check my latest messages that I recently sent to you about the
US-224 topic? Those that were being sent off the list. I'm still missing
your usbsnoop stuff.
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc@rncbc.org
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2004-04-01 15:01 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-29 11:34 Tascam US-224 support: MIDI OK, Audio KO? Rui Nuno Capela
2004-03-29 19:29 ` Karsten Wiese
2004-03-29 21:41 ` Rui Nuno Capela
2004-03-29 23:51 ` alsa-driver-1.0.4rc1 missing snd-usb-usx2y ? Rui Nuno Capela
2004-03-30 7:35 ` [Alsa-user] " Jaroslav Kysela
2004-03-30 7:49 ` Rui Nuno Capela
2004-03-30 20:51 ` Rui Nuno Capela
2004-04-01 12:57 ` Karsten Wiese
2004-04-01 15:01 ` Rui Nuno Capela
2004-03-29 23:57 ` Tascam US-224 support: MIDI OK, Audio KO? Karsten Wiese
2004-03-30 8:14 ` Rui Nuno Capela
2004-03-30 11:39 ` Karsten Wiese
2004-03-30 12:29 ` Rui Nuno Capela
2004-03-30 19:14 ` Karsten Wiese
2004-03-30 19:32 ` Rui Nuno Capela
2004-03-30 20:15 ` Karsten Wiese
2004-03-30 21:19 ` Rui Nuno Capela
2004-03-29 20:00 ` Martin Langer
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.