Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: stan <ghjeold_i_mwee@cox.net>
To: "Mitul Sen (misen)" <misen@cisco.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Setting format to SND_PCM_FORMAT_MU_LAW does not let	me apply hardware parameters
Date: Wed, 23 Jul 2008 11:25:54 -0700	[thread overview]
Message-ID: <488777B2.1060608@cox.net> (raw)
In-Reply-To: <3B6F5C9068D5864096EB291236C3386F02CE1663@xmb-sjc-21d.amer.cisco.com>

Mitul Sen (misen) wrote:
> Hi, 
> 
> I have tried using gdb both from the command line as you suggested and
> also from within eclipse. Even though I can step through the code and
> break properly, I think there is some mismatch between the source code
> and object code used by gdb. I say that because it sometimes steps
> through code in a way that makes no sense. For example, I see that a
> particular 'if' condition is satified and it goes into the 'if' clause
> and then again goes into the 'else' clause that is not expected. Is
> there any module that needs to be reloaded after building and installing
> the shared library? I have done a clean make at all times, checked
> timestamps, even rebooted the machine in case some driver related data
> needs to be reloaded at startup but none of this has helped.
I suspect you are debugging optimized code.  The 
optimizer rearranges and deletes instructions.  Did you 
specify -O0 so that no optimization occurs?  The other 
gotcha in the alsa-lib code is that some of the 
functions are actually macros.  They cannot be stepped 
through.  When you hit them in the debugger it is 
disconcerting.
> 
> Another thing that I notice is that when I use aplay to play the rtp
> data that I save to file (before writing to the sound device), and check
> the output of /proc/asound/card0/pcm0p/sub0/hw_params file, it is
> exactly the same as when I run my application. Using aplay does the
> playback properly even though hw_params still shows as
> 
> access: MMAP_INTERLEAVED
> format: S16_LE
> subformat: STD
> channels: 2
> rate: 48000 (48000/1) 
It is decoding it before it is playing it, it must be 
calling a routine somewhere to do that, or else it is 
built in.
> 
> Please note that I can play back the file using aplay, I only have the
> problem of bad audio when I try to write to the sound device in
> real-time. With this observation though I am not sure if the fact that
> the library seems to not use the card's decoder is really the problem. I
> am trying to look into the source code of aplay to see if I can spot any
> difference in the way the data is written to the buffer.
> 
Good not to limit the possibilities you are examining.
> Meanwhile, any comments and help will be greatly appreciated as usual.
> 
> Thanks for your help.
> 
> Regards,
> Mitul
> 

  reply	other threads:[~2008-07-23 18:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30 22:09 Setting format to SND_PCM_FORMAT_MU_LAW does not let me apply hardware parameters Mitul Sen (misen)
2008-07-01  7:39 ` Clemens Ladisch
2008-07-01 17:01   ` Mitul Sen (misen)
2008-07-01 13:59 ` stan
2008-07-01 18:42   ` Mitul Sen (misen)
2008-07-01 22:12     ` stan
2008-07-01 23:50       ` Mitul Sen (misen)
2008-07-02  2:20         ` stan
2008-07-03 18:55           ` Mitul Sen (misen)
2008-07-16 23:36           ` Mitul Sen (misen)
2008-07-17  3:30             ` stan
2008-07-23  0:11               ` Mitul Sen (misen)
2008-07-23 18:25                 ` stan [this message]
2008-07-23 21:31                   ` Mitul Sen (misen)
2008-07-24  0:46                     ` stan

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=488777B2.1060608@cox.net \
    --to=ghjeold_i_mwee@cox.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=misen@cisco.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