View Code? Open in Web Editor
NEW
Scripts for streamlining workflow with the cross-platform DAW Reaper, particularly with a focus on multitrack recording in the context of live events, such as theatre. This repository can be added to ReaPack.
License: MIT License
reaper-scripts's Introduction
🔭 I’m currently working on: A mix of
Qlab Scripting (applescript )
Reaper Scripting (Lua )
Javascript applets
Some web development (Hugo )
📫 How to reach me: Send me an email
😄 Pronouns: He/Him
reaper-scripts's People
Contributors
Stargazers
Watchers
reaper-scripts's Issues
When the script creates a split stereo track from a stereo ('--2') track which is the last track of a folder, the next track is not added in the folder.
Something like:
if trackToSplit.depth is -1 (end of folder)
make new
turn original to mono
make new mono
make original depth 0
make new depth -1
Like Script: X-Raym_Explode multi channel items on two tracks without render (stereo).lua
A) does it work with groups? Need to turn on mainsend on parent
B) cable you make "table.insert" neater?
C) note better what ipairs() does?
If no track is selected, or if the selected track is not a folder, then do the same as "ARM IN FOLDERS"
On both new routing scripts, show up as simply "undo: run reascript"
Play with OSC triggering of "create marker" script, and see if you can use scripts to interpret OSC information. (e.g. send the name via OSC)
Currently loops through all selected, replacing the variable each time. Get each time to add a new item into an array instead?
See if it's possible, or work out the best way to identify the folder tracks
Currently explodes into mono tracks all into a centre panned stereo channel. Option to explode to mono tracks, but route them to the same output? Particularly when exploding into a folder this would be useful - explode multichannel audio and balance it whilst keeping the routing.
Script to automatically create a parent for the currently selected tracks in either the Mixer or TCP.
Wip in another branch, adding an issue so I remember it
Change "(stereoSuffix, -3)" in fix to "stereoSuffix, [length of stereoSuffix]"
Make easily customisable (with heavy signposting) for different projects:
A template for how to record arm a large chunk (for loop)
A template for how to record a single track
Easily and quickly adaptable.
Ultimately… GUI the first time you set it up? Script to write and install the script?
Extension of the record arm tracks in folder script - select a folder track and run the script to arm only tracks within that group.
Discount other group tracks - e.g. select "band" and arm all band channels, but not the "drums" folder channel
Currently can be separate, which results in new items being placed in the wrong place.
The note for putting track details in the table is incorrect
currently selects the last track before setting it's folder depth unnecessarily
possibly move some notes around to make it slightly easier to follow too
trackName = string.sub (trackName , 1 , 0 - (stereoSuffix :len ()+ 1 ))
Consistent use of #stereoSuffix
and stereoSuffix:len()
?
Some scripts no longer work if you just use the source file - due to the use of provide and the use of find → create a default option?
(Top Hat show 1)
When soloing a top level track / folder to master, some other (the next?) folder in the same level also toggles? Is an odd one
Both to have 2 versions, affecting all tracks and selected tracks, based on file name.
When routing tracks to stereo inputs, currently the script alerts the user that it has skipped a channel.
Propose swapping it with the next channel instead, and alerting the user so they can update routing elsewhere accordingly?
Ultimately just needs to be set up correctly by the user, though.
User customisation as 2 scripts - ask for name and don't ask for name.
Also make the master the last two outputs? If not already occupied?