From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Keith A. Milner" Subject: Re: Boss GT-001 Date: Tue, 06 Oct 2015 20:58:01 +0100 Message-ID: <4761108.z7lHdDqPTH@kamdesktop> References: <1481883.Y22cmGKEIB@kamdesktop> <1837042.8ri5iYFGVx@kamdesktop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by alsa0.perex.cz (Postfix) with ESMTP id 03CDC2657D9 for ; Tue, 6 Oct 2015 21:58:04 +0200 (CEST) Received: by wiclk2 with SMTP id lk2so174851790wic.1 for ; Tue, 06 Oct 2015 12:58:03 -0700 (PDT) In-Reply-To: <1837042.8ri5iYFGVx@kamdesktop> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: alsa-devel@alsa-project.org Cc: 'Clemens Ladisch' List-Id: alsa-devel@alsa-project.org OK, so it seems that this hardware is substantially the same as the GT-100 which has previously (and recently) been raised as a problem on ALSA. Clemens Ladisch wrote: > Aaron Spike wrote: > > On Sat, Jan 10, 2015 at 2:41 PM, Clemens Ladisch wrote: > > > There is something that cannot be derived from the descriptors. > > > > In a nutshell, what would someone who knew what they were doing do in this > > situation? > > 1. Use some USB sniffer to find out what commands the Windows driver sends. > 2. Reverse engineer the firmware. > I'm going to attempt to capture some USB data using this device in Windows. If I do this, is there an accepted method for uploading the capture so it can be posted here? At this point, I'm not 100% sure what the capture format is going to be... Cheers, Keith