LMMS / LMMS/lmms

Cloning tracks and TCOs between Song Editor and B&B Editor

Open
#3,043 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Currently Ctrl+dragging a track from either editor to the other will bring its TCOs with it. This can be a problem because the order of TCOs in the B&B editor has no relation to song time, and likewise the order in the Song Editor has no relation to the B&B pattern number.

I'd like to suggest the behaviour be changed so that Ctrl+dragging an instrument between the two editors would work exactly like dragging a preset from the browser; in other words, if dragging onto an existing instrument track, keep its TCOs intact if there are any.

A related issue is that Ctrl+dragging TCOs from the B&B Editor to the Song Editor doesn't always work reliably (which will need some investigation), while the same in the other direction is not at all possible. Automation and Sample TCOs can't be cloned in either direction.

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 by tracing Ctrl-drag handling in the Song Editor and B&B Editor, then compare it with dragging a preset from the browser. Check the existing behavior for instrument, automation, sample, and other TCOs; done means cross-editor cloning follows the requested track and TCO rules and unreliable or unsupported directions are addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.