← Back to home
Help & Support

Getting Started with MidiPdfView

Everything you need to install the app and connect your MIDI footswitch so you can turn pages hands-free during your performance.

💾 Installing MidiPdfView

Download the .exe installer from the Download page. Run it and follow the wizard — MidiPdfView will be added to your Start menu automatically.

Windows SmartScreen warning: Because MidiPdfView is not signed by a large publisher, Windows Defender may show a blue "Windows protected your PC" dialog. Click More info, then Run anyway. This is a one-time prompt.

System requirements

  • Windows 10 or 11 (64-bit)
  • No additional software needed for USB MIDI devices

Download the .dmg file from the Download page. Open the .dmg, then drag MidiPdfView into your Applications folder.

macOS Gatekeeper: MidiPdfView is not notarised by Apple, so macOS may block it the first time. To open it:
  1. Right-click (or Control-click) the app in Applications
  2. Choose Open from the menu
  3. Click Open in the dialog that appears

Alternatively, go to System Settings → Privacy & Security and click "Open Anyway" next to the MidiPdfView entry.

System requirements

  • macOS 12 Monterey or later (Intel & Apple Silicon)
  • CoreMIDI is built-in — no extra drivers needed for USB MIDI

Download the .AppImage from the Download page. AppImages are self-contained — no installation required, just mark it as executable and run it.

Making it executable

Option A — file manager: Right-click the downloaded file → Properties → Permissions → tick "Allow executing file as program" → double-click to launch.

Option B — terminal:

chmod +x MidiPdfView-1.1.3.AppImage
./MidiPdfView-1.1.3.AppImage

System requirements

  • x86_64 Linux with glibc 2.28+ (Ubuntu 20.04+, Fedora 32+, Debian 10+)
  • ALSA or JACK for MIDI (usually pre-installed)
  • For Bluetooth MIDI: bluez package (standard on most distros)
FUSE note: Some newer Linux distributions disable FUSE 2 by default. If the AppImage won't launch, install it with: sudo apt install libfuse2 (Ubuntu/Debian) or sudo dnf install fuse (Fedora).

🎹 Connecting a MIDI Pedal

MidiPdfView works with any MIDI controller — dedicated MIDI footswitches, sustain pedals, expression pedals, and multi-button pedalboards. The most common connection methods are:

USB MIDI (plug-and-play)

Most modern MIDI footswitches (e.g. Yamaha FC4A, AirTurn BT-500, Logidy UMI3) connect via USB and are detected automatically by Windows, macOS, and Linux without any drivers. Just plug in and open the app.

Sustain pedal tip: A standard piano sustain pedal (like Yamaha FC4A or Roland DP-10) plugged into a MIDI keyboard’s sustain input won’t work — MidiPdfView needs to see MIDI messages directly. Use a pedal with its own USB output, or run a sustain pedal from a MIDI keyboard that is itself connected to the computer.

5-pin DIN MIDI (classic pedals)

Older MIDI footswitches use a 5-pin DIN connector. You'll need a USB-to-MIDI adapter (e.g. Roland UM-ONE mk2, Focusrite Scarlett with MIDI I/O). Connect the adapter to your computer and the pedal's MIDI OUT to the adapter's MIDI IN.

Bluetooth MIDI (built-in bridge)

MidiPdfView includes a built-in Bluetooth MIDI bridge on Windows and Linux. The bridge talks to the pedal through the operating system’s Bluetooth stack, so the pedal must be paired at the OS level first — this is what gives you a stable, auto-reconnecting connection.

Windows setup

  1. Put your BLE MIDI pedal into pairing mode (see the pedal’s manual — usually hold a button until an LED flashes rapidly).
  2. Go to Settings → Bluetooth & devices → Add device → Bluetooth and pair the pedal. It should appear by name in the device list once paired.
  3. Open MidiPdfView and click the Settings gear icon.
  4. In the Bluetooth MIDI section, choose your pedal from the device dropdown and click Save. The bridge connects immediately and reconnects automatically on every launch.
Pair first, then select in app. If you skip the OS pairing step and go straight to the app, the connection will be unreliable. The Windows bridge relies on an established OS-level bond with the device.
MIDI passthrough: MidiPdfView can simultaneously forward incoming BLE MIDI to a loopMIDI virtual port so a DAW or notation app receives the same pedal input at the same time. Enable this in the Bluetooth → MIDI PASSTHROUGH setting.

Linux setup

The Linux bridge uses the BlueZ Bluetooth stack directly. Whether OS-level pairing is required depends on the pedal — some BLE MIDI devices allow a direct connection without a bond, while others require it. If the bridge fails to connect, try pairing first via your desktop Bluetooth manager or bluetoothctl:

bluetoothctl
scan on
# wait for your pedal’s MAC address to appear, then:
pair AA:BB:CC:DD:EE:FF
trust AA:BB:CC:DD:EE:FF

After that, select the device in MidiPdfView Settings → Bluetooth MIDI as normal. Linux BLE MIDI support is new in v1.1 — if you run into issues, let us know.

macOS setup

BLE MIDI pedals pair via CoreMIDI: go to Audio MIDI Setup → MIDI Studio → Bluetooth, click the pedal, and click Connect. It then appears as a regular MIDI port inside MidiPdfView — no bridge required.

⚙️ Selecting Your Device in the App

After connecting your pedal:

  1. Open MidiPdfView.
  2. Click the Settings gear icon (top-right toolbar).
  3. Under MIDI Input, choose your device from the dropdown list. All detected MIDI ports are shown here.
  4. Click Save. MidiPdfView remembers your choice between sessions.
Device not showing? Make sure the pedal is connected before opening the app. If you connected it after the app was already running, the port list refreshes automatically every 2 seconds — wait a moment and check again.

🗺️ Default Button Mapping

Out of the box, MidiPdfView listens for the following MIDI Control Change (CC) messages. Most multi-button MIDI footswitches send CC messages and will work without any reconfiguration.

Action MIDI Message CC Number
Next page Control Change CC 66
Previous page Control Change CC 67
Next tab / file Control Change CC 64 (sustain)
Previous tab / file Control Change CC 65
Zoom in Control Change CC 68
Zoom out Control Change CC 69

A trigger fires when the CC value is 1 or higher (i.e. when you press the pedal). Releasing the pedal (value = 0) is ignored.

🎛️ Customising the Mapping

If your pedal sends different CC numbers, note-on events, or program changes, you can remap every action in Settings:

  1. Open Settings (gear icon).
  2. Click Edit MIDI Mapping.
  3. For each action, click Learn, then press the pedal button you want to assign. The app captures the message type, channel, and number automatically.
  4. Click Save Mapping when done.

Supported message types: Note On, Note Off, Control Change, Program Change. You can also set a minimum value threshold for expression pedals.

🔍 Smart Zoom & Viewing

Most PDF viewers scale the whole page to fit your screen — which means blank margins take up display space that could show music. MidiPdfView’s Smart Zoom is different: it detects where the actual notation lives on the page and scales that region to fill your screen, making the notes as large as possible without any manual pinching.

How to use Smart Zoom

In the top toolbar, click the zoom icon to cycle through modes:

Each PDF remembers its own zoom mode and level between sessions, so every score opens exactly where you left it.

Tip for wide-margin scores: Publisher PDFs often have substantial top and bottom margins. Smart Fit can make the notation noticeably larger compared to a standard page-fit, which is especially helpful on smaller tablet screens or if you prefer larger notation.

🔧 Troubleshooting

Bluetooth pedal not appearing in the scan list

Bluetooth pedal keeps disconnecting

Pedal not responding

PDF won't open

App won't launch on macOS

App won't launch on Linux (AppImage)

Trial / license issues

✉️ Still need help?

If your question isn't answered here, the fastest way to reach us is via the contact form. We typically reply within one business day.

Contact support