All of lore.kernel.org
 help / color / mirror / Atom feed
From: Natanael Olaiz <nolaiz@gmail.com>
To: Daniel Mack <zonque@gmail.com>
Cc: alsa-devel@alsa-project.org, Evan <evan.ta.88@gmail.com>
Subject: Re: Status of Zoom R16
Date: Thu, 08 Nov 2012 20:52:16 +0100	[thread overview]
Message-ID: <509C0D70.10603@gmail.com> (raw)
In-Reply-To: <CACTFLANrwV3TbK9L58DYOc_M29UuiaN4vYih=f7awQUErWmuog@mail.gmail.com>

El 08/30/2011 04:14 PM, Daniel Mack escribió:
> On Tue, Aug 30, 2011 at 4:05 PM, Evan <evan.ta.88@gmail.com> wrote:
>> On Tue, Aug 30, 2011 at 9:21 AM, Daniel Mack <zonque@gmail.com> wrote:
>>
>>> On Tue, Aug 30, 2011 at 9:04 AM, Evan Ta <evan.ta.88@gmail.com> wrote:
>>>> Hi,
>>>>
>>>> as subj says: can you tell me how the Zoom R16 is doing? The hardware looks nice, but the latest info I can find is a seemingly unresolved  failure to work with Alsa as of feb 2010.
>>> Yes, it's currently unsupported. The device doesn't comply to the USB
>>> audio spec, and nobody with such hardware has yet taken the time to
>>> implement a driver.
>>
>> How hard is this? If I buy it and help with testing, is this something that
>> can be done without too much hassle?
> Ideally, you would have an USB hardware analyzer to sniff the traffic.
> Software tracers are an alternative, but I never used any, so I can't
> tell how well they work, especially for isochronous transfers.
>
> Once you know how the device is set up and how the stream is
> organized, it should just be a matter of time and your programming
> skills to make it work. And there are several drivers for proprietary
> USB hardware in the kernel that you can take as an example. Needless
> to say that such effort would be much appreciated by many users :)

Sorry to reply such an old mail, but I want to ask: any news? I didn't
found any.

I have one R16, and I want to help to make it works as far as I can. I'm
specially interested in make it works as a MIDI controller.

Can you give me some tips about how to procede? I would go for the
software sniffer.

I'll be also glad if you can give any example of similar driver code
that I can use as a base to modify and do some tests with the device
communication.


Thanks in advance.

Best regards,
Natanael.



>
>
> Daniel
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>

      parent reply	other threads:[~2012-11-08 19:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30  7:04 Status of Zoom R16 Evan Ta
2011-08-30  7:21 ` Daniel Mack
2011-08-30  8:07   ` Evan
2011-08-30 14:05   ` Evan
2011-08-30 14:14     ` Daniel Mack
2011-08-30 14:30       ` Evan
2012-11-08 19:52       ` Natanael Olaiz [this message]

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=509C0D70.10603@gmail.com \
    --to=nolaiz@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=evan.ta.88@gmail.com \
    --cc=zonque@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.