Revert 237558 "Use MIDIMessageQueue/IsValidWebMIDIData for MIDI ..."

Revert 237558 "Use MIDIMessageQueue/IsValidWebMIDIData for MIDI ..."

Seems to have caused issues running perf tests.

BUG=324160
> Use MIDIMessageQueue/IsValidWebMIDIData for MIDI byte stream validation
> 
> WebMIDI spec draft: http://www.w3.org/TR/webmidi/ 
> 
> WebMIDI API guarantees that MIDIInput::onmessage is called back with a single MIDI message. To guarantee this, this CL introduces MIDIMessageQueue class, which allows you to
> - maintain fragmented MIDI message.
> - Skip any invalid data sequence.
> - Reorder MIDI messages so that "System Real Time Message", which can be inserted at any point of the byte stream, can be placed at the boundary of complete MIDI messages.
> - (Optional) Reconstruct complete MIDI messages from data stream that is compressed with "running status".
> 
> This CL also replaces existing System Exclusive message validation logic in MIDIHost::OnSendData with MIDIHost::IsValidWebMIDIData, which can detect SysEx message even when it is concatenated with non-SysEx messages.
> 
> With this change, renderer/blink can be much simpler and free from this kind of data validation.
> 
> BUG=303599, 317355
> TEST=media_unittests --gtest_filter=MIDI*, content_unittests --gtest_filter=MIDI*
> 
> Review URL: https://codereview.chromium.org/68353002

TBR=yukawa@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=237660

[Ilya Sherman, 2013-11-28 02:41:50]

Committed patchset #1 manually as r237660.

[Takashi Toyoshima, 2013-11-28 02:58:16]

any informative data?
I don't think this CL can affect performance since the code path runs iff a user
uses the MIDI API, and perf tests do not have such a test, AFAIK.

[Ilya Sherman, 2013-12-03 00:03:29]

On 2013/11/28 02:58:16, Takashi Toyoshima (chromium) wrote:
> any informative data?
> I don't think this CL can affect performance since the code path runs iff a
user
> uses the MIDI API, and perf tests do not have such a test, AFAIK.

Yeah, this was an erroneous revert.  Looks like it's already been un-reverted. 
Apologies for the trouble!