LMMS / LMMS/lmms

Insert automation into new automation track when value is Ctrl+dragged onto any other track type in Song Editor

Open
#4,804 0 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement gui
Dominant language
C++
Stars
10.4k
Forks
1.3k
Avg merge
2d 13h
Merged PRs (30d)
7

Description

So, to automate a knob or something, normally you have to create a new automation track, drag that autmation track to the location you want it, then Ctrl+Drag the knob to the place you want. I have two ideas:

1. Make it so when a knob is Ctrl+Dragged onto an empty space in the Song Editor, it automatically creates a new Automation Track and places the automation TCO at the same X position of the mouse.

2. Make it so when a knob is Ctrl+Dragged onto any track other than an Automation Track, it places an Automation Track right below the track it was released on and places the automation TCO at the same X position of the mouse.

This would be quite helpful for speeding up workflow, especially with LMMS projects with 30+ tracks (which is common). So then, instead of needing to create a new track, drag it up to where you want it, then Ctrl+Dragging the knob to that spot, you would instead Ctrl+Drag the knob to wherever you want to automate the value.

For example, if you wanted the notes of a certain track to fade out at measure 8, you would Ctrl+Drag the volume knob to measure 8 on that instrument track, and it would automatically insert a new automation track below that and place the automation there. A 1 step process rather than a 3 (or much more, depending on project size and situation) step process.

Is there anything wrong with this idea? I think it would definitely be an improvement to LMMS, making automation seem less tedious and/or frustrating. Would there be any potential negatives for this idea?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Song Editor's Ctrl+drag handling and trace how Automation Tracks and automation TCOs are currently created and positioned. First resolve whether the empty-space behavior, the non-automation-track behavior, or both are intended; done means the selected behavior creates or inserts the track and places the automation at the mouse's X position.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.