This issue has come up for me too. I routinely delete several Gigabytes of RPP-BAK files every day. This stuff is controlled via
Project Saving section in
Preferences/Project.
The "Keep multiple versions" checkbox and the "Ever x minutes" parameter are the usual culprits.
But we cannot control the number of backups Reaper should make, so +1 for doing something about massive backup files.
For example,
they're not compressed. Even compression-level 1 ZIP files would crunch this stuff to a fraction, and it's likely not too hard to manage. I set my backup frequency to "Every 3 minutes when stopped". My i7 can probably handle this. *.rpp-bak-zip
The user could set a size limit in megabytes. Reaper could warn the user, taking only backups of the past
d number of days in to account, and offer to
- Clean up x% of the backups in the project files directory no older than y number of days
- Keep x% of the backup files, saved at similar intervalls. 100 backups, x=10%, keep 10 backups between the first save date and time of the current project file and the current save and time.
I'm sure there are lots of other clever strategies.
My sessions are usually 2-3MB to start with. Some end up in the 50 MB range, so files go big fast.
I've gotten used to it, but it is a nuisance that could be handled more effectively.