Configuring MIDI Devices in Cakewalk Sonar

Learn how to manage your MIDI input and output devices in Cakewalk Sonar to ensure smooth communication with your MIDI hardware and controllers.

Devices

The Devices section in Cakewalk Sonar's Preferences allows you to choose which MIDI input and output devices are available for use in your projects. Configuring these settings correctly is essential for successful MIDI communication with your hardware.

MIDI InputThis section lists all available MIDI input devices. Select the ones you want to use for recording MIDI data into Cakewalk. If you only have one device, ensure it's selected here.
MIDI OutputChoose which MIDI output devices Sonar should use to send MIDI data to external hardware (e.g., synthesizers, sound modules). If your system has multiple outputs, you can:
Playback and Recording

The Playback and Recording section in Cakewalk Sonar lets you customize how MIDI data is recorded and played back. You can fine-tune everything from MIDI echo settings to buffer size and recorded event types, giving you more control and stability when working with MIDI.Driver Mode

Driver Mode
MME MIDI (Legacy)The traditional MIDI driver used in earlier Windows versions.
UWP MIDI (Universal Windows Platform)Introduced in Windows 10, UWP offers advanced support including Bluetooth LE MIDI and multi-client access to MIDI ports.

⚠️ Note: This setting is only available on Windows 10 or later, and only when no project is currently open.

Record Option
Choose which MIDI events you want Sonar to capture during recording:
  • Allow MIDI Recording without an Armed Track: Enables recording even when no track is armed.
  • Notes: Records standard note-on and note-off events.
  • Key Aftertouch: Records pressure data applied to individual keys.
  • Controller Events: Captures data from MIDI controllers (mod wheel, sustain pedal, etc.).
  • Patch Changes: Records instrument/program changes.
  • Channel Aftertouch: Captures channel-wide pressure data.
  • Pitch Wheel: Records pitch bend movements.
  • System Exclusive (Sysx): Captures manufacturer-specific MIDI data.
Number of Buffers: Set how many MIDI buffers Sonar should during playback and recording 
  • Default: 64
  • If you experience MIDI overflow, increase to 128 or more.
Echo System Exclusive: Enable this to send Sysx data to selected output ports.
MIDI Sysx Echo Ports: Specify which MIDI ports should receive echoed Sysx data.
Playback Settings
Prepare Using ‘N’ Millisecond Buffers: Determines how far in advance Sonar processes MIDI data before playing it.
  • Default: 200 ms
  • Increase this if playback stutters or cuts off.
  • Decrease it (e.g., to 50 ms) for more responsive MIDI effects changes.
Always Echo Current MIDI Track: When enabled (default), MIDI input is echoed through the currently selected track, even if that track’s Input Echo is turned off.
MIDI Files
Always Use Sysx Banks for MIDI Files:Converts imported Sysx data into Sysx banks (shown in the Event List), improving management.
  • If disabled, short Sysx data (≤255 bytes) remains as events, while longer ones are banke
Write Cable Meta Events to MIDI Files (Port Select): Inserts cable select messages to specify output ports in format 1 MIDI files. This lets Sonar route Sysx banks to specific devices more reliably.
Instrument

The Instruments section lets you assign instrument definitions to specific MIDI output and channel combinations. These assignments determine which bank names, patch names, note names, and controller names you’ll see throughout Sonar—helping you match your software with the hardware instruments you’re using.

How It Works

Each MIDI output can support up to 16 channels. For each output/channel combination, you can specify an instrument definition that aligns with the capabilities of your connected hardware.

For example:

  • If you have a Roland GS synthesizer connected to MIDI Output 1, you can assign all 16 channels of Output 1 to the Roland GS definition for consistent patch and controller naming.
  • If you’re using channel 10 for drums (standard in General MIDI), you might assign Roland GS Drumsets to just that channel, while keeping the other channels assigned to Roland GS.
  • If multiple instruments share one MIDI output but use different channel ranges, you can assign different instrument definitions to each channel group accordingly.
Instrument Section Settings
Output/ChannelThis column shows all MIDI outputs and their 16 associated channels. Select the channels you want to assign an instrument to. Use CTRL-click or SHIFT-click to select multiple channels at once.
Uses InstrumentThis column lists all available instrument definitions. Select one to assign it to the selected output/channel combinations. These definitions ensure Sonar displays the correct patch names and controller labels for your gear.
Save Changes for Next SessionCheck this box if you want your current instrument assignments to be remembered the next time you launch Sonar.
DefineClick this button to open the Define Instruments and Names dialog. This tool lets you create custom instrument definitions for non-standard MIDI gear or rare synths not included in Sonar’s default library.
Control Surface

The Control Surfaces section allows you to configure external hardware controllers that interact with Sonar’s mixer, transport, plug-ins, and more. You can add and remove devices, assign MIDI ports, customize WAI (Where Am I) markers, use ACT (Active Controller Technology), and fine-tune control surface performance.

Connected Controller / Surface List
Controller/SurfaceName of the connected control surface.
In Port / Out PortSelect the MIDI input/output ports used to communicate with Sonar.
ACTCheck this to enable ACT for the surface. ACT lets you map hardware controls to plug-in parameters.
WAIEnables/disables WAI markers for each surface. These help you visually track which tracks are being controlled.
WAI Color Choose a custom highlight color for each surface’s WAI region.

Control Surface Managament
Add  Opens the Controller/Surface Settings dialog to add a new control surface.
Delete Removes the selected surface from the active list.
ACT Data Managament

Import ACT Data:
If you use ACT with plug-ins, you can import XML files containing prebuilt control mappings. This gives you a strong starting point for custom mapping.

When importing mappings:

  • If you’ve already customized a plug-in’s mapping, Sonar will ask if you want to overwrite it.
WAI Display Options

Use these checkboxes to show/hide WAI markers in:

  • Track View
  • Console View

WAI markers visually indicate the tracks currently controlled by a surface.

Control Strips Visible In
Control surfaces can mirror different views in Sonar. Choose which strips are visible to your controller:
  • Track View: Only visible tracks in Track View are controlled.
  • Console View: Only visible strips in Console View are controlled.
  • All Strips: The surface can control all tracks, regardless of visibility in the UI.
Refresh Frequency (ms)
Sets how often Sonar refreshes communication with your control surface. Default is 75 milliseconds. You can:
  • Increase the value (up to 5000 ms) for less CPU load on high-track count projects.
  • Decrease it (minimum 50 ms) for more responsive updates—ideal for real-time control.
  • Note: Surfaces that are not bi-directional can use a slower refresh rate safely.

The MIDI Preferences section in Cakewalk Sonar offers powerful customization for routing, playback, recording, instrument definition, and controller integration. Whether you're working with hardware synths, external MIDI controllers, or complex virtual instrument setups, these settings allow you to fine-tune your workflow for optimal performance and creative flexibility. 

Take a moment to explore each section—Devices, Playback and Recording, Instruments, and Control Surfaces—to ensure your MIDI environment is configured exactly the way you want. With the right setup, you’ll unlock the full potential of MIDI in Sonar and streamline your music production process.

0 out of 0 found this helpful

Articles in this section