From: Takashi Iwai <tiwai@suse.de>
To: Pavel Hofman <pavel.hofman@ivitera.com>
Cc: alsa-devel@alsa-project.org, Chakravarthi Pradeep <doubleq7@gmail.com>
Subject: Re: Noise in begnning of alsa application
Date: Mon, 21 Jan 2019 22:07:14 +0100 [thread overview]
Message-ID: <s5htvi1yb25.wl-tiwai@suse.de> (raw)
In-Reply-To: <4a800a2a-50ce-8bda-3b5c-26d782c40810@ivitera.com>
On Mon, 21 Jan 2019 19:07:09 +0100,
Pavel Hofman wrote:
>
>
> Dne 21. 01. 19 v 18:46 Chakravarthi Pradeep napsal(a):
> > On Wed, Jan 16, 2019 at 5:07 PM Chakravarthi Pradeep <doubleq7@gmail.com> wrote:
> >>
> >> I have ALSA driver for capture device which works fine with VLC. when
> >> I try to capture and render using own application having some issues.
> >> When I start play, it has some noise in beginning and audio is
> >> discontinuous in between. Discontinuous means, some audio frame are
> >> getting dropped in between. cut cut sound for sine wave. I have tried
> >> snd_pcm_drop and snd_pcm_drain but no use. Kindly suggest how to
> >> remove the starting noise in ALSA.
>
> I have experienced the same issue, with ice172 driver. IMO part of the
> first period when opening the stream contains samples from the
> previous run. In one of my my projects I have to drop initial samples
> in order to get correct and stable results from FFT analysis.
>
> I do not know if the problem is in the driver, alsa-lib or if the
> application (in my case the SDL library) uses alsa-lib API
> incorrectly. To tell the truth I did not investigate details and
> "fixed" it by dropping the initial samples.
It's likely a driver-specific problem, but still wondering how it
happens. Does the whole first period contain the previous samples, or
just a few beginning samples?
Also is it on the x86 PC, or on other architecture?
thanks,
Takashi
next prev parent reply other threads:[~2019-01-21 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 11:37 Noise in begnning of alsa application Chakravarthi Pradeep
2019-01-16 11:56 ` Chakravarthi Pradeep
2019-01-21 17:46 ` Chakravarthi Pradeep
2019-01-21 18:07 ` Pavel Hofman
2019-01-21 21:07 ` Takashi Iwai [this message]
2019-01-21 20:29 ` 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=s5htvi1yb25.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=doubleq7@gmail.com \
--cc=pavel.hofman@ivitera.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