LMMS / LMMS/lmms

Discuss : Step-by-step recording 1.3

Open
#6,483 0 comments 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
C++
Stars
10.4k
Forks
1.3k
Avg merge
2d 13h
Merged PRs (30d)
7

Description

Discuss : Step-by-step recording 1.3
I would like a discussion around this 1.3 feature:
![image](https://user-images.githubusercontent.com/6662066/183703191-64cffcb0-c0e5-4700-9acc-121105f53c5a.png)

### Enhancement Summary
The feature should have a From-key-down -> To-key-Up Option.
The functionality would be that the recording would start emediately as a key is pressed, but end emediately when the key is released. That would result in dynamic length recording-steps.
My model also has a _record-toggle_ key, and a _step-back_-key, to be explained.

#### Justification
Current feature records in last-note steps. That would be the way you would work, if you make an absolutely quantized melody, but that is an unnatural rigid way to compose. Step-by-step, where you could _dynamically_ record what _is played_, would be more natural imo.
It could be called _free step-by-step_
The best way this could be implemented was that there was a _toggle-key_ for the record-feature, that would give the user an opportunity to _test the next_ note/ chord, before it was actually added to the melody.
If its difficult to understand what i mean, imagine this situation:
You are making a chord-progession like
I – vi – IV – V, then you are in doubt.
Here free step-by-step would be a good feature.
First new addition would be a _jump-back-key_ -could be back-space. Each press sends the play-head one note/ chord back, and then start replay, giving you a quick way to listen to 1,2,3 or more previous recorded chords, and _then_ you can _test_ a next chord.
You can repeat this sequence n times, until you have found the _best next_ chord, then you press the _step-by-step-toggle-key_ and play the found best chord in the free length you like, press the _step-by-step-toggle-key_ and search for the next best chord, in the same way.
I think that type of _step-by-step_ recording would be more natural functional, than the current rigid quantized, witch i find uninteresting to use.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named. Start by locating the existing step-by-step recording and keyboard-handling implementation, then clarify the proposed toggle, key-down/key-up timing, replay, and step-back behavior. Done would mean an agreed design and an implemented free-length recording workflow matching those behaviors.

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
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.