Integrated: 8319598: SMFParser misinterprets interrupted running status

2024-05-01 Thread Jan Trukenmüller
On Tue, 7 Nov 2023 19:18:28 GMT, Jan Trukenmüller wrote: > The MIDI file parser misinterprets events without status byte when they > appear directly after a Meta of SysEx event. > > For my bugfix I had to decide between two possible solutions: > - Strict sol

Re: RFR: 8319598: SMFParser misinterprets interrupted running status [v2]

2023-11-11 Thread Jan Trukenmüller
status of the last channel event as running > status > > I used the tolerant solution. > I will send an email to the list client-libs-dev with my reasons. Jan Trukenmüller has updated the pull request incrementally with one additional commit since the last revision: reduced line l

Re: RFR: 8319598: SMFParser misinterprets interrupted running status [v2]

2023-11-11 Thread Jan Trukenmüller
On Fri, 10 Nov 2023 21:08:27 GMT, Sergey Bylokhov wrote: >> Jan Trukenmüller has updated the pull request incrementally with one >> additional commit since the last revision: >> >> reduced line lengths > > test/jdk/javax/sound/midi/File/SMFInterruptedRunnin

Re: RFR: 8319598: SMFParser misinterprets interrupted running status

2023-11-08 Thread Jan Trukenmüller
On Tue, 7 Nov 2023 19:18:28 GMT, Jan Trukenmüller wrote: > The MIDI file parser misinterprets events without status byte when they > appear directly after a Meta of SysEx event. > > For my bugfix I had to decide between two possible solutions: > - Strict sol

Re: RFR: 8319598: SMFParser misinterprets interrupted running status

2023-11-07 Thread Jan Trukenmüller
Am 07.11.23 um 20:37 schrieb Jan Trukenmüller: The MIDI file parser misinterprets events without status byte when they appear directly after a Meta of SysEx event. For my bugfix I had to decide between two possible solutions: - Strict solution: Throw an InvalidMidiDataException - Tolerant

RFR: 8319598: SMFParser misinterprets interrupted running status

2023-11-07 Thread Jan Trukenmüller
The MIDI file parser misinterprets events without status byte when they appear directly after a Meta of SysEx event. For my bugfix I had to decide between two possible solutions: - Strict solution: Throw an InvalidMidiDataException - Tolerant solution: Use the status of the last channel event as