<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi Doron,</p>
    <p>'grep -ri ladspa <whatever_path> is a powerful tool that
      helped me to find my own '<span style="font-family:monospace"><span
          style="color:#000000;background-color:#ffffff;">README_pulseaudio.txt</span><br>
      </span>' file which says:</p>
    <p><span style="font-family:monospace"><span
style="font-weight:bold;color:#54ff54;background-color:#ffffff;">$</span><span
          style="color:#000000;background-color:#ffffff;"> cat -n
/media/sergei/d82573ae-e81f-472b-b2e5-4a9b31777d26/music/GenericBinauralFFTWsp/README_pulseaudio.txt</span><br>
            1  1) edit /etc/pulse/client.conf file to make sure
        <br>
            2
        <br>
            3  autospawn = no
        <br>
            4  .
        <br>
            5
        <br>
            6  Do I really need this ? Only while debugging the plugin
        while it crashes to prevent pulseaudio from constantly crashing
        and restarting ?
        <br>
            7
        <br>
            8  2) edit /etc/pulse/default.pa file to add to its end
        <br>
            9
        <br>
           10
        <br>
           11  .ifexists module-ladspa-sink.so
        <br>
           12  .nofail
        <br>
           13  load-module module-ladspa-sink
        sink_name=GenericBinauralFFTW plugin=GenericBinauralFFTW_1030
        label=1030
        <br>
           14  .fail
        <br>
           15  .endif
        <br>
           16
        <br>
           17  . the 'label' field must have the same value as
        (*LongEqPlusReverbDescriptor).Label field in the LADSPA plugin
        code - pay attention to capital 'L' vs small 'l';
        <br>
           18
        <br>
           19  3) kill pulseaudio with
        <br>
           20
        <br>
           21  pulseaudio -k
        <br>
           22  ;
        <br>
           23
        <br>
           24  4) start pulseaudio with
        <br>
           25
        <br>
           26  (export
        LADSPA_PATH=/mnt/althome/sergei/acoustics_work_sp/ladspa;
         pulseaudio -vvvvv --start --log-level=4 --log-target=syslog)
        <br>
           27
        <br>
           28  - adjust the
        '/mnt/althome/sergei/acoustics_work_sp/ladspa' path as
        necessary.
        <br>
        <span
style="font-weight:bold;color:#ff54ff;background-color:#ffffff;">sergei</span><span
          style="color:#000000;background-color:#ffffff;">@</span><span
style="font-weight:bold;color:#54ffff;background-color:#ffffff;">wdpurple</span><span
          style="color:#000000;background-color:#ffffff;">:</span><span
style="font-weight:bold;color:#54ff54;background-color:#ffffff;">~</span><br>
        <span style="color:#000000;background-color:#ffffff;">
        </span><br>
        <br>
      </span></p>
    <p>Pay special attention to the possible need to adjust LADSPA_PATH
      environment variable and to how 'pulseaudio' should be started
      with the adjusted LADSPA_PATH.</p>
    <p>Also, please find attached '/etc/pulse/client.conf',<span
        style="font-family:monospace"> '</span>/etc/pulse/default.pa'
      files reflecting what's written in the above README file.</p>
    <p>--Sergei.<br>
    </p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 6/9/24 11:24, Sergei Steshenko
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:9acd934f-dced-4509-9b92-7b60d3ee961d@yahoo.com">If you
      read LADSPA specification, you'll see that in a LADSPA plugin
      there are functions that are called once per plugin lifecycle. You
      can insert into those functions fprintf(stderr, ...) calls with
      diagnostic messages to make sure the plugin is indeed
      instantiated/used.
      <br>
      <br>
      For that matter, with big enough samples buffer you can insert the
      same kind of fprintf statements into the 'run' function.
      <br>
      <br>
      Also, LADSPA plugins should be listed in the PulseAudio
      configuration file. I did manage to run a pretty sophisticated
      LADSPA plugin of my own under PulseAudio several years ago; don't
      have PulseAudio configuration file at the moment at hand right
      now, maybe I'll find it later.
      <br>
      <br>
      --Sergei.
      <br>
      <br>
      On 09/06/2024 1:07, Doron Behar wrote:
      <br>
      <blockquote type="cite">Sorry for the late reply :) (I'm not used
        to mailing lists)
        <br>
        <br>
        On Mon, Jun 03, 2024 at 09:19:50PM -0700, Sean Greenslade wrote:
        <br>
        <blockquote type="cite">On Mon, Jun 03, 2024 at 06:17:59PM
          +0300, Doron Behar wrote:
          <br>
          <blockquote type="cite">I found this program I'd like to use:
            <br>
            <br>
            <a class="moz-txt-link-freetext" href="https://github.com/pulseaudio-equalizer-ladspa/equalizer">https://github.com/pulseaudio-equalizer-ladspa/equalizer</a>
            <br>
            <br>
            I managed to compile and run it, but I don't hear it makes a
            difference
            <br>
            in the sound. Do I need to enable the `module-ladspa-sink`
            module? Link:
            <br>
            <br>
<a class="moz-txt-link-freetext" href="https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/#module-ladspa-sink">https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/#module-ladspa-sink</a>
            <br>
            <br>
            What makes it difficult for me to figure this out myself, is
            the
            <br>
            [LADSPA](<a class="moz-txt-link-freetext" href="http://www.ladspa.org/">http://www.ladspa.org/</a>) link, which seems to
            general, because
            <br>
            this group develop many projects, or which I'm not sure
            which I should
            <br>
            compile as a pulseaudio plugin (some of which are available
            in my
            <br>
            distribution.
            <br>
            <br>
            Thanks for any help in advance.
            <br>
          </blockquote>
          What distro of Linux are you running?
          <br>
          <br>
          Eyeballing the Arch package for this equalizer, it looks like
          it needs
          <br>
          the swh-plugins package for the actual LADSPA plugin itself.
          It might be
          <br>
          named differently on your distro.
          <br>
        </blockquote>
        So I'm using NixOS and our `ladspaPlugins` package distributes
        the files
        <br>
        distributed by Arch Linux' `swh-plugins` package.
        <br>
        <br>
        <blockquote type="cite">You shouldn't need to manually load any
          modules in pulse; this equalizer
          <br>
          script seems to do all the module loading automagically.
          <br>
        </blockquote>
        OK, sounds promising. I'm still a bit confused how it won't
        output any
        <br>
        error if it doesn't find these plugins at all. Perhaps I'll
        continue to
        <br>
        discuss this with upstream at:
        <br>
        <br>
<a class="moz-txt-link-freetext" href="https://github.com/pulseaudio-equalizer-ladspa/equalizer/issues/58">https://github.com/pulseaudio-equalizer-ladspa/equalizer/issues/58</a>
        <br>
        <br>
        I will reply again to this thread if I'll learn something new
        after
        <br>
        discussing there.
        <br>
        <br>
        Thanks anyway.
        <br>
      </blockquote>
    </blockquote>
  </body>
</html>