Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Shirkey <pshirkey@boosthardware.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: USB recording - repetitive peaks
Date: Wed, 03 Jul 2002 00:35:03 +0900	[thread overview]
Message-ID: <3D21C827.2060602@boosthardware.com> (raw)
In-Reply-To: s5hy9curxdr.wl@alsa2.suse.de

Takashi Iwai wrote:
> Hi Patrick,
> 
> At Tue, 02 Jul 2002 23:28:08 +0900,
> Patrick Shirkey wrote:
> 
>>Thanks to your patch Takashi we have two people who have been able to 
>>record through the quattro.
>>
>>We have both found that there is a constant repetitive peak in the 
>>signal which reminds me of the problems I had with the cmipci for a 
>>brief period.
>>
>>Thorsten Hass has recorded a perfect example for you which he did using 
>>aplay and arecord. It is a sine wave so is easy on the ears.
>>
>>http://www.thorstenhaas.de/alsa/audio.file
> 
>  
> hmm, this sounds like the mismatching of packet size and copy
> destination.  i heard your ogg file, and this was similar, too.
> 
> under which condition were they recorded?
> with 24bit/96kHz/2ch?
> or does it happen generally on every condition?
> 

They were arecord -f cd

> you can see the running status and condition on streamX proc file
> during playback/capture.
> 

----
# cat /proc/asound/card2/stream1
M Audio USB AudioSport Quattro (tm) : USB Audio #1

Playback:
   Status: Stop
   Altset 3
     Format: S16_LE
     Channels: 2
     Endpoint: 3 OUT (ADAPTIVE)
     Rates: 11025, 22050, 44100, 48000
   Altset 2
     Format: S24_3LE
     Channels: 2
     Endpoint: 3 OUT (ADAPTIVE)
     Rates: 11025, 22050, 44100, 48000
   Altset 1
     Format: S24_3LE
     Channels: 2
     Endpoint: 3 OUT (ADAPTIVE)
     Rates: 88200, 96000

Capture:
   Status: Running
     Packets = 20
     URBs = 5
     Packet Size = 192
     Nominal freq = 44.          1682  Altset 3
     Format: S16_LE
     Channels: 2
     Endpoint: 5 IN (SYNC)
     Rates: 11025, 22050, 44100, 48000
   Altset 2
     Format: S24_3LE
     Channels: 2
     Endpoint: 5 IN (SYNC)
     Rates: 11025, 22050, 44100, 48000
   Altset 1
     Format: S24_3LE
     Channels: 2
     Endpoint: 5 IN (SYNC)
     Rates: 88200, 96000

----


> 
> 
>>He has also generated a jpeg plotted by an oscilloscope while recording 
>>which I can send you if it will help.
> 
> 
> can you figure out how long the period of puls is?

They are so regular you can set a use them as a metronome:) Would you 
like me to have a look at the timing in an editor or is there an more 
precise way to find out?

> i guess this has relation between the status shown in the proc file
> above.
> 
> 
> Takashi
> 
> 



-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-07-02 15:35 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-01 17:07 [PATCH] USB MIDI driver Clemens Ladisch
2002-07-02 10:36 ` Takashi Iwai
2002-07-02 14:28   ` USB recording - repetitive peaks Patrick Shirkey
2002-07-02 14:57     ` Takashi Iwai
2002-07-02 15:35       ` Patrick Shirkey [this message]
2002-07-02 16:03         ` Takashi Iwai
2002-07-02 16:37           ` Patrick Shirkey
2002-07-02 16:39             ` Takashi Iwai
2002-07-02 17:08               ` Patrick Shirkey
2002-07-02 17:29                 ` Takashi Iwai
2002-07-02 18:04                 ` Patrick Shirkey
2002-07-02 18:26                   ` Patrick Shirkey
2002-07-02 18:38                     ` Patrick Shirkey
2002-07-04  9:41                       ` Takashi Iwai
2002-07-03  8:55                   ` Takashi Iwai
2002-07-04 16:23                     ` Patrick Shirkey
2002-07-04 16:26                       ` Takashi Iwai
2002-07-04 17:15                         ` Patrick Shirkey
2002-07-04 17:27                           ` Paul Davis
2002-07-05 13:44                           ` Takashi Iwai
2002-07-05 18:19                             ` Patrick Shirkey
2002-07-05 18:37                               ` Patrick Shirkey
2002-07-04 18:59                       ` Thorsten Haas
2002-07-05  6:56                         ` Thorsten Haas
2002-07-05  8:34                           ` Patrick Shirkey
2002-07-05  8:38                             ` Thorsten Haas
2002-07-05  9:06                               ` Thorsten Haas
2002-07-05 15:35                                 ` Takashi Iwai
2002-07-03  5:18             ` Fernando Pablo Lopez-Lezcano
2002-07-03  8:50               ` Takashi Iwai
2002-07-02 16:07         ` Patrick Shirkey
2002-07-02 14:51   ` Re: [PATCH] USB MIDI driver Takashi Iwai
2002-07-02 20:40     ` Pedro Lopez-Cabanillas
2002-07-02 22:10       ` Pedro Lopez-Cabanillas
2002-07-03 12:52     ` Clemens Ladisch
2002-07-03 13:18       ` Takashi Iwai
2002-07-03 14:42         ` Clemens Ladisch
2002-07-04  9:47           ` Takashi Iwai
2002-07-04 11:52             ` Clemens Ladisch
2002-07-05  7:55               ` Clemens Ladisch
2002-07-05 13:40                 ` Takashi Iwai

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=3D21C827.2060602@boosthardware.com \
    --to=pshirkey@boosthardware.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=tiwai@suse.de \
    /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