alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Keith A. Milner" <maillist@superlative.org>
To: alsa-devel@alsa-project.org
Subject: Re: USB Quirks for Boss JS-8
Date: Mon, 21 Mar 2011 12:50:32 +0000	[thread overview]
Message-ID: <201103211250.32946.maillist@superlative.org> (raw)
In-Reply-To: <AANLkTikU+shHE6Z4cz0Gecy9VO6bg=Cxvpjywrfxfck5@mail.gmail.com>

On Monday 21 Mar 2011 07:54:13 Daniel Mack wrote:
> On Fri, Mar 18, 2011 at 6:56 PM, Keith A. Milner
> > 
> > {
> >        /* Boss JS-8 Jam Station  */
> >        USB_DEVICE(0x0582, 0x0109),
> 
> Does this quirk help anything? I'm just asking because looking at the
> descriptors,it's not clear whether this device does comply to any
> standard interfaces at all. Could be the vendor just hides the
> compliancy, but they might have implemented a proprietary protocol as
> well.

It's supposed to be a 2-in/2-out audio interface. At least that's what it 
shows up with on Windows. The Windows driver README contains the following:

"Of the total audio input/output channels provided by the JS-8, there are 2 
INs and 2 OUTs

[WAVE OUT Devices]
OUT (JS-8)
 
[WAVE IN Devices]
IN (JS-8)
 
[ASIO device]
When using the JS-8 with an ASIO-compatible application such as Cubase, select 
"JS-8" as the ASIO setting for your application.
*	To prevent an audio feedback loop or double monitoring, make settings on 
your application to turn monitoring off or use ASIO Direct Monitoring.
*	The JS-8 does not actually support ASIO Direct Monitoring. For greater 
ease of use, support is simulated.
*	When using the JS-8 with ASIO, we recommend that you set your application 
so that it does not use the Microsoft GS Wavetable SW Synth. (In order to 
decrease the load, and for convenience when changing Audio Buffer Size of the 
driver.)"

It could well be proprietary, but it's a Roland device and my understanding is 
it's not uncommon for Roland to hide standard usb-audio interfaces behind non-
standard identifiers.

I have USB Device Monitoring Studio on my Windows laptop so I can dig further, 
although I'm not entirely sure what I should be looking for.

Cheers,


-- 
Keith A. Milner

  reply	other threads:[~2011-03-21 12:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 17:56 USB Quirks for Boss JS-8 Keith A. Milner
2011-03-21  7:54 ` Daniel Mack
2011-03-21 12:50   ` Keith A. Milner [this message]
2011-03-21 13:32   ` Clemens Ladisch
2011-03-21 14:10     ` Keith A. Milner
2011-03-21 14:45     ` Keith A. Milner
2012-10-14 19:43       ` Adolfo
2012-10-16  7:47         ` Daniel Mack
2012-10-16  8:04           ` Adolfo Ranea
2013-04-14 23:00           ` Keith A. Milner

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=201103211250.32946.maillist@superlative.org \
    --to=maillist@superlative.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 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).