From: Daniel Mack <daniel@caiaq.de>
To: jordan johnston <triplesquarednine@gmail.com>
Cc: alsa-devel@alsa-project.org,
Tobias Hansen <Tobias.Hansen@physik.uni-hamburg.de>
Subject: Re: Status of the Tascam US-122mkII???
Date: Sun, 20 Jun 2010 01:05:27 +0200 [thread overview]
Message-ID: <20100619230527.GJ25445@buzzloop.caiaq.de> (raw)
*** Reply to ALL please! ***
On Sat, Jun 19, 2010 at 06:51:58PM -0400, jordan johnston wrote:
> On Sat, Jun 19, 2010 at 6:41 PM, Daniel Mack <daniel@caiaq.de> wrote:
> > Well, you can assume that audio is transported over dedicated
> > isochronous endpoints. The question is how audio parameters are set up.
> > And you can find out by tracing the traffic and see what happens when
> > you start or stop the stream, when you change the sample rate etc.
> >
>
> now, here you are referring, to tracing in OSX, or Windows right? (like before.)
Yes.
> i may try that out, but as i am not versed in this stuff it may be
> quite difficult
> without better understanding.
>
> do you know of any really insightful information on the
> subject(somewhere on the net).
> im going to google around a bit too.
Hmm, I can point you to the USB specs which gives you detailed
explanation about the low-level communication on the bus:
http://www.usb.org/developers/docs/usb_20_052510.zip
And you can read other Linux drivers and see what they do.
We have no clue what Tascam's engineers did when they designed the
MK2 version, and how close they kept to the protocol specs of their
earlier products. Maybe they just shifted some bytes around, maybe they
completely started over. All left for you to find out :)
> Ya, it was a gamble i had called the store earlier in the week, they
> actually had the device i wanted.
> however, i didn't end up going that day. so when i did come, it had
> been sold. i then decided to take
> a gamble on it.
>
> no big deal. - 30 day return policy, and they said it was fine that i
> returned it, if i couldn't get it
> supported under linux.
It might take you more than 30 days to fully support it under Linux if
you're going to do it yourself though ;)
Daniel
next reply other threads:[~2010-06-19 23:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 23:05 Daniel Mack [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-19 17:35 Status of the Tascam US-122mkII??? jordan johnston
2010-06-19 17:42 ` Daniel Mack
[not found] ` <AANLkTilfDBFqGH41TGF0H855CfCm8fOjGMW7lwH1tXi_@mail.gmail.com>
2010-06-19 18:09 ` Daniel Mack
[not found] ` <AANLkTikfeTzrOttiyI9BqqD3zHI7NXY8ScyXoY8Ruq8N@mail.gmail.com>
2010-06-19 18:57 ` Daniel Mack
2010-06-19 19:03 ` Tobias Hansen
[not found] ` <AANLkTimJ17dGo6K3Gy8_tlhIezFFY0XDRyj53i8tj1pi@mail.gmail.com>
2010-06-19 20:19 ` Tobias Hansen
2010-06-19 20:45 ` jordan johnston
2010-06-19 20:47 ` jordan johnston
2010-06-19 20:58 ` Tobias Hansen
2010-06-19 22:42 ` jordan johnston
2010-06-19 22:41 ` Daniel Mack
[not found] ` <AANLkTikUAdL-tQ4CslnBRUP5dFFvKofvFRZn5gOiWRrD@mail.gmail.com>
[not found] ` <20100619230147.GP17833@buzzloop.caiaq.de>
[not found] ` <AANLkTimMpFrOzMctNCYcohyT-btYpUornvYGk2Tz1WFu@mail.gmail.com>
[not found] ` <20100619232244.GR17833@buzzloop.caiaq.de>
2010-06-19 23:53 ` jordan johnston
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=20100619230527.GJ25445@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=Tobias.Hansen@physik.uni-hamburg.de \
--cc=alsa-devel@alsa-project.org \
--cc=triplesquarednine@gmail.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;
as well as URLs for NNTP newsgroup(s).