Open
Conversation
Got a crash during CollectEvents when navigating+activating. These changes might help tame the timing (tick called only once now and not using actualTicks, so less calculation during sequencer playback
Bundled "toggle" and "play" commands
…ication. PREF_UI_APP_STARTUP_SHOWPLAYPANEL shown as General option in Preferences will potentially override to force always showing at startup if enabled
…. Purpose is to not need to restart manually when a midi device has powered off and powered back on again
… if a single CR is selected
55fecd4 to
d8351dc
Compare
d8351dc to
8d8f692
Compare
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
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.
Various Fixes
Some new basic abilities:
Playback panel retains positioning and visibility from previous sessions
When starting playback, the sequencer will automatically reset midi input. For example, if a plugged-in MIDI device has been on for "too long", often it will automatically shut down. After powering it on again, MuseScore 3.x will not recognize MIDI input until resetting by restarting its sequencer in preferences or pressing the MIDI restart button. This just makes that happen automatically when starting playback. Used to take a few seconds but now feels immediate. Mainly a concern for a "Piano Tutor" addendum that requires the sequencer to be in playback state.
Using the program's built in "Fullscreen" function (not OS's fullscreen shortcut) now allows for possibly making invisible the file menu + the toolbars + the file tabs. Can save just a little bit more vertical space this way.
P.S. Once again got the sequencer to be not having that "jitter" update of view...