musescore / musescore/MuseScore
Add strength control to Muse Reverb
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Your idea
Either give the "Muse Reverb" Plug-in its own strength controls, or add Muse Reverb as one of the Reverb sound signatures in the MuseFX reverb library.
Problem to be solved
Muse Reverb is applied to Aux 1 and therefore not effected by the usual instrument panning.
So if you want to have the reverb correctly applied after panning, you need to it via plug-in.
The MuseFX Plugin gives you all the controls needed, but not the reverb sound Muse Reverb has.
And the Muse Reverb Plugin gives you the sound, but seemingly no way to control its strength, if used as a plug-in.
Prior art
No response
Additional context
I do not know if my version of Muse Reverb is bugged and you either shouldn't be able to use it as plug-in or a window should appear when double klicking on its name, like with all the other plug-ins.
I always directly downloaded all the FX and reverb Plug-ins upon their release since Musescore 4 came out. That is why I for example almost have every effect in the MuseFX library twice in the selection window.
Checklist
- This request follows the guidelines for reporting issues
- I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Reproduce Muse Reverb as a plug-in and compare it with the MuseFX reverb library, checking whether a plug-in window or strength control is available. Done requires a decided approach that enables Muse Reverb strength control after instrument panning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100