Ability to send CC to midi output
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
Although some software synthesizers are capable of very impressive things, there are cases when you can't avoid using some "metal". Being able to use hardware MIDI synthesizers is one of the many things that would make LMMS a much more professional program. There are many synths on the market that have no manual controls, only a black box with some ports, so MIDI is the only way of controlling them. Currently it is only possible to send note on/off and program change messages to an instrument, but it would be very nice if we could use hardware synths more or less the same way as the built-in ones.
There would be a new special track called "External synth" or something like that, in the row of Beat/Bassline, Sample track and Automation track buttons. This track could look the same as the existing instrument tracks, but without the volume and pan knobs. Maybe the blocks could be different color or something.
Clicking on a track could open a window, where the user could set up the MIDI device, channel and all this stuff, and on another tab you could create as many knobs as you want with each having a range of 0-127, and assign them to a MIDI CC number. This way you could directly control or automate the hardware synths.
What U think? :)
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
Start by inspecting the existing MIDI output handling for note on/off and program change messages, then compare it with the current instrument-track interface. The requested work would need a defined external-synth track, MIDI device and channel setup, configurable CC controls, and automation behavior; no files or tests are named in the issue.
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