Sound enhancers for freebsd (like old pulseeffects. or like easyeffects in linux)

[LibreQuest]

Did you switch to the freebsd-fixes-001 branch ?

I just copied the git and ran the build script. By the way it uninstalled plasma6-plasma, kate, chromium, pipewire and some others. But I re-installed the packages. I guess there are conflicts with the dependent programs needed by pulseeffects. What additional step should I follow to get the script to build properly. I am very interested in running pulse effects to see it working. I have actually used it previously in a Linux system. But I honestly don't find it useful for my needs. I still would like to see it running, just cool. And it would be great to see it in ports / pkgs in the future releases.

 

[ArgentoSoma]

ArgentoSoma Well, the thread is about pulseeffects or similar.. please explain how audacious or musicpd can behave in a similar way as pulseeffects

What's wrong, can't you install pulseeffects or easyeffects?

It's simple, although from what I see it needs some patches to work 100%.

 

[astyle]

Some DE's like KDE or GNOME, they provide their own utilities to regulate PulseAudio. Those utilities tend to be in Ports. Failing that, the alternative is to study PulseAudio itself, and see what config options it offers. Like a .conf file to feed a daemon.

 

[besta]

I just copied the git and ran the build script. By the way it uninstalled plasma6-plasma, kate, chromium, pipewire and some others. But I re-installed the packages. I guess there are conflicts with the dependent programs needed by pulseeffects. What additional step should I follow to get the script to build properly. I am very interested in running pulse effects to see it working. I have actually used it previously in a Linux system. But I honestly don't find it useful for my needs. I still would like to see it running, just cool. And it would be great to see it in ports / pkgs in the future releases.

Maybe try building it inside a new bsd14.3 vm ?

 

[besta]

What's wrong, can't you install pulseeffects or easyeffects?

It's simple, although from what I see it needs some patches to work 100%.

ArgentoSoma yes, the objective here is to get the pulseeffects port fixed so we can use it again. Either that, or get the easyeffects to build and run on freebsd

 

[ArgentoSoma]

ArgentoSoma yes, the objective here is to get the pulseeffects port fixed so we can use it again. Either that, or get the easyeffects to build and run on freebsd

Forget pulseeffects, it's not even well supported on Linux.

easyeffects requires multimedia/pipewire with sysutils/seatd or access to the audio group to work properly, plus a couple of patches to compile and connect properly with pipewire.

But as you can see, it's possible to compile and get it working.

 

[wolffnx]

I was able to build pulseeffects under freebsd 14.3.

If anybody cares to help me test it, and if people are mostly happy with it, i will update the freebsd port if this works good enough for you guys. Some filters are not working, ie. the equalizer.. it seems to be able to activate, however any changes to its settings does not reflect in sound output.

Most other filters work as expected.. especially the bass enhancer one which i am more interested in

Here is the branch "freebsd-fixes-001" with some fixes for freebsd under my fork: https://github.com/hernan604/pulseeffects-legacy-freebsd/tree/freebsd-fixes-001

Clone the repo:

git clone -b freebsd-fixes-001 https://github.com/hernan604/pulseeffects-legacy-freebsd

cd pulseeffects-legacy-freebsd

Install dependencies:

./install_deps.sh

And then run build.sh to build and install:

./build.sh

NOTE: You need to enable dbus in /etc/rc.conf:

sysrc dbus_enable="YES"

(and reboot) -- if you start it manually with "service dbus onestart" you might need to run pulseeffects a couple times.. i recommend you enable in /etc/rc.conf and reboot

After you enabled dbus, run:

pulseeffects

And it is possible to run pulseeffects inside a bhyve vm also.. you will need to add the required parameters to your bhyve conf to get soundoutput. But that also works

The reason some plugins/effects are not working is because some of those plugins might have outdated bindings from the gstreamer libraries and what not. I asked in the wwmm issues page, and thats what i was told ( https://github.com/wwmm/easyeffects/issues/2876#issuecomment-2993638849 ).. some bindings were renamed over the years. I dont really know how to debug that, but if anyone cares, please submit a PR patch in my branch https://github.com/hernan604/pulseeffects-legacy-freebsd/tree/freebsd-fixes-001

Check it out and reply here if you like it or not

Hi , when I try to build (build.sh) I get this errors from boost-lib(I think)

../src/pulse_info_ui.cpp:159:21: error: no type named 'ipstream' in namespace 'boost::process'
  159 |     boost::process::ipstream pipe_stream;
      |     ~~~~~~~~~~~~~~~~^
../src/pulse_info_ui.cpp:160:26: error: expected ';' after expression
  160 |     boost::process::child c(command, boost::process::std_out > pipe_stream);
      |                          ^
      |                          ;
../src/pulse_info_ui.cpp:160:21: error: no member named 'child' in namespace 'boost::process'
  160 |     boost::process::child c(command, boost::process::std_out > pipe_stream);
      |     ~~~~~~~~~~~~~~~~^
../src/pulse_info_ui.cpp:160:54: error: no member named 'std_out' in namespace 'boost::process'
  160 |     boost::process::child c(command, boost::process::std_out > pipe_stream);
      |                                      ~~~~~~~~~~~~~~~~^
../src/pulse_info_ui.cpp:209:21: error: no type named 'ipstream' in namespace 'boost::process'
  209 |     boost::process::ipstream pipe_stream;
      |     ~~~~~~~~~~~~~~~~^
../src/pulse_info_ui.cpp:210:26: error: expected ';' after expression
  210 |     boost::process::child c(command, boost::process::std_out > pipe_stream);
      |                          ^
      |                          ;
../src/pulse_info_ui.cpp:210:21: error: no member named 'child' in namespace 'boost::process'
  210 |     boost::process::child c(command, boost::process::std_out > pipe_stream);
      |     ~~~~~~~~~~~~~~~~^
../src/pulse_info_ui.cpp:210:54: error: no member named 'std_out' in namespace 'boost::process'
  210 |     boost::process::child c(command, boost::process::std_out > pipe_stream);

Is there some workaround for this?
Thanks