Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@zonque.org>
To: Tristan Chambers <tristan.chambers@gmail.com>,
	alsa-devel@alsa-project.org
Subject: Re: Echo Audio Echo 2 USB Interface
Date: Mon, 13 Oct 2014 16:45:52 +0200	[thread overview]
Message-ID: <543BE5A0.1090009@zonque.org> (raw)
In-Reply-To: <CABuEqK7VqOxFg8dBTwXoiKEqP-ZZPSZxwH5bapAP0uugio9qbg@mail.gmail.com>

Hi,

On 10/11/2014 07:32 PM, Tristan Chambers wrote:
> I picked up an Echo Audio Echo 2 USB Interface. The product specs list
> iPad support through camera connection kit, so I assume it is class
> compliant. http://echoaudio.com/blogs/news/6454472-echo-digital-audio-introduces-the-echo-2-usb-audio-interface
> 
> However, on most systems when I plug the device in, it shows up in my
> sound settings panel under the Input tab, but not under the Output
> tab.
> 
> Recording works. I can successfully record with arecord -vv -fdat -D
> "plughw:CARD=Audio,DEV=0" echo.wav. I also can increase the sample
> rate by changing the flags. I verified that the sample rate actually
> increases by recording a 50khz test tone into the input and examining
> the wave form in an editor. It's there! So this is very promising.
> (anyone know of a test to verify bit depth? I want to make sure it's
> actually recording at 24bits.)
> 
> Playback however, is nothing but trouble. Like I said, the output
> device doesn't show up in the Output tab in my sound settings
> (gnome/pulse). However, when I list devices and available PCMs with
> aplay -l and aplay -L the device shows up on the lists. See specimens
> #1, #2, and #3. When I try to play though I get about a 1/4 second of
> audio and then nothing, and subsequent attempts to play sound output
> nothing. The device then must be unplugged and plugged back in. I'm
> playing with the command aplay -vv foo.wav
> --device="plughw:CARD=Audio,DEV=0". See output screen on specimen #4.

Any messages in dmesg when you try this? And does PulseAudio generate
any logs that look suspicious? The output of 'lsusb -v' might also be
helpful.


Daniel

  reply	other threads:[~2014-10-13 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-11 17:32 Echo Audio Echo 2 USB Interface Tristan Chambers
2014-10-13 14:45 ` Daniel Mack [this message]
2014-10-23  3:16   ` Tristan Chambers

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=543BE5A0.1090009@zonque.org \
    --to=daniel@zonque.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=tristan.chambers@gmail.com \
    /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