alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: jordan johnston <triplesquarednine@gmail.com>
Cc: Tobias Hansen <Tobias.Hansen@physik.uni-hamburg.de>,
	alsa-devel@alsa-project.org
Subject: Re: Status of the Tascam US-122mkII???
Date: Sun, 20 Jun 2010 00:41:02 +0200	[thread overview]
Message-ID: <20100619224102.GO17833@buzzloop.caiaq.de> (raw)
In-Reply-To: <AANLkTil_QpNxgpXEaisHx1Xh-DG7Mi9rCtKjtAmcW_KO@mail.gmail.com>

On Sat, Jun 19, 2010 at 04:45:08PM -0400, jordan johnston wrote:
> So basically, many people have tried to get this working and
> failed????  no one was able to get it working?
> 
> alright, i might setup a spare partition to give this another shot, as
> i don't want to ruin my current setup that is needed every time
> i got out and play music, or jam(like tonight!). My "Linux VST/live
> input looper" must stay fully operational !
> but i will probably take another shot at it. even though! - in the
> end, i bet i am just going to purchase for FFADO "full-support".
> i would buy HDSP, but it's a little pricey for my laptop.
> I just thought that i would try to take advantage of the situation,
> maybe help debug the driver, but if the implementation of the
> us-122mkII is vastly different than what can you do???

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.

> It's too bad
> that companies don't put more effort into supporting linux,
> not that i need to tell you that!

The only thing you can do as a customer and end-user is to pay attention
to the state of Linux support of a new piece of hardware before you buy.

Or waste some weekends and help yourself and maybe lots of others ;)

Daniel

  parent reply	other threads:[~2010-06-19 22:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
     [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
  -- strict thread matches above, loose matches on Subject: below --
2010-06-19 23:05 Daniel Mack

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=20100619224102.GO17833@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).