Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Phillips <rustyp@freeshell.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Omnistudio USB
Date: Wed, 12 Jan 2005 12:48:47 -0500	[thread overview]
Message-ID: <1105552128.14676.36.camel@localhost> (raw)
In-Reply-To: <Pine.HPX.4.33n.0501121001170.22429-100000@studcom.urz.uni-halle.de>

[-- Attachment #1: Type: text/plain, Size: 1782 bytes --]

On Wed, 2005-01-12 at 10:02 +0100, Clemens Ladisch wrote:
> Rusty Phillips wrote:
> > I recently purchased one, and have been trying to find out
> > anything I can about getting it to work.  So far all I've gotten
> > is playback on two channels at 48Khz with alsa (from the 2.6.10
> > kernel as well as from alsa CVS).
> 
> What are the contents of /proc/asound/cardX/stream0?
> Is there a second output device in the output of "aplay -l"?
> 
> 
> Clemens
> 
Oh...sorry to mislead you there.  All four channels "work."  The problem
is that recording doesn't at all, and neither do higher bitrates.

First, aplay -l:
**** List of PLAYBACK Hardware Devices ****
card 0: USB [OmniStudio USB], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: USB [OmniStudio USB], device 1: USB Audio [USB Audio #1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

>From my asoundrc:
pcm.omni1 {
        type hw
        card 0
        device 0
}
ctl.omni1 {
        type hw
        card 0
}
pcm.omni2 {
        type hw
        card 0
        device 1
}
ctl.omni2 {
        type hw
        card 0
}

So I tested this with this:
arecord -D omni1 -r 48000 -t wav -v out.wav -f S24_3LE -c2
With a microphone plugged into channel 1.  The omnistudio shows signal
level varying via the LED, so I know I'm getting a signal into the
device.  However, the result I'm hearing is silence.  

Higher recording rates are even worse - I get a strange "beep" followed
by static.

Attached is /proc/asound/card0/stream0.

I've found this, which may also refer to the problem in my card (it's
about the USB Quattro)...unsure.  
http://www.music.columbia.edu/pipermail/linux-audio-user/2004-June/012737.html

Still...I should be getting some kind of signal, shouldn't I?  Thoughts?


[-- Attachment #2: stream0 output --]
[-- Type: text/plain, Size: 1110 bytes --]

M-Audio OmniStudio USB at usb-0000:00:07.2-1, full speed : USB Audio

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

Capture:
  Status: Stop
  Interface 2
    Altset 4
    Format: S16_LE
    Channels: 2
    Endpoint: 5 IN (SYNC)
    Rates: 11025, 22050, 44100
  Interface 5
    Altset 1
    Format: S24_3LE
    Channels: 2
    Endpoint: 5 IN (SYNC)
    Rates: 88200, 96000
  Interface 5
    Altset 3
    Format: S24_3LE
    Channels: 2
    Endpoint: 5 IN (SYNC)
    Rates: 11025, 22050, 44100, 48000
  Interface 5
    Altset 4
    Format: S16_LE
    Channels: 2
    Endpoint: 5 IN (SYNC)
    Rates: 11025, 22050, 44100, 48000

  reply	other threads:[~2005-01-12 17:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12  5:13 Omnistudio USB Rusty Phillips
2005-01-12  9:02 ` Clemens Ladisch
2005-01-12 17:48   ` Rusty Phillips [this message]
2005-01-12 20:50   ` Rusty Phillips
2005-01-14 11:34     ` Clemens Ladisch
2005-01-14 17:01       ` Rusty Phillips
2005-01-14 18:12         ` Clemens Ladisch
2005-01-14 20:07       ` Rusty Phillips

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=1105552128.14676.36.camel@localhost \
    --to=rustyp@freeshell.org \
    --cc=alsa-devel@lists.sourceforge.net \
    /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