Adjustment to get Musescore to jump to next page sooner during playback?

• Jul 25, 2024 - 02:49

When, during playback in page view mode, I'm singing along on the rightmost page of a score whose lyrics I haven't yet mastered, Musescore waits so late to jump to the next page that I don't have time to assimilate the lyrics on the new page quickly enough to sing them in tempo. Can the lead time for the switch to the new page be adjusted by the end user?


Comments

In reply to by Brer Fox

That solves about 1/4th of the problem. Another part of what I'm doing when rehearsing like this is becoming familiar with the score: where the repeats and jumps are, what the other parts are doing ... in short, assimilating the big picture. You don't get that in continuous view.

I often serve as a page turner for my wife when she's playing a new cello part. She always wants me to turn the page much sooner than Musescore does it. In anticipation, she looks ahead to the end of the line on the current page, takes what is there into short-term memory (from which she continues playing), and then wants a second or two to get reoriented on the new page.

In reply to by manonash

@manonash
Nicely described!

I hope practice and music education become forefront in MuseScore someday. That would dramatically expand the user base.

>> [Page view ] would only need to shift one system earlier of what its currently doing.
https://musescore.org/en/node/330306#comment-1217890

There are multiple problems with Continuous view>Horizontal + Settings>Advanced>Sooth Panning:

• at volta jumps MuseScore should arrive at the jump point slightly before it plays—ideally by an amount determined by the reader.

• horizontal scroll is jerky, even on my peppy MacBook Air M2, so that's tiring for the reader. (Perhaps a native silicon release will fix that?)

Most importantly: Even with smooth scrolling, horizontally "scrolling" the notation clashes with the concept of saccades and fixations.

Multiple studies have tracked eye movement of good music readers. The results show that visual processing only occurs effectively when the eyes are fixated on a point during which time a field of notes are perceived by peripheral vision. The rapid movement to the next fixation is called a saccade. During the saccade little if anything is processed due to saccadic masking.

MuseScore's horizontal notation scrolling via Continuous view>Horizontal + Settings>Advanced>Sooth Panning is somewhat akin to a constant saccade.

scorster

In reply to by scorster

>> I hope practice and music education become forefront in MuseScore someday. That would dramatically expand the user base. <<

Indeed. I use it regularly for practicing songs and choral pieces, and it's the best tool by far -- though of course I can, alas, only use it for that on pieces where I have the score in Musescore format. When I don't have a Musescore score, I use YouTube with an add-on that allows me to mark and jump to particular entrances, loop, and make fine-grained adjustments of tempo -- but it's far more convenient to do those things in Musescore. And then there's that ability to boost, in a choral piece, one particular part above the others, and/or to assign to it some instrument that makes the part stand out in bold relief -- both capabilities worth their weight in gold as learning aids!

In reply to by manonash

Glad we're thinking alike on MuseScore developing into the premiere music practice tool

Not to side track this thread, but you said >> I use YouTube with an add-on that allows me to mark and jump to particular entrances, loop, and make fine-grained adjustments of tempo <<

What is the name of that youTube add-on? I use Transcribe extensively, but of course it cannot "reach" into youTube. If you'd rather not post here, then please start a new thread. Or you can PM me.

scorster

In reply to by scorster

It's a browser extension called "Transpose". (It has functions named "Transpose" and "Pitch", along with the other stuff I mentioned, but I've never used them.) I use it in the Microsoft Edge browser at the moment, but I've used it in other browsers as well. It's probably just "Chrome compatible" or some such.

Do you still have an unanswered question? Please log in first to post your question.