TWO CHANNELS IN ONE EVENT TRACK — SAVED EDITOR CHECK, OCTOBER 15, 2026 Fresh own authored CC0 synthetic input, not a recording/recognition result. Editor session: https://midiviewer.io/midi-editor-online Exact editor release version was not shown/independently verified. The original input is 84 B, Type1, two tracks, PPQ480, tempo500000 us/quarter (120 BPM). Metadata track0 contains tempo and EOT at tick2880 (3s). Event track1 mixes two channels, with explicit status in every channel message: raw0/display1: note60 vel80 on0/off960 (0-1s), offvel0; CC64 127@0 (0s), 0@1920 (2s). raw1/display2: note64 vel64 on480/off1200 (.5-1.25s), offvel0; CC64 127@480 (.5s), 0@1440 (1.5s). Event track EOT tick2880 (3s). Both channels share track1; the file is NOT Type0 or single-track. The input includes no SysEx, port messages or unknown metadata. ACTUAL BROWSER ACTIONS Import the new input into the empty MIDIViewer editor widget. Download no-edit. Select all (two notes), choose+12, Apply once; download edited MIDI. No playback, quantization, tempo scaling, account save or public project save. Only actual completed actions/downloads support these results; UI wait/ref errors were kept in private records, not misreported as a failed editor export. The manufacturer's local-processing promise was not independently network-audited. No third-party UI screenshots or source code are distributed in this bundle. RESULTS Both real exports are82B. All four CC64 events keep original track/order/channel/ value/ticks/quarter-note positions/seconds. The two paired note numbers become 72/76 after +12; velocity and note start/off times stay unchanged. Both exports have different EOT fields: metadata track0 at0 instead of2880, event track1 at1920 instead of2880. The overall stored end becomes2s instead of3s. Each EOT delta uses one fewer byte; all channel status bytes stay explicit, no running-status savings here. Different bytes/file length do not mean channels or CC64 were lost. RECHECK Python3.12 + Mido1.3.3 in an existing suitable environment: python verify.py The verifier is read-only. It checks hashes, all11 ordered messages and this constant-tempo fixture's exact Fraction beat/second arithmetic. It does not run another browser export, upload/play/rewrite files or recreate third-party output. measurements.json includes the complete relevant stored fields and SHA256. Independent private production audit also used a separate raw SMF parser. LIMITS One fresh synthetic file and one browser editor session. No playback, receiver, DAW/hardware, audible-sustain, half-pedal, multiport, Omni, unknown metadata or all-editor preservation test. No real MP3 recognition or product-accuracy claim. EOT is stored file structure, not verified audible duration. Our site converter still does not recover/export CC64; this check does not add that capability. The same event track can contain separate channel-tagged histories; inspect both. LICENSE Own synthetic MIDI data, derived saved event data, measurements and diagram:CC0. Original verify.py:MIT. No third-party songs, software, screenshots or user drafts. See LICENSE.txt.