Bugfix in event decoder (?) #69
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
While running this decoder on a sequence of tokens (midifile ->
NoteSequence-> event_tokens), I realised that after every note is processed and we return to processing shifts, thecur_timeis reset (sincestart_timeis 0). This then causes an exception to be thrown fromnote_sequences#decode_note_event:I believe the
cur_timeshould be an offset ofstate.current_time, not ofstart_time- this allows the decoding sequence to pick up where it left off along the timeline.Code example: