-
Notifications
You must be signed in to change notification settings - Fork 252
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
Key change in mxl in every export #725
Comments
Perhaps, this is due to the lack of any header at the beginning of the second staff. |
I can confirm that the root cause is the lack of standard header at the beginning of second staff. The real solution would be to feed Audiveris with a legal / standard staff. A manual workaround is as follows (I just tried it):
Then export.
|
Thank you for your help. As my background in in music isn't so deep I didn't know that the sheet music wasn't legal. As I have currently 500 sheet music with this layout, (with more coming in) fixing them manually would be a bit tedious. If there is no flag or option I could use that doesn't allow key changes/ or a different default action on faulty staffs than I'll probably have to talk to the team. |
Hello everyone, I have to miss a setting somewhere.
In every single transcription I do, there is a key change on the new line:
This is the input:
And this is the mxl file loaded in muse score:
And also the same happens when transforming to abc notation.
It happens with all the music I tested.
I've looked into the xml file and I see this in the 5th measure:
When I delete that, all following notes of that key will have a natural sign:
Help pls.
I don't know why it does that.
Original start file:
Audiveris
Role: Optical Music Recognition
Version: 5.4-alpha:698b2bb69
Software license: GNU Affero GPL v3
OCR engine: Tesseract OCR, version 5.3.1
Java vendor: Microsoft
Java version: 17.0.10
Java runtime: OpenJDK Runtime Environment (build 17.0.10+7-LTS)
Java VM: OpenJDK 64-Bit Server VM (build 17.0.10+7-LTS, mixed mode, sharing)
Operating System: Windows 11 10.0
Architecture: amd64
The text was updated successfully, but these errors were encountered: