All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Bark <martin@barkynet.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] ladspa-sdk: new package
Date: Tue, 05 Aug 2014 21:50:28 +0100	[thread overview]
Message-ID: <53E14394.2030309@barkynet.com> (raw)
In-Reply-To: <20140804222345.65aacf17@free-electrons.com>


Thomas,

On 04/08/14 21:23, Thomas Petazzoni wrote:
> Dear Martin Bark,
>
> Sorry for the lack of feedback until now on these patches. See below
> for a number of comments.

That's fine, to be honest I forgot I submitted these patches :)

>
> On Thu, 24 Apr 2014 22:19:42 +0100, Martin Bark wrote:
>> LADSPA is a standard that allows software audio processors and
>> effects to be plugged into a wide range of audio synthesis and
>> recording packages.
>>
>> Signed-off-by: Martin Bark <martin@barkynet.com>
>
> First, looking at LADSPA, it seems like there has been no releases
> since 2007 or so. Is this still actively developed and used? Googling
> around, I've seen mentions of a new thing called LV2 which would be a
> LADSPA replacement.

Originally I started this because I wanted an equaliser for some work i 
was doing with acoustic echo cancellation. alsaeqaul was a quick easy 
way to add a equaliser i could change real time.  alsaequal needs caps 
which is an ladsp module hence the 3 patches.

I don't know if ladsp is under active development.  Really it's just the 
definition of an API in a C header file so I think it's not meant to 
change.  It's the packages like caps which implement the interface which 
i expect to be active.

caps is self contained (it includes a copy of ladsp.h) and does not need 
this ladsp-sdk package, i added it for completeness.

Is the lack of development activity an issue?  I could drop ladsp-sdk if 
you like.  Please let me know your thoughts.

Thanks

Martin

  reply	other threads:[~2014-08-05 20:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 21:19 [Buildroot] [PATCH 1/3] ladspa-sdk: new package Martin Bark
2014-04-24 21:19 ` [Buildroot] [PATCH 2/3] caps: " Martin Bark
2014-08-04 20:28   ` Thomas Petazzoni
2014-08-05 20:51     ` Martin Bark
2014-04-24 21:19 ` [Buildroot] [PATCH 3/3] alsaequal: " Martin Bark
2014-08-04 20:32   ` Thomas Petazzoni
2014-08-05 20:52     ` Martin Bark
2014-08-06  8:00       ` Thomas Petazzoni
2014-08-04 20:23 ` [Buildroot] [PATCH 1/3] ladspa-sdk: " Thomas Petazzoni
2014-08-05 20:50   ` Martin Bark [this message]
2014-08-06  7:59     ` Thomas Petazzoni

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=53E14394.2030309@barkynet.com \
    --to=martin@barkynet.com \
    --cc=buildroot@busybox.net \
    /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.