On Mon, 26 Jan 2004, Clemens Ladisch wrote:
> Bill Unruh wrote:
> > I am not sure that you got my report that S24_BE works for both
> > recording and playing and for both 44100 and 96000 and for duplex
> > at 44100. S16 does not work.
>
> Your tests were made with the default device, which is "plughw", which
> automatically converts sample formats. I.e., when you play a S24_BE
> file, the data is byte-swapped by ALSA because the device claims it
> supports LE only.
>
> Please do all your tests again ;-) with the "-D hw:0" parameter.
I have still not done this. Will get to it tonight. However, a few
comments:
All of S24_{LE,BE} worked at both 98000 and 44100 Note that I never
tried the S24_3{LE,BE}. However if I use the hw:0 then the S24_{LE,BE}
do not work, but the S24_3{LE,BE} do at least play (I am not at home so
do not know if they produce any sound)
Ie, does the plughw actually convert the 4 byte to 3 byte form?
Note that both recording and playback worked to 4 byte form (S24_LE)
.
>
> Please note that S24_?E is 24 bits data packed into four bytes, while
> S24_3?E is 24 bits in three bytes. USB devices support the latter
> only.
Of course sox I believe does not support 3 byte, so generating reasonable
files will be fun.
>
> > I have also run sniffusb on the windows side as 0763:2806 comes up,
> > [...]
> > Does this mean that if I use fxload to do a one stage loading using this
> > file, that it might work?
>
> Your effort is appreciated, but we already know that the Transit uses
> DFU to download its firmware. (DFU is a specification published by
> the USB-IF.) fxload is for EZ-USB chips, not for DFU-compatible ones.
>
> I've written a DFU loader
> http://prdownloads.sourceforge.net/usb-midi-fw/madfu-firmware-0.1beta3.tar.gz?download
> which does the same as the Windows loader. Unfortunately, it doesn't
> work because the 2.4 kernel gets confused when the device resets
> itself.
Apparently as it performed a slow crash ( different programs froze up at
time went on). However I removed the usb_reset() from the madfuload.c
The card was not recognized or rather stayed as a 2806 device
until I rebooted (without poweroff) at which point it came up as a 2006
device (ie with firmware.). I am tempted to open it up and put in a
small rechargeable battery into it, so it keeps up its power even when
disconnected from the bus. ( not clear how long a battery would last!)
Ie, on initial bootup of the usb bus, it is recognizing the firmware
loaded card.
Unloading the usb-uhci module is not enough. I cannot bring down usbcore
to try to see if that would reset stuff.
(doing a double reboot to set up the sound card seems a bit of a pain.)
Is anyone trying to discover why the usb bus is behaving so badly with
respect to this card?
Are there any other experiments I could try to help you all get to the
bottom of this?
Finally are there any usb cards (smaller the better) which have good
performance and work with Linux?
You mentioned the Edirol U2 as working well. It is a bit large (8oz) for
laptop lugging around, but I will use it if necessary.
Thanks again for all your attention.
Bill Unruh
>
>
> Regards,
> Clemens
>
>
--
William G. Unruh | Canadian Institute for| Tel: +1(604)822-3273
Physics&Astronomy | Advanced Research | Fax: +1(604)822-5324
UBC, Vancouver,BC | Program in Cosmology | [EMAIL PROTECTED]
Canada V6T 1Z1 | and Gravity | www.theory.physics.ubc.ca/
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user
