What can we help you with?
Keeping Pipe Organs Alive
- Providing technical services since 1999
- Manufacturer-independent assessment and recommendations
- Tuning, maintenance, repair, restoration, rebuilding and installation
- Expertise across pipework, wind systems, windchests, consoles and control systems
- A direct W-2 workforce for primary service, with third-party specialists used in collaboration with customers when unique projects require additional domain expertise
- In-house apprenticeship program for developing the next generation of pipe-organ technicians
- Written findings, work records and closeout documentation to support long-term continuity of instrument care
- Flat monthly billing programs offered for recurring tuning and maintenance
- National service coverage and long-term care relationships
Phone: +1 (888) 561-9121
MIDI Systems
A pipe-organ MIDI system sends and receives control events, not sound. On the systems documented below, a MIDI interface at the console turns key presses, stop changes, piston presses and expression shoe movements into MIDI data that an external device can use, and MIDI data arriving from outside is turned into playing requests that the instrument’s own stop control still governs. Whether an instrument can also record a performance and play it back, what media that depends on, and what external equipment it can exchange data with are product and generation questions rather than properties of MIDI itself.
This page is one of three under the combination, MIDI and software hub and covers only what MIDI carries and what a MIDI-equipped system can do with it. How a combination action stores and recalls registrations is explained in pipe-organ combination actions, and which settings an organist may change on a given system, as against those reserved to builder or technician access, is covered in configuration software, firmware and technician access boundaries.
What MIDI carries
A protocol for control data, not audio
MIDI is a protocol that lets musical instruments and devices communicate using digital messages that carry performance and device-control data such as notes, program changes and expression control, as its own standards body, the MIDI Association, defines it. The original 1983 specification set out a core data format and a serial transport on five-pin DIN connectors. Nothing in that stream is sound: a message reports that a key went down or a control changed, and whatever receives the message decides what to do with it. On a pipe organ, a MIDI system is the instrument’s implementation of that protocol, a way of moving control events into and out of the console.
What a console turns into MIDI
A MIDI interface turns the console’s switch closures into MIDI control data. Classic Organ Works’ 2009 manual for its MIDI Control Unit describes the unit converting key-switch information from keyboards, pedalboards, stops, pistons and other switches into MIDI control data, with drawknob, rocker-tab and pushbutton actions leaving as switch-on and switch-off messages. That is the whole job of an interface of this kind: it reduces every kind of console control to one stream of on and off events, and this unit provides no record or playback of its own.
Peterson’s ICS-4000 user manual describes its console record function from the other direction: all key presses, stop changes, expression shoe movements and other operations are encoded in standard MIDI format. Peterson’s catalog page for its MIDI Resource System likewise lists status-change information about keys, stops, expression contacts and miscellaneous controls as what that system records.
Stop changes deserve a note, because they are not a native MIDI concept. Solid State Organ Systems’ MIDI For MultiSystem Operation Guide documents stop changes, which it describes as not normally associated with MIDI, being sent and received on a designated port in addition to normal key information. Organ stop control over MIDI is therefore a system-specific extension, and two systems will not necessarily express a stop change the same way; Peterson’s ICS-4000 record and playback instructions, for example, encode organ stops in a proprietary MIDI System Exclusive format.
Record and playback
MIDI on the console does not mean the organ can record
A MIDI interface is not a recorder, and a console with MIDI sockets may have no way to capture a performance at all. The Classic Organ Works MIDI Control Unit converts console events into MIDI and provides no record or playback of its own. Peterson’s MIDI Resource System documented record and playback as depending on an external third-party MIDI sequencer, specifically the Yamaha MDF-3R MIDI data filer recording MIDI Format 0 files, and Peterson hosts the Yamaha MDF3 owner’s manual inside its own MIDI Resource System manuals folder.
The same separation shows up in how suppliers package the functions. As of September 1, 2026, Solid State Organ Systems lists MIDI (MFM) and an organ recorder (RFM) as two different MultiSystem add-on products, alongside tuning (TFM) and voicing (VFM) modules and an Organist Palette tablet control interface. Peterson’s documentation describes the MIDI Resource System in three configurations, ‘out only’, ‘record/playback only’ and ‘full in and out’, so within that one product family the presence of MIDI does not by itself say which configuration an instrument carries.
What a recording captures and what playback reproduces
A pipe-organ MIDI recording is a record of control gestures, not a sound recording. Peterson’s ICS-4000 user manual states that the console record function encodes all key presses, stop changes, expression shoe movements and other operations in standard MIDI format, and Peterson’s product page describes the ICS-4000 recording key, stop and expression data in standard MIDI format to internal memory without an external recorder. Syndyne documents MS8400 touchscreen recording and playback using Standard MIDI files, with record, play, pause, rewind, fast-forward and stop controls. Solid State Organ Systems’ RFM page says the recorder captures ‘the data stream from the MultiSystem at native speed’ to internal memory.
Because the file holds events rather than sound, playback reproduces the performance only on an instrument whose control system interprets those events the same way. A stop change stored in the proprietary System Exclusive encoding that Peterson documents for the ICS-4000 has no meaning to a system that never used that encoding. Solid State Organ Systems makes the point from the other side: the RFM can play other MIDI files from a USB stick, but its page notes that they will have to be manually registered, so the notes come from the file and the stops have to be drawn by hand. The record and playback functions Peterson’s ICS-4000 record and playback instruction sheet documents are recording, overwriting, a key pause feature, song selection, playback tempo adjustment and songlists.
Where recordings are stored and what they depend on
Storage media is one of the most product-specific parts of record and playback. Peterson’s ICS-4000 record and playback instructions name internal memory, floppy disk or USB flash drive, and state that the system reads .MID files as well as files with the .X?? extension used by Yamaha MDF sequencers. As of September 2, 2026, Peterson’s ICS-4000 product page states that users can ‘save MIDI recordings and combination action settings to an approved USB flash drive’ and describes built-in file utilities for renaming, copying and deleting those saved files. That product page does not state whether saving requires the supervisor password Peterson documents for configuration-level access, so who can perform it on a given instrument is a question for configuration software, firmware and technician access boundaries.
Solid State Organ Systems’ RFM page states that performance files ‘may be exported as MIDI files to a USB, edited and renamed on a computer, then reloaded.’ Syndyne’s MS8400 builder manual, in its 2019 revision, states that ‘Currently the MS8400 only plays MIDI type 0 single track files.’ The file type matters as much as the medium: a file one system writes is not automatically one that another system, or an earlier generation of the same system, will read.
MIDI input is routed through your stops
Why a stop must be open
For incoming MIDI to sound on the pipes, the relevant stop must be open. Solid State Organ Systems’ MIDI For MultiSystem Operation Guide, a 1996 revision still published as of September 1, 2026, records this as a functional boundary: MIDI input is routed through the instrument’s own stop control rather than bypassing it. An external keyboard or MIDI sequencer sending notes to a division with no stops drawn produces silence, and that silence is a normal routing condition rather than a fault.
The same guide describes stop changes traveling on a designated port in addition to key information, so on that system the stop state can itself be sent and received over MIDI, but only as that system’s extension of the protocol.
Channels, divisions and MIDI stop settings
MIDI channel assignment on an organ is an instrument-specific setup, not a fixed convention. The Solid State Organ Systems guide assigns MIDI channels per division as a configuration convention, with a worked example allocating channels sequentially from the top manual downward and giving divisions and MIDI stop outputs different channel numbering. The channel a division answers on therefore has to be read from that instrument’s own configuration record rather than assumed.
Some systems expose MIDI behavior as configurable settings. Syndyne’s 2019 MS8400 builder manual lists configurable Advanced MIDI Stops, MIDI Volume, MIDI Tuning, MIDI Stop Controls, MIDI Stops Pass-Thru and MIDI Pizzicato Set Time. Which of these an organist may change on a particular instrument, and which sit behind builder or technician access, is a configuration question covered in configuration software, firmware and technician access boundaries.
Connecting external devices
Ports and interfaces on the organ side
External devices connect through MIDI In, Out and Thru ports on a dedicated controller or interface unit, and what those ports do depends on the product. Syndyne documents MS8400 MIDI as MIDI In, MIDI Out and MIDI Thru ports on the MS8401 General Controller for external keyboard control and recording, with a separate MS8410 converting divisional keying, expression, console registration and temperature into MIDI messages for a digital sound module. Peterson describes the MIDI Resource System as a distinct product family that interfaces a pipe organ to external MIDI devices for recording, playback and sound-module control.
A dedicated interface of the MIDI Resource System kind carries its own organist controls. Its Version 1.68 operating instructions, dated 16 February 2000, document a front panel with Off/On/ANO, Prog/Use/Show, Channel Up/Down, Program Up/Down and Send/Receive controls, a Tuning potentiometer, Program, Channel and Manual LED readouts, a Set piston and a MIDI Cancel input. Those controls describe what the unit is for: selecting a channel and program, choosing between sending and receiving, and adjusting tuning against an external source.
Add-on and stand-alone units
Record and playback can also arrive as a separate unit rather than as part of the console’s control system. Syndyne’s Pro-Filer User Manual, revised 22 January 2010, documents the Pro-Filer 1 as a stand-alone MIDI sequencer with a 3.5-inch touchscreen, MIDI In, MIDI Out and MIDI Thru ports and a USB jack, recording and playing MIDI Type 0 files at 1/384 of a quarter note resolution on a standard USB flash drive, with adjustable tempo from 30 to 240 BPM and playlists of up to 100 songs. Solid State Organ Systems’ RFM page describes the recorder connecting to MultiSystem I through a proprietary MultiSystem PODI cable and to MultiSystem II through Ethernet, a reminder that an add-on is tied to the control-system generation it was designed for.
As of September 1, 2026, Peterson publishes named third-party integration notes in its manuals tree for both the MIDI Resource System and the ICS-4000, covering the Allen MDS-2 Expander, Allen Ensemble, Allen Smart Sequencer and Allen Vista Navigator II, the Rodgers PR-300 and Rodgers MX 200, the Viscount RD-70 and Viscount Expander EXL 150 and EXL 200, and the Ahlborn Archive Module. A published integration note is evidence that a named pairing was documented; it is not a statement that any device with a MIDI socket will work with the organ.
Which capabilities are product-specific
MIDI capability on a pipe organ belongs to a product generation, not to the instrument as such: the media a recorder writes to, the file types it reads and the devices it was documented with all change between generations, and suppliers qualify their own compatibility claims.
Generation and media limits
The same product family can depend on different media at different dates. Peterson’s ICS-4000 user manual states that beginning in late 2005 the ICS-4000 was supplied with a USB Port Panel and a separate Record/Playback Button Panel in place of the earlier Floppy Drive Control Panel. That is the only dated hardware-generation boundary Peterson states in its public ICS-4000 documentation, and it distinguishes console media panels rather than establishing a board, firmware or cabling revision.
Across Peterson generations, three separate media and platform dependencies are documented: the ICS-4000 application-software loading procedure names a 3.5-inch floppy disk alongside USB, the MIDI Resource System’s record and playback depended on the Yamaha MDF-3R floppy data filer, and the ICS ConfigTool configuration program is documented as a Windows 98/NT-based 32-bit program. Peterson’s catalog page for the MIDI Resource System describes recording to floppy disk through a MIDI sequencer and includes a DOS-based program for stop registration editing; the page remains linked from the 2026 catalog index, but its media and host-software assumptions date the described configuration to the 1990s.
On the Syndyne side, the 2019 MS8400 builder manual’s statement that the system ‘Currently’ plays only MIDI type 0 single track files is a dated capability statement, true of that revision and not necessarily of a later one. None of this says whether any of these products, media or programs is supported or obtainable today; that question is outside this page.
Compatibility statements and their limits
Compatibility claims in supplier literature are qualified by their own authors and should be read at their stated scope. Peterson’s MIDI Resource System brochure states that the system is compatible with nearly all pipe organs having electric key and stop action, and specifically that it works with the Peterson OrgaPlex switching and coupler system and with the Peterson Duo-Set or MSP-1000 combination actions; ‘nearly all’ is the brochure’s own hedge, and the specific pairings it names are Peterson’s own products. Syndyne’s Pro-Filer manual reports testing with Syndyne equipment and says the unit should work with general MIDI devices, while warning that non-standard MIDI messaging can produce undesired results.
Peterson’s 2015 MIDI Resource System installation instructions state that the system conforms to the MIDI Manufacturers Association MIDI 1.0 Specification Version 4.2. Conformance to the protocol is the floor for exchanging notes and control changes; it does not settle stop messages, which each system extends in its own way, or file types, which each recorder reads in its own set.
Scoping a recording or interface project starts with the system’s own documentation: which product family and generation the console carries, and what its documents say it can record and exchange. Settling that first is what keeps a project from being built around a capability the organ turns out not to have.
Frequently Asked Questions
MIDI carries control data between the organ and other equipment; it does not carry sound. The MIDI Association defines it as a protocol for digital messages carrying performance and device-control data such as notes, program changes and expression control. On a pipe organ a MIDI interface converts console gestures into that data: the 2009 manual for Classic Organ Works’ MIDI Control Unit describes key-switch information from keyboards, pedalboards, stops, pistons and other switches being converted into MIDI control data, with drawknob, rocker-tab and pushbutton actions sent as switch-on and switch-off messages. That conversion is documented for that one unit and manual generation; other systems document their own.
Not necessarily. MIDI on a console means control events can be sent or received; recording them is a separate function that some systems include and others leave to external equipment. The Classic Organ Works MIDI Control Unit converts console events to MIDI and provides no record or playback of its own, and Peterson’s MIDI Resource System documented record and playback as depending on an external third-party MIDI sequencer, the Yamaha MDF-3R MIDI data filer. Syndyne’s 2010 Pro-Filer manual documents the Pro-Filer 1 as a stand-alone MIDI sequencer that records and plays MIDI Type 0 files on a USB flash drive. Each of these statements speaks for the named product only, so whether your instrument records depends on which system and configuration it carries.
Control events, not audio. Peterson’s ICS-4000 user manual states that the console record function encodes all key presses, stop changes, expression shoe movements and other operations in standard MIDI format, and Peterson’s product page describes the ICS-4000 recording key, stop and expression data to internal memory without an external recorder; Syndyne documents MS8400 recording and playback using Standard MIDI files. Because the file holds the gestures rather than the sound, it is not a recording of the instrument’s tone, and playback reproduces the performance only on a system that interprets those events the same way, with stops in particular liable to be encoded in a system-specific format. Each of these descriptions is documented for the named product.
On the documented Solid State Organ Systems MultiSystem, no: the relevant stop must be open because MIDI input is routed through the instrument’s own stop control rather than bypassing it. Its MIDI For MultiSystem Operation Guide, as published as of September 1, 2026, also documents stop changes being sent and received on a designated port as that system’s own extension of MIDI. Silence from an external MIDI source when no stops are drawn is therefore a normal routing condition on that system, not a fault.
Yes, where the control system provides a MIDI interface for it, and the documented interfaces are product-specific. Peterson describes its MIDI Resource System as a product family that interfaces a pipe organ to external MIDI devices for recording, playback and sound-module control, documented in ‘out only’, ‘record/playback only’ and ‘full in and out’ configurations. Syndyne documents MIDI In, MIDI Out and MIDI Thru ports on the MS8401 General Controller for external keyboard control and recording, with the MS8410 converting divisional keying, expression, console registration and temperature into MIDI messages for a digital sound module, and Solid State Organ Systems lists MIDI (MFM) as one of four MultiSystem add-on products. Each is a product statement whose manufacturer qualifies its own compatibility claims, so a MIDI socket on a device does not by itself establish that it will work with a particular organ.