Conversation
There is also a filter based on the link, but it is hidden
There was a problem hiding this comment.
Pull request overview
Adds a new RNNoise-based audio noise reduction filter to Shotcut’s QML filter catalog, along with build-script support to fetch/build the rnnoise library as part of the Shotcut dependency build workflow (noting the dependency on the referenced MLT change).
Changes:
- Added
audio_rnnoisefilter UI + metadata for an RNNoise noise reduction audio filter. - Added a hidden
audio_rnnoise_linkmetadata entry (and UI) for an RNNoise-based link filter. - Updated
build-shotcut.shandbuild-shotcut-msys2.shto optionally clone/build/installxiph/rnnoise(v0.2).
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 10 comments.
Show a summary per file
| File | Description |
|---|---|
| src/qml/filters/audio_rnnoise/ui.qml | New QML UI for RNNoise suppression (“mix”) control + preset integration. |
| src/qml/filters/audio_rnnoise/meta.qml | New filter metadata entry for the RNNoise audio filter. |
| src/qml/filters/audio_rnnoise_link/ui.qml | New QML UI (duplicated) for the hidden RNNoise link entry. |
| src/qml/filters/audio_rnnoise_link/meta.qml | New hidden link metadata entry for RNNoise. |
| scripts/build-shotcut.sh | Adds rnnoise repo/config/build/install steps to the dependency build script. |
| scripts/build-shotcut-msys2.sh | Adds rnnoise repo/config/build/install steps for the MSYS2 build script. |
|
Why is the link hidden? Is there some magical way that links are automatically added that I forgot about? |
I implemented both filter and link to make it easy to test both services in MLT. But I only exposed the filter. Here is the complication:
Ideally, the filter would be applied to tracks and the link would be applied to clips. But I do not think that is user friendly. It is easy to hide/unhide either or both. I wonder what you think about this. |
I tried it myself and I am surprised that it works that well. I'm sure users will find it to be unexpected and report it as a bug. Or at least ask why they can't move it around. Maybe, we could name audio links something else so users can understand the order. Like we could call that section heading "Audio Preprocess". Or, since we only have noise reduction and declick, the section heading could be "Noise & Repair". To be clear, I am only suggesting to change the text in the section header of the applied filters list. When selecting filters, they would both still be in the "Audio" list. I am not proposing to add a whole new category of filters. |
|
Here is a patch that demonstrates my suggestion. I do not feel strongly about the name of the section as long as we don't duplicate "Audio" twice. |
That's my favorite version so far. I asked AI for more name ideas for "Preprocess":
I kind of like Input/Source/Clip to imply that the processing occurs on the source clip rather than on individual frames. But I do not know if it is good to expose that implementation detail to the user. And "Preprocess" is a pretty common word that people can understand conceptually. |



There is also a filter based on the link, but it is hidden
Depends on mltframework/mlt#1249