Merge upstream #2263: Add vertical playback auto-scroll and note highlighting - #54
Merged
Conversation
Add optional vertical note following during piano roll playback. Center the active note vertically using frame-rate-independent exponential smoothing, configurable follow margin and damping, and a per-frame movement limit. Prepare scrolling before upcoming notes and ignore isolated melodic outliers to avoid abrupt jumps. Add the toggle to the piano roll View menu and expose vertical follow settings in Preferences.
Highlight the active piano roll note during playback with configurable fade-in and fade-out speeds. Add an opt-in View menu toggle, persist the preference, and avoid repainting NotesCanvas on playback tick updates when highlighting is disabled.
…ghlighting Cherry-picked from openutau#2263: openutau#2263 Conflicts were independent additions colliding at the same insertion points against already-merged features (openutau#2182's DiffSinger phrase boundary rendering, openutau#2230's detach-pianoroll menu item, openutau#2067's metronome preferences UI): - NotesCanvas.cs: combined the phoneme-error-aware hasError computation (existing) with this PR's playback-highlight blending, using consistent brush constants; kept both private method blocks (phrase boundary rendering + highlight animation) side by side, no actual overlap. - PianoRoll.axaml / PreferencesDialog.axaml: concatenated both menu items / settings sections, no overlap.
runit-xze
added a commit
that referenced
this pull request
Jul 25, 2026
Merge upstream openutau#2263: Add vertical playback auto-scroll and note highlighting
runit-xze
added a commit
that referenced
this pull request
Jul 25, 2026
Merge upstream openutau#2263: Add vertical playback auto-scroll and note highlighting
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pulls in stakira/OpenUtau#2263.
Previously closed as #42. Conflicts were independent additions colliding at the same insertion points against openutau#2182, openutau#2230, and openutau#2067 (all already merged). Resolved by combining rather than picking a side — see commit message for details, notably the note-brush logic now uses the phoneme-error-aware hasError check together with playback-highlight blending.