ReaLab

For the Mac lab administrator

One configuration for your lab

The lab administrator selects the repositories and other ReaPackLab settings in a hosted configuration file. The normal per-lab setup uses a protected, machine-wide pointer on each Mac; this is separate from each student's REAPER resource folder.

1. Create a valid configuration file. Use the ReaPackLab configuration editor ↗ to create ReaPackLab.ini with the repository list and other settings. Host the resulting file at an HTTPS address that the lab Macs can reach. The editor generates a file; it does not publish it for you.
2. Place url.txt on every Mac. Put this plain-text file in the protected system folder /Library/Application Support/ReaPackLab/. The full path is /Library/Application Support/ReaPackLab/url.txt. Use the system Library, not a student's ~/Library, and keep the folder and file under administrator control.
3. Point it to the hosted configuration. The file must contain one full HTTPS URL pointing to a valid configuration file—not the repository list itself. For example, replace this illustrative address with your own:

   https://www.example.com/exampledirectory/ReaPackLab.ini

ReaBootLab installs ReaPackLabSetup, which bootstraps ReaPackLab inside REAPER. In the normal per-lab workflow, the setup chain follows url.txt to the hosted configuration, and ReaPackLab downloads and synchronizes the repositories listed there.

Choose an installer

Which installer do I need?

You only need one of these two Mac apps. Both install the ReaPackLabSetup companion for your user account.

Unlike ReaBoot, ReaBootLab does not let students choose which repositories or packages are installed. Those choices belong to the lab administrator.

These downloads are for Apple Silicon Macs running macOS 15 or newer. Intel Mac and Windows builds are not included.

After downloading

A few steps, and a couple of restarts

1. Extract the ZIP and open the app normally. Follow its prompts. If you chose ReaBootLabReaper, complete the separate REAPER installation handoff.
2. Restart REAPER to load Setup. The installer places ReaPackLabSetup in your current user's standard REAPER resources.
3. When Setup installs ReaPackLab, restart REAPER again. Native extensions need a restart before the newly installed version can load.

The bootstrap apps use the standard REAPER resource location. They do not offer portable installations or arbitrary destination folders. Complete the administrator setup before student use, accounting for the recovery-build exception above.

A managed student environment

Keep the focus on making music

Unlike standard ReaPack, ReaPackLab is built around administrator-selected repositories and a controlled student workflow.

• Blocks script editing through REAPER’s built-in tools.
• Blocks creation of new scripts through REAPER’s built-in tools.
• Blocks loading user-selected scripts through REAPER’s built-in tools.
• Blocks students from adding, deleting or altering ReaPack repository listings.
• Attempts to remove standard ReaPack when found.

These are restrictions on REAPER's built-in operations in the managed setup, not operating-system-wide restrictions on external editors or other software.

Shared plug-in scanning

ReaPackLab adds these shared Mac directories to REAPER's plug-in scan paths for VST, VST3 and CLAP:

• /Users/Shared/Library/Audio/Plug-Ins/VST
• /Users/Shared/Library/Audio/Plug-Ins/VST3
• /Users/Shared/Library/Audio/Plug-Ins/CLAP
• /Users/Shared/Plug-Ins/VST
• /Users/Shared/Plug-Ins/VST3
• /Users/Shared/Plug-Ins/CLAP

A useful report at launch

At launch, ReaPackLab presents a report showing:

• Number of repositories
• Number of plug-ins
• Number of extensions
• Active MIDI devices

Teacher dashboard

A teacher dashboard with additional features is in development.

How it fits together

The pieces, in plain English

ReaLab is the family name. The installers get you started; Setup and the managed package manager run inside REAPER.

The components have independent release schedules. ReaBootLab 0.1.0 currently installs the verified, pinned Setup 0.1.1; a newer standalone Setup release does not change that installer automatically.

Documentation

More to come

Development continues, and more guides and video walkthroughs will be added as they are ready. For now, start with the administrator setup, installation steps and public release notes.