LMMS / LMMS/lmms

Beat&Bass-Editor Pattern cloning -Include automation and sample-tracks

Open
#3,337 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

#457 is the ticket for the neat method to clone B&B-patterns.
During testing, i realized that B&B inserted automation and sample-tracks, will be wrong after a pattern-cloning. This is a specific ticket for this improvement.

![bbandclonedsteps](https://cloud.githubusercontent.com/assets/6662066/22741478/a8a6ec7a-ee13-11e6-8c7a-5cebf7ceb3b4.jpg)
In top we have a pattern with two BB-instruments, but 3. and 4. track are resp. a sample, and an automation-track.

The second part of the img shows the result after a cloning of the two top tracks.
Now both the sample, and automation-track are 'wrong'. They need to be completely redone, but there really are no option to do that.
What i think is that the sample, and an automation-track actually also should have been cloned, and then placed in context of the cloned instrument-tracks.
like
![bbandclonedsteps3](https://cloud.githubusercontent.com/assets/6662066/22741602/0737f61c-ee14-11e6-9e50-14c3cbccc54d.jpg)

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 reading issue #457 and reproducing the Beat&Bass pattern-cloning case described in the screenshots, including automation and sample tracks. Done means cloning the instrument tracks also preserves and correctly relocates their associated sample and automation tracks in the cloned pattern.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
audio-video-rtc, 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.