All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Hofman <pavel.hofman@insite.cz>
To: Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] PCM parameters in file plugin
Date: Mon, 26 Jan 2009 15:28:51 +0100	[thread overview]
Message-ID: <497DC8A3.4060706@insite.cz> (raw)
In-Reply-To: <4974FCC1.70907@insite.cz>

Pavel Hofman wrote:
> Pavel Hofman wrote:
>> Jaroslav Kysela wrote:
>>> On Tue, 6 Jan 2009, Pavel Hofman wrote:
>>>
>>>> Pavel Hofman napsal(a):
>>>>> Hello,
>>>>>
>>>>> I am working on a file plugin patch to allow adding PCM parameters 
>>>>> (rate, format) to  the name of the file created (plus the ability 
>>>>> to run an external command via popen, such as upsampling with sox). 
>>>>> I got stuck in trying to obtain these parameters in 
>>>>> pcm_file.c:_snd_pcm_file_open(). Is it actually possible or the 
>>>>> information is not available at the time of opening the file (and 
>>>>> the whole patch is thus nonsense)?
>>>>>
>>>>> Thanks a lot for help.
>>>>>
>>>> I am now opening the output file in 
>>>> pcm_file.c:snd_pcm_file_write_bytes.
>>>> Surprisingly it seems to work fine. Could such hack be accepted as a
>>>> patch to the plugin (if coded properly)? Is there a better place to 
>>>> open the file?
>>>
>>> The file should be opened in the hw_params callback (all PCM 
>>> parameters are known in this time). Also, extending filename with PCM 
>>> parameters should be optional (configurable). But the idea looks nice.
>>>
>>>                         Jaroslav
>>
> 
> Hello,
> 
> please find enclosed a patch for the file plugin. The
> checkpatch.pl script throws 5 bogus errors in doxygen comments.
> 
> Signed-off-by: Pavel Hofman <pavel.hofman@insite.cz>
> 
> * added support for including pcm stream params in the output filename
> * added support for piping the stream to a shell command if the filename
> string starts with a pipe char
> 
> Thanks a lot,
> 
> Pavel.

Hi,

Please let me know if there some areas to work on before the patch can
be accepted for merge.

Thanks a lot,

Pavel.

  reply	other threads:[~2009-01-26 14:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 20:54 PCM parameters in file plugin Pavel Hofman
2009-01-06  9:51 ` Pavel Hofman
2009-01-06 10:31   ` Jaroslav Kysela
2009-01-06 11:33     ` Pavel Hofman
2009-01-19 22:20       ` [PATCH] " Pavel Hofman
2009-01-26 14:28         ` Pavel Hofman [this message]
2009-01-28 15:41         ` Takashi Iwai
2009-01-28 23:00           ` Pavel Hofman
2009-01-29  8:28             ` Takashi Iwai
2009-01-29 10:54               ` Pavel Hofman
2009-01-29 11:01                 ` 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=497DC8A3.4060706@insite.cz \
    --to=pavel.hofman@insite.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    /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.