[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: optical recognition for input
From: |
Valentin Petzel |
Subject: |
Re: optical recognition for input |
Date: |
Tue, 18 Jan 2022 20:30:24 +0100 |
Out of interest I tried Audiveris on a rather simple Lilypond score. The
results are somewhat okay, but not stellar (see for yourself). I think with
more complex scores this will quickly get messy. So I guess this could save
some time in very specific situations.
But the question is: Would you want that? In situations where this works you
probably have a high quality scan of a quality score, so the only reason why
you’d want to engrave it is to change things. But going the Scan→MusicXML→Ly
will not give you the clean structure you’d get from typing it yourself, so
working with these files is harder.
Cheers,
Valentin
Am Dienstag, 18. Jänner 2022, 10:36:36 CET schrieb Paul Hodges:
> From: Vincent Gay <vgay@vintherine.org>
>
> By curiosity I tried it with a score produced by Lilypond, the result is
> not very satisfactory. As it is, it seems to me that it is quicker to
> enter everything on the keyboard than to correct what the software has
> recognized.
>
> I've not tried Audiveris; but this is my impression from the Music OCR
> programs I've tried. I found PhotoScore (which came with Sibelius)
> essentially useless.
>
>
> I do use SharpEye (http://www.visiv.co.uk/) sometimes, on a clean score, but
> only some very specific styles of music make it worth it. The ability to
> edit on the spot, with the original in view is handy - except that the
> editor is extremely strange and hard to use. The current version is
> fifteen years old...
>
>
> Paul
Audiveris.pdf
Description: Adobe PDF document
Ly.pdf
Description: Adobe PDF document
signature.asc
Description: This is a digitally signed message part.
- optical recognition for input, James B. Wilkinson, 2022/01/15
- Re: optical recognition for input, Adam M. Griggs, 2022/01/15
- Re: optical recognition for input, James B. Wilkinson, 2022/01/17
- Re: optical recognition for input, Adam M. Griggs, 2022/01/17
- Re: optical recognition for input, James B. Wilkinson, 2022/01/17
- Re: optical recognition for input, Josiah Boothby, 2022/01/17
- Re: optical recognition for input, Kevin Pye, 2022/01/17
- Re: optical recognition for input, Vincent Gay, 2022/01/18
- Re: optical recognition for input, Paul Hodges, 2022/01/18
- Re: optical recognition for input,
Valentin Petzel <=
- Re: optical recognition for input, Paul Hodges, 2022/01/18