From: Martin Cracauer <cracauer@cons.org>
To: alsa-devel@alsa-project.org
Subject: Guide to USB debugging in Windows?
Date: Fri, 29 Mar 2013 11:36:39 -0400 [thread overview]
Message-ID: <20130329153639.GA72429@cons.org> (raw)
Does anyone have instructions on how to use a USB traffic monitor on
windows to extract some bits needed to control a sound device under
ALSA? As in, for people not normally developing in windows?
I have here a Sound Devices USBPre v1. It is mostly USB 1.1 sound
interface compatible and it accepts a stream played from ALSA under
Linux just fine. The problem is that the manufacturer has decided to,
in addition to the standard usb sound interface, have all the
different inputs on the device behind on/off switches, all of them
controlled by secret bits in the windows and mac drivers, all of them
default to off. So thingie is a brick as-is. I don't blame them too
hard, they now make a v2 of this devices and fixed it.
Just so that I don't appear more insane than usual, let me say why I
want to bother.
The windows drivers for this are only available in 32 bit, and the mac
drivers are 32 bit only as well, in addition the mac drivers never
went > 16bit/48KHz. The inability to use this on modern macs and
windows machines has pushed the price of these things very low on
Ebay, considering it is a fully professional device with the best mic
preamps you can get. If would be really cool if this could work under
ALSA, and as you see I figured it needs just a couple of bits that you
need to flip with some magic to at least get it to run up to 16bit/48KHz.
Martin
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
next reply other threads:[~2013-03-29 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 15:36 Martin Cracauer [this message]
2013-03-29 20:36 ` Guide to USB debugging in Windows? Clemens Ladisch
2013-03-30 16:49 ` PrasannaKumar Muralidharan
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=20130329153639.GA72429@cons.org \
--to=cracauer@cons.org \
--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 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.