Display bugs (2 - recent), a Measure bug (1 - always been there) & upgrade suggestions
Morning guys,
PC being used: Apple MacBook "Air"
OS: Sierra Ver 10.02
New Display Bugs:
After using MuseScore daily (with delight, I might add) for many months, yesterday two bugs appeared. After 'repairing' them using the dropdowns, today on opening MuseScore again, they're back.
1. Wallpaper colour and score colour are defaulting to black on black - took me a while yesterday to realise the file HAD loaded (and would play) but it was just that I couldn't see it.
2. The highlight feature which tells you where you are in editing the score has disappeared. Not being able to see exactly where I am is intensely annoying and slows down the transcription process unbelievably.
Permanent Bug (as in, it was there on first downloading MuseScore) Measure Size bug.
3. Using dropdowns to set the number of bars per line simply doesn't work and never has. MuseScore sets the measures/line itself and every single line has to be modified manually.
This desperately needs fixing.
If the piece is difficult (yes), and the music highly syncopated (often yes), you need to spread out the score to clearly identify the timing of the right and left hands.
Suggestion: Offer the ability to set the number of bars per line within a user-defined range. For example the screen could read/offer:
Bar range: xxx to yyy
Bars per line: zzz
Like this...
Bars 25-32: 2 Bars per line
Bars 33-34: 1 Bar per line
Bars 35 to end: 5 Bars per line
Further suggestion for Ver 03:
4. Setting the number of bars for the piece in a new composition needs to be retained. Default is 32 bars (way too few). Every time I set it to 50 and the next time, it's back at 32.
Screen needs a click box beside it to ask "Do you want to use this number of bars(measures) as your default?"
BTW: Please consider using the conventional names for things - it's not a "measure" it's a BAR.
5. After all this time, I still don't understand what you mean by the term "beam". Reading the Manual hasn't enlightened me... another example of you creating your own term for something that already has a conventional name??? What on earth IS a "beam"??
_______
All that said, I am looking forwards to Ver 3.0. I have abandoned Finale forever (deleted the software) and as a simple home pianist, never considered Sibelius... MuseScore is fabulous.
Thank you for the work you do.
Looking forwards to hearing from you.
Victoria
Comments
Can you explain further what you mean about #2 and #3? #1 is a known issue with Sierra apparently, but I don't understand there others are all. I don't know what highlighting you mean for #2. For #3, what drop down, and what are you trying to do exactly? Line breaks work normally for me, so doing what you describe should be simple. Perhaps you are misunderstanding the process?
As for measure versus bar, measure *is* the correct term in US English. If you use the British "translation", it will say bar. Beam as far as I know is the standard term in both US and Britain - it is the thing that connects eighth notes (also sixteenths etc).
In general, you should use the forum when asking for help with MuseScore, one thread per problem. Only turn to the issue tracker once a problem is confirmed as a bug.
1. See #126041: Black score view with MacOS Sierra.
2. Could you possibly be referring to the Navigator? That's still an option under the View menu, exactly the same as in the current MuseScore 2.
3. "Offer the ability to set the number of bars per line within a user-defined range." We do, in a much more straightforward way. Select measures (or bars in British English) 25-32, and use the menu to set them to two measure per line; select measures 33-34 and set them to one per line; select 35 to the end and set them to 5 per line.
4. Reasonable suggestion.
BTW: Switch your language setting in MuseScore's Preferences to "English (GB)" if you want.
5. https://en.wikipedia.org/wiki/Beam_(music)
BTW, the "Assigned" field is for the person who will fix a problem, not the person who reported it. Also, I'm changing this to "feature request" because I don't see any actual bugs described here. Most appears to be simple misunderstanding, but #4 does indeed seem to be an actual feature request, so once we clarify what is meant by #2 and #3 and hopefully confirm it is indeed a misunderstanding, we can mark this "active" again for the sake of #4.
No feedback