Tips 'n' Tricks

Share Project

In order to share an instrument-project with an other musician, only the directory of the instrument in question has to be shared - the main-project and the other instrument-projects are not required for this other musician to be able to work with his project.

However, neither the name of the instrument-project nor the its directory may be changed!

Clean Project Directory

During recording sessions, a lot of data is generated, a significant amount of which is usually not required after the recording sessions (takes which are not used). It is good practice to clean the project directory after a recording session with the help of the respective Reaper function found in the file menu.

Data Synchronization

In order to avoid data access conflicts and also to avoid synchronizing temporary data (ref. previous point), it strongly recommended to interrupt the automated data synchronization of your cloud solution during recording sessions and also during the execution of the MuCol-scripts.

Be aware, that if you are synchronising projects and sound files, it might take quite some time for the process to be completed - check the status of your synchronisation tool.

Temporary Projects

The project processing uses a number of temporary projects in order for the data copy processes to work asynchroniously, i.e. when the main- or an instrument-project is processed, the other instrument-projecs do not need to be accessed. The temporay files are stored in directoires named "#MC-SYNC". Unfortunately the temporary projects appear in the recent projects list. Those projects should not be changed, though, for the automations to work flawlessly.

Backtrack Effects

The backtracks do not include any send effects (such as reverb). But you can alsways add effects to any of the backtracks (send or insert). When the backtracks are updated with new recordings, the mix settings (levels, effects, track structure and settings etc.) are retained.

Wait During Script Execution

The MuCol-script contains numerous automations of Reaper-functions. Changing the application focus, i.e. switching to another program while a script is beeing run, is not recommended as it might cause the script to fail. Please be patient until the execution confirmation with the summary is displayed.

Also, when marking tracks a little bit of patience is inevitable, as there are various validations taking place which consume some time. So please wait until you see the indications change before clicking on the ">>"-button once again.

Changing Arrangement and Song Structure

Situation: You have put together a song idea and created the instrument-projects. Somewhen along the way, you decide that the intro needs to be way longer. Obviously you would want to change the corresponding markers or regions to reflect the new song structure. The markers and regions are not synchronized between the projects, but they can be exported and imported from within the "Region/Marker Manager" (found in the "View"-menu in Reaper). The file format is a CSV (Comma Separated Values) which then can be shared.