From: Paul Menzel <paulepanter@users.sourceforge.net>
To: alsa-devel@alsa-project.org
Subject: Re: TASCAM US-122mkII
Date: Fri, 19 Aug 2011 15:06:53 +0200 [thread overview]
Message-ID: <1313759213.3673.40.camel@mattotaupa> (raw)
In-Reply-To: <CACTFLAPnWpq7AQ3KZakqkLRV7CtgDG-fXM77T9NLK5o90hfxzA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 743 bytes --]
Am Freitag, den 19.08.2011, 13:46 +0200 schrieb Daniel Mack:
> On Fri, Aug 19, 2011 at 1:37 PM, Cyril Hrubis <metan.lists@gmail.com> wrote:
[…]
> > As far as I understand it, there are two endpoints for audio and two for
> > MIDI. The MIDI part seems to be initalized fine although I don't have
> > any MIDI device to test it.
> >
> > And in the log from windows machine the audio part does some
> > intialization and then only buch of isochronous transfers.
>
> Hmm, so it seems that our only option is really to look at these
> Windows dumps and reverse-engineer the protocol.
Is there a chance to talk to the manufacturer or are they known to not
cooperate? Cyril, did you contact their support?
Thanks,
Paul
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2011-08-19 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 10:01 TASCAM US-122mkII Cyril Hrubis
2011-08-19 11:02 ` Daniel Mack
2011-08-19 11:37 ` Cyril Hrubis
2011-08-19 11:46 ` Daniel Mack
2011-08-19 11:54 ` Cyril Hrubis
2011-08-19 12:09 ` Cyril Hrubis
2011-08-19 13:06 ` Paul Menzel [this message]
2011-08-19 13:11 ` Cyril Hrubis
2011-08-26 14:52 ` Cyril Hrubis
2011-08-26 16:24 ` Cyril Hrubis
[not found] <BANLkTikBtN28qNwJf4nuTGL6jEGOw_jo6Q@mail.gmail.com>
2011-04-12 14:29 ` TASCAM US-122MKII Dominic Powell
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=1313759213.3673.40.camel@mattotaupa \
--to=paulepanter@users.sourceforge.net \
--cc=alsa-devel@alsa-project.org \
/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).