Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Keyon.Jey" <yang.jie@linux.intel.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
	alsa-devel@alsa-project.org,
	"Keyon.Jey" <yang.jie@linux.jf.intel.com>
Subject: Re: [tinycompress]how should I call compress_open	for aac ltp file playback?
Date: Fri, 07 Jun 2013 14:46:08 +0800	[thread overview]
Message-ID: <51B181B0.6070001@linux.intel.com> (raw)
In-Reply-To: <20130607002308.GD23045@intel.com>

On 06/07/2013 08:23 AM, Vinod Koul wrote:
> On Wed, Jun 05, 2013 at 04:27:44PM +0800, Keyon.Jey wrote:
>> On 06/05/2013 04:01 PM, Charles Keepax wrote:
>>> On Wed, Jun 05, 2013 at 02:46:04PM +0800, Keyon.Jey wrote:
>>>> I am trying to use tinycompress for hwdecoder. everything works fine,
>>>> but after compress_open (with profile = SND_AUDIOPROFILE_AAC level=0
>>>> ch_mode=0 rate_control=0), the playback of my aac-ltp-16bit-48KHz-Stereo
>>>> file is faster than it should be.  Am I wrong?
>>> Vinod is probably the person for this one, as I am not so
>>> familiar with what you guys have done internally. However, my
>>> guess would be you are not setting the sample_rate correctly? It
>>> likely needs to be set to the appropriate SNDRV_PCM_RATE_XXXX
>>> define. The source for cplay included in the tinycompress
>>> repository is a good example of using the tinycompress library.
>>>
>> thanks, Charles. the print log showed me that I have set
>> SNDRV_PCM_RATE_48000 which seems no problem.
>> the cplay example code is only for mp3 file, and it also not set
>> .level, .ch_mode and .rate_control.
>> Vinod, what's your suggestion?
> You need to ask your firmware guys, what are they expecting the these fields.
> Some decoder implementations can be different. But i would expect the audio to
> be broken, bad quality if that is the case.
>
> But the speed of playback can be due to different decoder output rate and
> different sampling rate configured. You are telling decoder 48Khz as CPM sample
> rate, is that what decoder is understanding and conversion to decoder values
> correct. Then you should check if the rendering to DAC is at 48KHz or not.
>
> --
> ~Vinod
>
thanks, Vinod, I will check with the firmware guys for these detail fields.

~Keyon

      reply	other threads:[~2013-06-07  6:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05  6:46 [tinycompress]how should I call compress_open for aac ltp file playback? Keyon.Jey
2013-06-05  8:01 ` Charles Keepax
2013-06-05  8:27   ` Keyon.Jey
2013-06-07  0:23     ` Vinod Koul
2013-06-07  6:46       ` Keyon.Jey [this message]

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=51B181B0.6070001@linux.intel.com \
    --to=yang.jie@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=vinod.koul@intel.com \
    --cc=yang.jie@linux.jf.intel.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