This article follows the ongoing development of REAPER tools requested by Strata subscribers, new scripts that facilitate efficient workflows in REAPER. We previously already published two parts in the “Accelerate Your Strata Workflows” series:
- Part 1 dives into integrating a script that makes it easy to jump to a selected audio file’s associated Strata project with the click of a button. Read it here.
- Part 2 introduces a script that lets you instantly open the associated REAPER project and start auditioning and visualizing sound elements directly in REAPER. Read it here.
- This article (Part 3) dives into "Strata_Copy selection to next project", a REAPER script package that makes it easy to copy items and tracks from one REAPER project to another.
What is "Strata_Copy selection to next project"?
"Strata_Copy selection to next project" is a REAPER Command Action that copies the items and tracks within a Timeline Selection of a Source Project to the next project tab Target Project.
Benefit:
This Command Action significantly reduces a multi-click operation into a single click, speeding up a sound-building workflow, leveraging the scripting functionality of REAPER.
An example of use:
When creating a cutscene sound edit in a REAPER Project, let’s say you have a Strata REAPER Project open and want to copy a sound with all of its elements to the cutscene sound edit.
- Move the Strata Project Tab (Source Project) so that it's immediately to the left of the cutscene edit Project Tab (Target Project).
- In the Target Project, place the cursor at the position in the timeline that you would like to copy the sound to.
- In the Source Project, make a time selection including the items that make up the sound(s) you would like to copy; then select the tracks you would like to copy.
Tip 1: Select all the tracks. Note that only the tracks that have items or are involved with the routing of the tracks will be copied.
- Run the Action "Strata_Copy selection to next project".
Tip 2: Once installed, the command is available from the Action list in the Main section. To find it, quickly filter for "Strata", as there are only a few Strata scripts with the prefix "Strata".
- The Items, tracks, and region markers, are copied to the Target Project, and the Target Project is now the active Tab. Note the first Item in the timeline selection of the Source Project is copied to the Destination Project cursor position.
Where do I get the script?
The "Strata_Copy selection to next project" script is available through ReaPack, from the Audiokinetic Reaper Tools Repository
Add this URL to your managed ReaPack repository list: https://github.com/Audiokinetic/Reaper-Tools/raw/main/index.xml
ReaPack
- Go to ReaPack: Package manager for REAPER to download ReaPack. Refer to the ReaPack User Guide for installation instructions.
- After ReaPack is installed, from the REAPER menu bar, click Extensions > ReaPack > Import Repositories.
- In the dialog that opens, enter the URL of Audiokinetic's Reaper Tools repository (https://github.com/Audiokinetic/Reaper-Tools/raw/main/index.xml) and click OK.
- From the REAPER menu bar, click Extensions > ReaPack > Browse packages.
ReaPack is the easiest way to install and keep REAPER scripts up to date. It is possible to configure ReaPack to download and install release versions or pre-release versions of REAPER-Tools scripts. Release versions are numbered v 0.0.0. Pre-release versions will have a letter after them; for example, 0.0.0a for alpha and 0.0.0b for beta.
Once installed and REAPER has been re-launched, the script will be available to run from the Action list in the Main section.
Running into Issues? Let us know!
Should you encounter an issue or have a feature request for existing tools please go to the GitHub repository, https://github.com/audiokinetic/Reaper-Tools/issues. If you find an issue that still needs to be resolved, please comment on it and detail any information that might help lead to a resolution. If your Issue does not already exist, please create a New Issue, and provide as much information as you can, as we are monitoring the repository.
Comments