From: Jan Depner <eviltwin69@cableone.net>
To: Karsten Wiese <fzuuzf@googlemail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: TASCAM US-1641
Date: Thu, 25 Mar 2010 18:48:26 -0500 [thread overview]
Message-ID: <1269560906.6504.2.camel@eviltwin> (raw)
In-Reply-To: <201003251100.16073.fzuuzf@googlemail.com>
On Thu, 2010-03-25 at 11:00 +0100, Karsten Wiese wrote:
> Am Mittwoch 24 März 2010 schrieb Jan Depner:
> >
> >
> > > I suggest adding some printk()s to the driver and see what it actually
> > > does and which values it passes around. Most probably there is more
> > > differences in the data format, and descriptors and/or message blocks
> > > have different meanings for this hardware model.
> > >
> >
> > I did as suggested and got back reasonable appearing numbers for
> > rate, use_packsize, and period_frames of 44100, 36, and 256 respectively
> > but am not sure how to relate this to my interface.
>
> I heard the US-1641 uses bulk and/or iso packets, while US-122L uses iso only.
> so snd_usb_us122l would need some deep tweaking.
> also all the incantation stuff looks propably different.
>
Sounds complicated ;-)
> > Is there some
> > documentation somewhere that would explain the output of lsusb -v with
> > respect to variable names in us122l.c.
>
> erm, no. there are the interface and endpoint numbers.
>
> > My problem here is that I don't
> > know what would actually be reasonable for this interface nor how to
> > find out.
>
> usbsnoop and/or the developers at http://usbaudio.com.
> >
I've got usbsnoop and UsbSnoop on Windows. Would the guys at
usbaudio actually help out??? It seems counterintuitive.
>
> >
> > Many thanks for your help with this. Karsten had asked me to get
> > back with him if I got one of these but my email to him must have gone
> > to the spam filter as I haven't heard anything.
>
> no spam filters, just work and short hollidays.
I know how that is ;-)
>
> looking back at developing snd_usb_us122l, i'm unsure if I spent my time wisely:
> the actual hardware one can buy now doesn't talk to the driver anymore. and i'm
> busy caring for real life, which i've been omitting a tad too much that time.
>
> If in doubt, don't bother hacking on the tascam, enjoy spring instead!
>
>
Probably the best advice ever ;-)
> regards,
> Karsten
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2010-03-25 23:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 1:34 TASCAM US-1641 Jan Depner
2010-03-24 5:56 ` Daniel Mack
2010-03-24 22:02 ` Jan Depner
2010-03-24 22:50 ` Daniel Mack
2010-03-25 10:00 ` Karsten Wiese
2010-03-25 23:48 ` Jan Depner [this message]
2010-03-25 10:03 ` Karsten Wiese
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1269560906.6504.2.camel@eviltwin \
--to=eviltwin69@cableone.net \
--cc=alsa-devel@alsa-project.org \
--cc=fzuuzf@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox