Automatically Flagging Unprocessed Sheets In A CLI

[olizam]

Most of a piano score I have encountered comes with a front / rear cover, sample, and / or blank pages that don't usually get included in the OMR process. In other words, if a piano score has 6 pages and the song is only 3 pages, it usually starts from page #3 and ends on page #5. In a CLI, this is simple to instruct Audiveris to process ONLY pages starting from page 3 and ending on page 5. However, once the process has completed, Audiveris will still try to load the unprocessed pages when the processed score is loaded into Audiveris GUI until manually flagged as "INVALID". My question: Is there a way to flag unprocessed pages as "INVALID" during the CLI process so that the unprocessed page(s) won't get loaded by Audiveris GUI.

[hbitteur]

@olizam
Sorry for my late answer, I was on the road.

There is no immediate answer to your question.

First, sheet selection is different from sheet validity.
You can for instance select the sheets range X-Y, the engine will then process the (valid) sheets from number X to number Y.

Validity:
At processing time, the engine can guess if a sheet is invalid (and will ask the interactive user for confirmation).

• via GUI (Sheet | Current Status menu), at any time, you can set any sheet as either valid or invalid. And the status persists from one application run to another in the omr file.
• via CLI, there is no way to set the validity status.

Selection:

• via CLI (the -sheets command), the selection does not persist.
• via GUI (the Book | Select sheets menu), the selection persists.

In your particular case, you have selected and processed a few sheets (3-5) via CLI.
When you later open the resulting omr file, you would have to manually make the same sheet selection (once) at the GUI level.

The rationale is to not persist CLI arguments, since the command line itself can be persisted, for instance within a command file.
On the opposite, interactions made via the GUI need to be persisted.

[olizam]

Thank you for you response with a thorough explanation. Unfortunately, it looks like there's no way to flag unprocessed page(s) as invalid in CLI.