brassplyer
Well-known member
Subject line says it. How do you archive a track in Reaper?
Thanks
Thanks
TalismanRich
Well-known member
There's no special need to archive a project. There are no proprietary file formats, except for the small .rpp file which is where all the program setting reside.
Make sure that when you save the project, you put all media files in the project folder, then just zip that folder and stick it away. Except for plug-ins, there's nothing special you need. All the audio files, the .rpp project file and if you use an IR files they should all be in the file folder. If you use an amp sim, or e-drums, then the data will be there, but the actual plug in itself won't be.
I don't even bother zipping the folders. I have a 4tb drive and just copy the folder from my computer to the external drive.
Make sure that when you save the project, you put all media files in the project folder, then just zip that folder and stick it away. Except for plug-ins, there's nothing special you need. All the audio files, the .rpp project file and if you use an IR files they should all be in the file folder. If you use an amp sim, or e-drums, then the data will be there, but the actual plug in itself won't be.
I don't even bother zipping the folders. I have a 4tb drive and just copy the folder from my computer to the external drive.
VomitHatSteve
Hat STYLE. Not contents.
Archiving just means storing the project long-term somewhere, right? So you kind of just make up what's important to you to archive and figure out a process for that.
If I wanted to be exacting in my archiving of a project, I would do the following:
1. Go to File > Clean Current Project Directory... to delete any files that are no longer used
2. Select all tracks that have FX of any sort (including VSTis)
3. Right click one of them > Render/freeze tracks > Render to stereo stem tracks (and mute originals) to ensure that if I lose access to any FX, I don't lose the results I had earlier
4. Tar the whole project file up and move it to a new location
Or you could just to step 4 alone or make up a whole different process
If I wanted to be exacting in my archiving of a project, I would do the following:
1. Go to File > Clean Current Project Directory... to delete any files that are no longer used
2. Select all tracks that have FX of any sort (including VSTis)
3. Right click one of them > Render/freeze tracks > Render to stereo stem tracks (and mute originals) to ensure that if I lose access to any FX, I don't lose the results I had earlier
4. Tar the whole project file up and move it to a new location
Or you could just to step 4 alone or make up a whole different process
brassplyer
Well-known member
Not a project a track. Cakewalk has the option to archive tracks so the system doesn't have to work playing tracks that aren't being used.
ashcat_lt
Well-known member
By default I think simple mute off lines all the plugins on the track. If you also don’t want to see it, hide it from tcp/mcp after muting. If you really want you can render or freeze first, but generally mute just does it.
PorterhouseMusic
Well-known member
Yep - it seems the OP is looking to conserve system resources.
From what I can tell (like ashcat suggests) - muting a track in Reaper takes it offline and is essentially the same or similar function as the "archive" function in Cakewalk.
Good to know!
From what I can tell (like ashcat suggests) - muting a track in Reaper takes it offline and is essentially the same or similar function as the "archive" function in Cakewalk.
Good to know!
TalismanRich
Well-known member
Obviously I didn't understand Cakewalk's use of "archive". It seems a strange term for that function.
Just a confirmation of what Ashcat stated, I loaded a 20 track project, and it was using around 9-10% CPU resources. Muting the tracks dropped the CPU usage to less than 1%. As each track was unmuted, it added a half percent of CPU or so depending on the use of FX on that channel.
Freezing tracks also drops the usage. I took the same project and froze all the tracks, Again, CPU usage was around 1%. FX usage drops to 0 except for the two FX on the master track.
Here's the performance meter readings for the same section before and after freezing.
Just a confirmation of what Ashcat stated, I loaded a 20 track project, and it was using around 9-10% CPU resources. Muting the tracks dropped the CPU usage to less than 1%. As each track was unmuted, it added a half percent of CPU or so depending on the use of FX on that channel.
Freezing tracks also drops the usage. I took the same project and froze all the tracks, Again, CPU usage was around 1%. FX usage drops to 0 except for the two FX on the master track.
Here's the performance meter readings for the same section before and after freezing.
PorterhouseMusic
Well-known member
Interesting! Thanks for doing that and sharing your results.