Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: "Brand, Mark (Mr) (Summerstrand Campus South)" <Mark.Brand@nmmu.ac.za>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"ffado-devel@lists.sf.net" <ffado-devel@lists.sf.net>
Subject: Re: Call for testing: ALSA driver for Fireworks/BeBoB based devices
Date: Mon, 24 Feb 2014 16:17:11 +0900	[thread overview]
Message-ID: <530AF1F7.50901@sakamocchi.jp> (raw)
In-Reply-To: <35FE09CFAB387A4BA7ACDDED49F34518187561E7@CRETE.nmmu.ac.za>

Hi Mark,

 > The terminal output of aplay seems to reflect successful playback, 
and I hear audible clicks as
 >  the file starts and ends its playback.

It's quirk of BeBoB. If you avoid the click noise, add silent PCM 
samples into your file or use sound server such like jackd/PulseAudio.

But PulseAudio have an issue. See:
[pulseaudio-discuss] 'Failed to find a working profile' for firewire 
sound devices
http://lists.freedesktop.org/archives/pulseaudio-discuss/2014-January/019685.html

 > Please, is there anything you can suggest that I should try next?
 > Is there anything obvious that I appear to have overlooked?

A combination of these tools will help your debug.
  - ffado-mixer/ffado-dbus (the recent revision)
  - aplay/arecord
  - /proc/asound/Ozonic/#meter

Especially, Ozonic can reports its metering for each Analog input/Stream 
input/Analog output.

 > However, I have not yet been able to get audio playback (using "aplay 
-D plughw:2,0
 > Desktop/test.wav").  The .wav file is a short, 44.1/16 mono file 
saved from Audacity,
 > if that's relevant.

I guess that:
  - You expected to listen to 'Analog out 3/4'.
  - The aplay with plughw playbacks into 'Stream in 1/2'.
  - Ozonic's internal mixer didn't route 'Stream in 1/2' into 'Analog 
out 3/4'.


Regards

Takashi Sakamoto
o-takashi@sakamocchi.jp

  reply	other threads:[~2014-02-24  7:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14  3:17 [LAD] Call for testing: ALSA driver for Fireworks/BeBoB based devices Takashi Sakamoto
2014-02-01 23:49 ` [FFADO-devel] " Maximilian Engelhardt
2014-02-23  6:20 ` Brand, Mark (Mr) (Summerstrand Campus South)
2014-02-23  7:55   ` Takashi Sakamoto
     [not found]     ` <35FE09CFAB387A4BA7ACDDED49F3451818755DD6@CRETE.nmmu.ac.za>
2014-02-24  6:34       ` Brand, Mark (Mr) (Summerstrand Campus South)
2014-02-24  7:17         ` Takashi Sakamoto [this message]
2014-03-07 11:21           ` Brand, Mark (Mr) (Summerstrand Campus South)

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=530AF1F7.50901@sakamocchi.jp \
    --to=o-takashi@sakamocchi.jp \
    --cc=Mark.Brand@nmmu.ac.za \
    --cc=alsa-devel@alsa-project.org \
    --cc=ffado-devel@lists.sf.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