Using multi/poly hardware with multi/poly native

multi/poly hardware works with multi/poly native in the following ways:

• You can exchange sounds between the hardware and native versions. Export from the hardware using the Editor/Librarian for macOS and Windows, and import using the Librarian page in the native version - or vice-versa. This includes all types of sound data, including Performances, Programs, Patches, Wavetables, Effects and Kaoss Physics Presets, Motion Sequences and Motion Sequence Lanes, Scales, and Set Lists.
• You can control the native version's Kaoss Physics from the x/y pad of any multi/poly hardware instrument, the modwave mkII or module, or finally an original modwave keyboard running software version 1.1.2 or later. Make sure that the Kaoss Physics MIDI CC assignments match between the hardware and native versions. On the hardware, these are on the MIDI CC Assign page; in the native version, they are in the Settings window. Note that the hardware communicates the direction and velocity as you “throw” the ball into the Kaoss Physics environment; the results are controlled by the Kaoss Physics settings of the native version, and not those of the hardware.
• You can control the native version's Mod Knobs with the Mod Knobs on the hardware. As with Kaoss Physics, make sure that the MIDI CC assignments match between the hardware and native versions.
• Naturally, you can also use the hardware as a standard MIDI controller for notes, mod wheel, pitch bend, and sustain pedal.

Realtime communication is via MIDI only, and is only from the hardware's MIDI output to the native version's MIDI input. If you're using multi/poly native within a DAW, you'll need to route the hardware's MIDI output to the native plug-in using your DAW's normal methods; record-enabling the track containing the plug-in generally works.