All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fernando Rodriguez <cyklonite@gmail.com>
To: Alsa-devel@alsa-project.org
Subject: Re: Question about the buffer length in the transfer callback of the PCM External Plugin
Date: Mon, 31 Oct 2016 14:11:17 -0400	[thread overview]
Message-ID: <20161031181116.GA25567@navi.local> (raw)
In-Reply-To: <a68475dd084f4a45b224791224c7c244@LGNMSXB01.prod.bk.dfs>

On Mon, Oct 31, 2016 at 09:01:02AM +0000, Bach, Andrea wrote:
> Hello,
> 
> how can I change the size that is provided inside the „transfer“-callback of an external PCM plugin?
> 
> Background:
> I need to write a filter plugin and I have to use for processing a chunk size of power of two (32, 64, or 128 bytes … that’s because of the use of FFT). But I get inside the transfer callback a buffer of length 1000. That would be ok if I could just return let's say  960 bytes – but after some struggling I have some doubt about it because I got the impression that ALSA cannot change the bitrate inside such a plugin – the documentation states it could not change the sample rate – but actually how can I return less or more bytes – so maybe the bitrate should also be constant? Maybe I misunderstood the concepts of ALSA completely?
> 

Yes.
You're working with raw PCM data, so the bitrate (bits per second) is
constant ((bit_depth/8) * samplerate * channels). The term usually
refers to compressed audio streams.

I haven't done this but by looking at the definition for the transfer
callback it looks pretty standard. It returns snd_pcm_sframes_t so I
suppose you can write less than *size* frames and return what was
actually written. It is signed so a negative value would indicate an
error. So you'll probably have to buffer any leftovers and write them on
the next call. That's not the same as changing the framerate because
at the end of the pipeline alsa will take care of playing it at the
right rate).

That should clear some of the confussion. You'll probably have to look
at alsa-lib or some plugin's source code for more details.


> Kind regards
> 
> Dr. A. Bach, Software-Entwicklung Simulatoren
> DFS Deutsche Flugsicherung GmbH
> Forschungszentrum
> Am DFS-Campus 5
> 63225 Langen
> 06103-707-5709
> 
> DFS Deutsche Flugsicherung GmbH
> Am DFS-Campus
> D - 63225 Langen
> 
> Tel.: +49-(0)6103-707-0
> 
> Sitz der Gesellschaft: Langen/Hessen
> Zuständiges Registergericht: AG Offenbach am Main, HRB 34977
> Vorsitzende des Aufsichtsrats: Dr. Martina Hinricher
> Geschäftsführer: Prof. Klaus-Dieter Scheurle (Vors.), Robert Schickling, Dr. Michael Hann
> 
> Internet: http://www.dfs.de
> Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

-- 
Fernando Rodriguez
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  parent reply	other threads:[~2016-10-31 18:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31  9:01 Question about the buffer length in the transfer callback of the PCM External Plugin Bach, Andrea
2016-10-31 10:10 ` Clemens Ladisch
     [not found]   ` <6c2af613d3b64138bc6e7c6cf69486cf@LGNMSXB01.prod.bk.dfs>
2016-11-01 11:49     ` Clemens Ladisch
     [not found]       ` <165e6496dc554e18836006a6b77461ce@LGNMSXB01.prod.bk.dfs>
2016-11-03 10:26         ` Clemens Ladisch
     [not found]           ` <1ce46f88056b4b2caa2ecf770da07d76@LGNMSXB01.prod.bk.dfs>
2016-11-03 14:44             ` Clemens Ladisch
     [not found]               ` <e48b1619d89d4f7faf5640fd2d337555@LGNMSXB01.prod.bk.dfs>
2016-11-06 11:26                 ` Clemens Ladisch
2016-10-31 18:11 ` Fernando Rodriguez [this message]
2016-10-31 18:47   ` Fernando Rodriguez

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=20161031181116.GA25567@navi.local \
    --to=cyklonite@gmail.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.