This page covers:
- What is stored in the Log
- How the Log can be useful
Note
Personal note: the Log was built as a quick afterthought and never really fleshed out, so it's only minimally useful and implemented really poorly!
What gets logged
The log has four categories. Each category is capped to just 50 of the most recent entries for that category.
Logs can be saved to a text file for ease of sharing (realistically, only to me) using the top right icon:
With the other icons to open log file locations and reset the current log respectively.
Notes
Logs MIDI note-on and note-off(*) events from both the live input MIDI device(*) and MIDI file playback(*) to assist in finding out specific velocities(*) or MIDI channels.(*)
Sustain
Logs sustain pedalling(*) events (Control Change, ID 67). Useful for setting sustain pedal floor and ceiling values under Simulation.(*)
Control
Logs any non-sustain control change MIDI events (typically Soft pedal or Sostenuto).
Other
The only somewhat useful tab. Logs:
- Any messages that appear on the bottom left of the screen
- Some system information (like MIDI file loading)
- Settings used when triggering render-to-video
- Time taken to render videos