All of lore.kernel.org
 help / color / mirror / Atom feed
From: Craig McQueen <craig.mcqueen@beamcommunications.com>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Pop and offsets at start of audio playback/record for SGTL5000 on i.MX28
Date: Fri, 14 Nov 2014 12:43:17 +1100	[thread overview]
Message-ID: <54655E35.9000807@beamcommunications.com> (raw)

I'm testing the 3.14.19 kernel for i.MX28 EVK, which has an SGTL5000 
CODEC. I've also tested on the 3.18-rc4 kernel and confirmed this issue 
still occurs.


Playback

When doing audio playback, I notice that the audio "fades in" over the 
first (approximately) 500 ms of playback. This is very noticeable and 
not ideal in certain applications (e.g. audio notifications that are of 
short duration).

However, if audio playback starts while audio recording is already 
in-progress, then there is no fade-in; instead there is a loud pop. I 
assume the fade-in is there to mask the pop. The pop is very unpleasant 
through headphones. (However, if I do audio playback a _second_ time 
while audio recording is still in-progress, then there is no loud pop 
the second time.)

I didn't think either the pop or the fade-in occurred on the 2.6.35 
kernel. How feasible is it to improve the driver to avoid or reduce the 
pop, and remove the necessity for a fade-in?


Record

When recording, I notice there is a low-frequency ramping offset at the 
start of a recording (after the 400-500 ms of previous audio) of approx 
600-700 ms duration. This also reduces the audio quality at the start of 
the recording. It could reduce the quality of captured audio depending 
on the application usage. I am getting distortion (clipping I assume) of 
my audio input during this time. It could cause a pop on playback (local 
playback or e.g. VoIP transmission to a remote device). It could reduce 
the audio quality through an audio CODEC.

How feasible is it to improve the driver to avoid a ramping offset at 
the start of recording?

-- 
Craig McQueen

             reply	other threads:[~2014-11-14  1:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14  1:43 Craig McQueen [this message]
2014-11-14  1:45 ` Pop and offsets at start of audio playback/record for SGTL5000 on i.MX28 Michael Trimarchi
2014-11-14  1:58   ` Craig McQueen
2014-11-14  2:04     ` Michael Trimarchi
2014-11-17  0:35       ` Craig McQueen
2014-11-17  0:41         ` Michael Trimarchi
2014-11-14  3:59 ` Fabio Estevam

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=54655E35.9000807@beamcommunications.com \
    --to=craig.mcqueen@beamcommunications.com \
    --cc=alsa-devel@alsa-project.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.