Connect sub-synth and add-synth's cutoff and resonance to existing zyn controls
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
This is an old 'problem'. When the lmms GUI was made, the lmms' FREQ and RES was connected to zasfx C.freq and Q resp. in the zasfx engine. A pecularity in zasufx means that the Q connection only is active if the chosen filter is a pole2. the two pole1 (LP/HPf1) has no handle. If possible these should also be handled from lmms-gui. Both the two other synths (sub-synt and PADsynth also needs handles)
All of this is perhaps futile to tacle, if a complete new version of zasfx are to be included in 1.1, then i gues these omitions should be disregarded. However -when- the new implemettion zasfx is made, these connetions should definately be made (and if for some reason the 'new' zasfx is prosponed, then the handles should be fixed in a ..next? release :)
Contributor guide
No contributing guide indexed for this repository
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
The issue names the LMMS GUI, zasfx engine, sub-synth and PADsynth, but no files or tests. Start by tracing the existing FREQ and RES connections from the GUI into zasfx, then determine how pole1 filters and the other synth controls are represented. Done requires an agreed scope and working cutoff/resonance handles, but the possible zasfx rewrite must be resolved first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100