Tasks Output
Whenever a task execute button is pressed, output is sent to the tasks output console at the bottom of the tool.
The console runs in its own thread so that output doesn't interfere with task execution.
Task output form
Task output takes the following form:
- Task output beginning
- Task progress output (for some conversion tasks)
- Task output ending
- Task completion output indicating success or failure
- Database connection attempt output
- SQL query output (when selected)
Redirecting output
Output may be redirected to a file instead of to the tasks console.
Task output and SQL query output are handled separately.
The user can choose to direct each of these two types of output to either console or file.
SQL query output is only displayed when a "Show SQL" checkbox is selected for a database record conversion task.
To redirect output to a file:
- Go to the Output tab
- Select the To File option from the Task Output and/or SQL Output select lists
- Choose or enter the output file location
- Press the Save Settings button to save the output selections
XML validation output
see Tasks Interface -> Tasks Pages -> Validate XML
Conversion output to and from a MusicXML file or a database record
From MusicXML
The XML file is first validated against the MusicXML 4.0 schema before the actual data conversion takes place.
If schema validation fails, the task exits with exception, and the validation errors are displayed.
See XML validation output for validation error output examples.
From a database record
If a database connection hasn't been established, a database connection attempt is made.
The connection attempt will cause a delay in the loading of the Database Record from-conversion pane.
Connection attempt output is sent to the output console or file.
To MusicXML
To a database record
If a database connection hasn't been established, a database connection attempt will be made,
and output from the connection attempt will be sent to the output console or file.
Output for conversion to a LilyPond file
Any problems that the application's LilyPond conversion code encounters during conversion is output within the measure-by-measure progress output
so that the user can isolate any corrections that they might need to make.
Most commonly, these involve a measure's total duration amount, or problems handling slurs, ties, or wedges.
Output for conversion to PDF
Conversion to PDF uses LilyPond ly to PDF conversion functionality, and output sent to console or fle is LilyPond's own output.
Example output:
Progress output
Conversion progress output occurs when converting to or from a MusicXML file, or to a LilyPond file.
Display is by part and measure, with any errors, exceptions, or processing anomalies displayed within the measure
they occur so that the user can isolate any changes they want to make.
Database connection output
An example of successful connection output:
An unsuccessful connection attempt (incorrect login info):
Task output on completion
Successful completion:
Completion with errors:
followed by the exception message.
SQL output
SQL query output is generated by Hibernate.
For example:
Because of the volume of query output for many scores, it's recommended that SQL output be redirected to file (see above).