LMMS / LMMS/lmms

Looping Beat/Bassline Pattern Records Incorrectly

Open
#975 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Edited @tresf, added picture, better description

image


  1. Open a new BB pattern
  2. Add a new Automation Track
  3. Ctrl + Drag the Volume knob from the Kicker to the automation pattern
  4. Right-click the Automation Pattern, Set/Clear Record
  5. Click "Play"

Expected Behavior:

  • Knob position of kicker should be recorded inside Automation Pattern

Actual Behavior:

  • Recording is ok until a loop occurs; resetting to zero as depicted in the picture above

Original bug report

winXp32 1.0.92 tresf 10 jul.
to reproduce:

insert BB -make notes
insert AU-track
bind VOL
set AU-track rec
rec 1 bar of variation
let rec continue at fixed value != 0
The pattern will set to 0 during continued automation rec, not as expected, to the set-value
But, instead of seaching and killing that odd bug, usability wise, I Think REC should be automatically terminated as the length of the pattern is reached -eg Avoid over-writing recorded patterns, then this bug would not matter.
btw , had one crash clicking the overwrited track, but not reproduceable

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

Reproduce the issue in LMMS using the listed Beat/Bassline pattern, Automation Track, volume binding, and continued recording steps. Trace the automation recording path from this behavior and verify that a looping pattern preserves the set value instead of resetting to zero; no source file or test is named in the issue.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.