-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plans for the Play Panel #16723
Comments
Nine months later ... here's a mockup of an expanded Play Panel concept! And I've posted an image on.org the shows a study guide concept. scorster |
Here's a related proposal for a making a tempo override field visible in the main Toolbar's Playback panel. [oMrSmith] (https://github.com/oMrSmith)'s proposal would expose the tempo override as a combi-button ... as opposed to a real estate hungry horizontal slider. Without this users have to undock the Playback panel to override tempo. I see oMrSmith's proposal as nicely compatible adjunct to the Practice Palette I proposed above—and hopefully a welcomed precursor! |
There are quite a few controls for a relatively small panel space. Edit. Should it be |
This looks very promising and would be a huge help for rehearsing. |
Revamp the Play Panel for MuseScore 4
No matter how I look at MS3's Play Panel it seems roughly cobbled together. I recommend a review of the design intent of MuseScore's Play Panel before reinstating it in MS4 and addressing the current behaviors that fail to meet those criteria. Additionally, reconstruct the Play Panel into a substantive and efficient Looping tool for composers, arrangers, and particularly for practicing musicians and students.
I've posted some ideas on .org's issue tracker and forum.
If others on Github express interest I'll gladly update the v3 Issue Tracker post and consolidate points made there, combine them with addition observations and suggestions, and post the result here.
Problem to be solved
The MS3 Play Panel mainly houses instances of controls found elsewhere in the UI:
• Play/Pause
• Rewind to Start
• the Loop Playback toggle
• a Playback Position slider—doesn't seem like a great feature, AND it doesn't work well.
• Count-in click toggle
• Metronome toggle
• Master Volume
• Metronome volume field and slider (you'd think we'd get those by double-clicking the Transport's Metronome icon, or via a right click contextual menu. And possibly the only MS3 control was in the Play Panel. Nicely MS4's mixer has a Metronome channel.)
In all, MS4's Play Panel houses only two unique features:
• Tempo Override
• the flag buttons—which are essentially superfluous because the user can more reliably define the selection by performing a range selection in the score.
So really v4's Play Panel ONLY offers the Tempo Override ... at the expense of undocking the Playback from the tool bar, with the result of wasting screen real estate. (As mentioned, MS4 has Metronome volume control via a Mixer channel.)
I'd like to see the Play Panel house more transport controls, like transport locator options never yet available in MuseScore, making it worth undocking.
A new design intent specification might benefit from a review of some of the Play Panel issues and requests discussed on .org. Here's another search.
Requested enhancements: The addition of new Play Panel "Study Guide" features would aid students in practicing. It would also attract to MuseScore educators and students who wish to use such features.
Examples of existing study guide software
Transcribe (seventhstring.com) has strong looping features. I can provide a concise screencast that demonstrates
MakeMusic has made large efforts in the direction music practice, but having never used it, I can't report on its efficacy.
Study Guide Mockup
Here's a mockup of a Play Panel study guide. The example shows Measure 7 selected (and therefore looping during playback). The student can click to move to another section in the list. Or if the student selected an Automated Study Guide then the Play Panel serves up the loops as designated by the scorist or an instructor, playing them in a particular order, for a certain number of iterations, possibly with increase levels of tempo, followed by review regimes:
And when the tempo reaches three to four notes per second the "script" could overlay an opaque rectangle atop the looped notation, or make it otherwise not readable. This means that once the speed is sufficient to established the memorization in working (short term) memory the script requires the student to play by heart. And looping by heart at three to four notes per second produces long term memory. A system like this teaches memorization techniques, it can escort students through various approaches, and encourages students to adopt effective practice techniques due to rewards naturally and reliably garnered.
Another option: Toggle sound output every other time through the loop. This would test the players ability to maintain time, and allow them to hear their instrument "soloed."
scorster
The text was updated successfully, but these errors were encountered: