Skip to content
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

Braille Interval dirrection preferences not working correctly #23953

Open
4 tasks done
jmwmusic opened this issue Aug 8, 2024 · 2 comments
Open
4 tasks done

Braille Interval dirrection preferences not working correctly #23953

jmwmusic opened this issue Aug 8, 2024 · 2 comments
Assignees
Labels
accessibility Issues related to accessibility needs info More information is required before action can be taken UX/interaction

Comments

@jmwmusic
Copy link

jmwmusic commented Aug 8, 2024

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

Changing the Interval direction in the Braille preferences seems to have no effect on output in the Live Braille panel.

Some files seem to be stuck reading one way and others another and changing the preferences has no effect.

For example: The attached Star Wars file made for me by a sighted user using OCR then xml import has left hand intervals reading down even though I have my Preferences set to auto in which case treble should read down and bass up. I'm not sure if it is relevant that the file creator would not have had Braille panel activated.

A file created by another blind user as a test (also attached) works correctly for us both for auto with treble down and bass up.

However, changing the preferences does not seem to change the output for either of us, it is like the output preference has become somehow stuck in the file when created. downloading some sample files from MuseScore.com gives the same result, some are one way, some are the other, but none seem to be able to be changed.

To reproduce:

  1. Open the attached Star Wars file.
  2. Tab across to the Live Braille panel and note that the left hand intervals are reading down.
  3. Go to Edit, Preferences, Braille and change interval direction to Up.
  4. Go back to the score and again check the live Braille panel. Note the interval direction has not changed. Both hands still read down. Expected behaviour they would both now read Up.
  5. Go to Edit, preferences, Braille again and this time select interval direction as auto.
  6. Check the score output again and note it has still not changed, both hands still read down. Expected behaviour is that on Auto Treble will read down and bass up.
  7. Repeat this process with various other scores noting that whatever they first show as will not be able to be changed and will vary from file to file.

Supporting files, videos and screenshots

14 Star Wars - Chord Time Popular 2nd Ed.zip

What is the latest version of MuseScore Studio where this issue is present?

4.3

Regression

I was unable to check

Operating system

Windows 11

Additional context

Windows 11

Checklist

  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
@jmwmusic
Copy link
Author

jmwmusic commented Aug 8, 2024

Interval Test.zip

@bkunda bkunda added needs info More information is required before action can be taken accessibility Issues related to accessibility labels Aug 9, 2024
@bkunda bkunda assigned shoogle and oktophonie and unassigned Eism and oktophonie Aug 9, 2024
@bkunda
Copy link

bkunda commented Aug 9, 2024

@shoogle this needs more info about regression status before triaging. Pls investigate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Issues related to accessibility needs info More information is required before action can be taken UX/interaction
Projects
None yet
Development

No branches or pull requests

6 participants