-
Notifications
You must be signed in to change notification settings - Fork 263
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
Audiveris option tweaks for orchestral scores #762
Comments
@Alterrien The scale step computed a interline value of 8 which is lower than the accepted minimum (11). The problem is that the engine now operates in some abnormal land. Here again I somehow cheated, by setting this constant from 0.15 to 0.5, and the BEAMS step no longer crashed. I was able to get the whole sheet transcribed, but many mistakes remain that would need manual correction by the end user. For example, here is a sharp ? And here, see the head, the augmentation dot, and a slur which appears rather thick (still by comparison). Is there any way to get this score with a higher resolution? |
Update: |
Hi Hervé, thanks a lot for all your feedback! |
Very good idea, assuming of course that the PDF uses vector graphics. |
Just my two cents: |
Thanks for the tip ! I did a very simple test using imagemagick to upscale
the pdf to 600dpi (and convert it to png). I can send you the image next
time I'm on my computer.
Audiveris fared much better, going through all the steps successfully and
correctly figuring out a bunch of the first page, but it still feels like I
was running against the limit of the system. Most notably the resulting PNG
went above the pixel size limit of 20M that I had to go over, and there was
still a fair amount of misidentifying glyphs and some poor dealing with
quirks of orchestral notations.
Le mar. 10 déc. 2024, 18:26, Hervé Bitteur ***@***.***> a
écrit :
… Just my two cents:
You might be interested by this handbook section enlarging low resolution
scans
<https://audiveris.github.io/audiveris/_pages/advanced/improve_input/#enlarging-low-resolution-scans>
contributed a couple of years ago by Ram Kromberg
—
Reply to this email directly, view it on GitHub
<#762 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACRNXCMQDDRJE6TIYGLNBDD2E4P3NAVCNFSM6AAAAABTBEJPF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZSGM2DSNBQGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hey again, |
Quality is much better this time. FYI, I'm attaching TheCloudMessenger.zip wich contains the resulting .omr (which I cannot upload directly on this forum) |
Hey there,
I'm trying to get Audiveris to work on a full orchestral score. The PDF in itself seems to be a direct export from an engraving software, so it should be fairly clean to work with. However, it seems like Audiveris struggles a lot with the smallness of all parts of the score.
You can get the PDF directly from IMSLP there: https://vmirror.imslp.org/files/imglnks/usimg/d/de/IMSLP741670-PMLP690923-THE_CLOUD_MESSENGER_FINAL.pdf.
One thing I had to tune is to set the min interline value to be much lower. It correctly detected the interline of 8, but could not apply it as it was lower than that setting. The error shown in the "should we set this page as invalid" was a bit misleading. See the logs below.
With this issue fixed, I can get a bit further in the pipeline, but it quickly fails at the BEAMS step with a nasty
java.lang.RuntimeException: org.audiveris.omr.math.Line$UndefinedLineException: Not enough defining points : 1
Would you have an idea on both how to fix my particular issue, and if there is a set of options I can set for Audiveris to better handle my score?
Thanks in advance!
The text was updated successfully, but these errors were encountered: