Replies: 4 comments
-
@Blaxzter Here, the image is of very good quality, therefore we can suspect a wrong height guess (due to the lack of enough beams in the sheet at hand). |
Beta Was this translation helpful? Give feedback.
-
Do you have any information regarding the second question about errors? |
Beta Was this translation helpful? Give feedback.
-
Output from GUI:
And the cli command:
My question: Is the log indicating a warning / error this one: Measure{#8P1} No timeOffset for HeadChordInter#400{(0.947/0.947) slot#5 dur:1/4} ? |
Beta Was this translation helpful? Give feedback.
-
@Blaxzter I just ran Audiveris 5.4-alpha on your input file, and I got this:
to be compared with "your" results:
In "my" results, the measured beam height (29 pixels) has been rejected, and the guessed value (15 pixels) was finally chosen. Not surprisingly, the later BEAMS step is able to recognize the beam element. While in your case, 29 pixels is way too big, resulting in no beam being recognized. The question is: Why do we get different behaviors of the SCALE step? Please make sure you are using the latest development version. For this use:
Final transcription result is: Note that Audiveris complains:
|
Beta Was this translation helpful? Give feedback.
-
Hey everyone,
i'm using the tool to transcribe a bunch of sheet music and had to realize that this:
was sadly transcribed to this
which is then - in an opened audiveris GUI - marked as error, which I can correct.
But when using the CLI it happily exports the music (mxl) and removes the second note.
Here are my questions:
What would we have to change in the original score to minimize these detection errors, as I don't really understand why it was unable to detect the beam.
And when using the CLI, how do I mute all output and get wrong tabs. Or parse the output so I can flag it for error and go over it later.
Best wishes
Frederic
Beta Was this translation helpful? Give feedback.
All reactions