Minimum track size
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
Enhancement Summary
Currently you can increase the size of the tracks but you can't reduce them to a smaller size than the standard one, and this is a problem for those projects that have many tracks because you have to be constantly scrolling, but this is solved by decreasing the size of the tracks and having a visible scrollable button that controls the vertical zoom of the tracks like this photo:
Implementation Details / Mockup
Before
After
1- In this photo the tracks are smaller than the standard size.
2- A scrollable button that controls the vertical size of the tracks.
3- When the tracks are at the minimum size:
A- The titles of the tracks and clips are shown.
B- The "Vol" and "Pan" titles are hidden.
C- The LED indicator for playing the instruments is reduced.
D- The icons of the editors are shown, (the one of the Piano Roll is used instead of the icons of each instrument).
E- The LED screen of the mixer channels is hidden.
F- The tracks are not seen cut but scaled.
(Google Translate)
Please search the issue tracker for existing feature requests before submitting your own.
- I have searched all existing issues and confirmed that this is not a duplicate.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue's Before/After mockups and the listed minimum-size behavior; no source files or tests are identified in the issue. Trace the existing track-size and vertical-zoom controls, then verify that the smaller tracks preserve the specified titles, indicators, editor icons, mixer display, and scaling behavior.
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
- 35/100