Introduction
HeartSync connects a Bluetooth heart rate monitor to your DAW and syncs the tempo to your heartbeat in real time. No coding, no Terminal, no complicated configuration — install the plugin through the Conscious Audio Installer, connect your sensor, point your DAW at HeartSync's tempo, and confirm the BPM follows.
What You Need
- A Mac — macOS 10.15 or later on Intel, macOS 11 or later on Apple Silicon — or a Windows PC (Windows 10 / 11, x64). These are the declared build targets of the shipped Hub and HeartSync Beta binaries; the tested macOS range is not yet published.
- A Bluetooth heart rate monitor — Polar H10, H9, H7; Garmin HRM-Pro, HRM-Dual; Wahoo TICKR, TICKR X; Apple Watch (with HR broadcast enabled); or any chest strap / wrist sensor that broadcasts heart rate over Bluetooth
- A DAW that loads VST3 (macOS and Windows) or Audio Unit (macOS only). For heartbeat-to-tempo sync you also need a DAW that can follow an external tempo source (OSC, Ableton Link, or external MIDI clock) — see the per-DAW notes below
1 — Install the Conscious Audio Installer, then HeartSync
HeartSync is installed through the Conscious Audio Installer (the Hub app) on both Mac and Windows. You install the Hub once, then install and update HeartSync from inside it. No Terminal commands, no build tools.
- Go to consciousaudio.com.au/heartsync and download the installer for your platform.
- Run it, then open it and follow its on-screen prompts.
- In Products, select HeartSync and click Install.
- The plugin is placed in your system's plugin folder — VST3 on macOS and Windows, plus the Audio Unit on macOS.
You'll know it worked when: You open your DAW, scan your plugins list, and see HeartSync listed alongside your other plugins.
2 — Connect Your Heart Rate Monitor
This works the same in every DAW.
- Put on your heart rate monitor and make sure it's turned on. Most chest straps activate when you put them on; wrist devices may need Bluetooth broadcasting turned on manually.
- Open your DAW and load HeartSync on any track — find it in your plugin list like you would any other plugin.
- Click SCAN in the HeartSync plugin window.
- Wait a few seconds — your device name will appear in the dropdown.
- Select your device and click CONNECT.
You'll know it worked when: You see your live heart rate number updating in the HeartSync display. The number should change as your heart rate changes — try standing up or taking a few deep breaths.
3 — Enable Tempo Sync in HeartSync
Once you see your heart rate in the plugin, turn on Tempo Sync:
- Right-click the Smoothed HR dial (or the Original HR dial if you want raw values).
- Select Tempo Sync from the menu.
HeartSync now publishes heart-driven BPM over every available sync method (Link, OSC, external MIDI). Your DAW only acts on it once its tempo input is configured — that is section 4. Depending on the route, you may need to do section 4 before this step; the per-DAW notes say which.
Fine-Tuning
- Smoothed HR vs. Original HR: Smoothed gives you gradual, musical tempo changes. Original is raw and reactive — jumps more, feels more alive.
- Offset: Shift the BPM up or down from your actual heart rate. If your resting HR is 65 but you want the track around 120 BPM, use offset.
- Smoothing Amount: Control how gradually tempo transitions happen. Higher smoothing = slower, gentler changes.
4 — DAW-Specific Setup
HeartSync broadcasts tempo automatically, but your DAW needs to be told to listen. This is a one-time setup — once configured, it stays set for every future session.
Ableton Live
All three options are configured in the same place: Settings → Link, Tempo & MIDI (Live 12) or Preferences → Link Tempo MIDI (Live 11).
Option A — OSC (recommended, fastest)
The Conscious Audio installer sets up AbletonOSC for you — you do not need to download or install it yourself. If Ableton Live was open during installation, restart Live so it picks up the new control surface. (Supported Live versions and repair behaviour are documented with the installer.)
- Open Settings → Link, Tempo & MIDI.
- Under Control Surface, select AbletonOSC from the dropdown.
- You should see a message: "AbletonOSC: Listening for OSC on port 11000".
- Done — HeartSync's tempo sync is now received automatically.
Option B — Ableton Link
- Open Settings → Link, Tempo & MIDI.
- Toggle Show Link Toggle to on.
- Back in the main Ableton window, a Link button now appears in the top left of the Control Bar. Click it to enable Link.
Option C — External MIDI
- Open Settings → Link, Tempo & MIDI.
- Scroll down to MIDI Ports. Find HeartSync Clock in the Input row.
- Enable the Sync checkbox for HeartSync Clock.
Logic Pro
Logic Pro uses Ableton Link for tempo sync.
- Go to Logic Pro → Settings (Logic Pro 11+) or Logic Pro → Preferences (Logic Pro X / 10).
- Click the MIDI tab at the top.
- Click the Sync sub-tab.
- Find the Ableton Link section and enable it.
It's a bit of a menu dive, but once Link is on, HeartSync's tempo sync reaches Logic automatically — no further configuration needed.
FL Studio
FL Studio follows an external MIDI clock through Options → MIDI settings → External Sync, per Image-Line's MIDI settings manual. Two separate things are involved: enabling the HeartSync clock port as an input just makes it available to FL Studio; selecting it under External clock sync is what actually slaves the tempo.
- Go to Options → MIDI settings (or press F10).
- Find the HeartSync clock source in the Input list, select it and make sure it is Enabled. Enabling only makes the port available — it does not start tempo-follow on its own.
- Scroll to the External Sync section. Set External clock sync (the dropdown) to that same HeartSync clock source. This is the step that makes FL Studio slave its tempo to the incoming clock.
- Optionally adjust External sync offset (ms) if the timing needs fine-tuning.
- FL Studio's transport tempo should now follow HeartSync's clock.
Reaper
Reaper supports OSC natively. The steps below are the procedure shown by the macOS HeartSync Beta 2.3.1 plugin's built-in DAW setup wizard for Reaper:
- Open Options → Preferences → Control/OSC/web.
- Add a new OSC (Open Sound Control) control surface.
- Set the local port to 8000.
- Load the HeartSync .ReaperOSC pattern file if it is available, then click OK.
- Reaper will then follow HeartSync's tempo.
Alternatively, for external MIDI: go to Options → Preferences → MIDI Devices, enable HeartSync Clock, then set it as a sync source under Options → Preferences → Synchronization.
Cubase / Nuendo
Cubase and Nuendo can send MIDI Clock but, per Steinberg, cannot slave their tempo to an incoming MIDI Clock. They also do not support OSC tempo control or Ableton Link. There is currently no supported way to drive Cubase/Nuendo tempo from HeartSync. You can still run the HeartSync plugin in Cubase to read your heart rate; the project tempo just will not follow it.
Bitwig Studio
- Go to Settings (gear icon in the bottom-left panel).
- Click the Synchronization tab.
- Enable Link to sync tempo via Ableton Link, or:
- Under MIDI Clock, set HeartSync Clock as a clock source.
Studio One
We have not found a working way to make Studio One follow an external tempo source — it has no OSC tempo control or Ableton Link, and we could not verify an external-MIDI-clock slave path. Until that is confirmed, Studio One is not a supported host for heartbeat-to-tempo sync. The HeartSync plugin still loads and reads your heart rate.
Any Other DAW
If your DAW supports VST3 (or AU) plugins, the HeartSync plugin will load. Heartbeat-to-tempo sync additionally requires that the DAW can follow an external tempo source:
- If your DAW can slave to an external MIDI clock, enable HeartSync Clock as an input and turn on external clock sync (enabling the input alone is not enough).
- If your DAW supports OSC but is not Ableton Live or Reaper: HeartSync's built-in setup only covers those two, and the plugin does not expose an OSC-port setting for other hosts. This route is awaiting confirmed port configuration — tell us your DAW and we'll follow up.
- If your DAW supports Ableton Link, enable Link — HeartSync broadcasts over Link automatically.
- Some DAWs cannot do any of the above — Cubase/Nuendo cannot slave to an incoming MIDI clock (per Steinberg), and we have not found a tempo-follow path in Studio One. They can run the plugin but will not follow your heart rate.
5 — Confirm the Tempo Is Following
With the DAW tempo input configured (section 4) and HeartSync Tempo Sync on (section 3), watch your DAW's BPM readout.
You'll know it worked when: the DAW BPM moves with your heart rate — smoothly, not jumpily, because the Smoothed HR dial filters out sudden spikes. A live heart-rate number in the plugin alone only confirms the sensor; it does not confirm the DAW is following. If the BPM does not move, the host tempo input is not receiving the clock yet — recheck your DAW's step above.
Troubleshooting
Nothing shows up when I scan for devices
- Is Bluetooth on? Check your system settings — Mac: System Settings → Bluetooth. Windows: Settings → Bluetooth & Devices.
- Is your heart rate monitor on? Chest straps need to be worn to activate. Wrist devices may need Bluetooth turned on in the device's own settings.
- Are you close enough? Keep within about 10 feet / 3 meters of your computer.
- Mac: Did you grant permission? If you accidentally denied the Bluetooth prompt, go to System Settings → Privacy & Security → Bluetooth and make sure your DAW is allowed.
- Windows: Is the Bluetooth service running? Open Services (search "Services" in Start menu), find "Bluetooth Support Service," and make sure it's running. Restart it if needed.
I see my heart rate but the tempo isn't changing
- Did you enable Tempo Sync? Right-click the Smoothed HR or Original HR dial in HeartSync and make sure Tempo Sync is checked.
- Is your DAW set up to receive? Check the DAW-specific section above — most DAWs need one setting toggled to accept external tempo.
- Try restarting your DAW after making sync setting changes. Some DAWs don't pick up new MIDI or OSC inputs until restarted.
My heart rate shows but the numbers seem wrong
- Make sure the sensor has good contact. Chest straps need moisture on the electrode pads to get an accurate reading. Wrist monitors need a snug fit.
- Give it 10–15 seconds. Most sensors need a moment to stabilize after being put on.
The plugin doesn't appear in my DAW
- Restart your DAW. Most DAWs only scan for new plugins on launch.
- Rescan plugins manually. Most DAWs have a "Rescan" or "Refresh" button in their plugin manager (usually in Preferences).
- Check the right category. HeartSync may appear under VST3 effects or instruments depending on your DAW — look in both.
Bluetooth keeps disconnecting
- Get closer to your computer — Bluetooth range is limited.
- Check your battery. Low battery causes unreliable connections.
- Reduce interference. Wi-Fi routers, USB 3.0 hubs, and microwave ovens can all disrupt Bluetooth. Move the monitor or your computer if possible.
- Wait a moment. HeartSync auto-reconnects when a device drops. It will retry within a few seconds — you don't need to scan again.
Windows: Device pairs in system settings but not in HeartSync
- Some Bluetooth adapters have flaky drivers. Try updating your Bluetooth driver through Device Manager.
- If using a USB Bluetooth dongle, try a different USB port (avoid USB 3.0 hubs).
- Restart the Bluetooth Support Service (search "Services" in Start menu).
The tempo is too jumpy / changing too fast
- Use the Smoothed HR dial instead of Original HR for tempo sync — it filters out spikes.
- Increase the Smoothing Amount for gentler transitions.
- Use Offset to center the BPM range where you want it.
Quick Reference
| Sync Method | How It Works | Best For |
|---|---|---|
| OSC | HeartSync sends BPM over the network. For Live this goes through AbletonOSC, whose documented default listen port is 11000. For Reaper, the macOS HeartSync Beta 2.3.1 setup wizard specifies port 8000 (not yet confirmed end to end; Windows may differ). Other OSC hosts are awaiting confirmed port configuration. | Ableton Live, Reaper |
| Ableton Link | Shared tempo over local network | Logic Pro, Ableton Live, Bitwig |
| External MIDI clock | Tempo sent as MIDI clock; the DAW must be set to slave to it. On macOS 2.3.1 the port is named "HeartSync Clock". | FL Studio (via External clock sync), Bitwig, Reaper |
HeartSync sends tempo over all available methods at once — use whichever your DAW can follow. A DAW that cannot follow OSC, Link, or an external MIDI clock can run the plugin but its tempo will not track your heart rate. Known cases: Cubase/Nuendo (cannot slave to incoming MIDI clock, per Steinberg) and Studio One (no verified tempo-follow path).