LMMS / LMMS/lmms

In piano roll view, change to another track without losing the time position

Open
#2,093 3 comments 1 reaction 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

Hi... I'm erally new in LMMS and I don't know if there is an easy way to solve this difficulty:

Basically, I need to change between instruments mantaining the time position in the piano roll allowing me to compare notes between tracks easily (Like the old Voyetra Sequencer Plus or ...)

Actually, LMMS forces me to double-click on "Song-editor" window each time I need to change viewed track... then the piano roll is scrolled at the beginning of the "pattern" and I have to reposition manually to the dessired time point... this is really discouraging to double-click + reposition about 10+ times per minute.

If no actual solution, one possible one could be a CTRL+PgUp/PgDown in Piano Roll Window.

Thank you

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 reproducing the track-switching workflow between the Song Editor and Piano Roll, noting how the current time position is reset. Read the Piano Roll and Song Editor entry points you find while tracing that workflow; done means switching tracks preserves the viewed time position or provides the requested keyboard navigation without manual repositioning.

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
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.