From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Mack Subject: Re: Behringer Uphoria UMC204 usb audio capture only pops and clicks Date: Tue, 29 Apr 2014 18:58:56 +0100 Message-ID: References: <53555A0F.4080406@zonque.org> <5355655B.3050705@zonque.org> <53556961.5060600@zonque.org> <93266364-0c59-429e-9f8a-fe9ec89347c0@email.android.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail.zonque.de (svenfoo.org [82.94.215.22]) by alsa0.perex.cz (Postfix) with ESMTP id 4C18326500A for ; Tue, 29 Apr 2014 19:59:17 +0200 (CEST) In-Reply-To: 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: Andrew Reyes Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org (please, do not top post!) On April 29, 2014 6:53:36 PM WAT, Andrew Reyes wrote: >Daniel it turns out with a brand new UMC204 it still does it on my >linux >box. I'm at a loss. Try that one on Windows as well. Uf it doesn't work there either, send tge hardqare back and get a different model. If the hardware has such severe bugs, there nothing the Linux driver can do to fix it up. Daniel >On Thu, Apr 24, 2014 at 9:14 AM, Andrew Reyes >wrote: > >> Daniel I got my hands on Windows 7 PC and installed the drivers from >the >> website and it does the samething. So now I'm leaning toward a >defective >> soundcard. I'm sending it back for a new one. >> >> >> On Wed, Apr 23, 2014 at 11:18 AM, Andrew Reyes >wrote: >> >>> Ok I got the two different logs and I don't what I'm looking for >lol. >>> It's just raw data. My last option is to try using it on Windows or >Mac >>> just to make sure it's not the interface. >>> >>> >>> On Wed, Apr 23, 2014 at 10:40 AM, Andrew Reyes >wrote: >>> >>>> > I can just give you a few more ideas to debug this, but that >includes >>>> more action from your side. >>>> >>>> > * First of all, try the same device on a different computer, >and/or a >>>> different USB port, especially if you're using an XHCI (USB3) port. >>>> >>>> > * Try the device on Mac OS X, without installing a driver and see >if >>>> you have the same problem here. >>>> >>>> > * Use usbmon and analyze the data stream when a pop occurs. >Compare >>>> that with settings that don't produce pops. There's good >documentation on >>>> usbmon in Documentation/usb/ in the Linux kernel. >>>> >>>> Ok cool. I'll get right on that. I did try the first suggestion on >four >>>> different computers and different ports and it's the same issue but >just to >>>> be thorough I'll check again. >>>> >>>> >>>> On Wed, Apr 23, 2014 at 9:59 AM, Daniel Mack >wrote: >>>> >>>>> >>>>> >>>>> On April 23, 2014 4:40:07 PM CEST, Andrew Reyes > >>>>> wrote: >>>>> >Is there something else I could do to get to the problem? >>>>> >>>>> I can just give you a few more ideas to debug this, but that >includes >>>>> more action from your side. >>>>> >>>>> * First of all, try the same device on a different computer, >and/or a >>>>> different USB port, especially if you're using an XHCI (USB3) >port. >>>>> >>>>> * Try the device on Mac OS X, without installing a driver and see >if >>>>> you have the same problem here. >>>>> >>>>> * Use usbmon and analyze the data stream when a pop occurs. >Compare >>>>> that with settings that don't produce pops. There's good >documentation on >>>>> usbmon in Documentation/usb/ in the Linux kernel. >>>>> >>>>> >>>>> Best regards, >>>>> Daniel >>>>> >>>>> -- >>>>> Sent from my Android phone with K-9 Mail. Please excuse my >brevity. >>>>> >>>> >>>> >>> >> -- Sent from my phone. Please excuse my brevity and typos.