Common Setup for multiple clients

Hi I'm working as a freelance broadcast sound engineer, using Reaper for much of my work these days. I have a small group of producers who are interested in switching to Reaper with some help and training from me. This would certainly help me, if they deliver projects for editing and mixing already in rpp format. As part of a training session, I'd like to give them all a "starting setup" with the preferences set appropriately for the kind of work they're doing, and with various scripts and extensions loaded and assigned to hotkeys etc. Then all they need to do when they leave is load that onto their own PC/Mac and set the audio outputs for their particular interface etc. What's the best way to do this? Create a portable install including all the scripts/SWS etc and with a config, and save it to a memory stick for each of them? Anything else I need to be aware of? Thanks Andy

yes, creating a portable install makes sure that everything (all settings) are stored under a single main folder. If the settings have to be shared on multiple platforms, it will probably get more dificult to keep all installs sync'ed, though. You can also use the import/export function in the Reaper preferences to exchange settings (even across platforms). I created a portable Reaper install with everything I require. The only things left at default were the audio and MIDI device settings. I then gave the zipped install folder to others. As I rather frequently update my own preferences (keyboard shortcuts, tool bars, actions, scripts) I have to import and update those settings from time to time in the collaborating installs. I think it's worth discussing and normalize the way to create and manage projects and to find some common guidelines to make project exchange as smooth as possible. First thing is to have a common project storage path scheme/structure if possible. Having a main Reaper project folder is the starting point. I then have sub-directories for each client/artist (labelled by client's/artist's name). Below this folder, I create project folders for each project/song (labelled with the project's/song's name) in which the actual project files are stored. Basic project template settings are also shared. Among the settings is the common project sample rate, recorded file format, video frame rate, pan law and a relative media file sub-folder. You can further enhance the user experience by tweaking Reaper's naming scheme for recorded files and master file labelling in the render dialog by using the power of Reaper's auto-labelling wild cards. I find that exchanging track templates (including media items and automation data) instead of project files is often prone to less hassle when sharing projects because this doesn't mess with local audio input and output particularities for instance. All Reaper installs should use the same master output routing. Another topic is plugin management. Every member of the group has to have the same plugins to make project data play identically. It might be a huge challenge to consolidate this. Using WavPack of FLAC as the default recorded files format allows for much smaller project media file sizes and faster transfer via the internet without compromizing audio quality. Those file formats also support to include meta data (notably positioning data which allows them to automatically find their original position in a project). .

Thanks SonicAxiom Useful info to consider. Things are made a bit easier by the fact that the group is all making mainly speech based programmes for the same broadcaster, so all work at the same sample rate etc. They will be recording their own source material and rough editing it in Reaper then bringing it to me to mix, so they don't need anything apart from the stock plugins. I can then use my collection of VST processors etc, because they don't generally need to access the project after passing it onto me. I'll think carefully about sharing Track Templates (with all the audio embedded) instead of projects - good suggestion. And also about folder and naming conventions. Cheers