Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo Gabrielli <l.gabrielli@univpm.it>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: twl4030 latency update
Date: Wed, 26 Mar 2014 10:35:16 +0100	[thread overview]
Message-ID: <53329F54.3030305@univpm.it> (raw)
In-Reply-To: <53328F4C.8030205@ti.com>


On 26/03/2014 09:26, Peter Ujfalusi wrote:
> Can you elaborate on the corrupted/scrambled audio? I just don't see how it
> can happen. Can you get the /proc/asound/card0/pcm0p/sub0/hw_params when you
> have the audio quality issue?
Hello,
Here you are:

cat /proc/asound/card0/pcm0p/sub0/hw_params
access: MMAP_INTERLEAVED
format: S16_LE
subformat: STD
channels: 2
rate: 22050 (22050/1)
period_size: 512
buffer_size: 1024

And this is jack output:

jackd -P62 -t2000 -dalsa -dhw:0 -r22050 -p512 -n2 -s -S -i2 -o2 &

jackd 0.124.1
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn 
and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

JACK compiled with System V SHM support.
loading driver ..
apparent rate = 22050
creating alsa driver ... 
hw:0|hw:0|512|2|22050|2|2|nomon|swmeter|soft-mode|16bit
configuring for 22050Hz, period = 512 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 16bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 16bit little-endian
ALSA: use 2 periods for playback

I can send you saomething to get it clearer. I recorded  a 10Hz sine 
wave with jaaa. The wave is totally scrambled (probably buffers are not 
read in order). But it may well be an issue with jack.

When the output sounds correct (256 period) hw_param is:
cat /proc/asound/card0/pcm0p/sub0/hw_params
access: MMAP_INTERLEAVED
format: S16_LE
subformat: STD
channels: 2
rate: 22050 (22050/1)
period_size: 256
buffer_size: 768


> I can not run jackd on the board anymore (with linux-next at least):
> FATAL: cannot locate cpu MHz in /proc/cpuinfo

Yes, there's been a recent fix to that (you can checkout the latest 
jackd from git repos, see this thread: 
http://lists.jackaudio.org/private.cgi/jack-devel-jackaudio.org/2014-March/012167.html

Or maybe you can just start jackd specifying a different clock with the 
-c switch i.e.
jackd -P62 -t2000 -c s -dalsa -dhw:0 -r22050 -p512 -n2 -s -S -i2 -o2 &

  parent reply	other threads:[~2014-03-26  9:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20 11:13 twl4030 latency update Leonardo Gabrielli
2014-03-20 13:35 ` Peter Ujfalusi
2014-03-20 14:31   ` Leonardo Gabrielli
2014-03-21  7:08     ` Peter Ujfalusi
2014-03-25 18:50       ` Leonardo Gabrielli
2014-03-26  8:26         ` Peter Ujfalusi
2014-03-26  8:41           ` Peter Ujfalusi
2014-03-26  9:35           ` Leonardo Gabrielli [this message]
2014-03-26 12:28             ` Peter Ujfalusi
2014-03-26  9:45           ` Leonardo Gabrielli
2014-03-26 12:51             ` Peter Ujfalusi
2014-03-26 15:40               ` Leonardo Gabrielli
     [not found]               ` <533A89D2.5050906@univpm.it>
2014-04-01 13:31                 ` Peter Ujfalusi

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=53329F54.3030305@univpm.it \
    --to=l.gabrielli@univpm.it \
    --cc=alsa-devel@alsa-project.org \
    --cc=peter.ujfalusi@ti.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