-
Consider the following scenario: I've got a PDF file with sheet music, which I can parse easily with my own tools, resulting in precise information about all the glyphs, barlines and such stuff. In other words, I can skip the (supposedly) "hardest" part of what Audiveris is usually doing roughly up to the HEADS step. However, I'd still like to use Audiveris' capabilities of putting objects together in a meaningful way (stems with heads, beams with stems, dots, slurs…). What would be the best way to achieve this? Should I try to produce an .omr which would be then loaded into Audiveris? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
As long as you can craft a valid .omr file, Audiveris will accept it as an input for both the engine and the UI. A .omr file is just a zip archive of a hierarchy of .png and .xml files, for further details you can start with this section. What is not clear in your message is what you mean by "putting objects together". Are you referring to the engine or the user interface? |
Beta Was this translation helpful? Give feedback.
As long as you can craft a valid .omr file, Audiveris will accept it as an input for both the engine and the UI.
A .omr file is just a zip archive of a hierarchy of .png and .xml files, for further details you can start with this section.
What is not clear in your message is what you mean by "putting objects together". Are you referring to the engine or the user interface?