Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
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 [EMAIL PROTECTED] --- 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=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
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.exesomefile.
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:
ListeningPipef1up_m1.h
Moved Fader 1 up (1/5 Full scale).
Switched Mute 1 ON.
Switched off us428. ListeningPipe finished ok.
Cheers,
Karsten
attachment: ui.jpg//Pipe Connected!
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW [EMAIL PROTECTED], 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 [EMAIL PROTECTED], 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 [EMAIL PROTECTED], 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 [EMAIL PROTECTED], len=0x5
{ 0x00, 0x00, 0x09, 0x00, 0x0A,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW [EMAIL PROTECTED], 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 [EMAIL PROTECTED], len=0x5
{ 0x00, 0x00, 0x13, 0x00, 0x14,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW [EMAIL PROTECTED], 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 [EMAIL PROTECTED], len=0x5
{ 0x00, 0x00, 0x1D, 0x00, 0x1E,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW [EMAIL PROTECTED], 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 [EMAIL PROTECTED], len=0x5
{ 0x00, 0x00, 0x26, 0x00, 0x28,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW [EMAIL PROTECTED], 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 [EMAIL PROTECTED], len=0x5
{ 0x00, 0x00, 0x30, 0x00, 0x32,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW [EMAIL PROTECTED], 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 [EMAIL PROTECTED], len=0x5
{ 0x00, 0x00, 0x3A, 0x00, 0x3C,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW [EMAIL PROTECTED], 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 [EMAIL PROTECTED], len=0x5
{ 0x00, 0x00, 0x43, 0x00, 0x46,
};
// _URB_HEADER 09
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
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 [EMAIL PROTECTED] attachment: USB224_Snoop1.png
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
Am Dienstag 30 Mrz 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_id70alloc_id638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
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 [EMAIL PROTECTED] --- 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=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
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 [EMAIL PROTECTED] 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_id70alloc_id638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
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 [EMAIL PROTECTED] --- 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=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
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_id70alloc_id638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
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/[EMAIL PROTECTED]/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=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
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
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
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 . . . . . .
