Skip to content

Quick start user guide

ak5k edited this page Dec 25, 2023 · 27 revisions
  1. Install from ReaPack or download ReaBlink. Pre-built Linux releases require a quite recent distro to run. Windows XP and 32-bit Macs not supported. For older platforms, see build from source. Technically works with any audio drivers, but ALSA, ASIO or CoreAudio are strongly recommended.
  2. Place reaper_reablink...{dll,dylib,so} into REAPER UserPlugins directory.
  3. Start REAPER.
  4. Load helper/example scripts into REAPER (Actions > Show action list... > New action... > Load ReaScript... and select ReaBlink .lua files). (optional)
  5. Start ReaBlink Monitor from action list, if installed. ReaBlink Monitor enables Blink (SetEnabled), SetStartStopSyncEnabled, SetCaptureTransportCommands and SetPuppet. REAPER should now be listening for transport and tempo changes in Link session, and broadcast local changes in transport state or tempo. Master and Puppet modes use current active tempo/time signature marker, so they can be used to divide REAPER timeline into 'scene-like' sections.

ReaScript API documentation is provided (Help > ReaScript documentation > 'Blink_' prefixed entries). When developing Link session scripts using ReaBlink, it's probably beneficial to modify ReaBlink Monitor (or create new), and remove SetEnabled, SetStartStopSyncEnabled, SetCaptureTransportCommands and SetPuppet entries. Lowering or disabling REAPER media buffering can increase Master/Puppet mode performance and stability.

In case of one ReaBlink in a Link session, setting ReaBlink to run in Master mode might also help. In case of multiple ReaBlinks in a session, only one should be Master.

Disabling media buffering and prebuffering from REAPER preferences > Audio > Buffering will likely result in better ReaBlink sync and response.

Check forum thread for more information and discussion.

Clone this wiki locally