From: JamiKettunen <JamiKettunen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: noise-suppression-for-voice-0.91
Date: Mon, 05 Sep 2022 10:42:58 +0200 [thread overview]
Message-ID: <20220905084258.LPqN4dreMt6nQcWZ_JMXz-MZ3YuPctex269cKzK25p4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36491@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]
New comment by JamiKettunen on void-packages repository
https://github.com/void-linux/void-packages/pull/36491#issuecomment-1236708557
Comment:
@mustaqimM Could this be bumped to [v1.03](https://github.com/werman/noise-suppression-for-voice/releases/tag/v1.03)?
> The same goes for LV2. I suggest building LV2 only for now.
@prez Why not both? I'm using this as a PipeWire LADSPA plugin as [documented on the README](https://github.com/werman/noise-suppression-for-voice#pipewire) and just tried to make it use the LV2 plugin but was unsuccessful.
I checked `lv2ls` (from `lilv`) and this could be problematic:
```
$ lv2ls
lilv_world_add_plugin(): warning: Duplicate plugin <https://github.com/werman/noise-suppression-for-voice>
lilv_world_add_plugin(): warning: ... found in file:///usr/lib64/lv2/rnnoise_stereo.lv2/
lilv_world_add_plugin(): warning: ... and file:///usr/lib64/lv2/rnnoise_mono.lv2/ (ignored)
...
https://github.com/werman/noise-suppression-for-voice
```
Considering the README itself mentions `It also would consume 2x resources` with regards to using the `stereo` plugin as compared to the `mono` one (which I know my microphone only is mono channel).
https://docs.pipewire.org/page_module_filter_chain.html mentions `For LV2, this is the plugin URI obtained with lv2ls` but I couldn't get it working. I'm very much a newbie when it comes to PipeWire configuration so if someone has a working LV2 `mono` plugin config I wouldn't mind LADSPA wasn't present in this package; I just want a working configuration with the `mono` plugin that's all.
next prev parent reply other threads:[~2022-09-05 8:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 6:12 [PR PATCH] " mustaqimM
2022-04-06 22:01 ` prez
2022-04-07 15:06 ` mustaqimM
2022-04-07 17:15 ` prez
2022-07-07 2:14 ` github-actions
2022-07-08 1:31 ` cinerea0
2022-09-05 8:42 ` JamiKettunen [this message]
2022-12-05 1:59 ` github-actions
2022-12-05 2:12 ` JamiKettunen
2022-12-05 2:12 ` JamiKettunen
2022-12-05 2:13 ` [PR REVIEW] " JamiKettunen
2022-12-05 3:16 ` [PR PATCH] [Updated] " mustaqimM
2022-12-05 3:51 ` mustaqimM
2023-02-09 4:27 ` [PR PATCH] [Closed]: " mustaqimM
2022-05-19 17:30 [PR PATCH] " optlink
2022-09-02 2:16 ` github-actions
2022-09-05 8:21 ` JamiKettunen
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=20220905084258.LPqN4dreMt6nQcWZ_JMXz-MZ3YuPctex269cKzK25p4@z \
--to=jamikettunen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).