Troubleshooting - matthew-alex-hill/Transupposer GitHub Wiki
Error messages
... File not selected
A file needed for transposition such as the input file or the output file if you are writing to a file has not been selected.
Invalid file path
A file or directory you have provided does not exist
Invalid note entered, cannot change ... root
You have written something that is not understood as a note in one of the root selection text fields. Notes should be a letter corresponding to a note and any number of #s or bs only.
Note ... not found in transpose map Transposing may have unexpected results
A problem was found in a custom scale, one of the notes selected to be customised was not given a value.
Cannot locate device ...
A selected midi device cannot be found, it may have been unplugged during the selection process
... midi playback will likely not work
An error occurred in finding default a midi sequencer in your system, install one from the internet or check system settings to see what your default is.
Midi Write Error: ...
An error occurred when writing to a midi file. This is an IO problem and it is likely the file was lost or corrupted mid write.
Invalid Transposition.Note: ...
A note in a midi file is not recognised an cannot be transposed, the file does not follow the standard midi protocol and cannot be transposed.
No Transposer Found For Tick ...
An error has occurred in finding a relevant transposer at a timestamp for a recorded piece. Likely caused by either too frequent transposer switching (if sliders are used and auto-switching is on) or by a Midi file problem like events being stored in an unusual order.
Other
All other error messages have standard java sound or IO error messages and can be searched up online to find what the problem is.
Known Bugs
Midi File Played at Wrong Speed
A tempo change message was not found for the midi file, this is likely due to Transupposer not understanding the layout of this file. This shouldn't occur on files generated by software like MuseScore or Sibelius, as these programs were used in testing.
Resulting Midi File From Recording has Unwanted Sustained Notes Throughout The Piece
If your recording result has unwanted sustained notes that never end, it is due to a note off event for that note not being able to be found in the track, this could be caused by unusual midi event formatting like having note on and note off events in separate tracks and means that the file cannot be recorded from well. Files generated by software like MuseScore or Sibelius should be fine and not encounter this issue.